Is dumping database backups to file shares normal, or is there a better way?

November 17, 2026 4 answers
Asked by _m83+claspmarble.7

Our database servers dump backups to mapped file shares. It works across PostgreSQL, SQL Server, and MySQL, but there are a lot of service accounts and mappings to maintain.

Is this a common setup? What would make it more robust without necessarily buying an expensive backup product?

Answers

Ruz

Database dumps to a share are a reasonable approach, but the share is only one part of the backup system. You still need retention, monitoring, enough storage, and regular test restores. The scripts may be free, but maintaining them and paying for storage isn't.

You might simplify the mappings with a shared destination and permissions that restrict each service account to its own backups. Keep a separate off-site copy too, preferably one that the database servers cannot modify or delete.

Reply to this answer
_p49!zunvexa.6

Start with the recovery target for each database. A nightly dump means you could lose up to a day's changes. If that isn't acceptable, look at database-native backups plus transaction log or binlog backups for point-in-time recovery.

For PostgreSQL, pgBackRest is one option. SQL Server has native backup and log backup features, and MySQL or MariaDB setups can use appropriate backup tools alongside binary logs. The details differ, so check that the backup and log chain actually supports the restore window you need. Budget space for the logs as well as the full backups.

Tivmexa.3r:

Test a restore to a specific time, not just a restore of the latest full backup. That checks whether the necessary logs are available and usable.

Reply to this answer
_x38!brasspocket.6

A commercial backup application can centralize scheduling, retention, monitoring, and restores across multiple databases. Some also support local, off-site, and immutable copies. Check the actual database and version support before buying, because capabilities vary between products and agents.

Also, don't assume a whole-VM snapshot is automatically a usable database backup. Check how the product handles application consistency and whether it can restore the database and logs at the level you need.

Reply to this answer
Tervilo-3m

Don't forget the application around the database. If its files or state live on another server, restoring only the database to an earlier point may leave them out of sync. Include those dependencies in the recovery plan and test the application after a restore.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions