Is your feature request related to a problem? Please describe

There are several scenarios where database corruption can occur.
This may happen if someone does something unsupported (put db on cifs/nfs)

Can also happen in scenarios outside of this unsupported scenario (e.g. unanticipated power loss, hardware issues, etc)

Today portainer can keep running just fine even if the on-disk database is corrupted.

This means portainer can run for weeks or months with corrupted database and because backup is a copy of the on-disk database all the backups can be corrupted without this being obvious.

Describe the solution you'd like

Change backup from a file copy process to a process that backs up (exports?) the tables to a new fresh and VALIDATED GOOD database file.

Describe alternatives you've considered

Doing manual script to stop portainer, backup the file, start portainer, then validate the file with bbolt / bolt db command like tools.

Additional context

I had this issue, this is not theoretical, the file was not on cifs/smb/nfs (i was using virtiofs to surface the bind mounts from a host into a swarm VM). I had no working backup file due to only keeping a few (bonus ask, let me do automate backup to Azure or SMB too)