Guide · Backups
A website, a database and a whole PC disk fail in different ways, so they are not protected in the same way. This guide shows which backup fits which job, where to send the copy, and how to prove it works before you need it.
In this guide: The short answer · A worked scenario · Websites · Databases · Full-disk backups · Where the copy goes · Prove the restore · Questions
Match the backup to what you would have to bring back. For a site, back up its files together with its database on a schedule. For a database instance, back up the instance and keep several runs. For a cloud PC, take a backup of the whole disk and keep snapshots for quick undo. Whatever you protect, send one copy off the machine and restore it once on purpose.
| You need to bring back… | Use | Plan |
|---|---|---|
| A site’s files, or a site and its data together | A scheduled backup job for websites, or websites plus databases | Free and up |
| A MySQL, PostgreSQL or MongoDB instance | A scheduled backup job for databases, with retention | Free and up |
| A virtual machine | A scheduled backup job for VMs | Pro and up |
| An entire cloud PC, system disk included | A full-disk backup of the cloud PC | Business and up |
| The state of a cloud PC a few minutes or hours ago | A snapshot, then roll back | Business and up |
Imagine a small web agency that hosts several client sites and a MySQL instance on its servers, and whose office PCs are network-booted with their system disks on central storage. Three things can go wrong on a normal week:
One backup type does not answer all three. The sections below pair each failure with the workflow that fits.
A website backup job picks a target type (websites, databases, VMs, or websites plus databases), a local save directory, a schedule and a retention count. Choosing websites plus databases keeps a site’s files and its data from the same run, so a restore does not mix Monday’s files with Thursday’s database.
Nodekeeper backs up MySQL, PostgreSQL and MongoDB instances that it manages, with the same schedule, retention and destination options as sites. If a site depends on a database, use the combined websites-plus-databases target so both come from one run.
Replication is a different tool. A database replica keeps a second server ready if the first one fails (Business and up), but a bad query or an accidental delete is copied to the replica as well. A backup is what lets you go back to before the mistake.
Office PCs that boot from the cluster keep their system disk on central storage. That changes what a backup should be: you want the whole disk, not a folder of documents. Nodekeeper supports full-disk backup and recovery of a cloud PC: the unit you protect is the whole system disk, not a folder of documents. It is part of Business.
Snapshots and backups answer different questions:
Website and database jobs write to a local directory first. After a successful run the job can upload to a remote, with each run in its own folder.
Fastest to restore from, but on the same machine. Treat it as the first copy, not the only one.
Object storage you own, added as a remote in the panel. This is the usual off-machine copy.
rclone supports many providers. Treat one as supported only after you have run a test restore from it.
A rule that works for most teams: one copy on the machine for fast restores, one in a bucket you own for when the machine is gone.
A green “completed” on a job means files were written. It does not mean they are the right files. Before you trust a schedule:
Every run is recorded with its result in the operation log, which gives you a history to check against when something looks wrong.
Yes. Scheduled website and database backups, local and remote destinations, retention and restore are part of every plan, Free included. VM backups start with Pro, and full-disk backups of cloud PCs with Business.
Yes. Replicas and erasure coding protect against a failed disk or host. Deleted or corrupted data is replicated too, which is what a backup is for.
Enough to reach back past the time it takes you to notice a problem. A site that is edited daily and checked weekly needs more than three runs. Size it from the space each run uses.
Permissions are granted by user group, so you decide who may create jobs and who may restore. Members work only in their own file area.
Backup jobs, destinations and restore are in the same panel as your sites and databases, so you do not need a separate tool for each.
Related: backup documentation · full-disk backup and recovery for office PCs · distributed storage management · web hosting
Manage websites, office PCs and servers from one panel on your own hardware.