Backup and Recovery

A VPS gives you full control of a server, and with it full responsibility for the data on it. A disk mistake, a bad update, ransomware or a deleted database can undo months of work in seconds. This guide explains how to plan backups for a Domain India VPS, which tools to use, how to restore, and how to test that your backups really work.

1. Who backs up what

On shared hosting, the weekly JetBackup 5 backups are described in backup and restore with JetBackup. This page is about a VPS, where you have root access and decide what to back up.

Even where a provider-side copy exists, treat it as a last resort, not your plan. It may be days old, it may not include the moment you need, and restoring it rolls back the whole server.

2. Backup types and the 3-2-1 rule

Modern tools such as restic and BorgBackup use deduplication: each run stores only new data, yet every backup can be restored as if it were full. That gives you the space savings of incrementals without their complexity.

Follow the 3-2-1 rule: three copies of your data, on two kinds of storage, with one copy off-site. For a VPS that means the live data, a backup on separate storage, and a copy with a different provider or on your own computer. Keep at least one copy that the server itself can't delete, so ransomware on the VPS can't wipe your backups too.

3. What to back up on a VPS

• Databases. Never copy live MySQL or PostgreSQL data files; take a consistent dump.
• Website and application files, for example /var/www or your app folder.
• Configuration: /etc (web server, PHP, firewall, cron), SSL certificates and your own scripts.
• User data: uploads, mail stores, anything your app writes.
• A package list, so you can rebuild: dpkg --get-selections on Debian or Ubuntu, rpm -qa on AlmaLinux or Rocky Linux.

Database dumps:

# MySQL or MariaDB: consistent dump of InnoDB tables without locking the site
mysqldump --single-transaction --routines --triggers --all-databases | gzip > /backup/db-$(date +%F).sql.gz

# PostgreSQL
sudo -u postgres pg_dumpall | gzip > /backup/pg-$(date +%F).sql.gz

Store database credentials in ~/.my.cnf with permissions 600 rather than on the command line.

4. Automate off-server backups

A backup on the same disk as the data doesn't protect you from losing the server. Send it somewhere else with one of these well-maintained tools:

A minimal restic setup:

export RESTIC_REPOSITORY="s3:https://s3.example-provider.com/my-vps-backups"
export RESTIC_PASSWORD_FILE=/root/.restic-pass     # keep a copy of this password somewhere safe
restic init                                          # once
restic backup /etc /var/www /backup                  # each run
restic forget --keep-daily 7 --keep-weekly 4 --keep-monthly 6 --prune

Put the dump and the backup commands in one script and run it from cron at a quiet hour:

30 2 * * * /usr/local/bin/vps-backup.sh >> /var/log/vps-backup.log 2>&1

For step-by-step versions, see automated backups with cron and rclone and VPS backups to Amazon S3.

5. Restoring

If the VPS itself is broken, you can order a fresh VPS, restore onto it, and switch DNS once it works. That route also works as a disaster-recovery test.

6. Snapshots on a Domain India VPS

The Domain India client area has no controls for VPS snapshots, reinstalls or restores; support handles them. Before a risky change, such as an OS upgrade, ask support what your plan includes and whether a snapshot can be taken. If you need a snapshot restored, open a ticket with the VPS's IP address and the date you want to go back to.

A snapshot restore rolls the whole disk back: everything written after the snapshot is lost, including orders, emails and uploads. Take a fresh database dump and file copy before you ask for one, so you can bring back recent data afterwards.

7. Plan for disaster and test it

• Write down the rebuild steps: OS, packages, config, where the backups are, and the order to restore them.
• Decide what loss you can accept. If losing a day of orders is too much, back up the database more often than daily.
• Test a full restore onto a spare VPS or a local virtual machine a few times a year. A backup you have never restored is a hope, not a backup.
• Monitor the job. Check the log, or have the script send you a message when it fails.

8. Where Domain India fits

A Domain India VPS gives you root access to run any of the tools above. If you'd rather not manage server backups yourself, our cPanel and DirectAdmin shared hosting includes weekly JetBackup 5 backups you can restore or download from the panel.

Prices on the cards are live Domain India list prices and exclude 18% GST.

Frequently asked questions

Ready to protect your server? Set up automated off-server backups, compare VPS plans, or open a support ticket to ask what your VPS plan includes.