Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Backups

Database backup strategy: how to protect changing data

Published August 2026 · 9 min read

Databases are often the fastest-changing and hardest-to-recreate part of an application. Protecting them well requires more than copying database files while the service is running; the backup method should produce a known recoverable state and match how much data loss the business can accept.

Choose logical or physical methods for the workload

Logical dumps can be portable and easy to inspect, while physical or snapshot-based methods can be faster for large datasets when performed correctly. The engine, dataset size, recovery objective, and available tooling determine the right combination.

Protect consistency during backup

Transactions can change related tables while a backup runs. Use database-supported backup tools, coordinated snapshots, replication, or another engine-appropriate method so the recovered data represents a consistent point in time.

Increase frequency for high-value changing data

A daily database backup may imply losing nearly a day of orders or user activity. More frequent dumps, logs, replication-based recovery, or point-in-time mechanisms can reduce the recovery-point gap when the workload justifies the complexity.

Restore and query the result

Periodically create a test database from backup, run integrity checks, verify representative records, and make the application connect to the recovered copy. The test should prove the backup is usable, not merely that a file exists.

Next step

A database backup strategy should address consistency, recovery points, transaction volume, dumps vs physical copies, encryption, off-site storage, retention, and restore verification.

Plan database backup storage

Keep reading

Related guides.

Backup capacity planning: estimate storage from change rate and retention

Model source size, daily change, compression, deduplication, retention and growth so backup storage is sized from the workload instead of one full-copy estimate.

Read the guide

Backup encryption basics: protect copies at rest and in transit

Choose where backup data is encrypted, how keys are stored and recovered, and how restore operators gain access without putting the only key beside the backup.

Read the guide

Backup recovery drills: prove the restore process before an outage

Run isolated recovery tests, measure restore time, verify application state and record missing dependencies so the backup plan is based on tested recovery.

Read the guide

More backups guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move