Solution for this

[venkata harish]

[Dirk Ronsmans]

@venkata harish ,

Most likely the automatic backup scheduler was enabled at upgrade or installation.

https://confluence.atlassian.com/adminjiraserver/configuring-automatic-database-backups-938847675.html

I'd suggest to turn that off anyway and actually take a VM snapshot and manage your databases propperly. If you were to rely on thos xml backups and the VM corrupts anyway you'll lose all those "backups"

To fix it for now (but not permanently) i'd suggest looking at @David Freitez 's answer. 

Moving the files will fix the health check but honestly if you have a proper backup solution it's not much to worry about except your disk getting full.

[David Freitez]

Hi @venkata harish ,

According to the explanation on on the KB: Health Check: Local backup security
(https://confluence.atlassian.com/jirakb/health-check-local-backup-security-1346245564.html), it is a security hazzard to have an unencrypted backup. 

This health check looks for backups in the application storage and warns you if any backup files are found there. Storing backups in the application's local/shared filesystem is a security risk that may expose sensitive data to attackers.

...

Storing unencrypted backups that contain sensitive information on the application file system is a security risk. When an attacker gains access to the file system, this sensitive data becomes exposed. Furthermore, attackers can compromise the application and then encrypt or remove the backups, preventing administrators from being able to restore the application's data and settings.

It also states: To immediately fix this warning, move all existing backup files to a dedicated secure storage location

I recommend you to check the KB so you can understand what the check was created for and the options you have available to do with the backups.

If my comment answers your question, kindly consider to mark as the answer.

Regards,
David