Backup your sh$t
Everyone Needs Backups
I have no backups.
Most people do not have any form of backup for their data. Many people do not see this as a necessity. This book covers:
- Understanding the importance of backups
- Knowing what you should (and should not) backup
- Making a backup plan
- Using the tools to execute that plan
Why do I need backups?
Every disk, every phone, every flash drive dies, and odds are they will die with unique data on them that you will suddenly miss very much. Recovery is a time consuming and often expensive process.
Drives do not broadcast imminent death. Assume they will just die. Every time.
Think of where the following exist:
- Your first child's baby pictures
- Your Wedding photos
- Your Resume
- Your tax documents
- Your thesis
- All of that school work due at the end of the week
- Your Minecraft world that you have been working on for 6 months
- The assignments your students turned in this afternoon
We have seen all of these, and many more, come through the subreddit or our live chats. Often times the users are completely out of luck when it comes to recovering these lost memories or incredibly important documents.
Some are lucky enough to be able to recover themselves, others have to spend hundreds or thousands of dollars for a professional to handle it.
How do I get started with backups?
Hopefully, you are interested in creating a backup plan now. If so keep reading as backups are not simply drag-dropping your files once and forgetting about them. It is an ongoing process that requires at least a little bit of planning.
Creating a Backup Process
The 3-2-1 Rule
The basis of all backup plans revolves around the 3-2-1 rule.
- 3 copies of your data
- 2 of the copies are on different devices on-site
- 1 copy is 'off-site'
In a perfect world this would mean that your
Thesis.docx exists on your computer, on your external backup drive, and on a cloud drive (gdrive, onedrive etc). How far you want to go with this rule is part of your planning.
Create a plan
What needs to be backed up?
Go back to the previous page to see the scary list of things that people have lost over the years, and think about what you have that you care about.
Generally bulky things like games and the OS itself do not need to be backed up, redownload/reinstall these things after recovering your environment.
For this reason we discourage the use of image based backups when an image is not explicity needed. By minimizing the size of your backups you can complete your backup/restore process quicker and for cheaper.
How often does your data change?
Determine how often your data is going to change. Your wedding photos will never change, but the thesis you are working on will change quite often.
When things change more often you need to decide how much time/work you can lose in a disaster. If you cannot afford to lose more than a few hours you need to run your backups much more often than if losing a full day was OK.
With all backups you need to also decide if you need version history. This is how many copies of backups you keep, like a timeline. If you overwrite your old backup every time you make a new one then you will be in big trouble if there is an error in your only backup.
Where will the data be backed up to?
Critical data should fully follow the 3-2-1 rule while less critical can be more lax.
The simplest method most users start with is backing up to a local external hard drive. Replacing data infrequently. This is fine for unchanging data or less critical data.
More comprehensive backup procedures should be auotmatic. These can use network attached storage (NAS) solutions, scripts or applications to manage the backup creation, frequency, and version control. "Personal Cloud" based solutions such as Nextcloud can check most of these boxes.
To gain a full 3-2-1 scope you can push backups of your NAS to an offsite solution such as AWS S3 or Backblaze.