A database backup is the most important copy you can keep. Your files hold the design, but the database holds orders, users, posts and settings. Losing it means losing your business history. Fortunately, backing it up is easy once you have a routine.
Why databases need special care
Databases change every minute on an active site. A copy from last week may miss hundreds of orders. Copying the raw files while the server runs can also create a broken copy. That is why you should use proper export tools.
Ways to make a database backup
- Use the backup tool in your control panel.
- Export with phpMyAdmin for small databases.
- Run mysqldump from the command line on a VPS.
- Schedule automatic dumps with a cron job.
Follow the 3-2-1 rule
Keep three copies of your data. Store them on two different types of storage. Keep one copy in another location, away from your server. If the server fails or is hacked, the off-site copy saves you.
How often?
Match the schedule to how often your data changes. A blog may need a daily copy. A busy store may need one every hour. Keep several older copies too, because problems are sometimes found days later.
Test your restores
A backup you cannot restore is useless. Once a month, restore a copy on a test database. Check that tables and recent records are there. Write down the steps, so anyone on your team can do it under pressure.
Protect your copies
Backups contain personal data, so treat them carefully. Encrypt files stored outside your server. Limit who can download them. Delete very old copies you no longer need.
On our plans, daily backups are included, and you can download a copy at any time. Read our backup and restore policy for details. For full control, a VPS lets you run your own schedule.
