4 ms·
The Holy Trinity of Making Backups: 1) If it's not automated, it's not a real backup. 2) If it's not redundant, it's not a real backup. 3) If it's not regula
by Samuel_Michon 15y ago
The Holy Trinity of Making Backups:
1) If it's not automated, it's not a real backup.
2) If it's not redundant, it's not a real backup.
3) If it's not regularly rotated off-site, it's not a real backup.
Doing any one of these things by itself or in tandem produces "a copy." A copy is handy, and it may really save you, even a majority of the time. But, making casual copies is optimistic at best. Someday, you will need the benefits of all three layers.
http://www.43folders.com/2010/03/15/yes-another-backup-lecture http://www.43folders.com/2010/03/15/yes-another-backup-lectu...
- patio11 15y agoYou also probably want backups to be tested. Many people, myself included, have been bitten by "I did not quite have what I needed to bring the production environment up again." With regards to coders specifically: git and similar DVCSes is a lifesaver. If you have a sensible push workflow, loss of a laptop only costs you the laptop, the time it takes you to get a new machine to the state where you are productive (+), and whatever your average not-pushed-to-somewhere batch size is. + Having recent experience with this, Ninite + Dropbox + a monthly backup of my Ubuntu VM (where dev happens) in Dropbox = total recovery time was about three hours.
- kabdib 15y agoThese days I freeze development environments by - checking in the tools, as well as the sources - running them in a VM, and backing /that/ up - ensuring that none of the tools, certificates, etc. will expire Gigabytes are cheap.