Data backup means keeping a copy of files, databases and systems separate from the original so you can restore them after deletion, corruption or an attack. A backup is only as good as its restore: if you have never restored it, you cannot be sure it works.
Why Back Up?
- Hardware failure: broken disks or servers.
- Human error: deleted files, bad updates.
- Ransomware and attacks: encrypted or wiped data.
- Software bugs: corrupted databases, failed plugin or system updates.
- Disasters: fire, flood, theft; a backup in the same building can be lost too.
Backup Types: Full, Incremental and Differential
| Type | What is copied | Pro | Con |
|---|---|---|---|
| Full | Everything, every time | Simplest, fastest restore | Most space and time |
| Incremental | Changes since the last backup of any type | Small and fast | Restore needs the last full plus every incremental since |
| Differential | All changes since the last full backup | Restore needs only the last full and last differential | Grows until the next full |
| Snapshot | State of a disk or VM at a point in time | Taken in seconds, quick rollback | Usually on the same storage; not a backup on its own |
A common schedule is a weekly full backup with incremental or differential backups on other days.
The 3-2-1 Backup Rule
- Keep 3 copies of your data (the original plus 2 backups),
- on 2 different types of storage,
- with at least 1 copy offsite.
Against ransomware, keep one copy offline or immutable; a backup that is always connected and writable can be encrypted along with the original.
Where to Store Backups
| Location | Good for | Watch out |
|---|---|---|
| External disk / NAS | Office and personal data, fast restores | Same building; add an offsite copy |
| Separate backup server | Websites and servers | Prefer a different data centre |
| Cloud / object storage | Offsite copies, growing data | Restore speed depends on bandwidth; protect access keys |
| Hosting panel backups | Quick rollback in cPanel or Plesk | Also download your own copy |
RPO and RTO: How Often to Back Up
- RPO (Recovery Point Objective): how much data loss you can accept. Daily backups mean you may lose up to a day; an online store’s database needs hours or minutes.
- RTO (Recovery Time Objective): how fast the system must be back. Downloading a large backup over a slow link can take hours; critical systems need a local copy or a standby server.
Restoring and Testing Backups
- Monitor backup jobs and get alerts on failure.
- Periodically restore a backup to a test environment and check files and databases open.
- Document the restore steps and who does what.
- Rotate old backups but keep at least one older version: unnoticed corruption may already be in recent backups.
- Encrypt backups and restrict access; they are as sensitive as the original data.
Platform Guides
- WordPress database backup and recovery
- Backup and restore with CyberPanel
- Backing up VMware virtual machines
- Server backup and restore
For resilient infrastructure, see our hosting and VDS server plans.
Frequently Asked Questions
Is RAID a backup?
No. RAID keeps a system running when a disk fails, but a deleted or encrypted file is deleted or encrypted on every disk at once.
Is file sync (Drive, Dropbox) a backup?
Not on its own: sync also spreads deletions and corruption. Version history helps, but a separate backup is still recommended.
Categories
-
CentOS 7 guides
-
cPanel 20 guides
-
CyberPanel 18 guides
-
Operating Systems 81 guides
-
Juniper Networks 18 guides
-
Control Panels 50 guides
-
Linux 17 guides
-
MySQL 29 guides
-
Network 95 guides
-
Plesk Panel 12 guides
-
Virtual Servers 273 guides
-
SEO 3 guides
-
Cyber Security 8 guides
-
Technology 162 guides
-
VMware 36 guides
-
WordPress 20 guides
-
Artificial Intelligence 22 guides