How do I back up an unmanaged VPS?

On an unmanaged KVM VPS, backups are your responsibility. Take a snapshot in the VPS panel before big changes, consider the backup add-on, and run your own nightly backup of files and databases to storage off the server.

An unmanaged VPS is yours to run, and that includes backups. Our Service Level Agreement is plain about it: unless backups are part of the package, they are not guaranteed, and you should always keep an independent copy outside the hosting environment.

1. Snapshots before every big change

Every KVM plan includes snapshots in the VPS panel. Take one before an upgrade, an OS reinstall or a risky configuration change, and roll back if it goes wrong. Treat a snapshot as an undo button, not as your only copy: it lives on the same platform as your server.

2. The backup add-on

Backups are an add-on you can choose when you order a KVM VPS. If you did not add one, ask us on WhatsApp whether it can be added to your server now and what it costs.

3. Your own copy, off the server

1. Decide what matters. Usually your databases, your application files (for example /var/www or /home) and your configuration in /etc. The operating system itself can be reinstalled.
2. Dump the databases. Copying a running database's files can give you a broken backup, so use the database's own tool: for example mysqldump --all-databases --single-transaction > /root/backup/db.sql for MySQL or MariaDB, or sudo -u postgres pg_dumpall > /root/backup/db.sql for PostgreSQL.
3. Bundle the files. For example tar -czf /root/backup/files-$(date +%F).tar.gz /etc /var/www.
4. Send the copy somewhere else. Copy it to another server, for example with rsync -az /root/backup/ user@backup-server:/backups/, or use a tool that encrypts and only sends what changed: restic can write to S3-compatible storage such as Tremhost S3 storage, and BorgBackup works over SSH to another server.
5. Automate it. Put the commands in a script and run it nightly with cron: run crontab -e and add a line such as 30 2 * * * /root/backup.sh. Have the script delete local copies older than a week, for example with find /root/backup -mtime +7 -delete, so the disk does not fill up.
6. Test a restore. Every few months, restore a backup to a spare VPS or a test database. You only know a backup works once you have restored from it.

Tip: Push backups to another server or to S3 storage rather than downloading them to the office. It saves mobile data, and a ZESA power cut will not stop the copy halfway.

Would you rather not manage backups yourself?

A managed cPanel VPS (from $80 a month) includes daily backups, kept for 7 days, run by our technicians. See Managed or unmanaged VPS: which do I need?

Is a snapshot enough before I reinstall the OS?

Take one, but copy your data off the server as well. A reinstall wipes the disk.

Still stuck? Open a support ticket or message us on WhatsApp.

Updated 6 November 2026. Something here out of date? Tell us.