Snapshots & Backups: Saving Your Infrastructure
Save now. Restore later. Sleep well.
Save now. Restore later. Sleep well.
A snapshot captures the entire state of a server at one moment. Make changes to the server below, then take a snapshot. Break something, then restore. Your server is back to the saved state.
The industry standard for data safety. Three copies, two storage types, one off-site. Click each layer to see why it matters.
Without backups, any of these scenarios means permanent data loss.
SSDs and hard drives fail. A server's disk can die without warning. RAID mirrors data across multiple disks, but if both fail, data is gone without off-server backups.
"rm -rf /" deletes everything. A bad database migration drops tables. An accidental config change takes the site down. The most common cause of data loss is people, not hardware.
Ransomware encrypts all your files and demands payment. If your backups are on the same server, they get encrypted too. Off-site backups are the only defense.
A deploy introduces a bug that corrupts the database. You notice three days later. Without point-in-time backups, you cannot roll back to before the corruption.
GitLab accidentally deleted their production database in 2017. They had 5 backup systems in place. Four of them had silently failed. The one that worked was an accidental snapshot taken 6 hours earlier. They lost 6 hours of data but survived. They now test their backups daily.
You've learned why backups matter, how snapshots capture a point in time, and why the 3-2-1 rule keeps data safe. Every professional system has a backup strategy. Now yours will too.
A snapshot captures everything on a server at one moment: files, databases, config. Like a save point in a game. Restore it and you are exactly where you were.
Hardware fails. Software has bugs. Humans make mistakes. Backups are the safety net. Without them, a single mistake can destroy months of work permanently.
Keep 3 copies of data, on 2 different types of storage, with 1 copy off-site. This protects against hardware failure, corruption, AND physical disasters like fire.
A backup you have never restored is a backup you cannot trust. Regularly test restoring from backups. Many companies have discovered their backups were broken only when they needed them.
Put your new knowledge into practice!