Backup and storage server setup
A backup stored on the same server as your websites isn’t a backup: a disk failure, a hack or a mistake takes both at once. Backups need to live somewhere else, and to be tested.
The short answer
We set up backup and storage servers: a dedicated backup server, a storage server at another provider, or S3-compatible object storage, receiving automatic backups from your web and mail servers. For WHM/cPanel we configure the built-in backup system with an offsite destination, retention and encryption, then test a full restore so you know it works.
What’s included
- A backup destination away from your main server: a backup server, a storage server, or S3-compatible storage.
- WHM/cPanel backups configured: accounts, databases, email and server settings, sent offsite automatically.
- Schedules and retention: daily, weekly and monthly copies, kept as long as you need.
- Encryption and access control for the backups themselves.
- Monitoring: an alert if a backup fails or stops.
- A test restore, and plain instructions for restoring a site, a mailbox or the whole server.
How we do it
- Review what needs backing up and how fast you’d need it back.
- Set up the backup server or storage.
- Configure backups, retention and encryption.
- Test a restore.
- Monitor and document.
Backups that nobody tested
The most common backup problem we find isn’t a missing backup, it’s a backup that doesn’t restore: incomplete databases, a destination that filled up months ago, or credentials that expired. That’s why a test restore is part of every setup.
Common questions
Should backups go to a server or to S3?
Both work. Object storage is simple and durable; a backup server gives faster full restores and more control. Many businesses use one of each.
How much storage do we need?
Roughly your data size times the number of copies kept, reduced by compression. We estimate it during the free check.
Can you back up servers that don’t use cPanel?
Yes, with other backup tools suited to the server.