https://devsummit.aspirationtech.org/index.php?title=Backup_Strategies_and_Best_Practices&feed=atom&action=historyBackup Strategies and Best Practices - Revision history2024-03-28T16:45:03ZRevision history for this page on the wikiMediaWiki 1.35.1https://devsummit.aspirationtech.org/index.php?title=Backup_Strategies_and_Best_Practices&diff=209&oldid=prevVivian: 1 revision imported2015-05-05T17:21:40Z<p>1 revision imported</p>
<p><b>New page</b></p><div>'''Back up Strategies & Best Practices'''<br />
<br />
Identifying a reason why you or your organization wants to backup and also make sure you're not giving away your data is important – a lot of security motivation in NSA news recently<br />
* many groups are not motivated to think about back-ups or security in general<br />
* would rather have someone do it for them<br />
* often motivated by a known threat<br />
<br />
First step is to figure out What Data you have & where it lives<br />
* create an inventory of where you have data and where it is stored<br />
* something like an Online Accounts Inventory<br />
<br />
For Data that you want to keep – what options seem reasonable?<br />
<br />
What are safe strategies – different kinds of data have different characteristics<br />
<br />
'''different characteristics of the data means that you may think about how it is backed up in different ways'''<br />
<br />
* if data set only grows<br />
** raw video archive<br />
<br />
* if data set changes<br />
** a database of contacts<br />
** snapshots of the changes<br />
<br />
<br />
* '''video'''<br />
** multiple pieces of physical media<br />
** different physical locations<br />
** hard drives (cheap drives)<br />
** Rsync – command line tool to backup changes <br />
<br />
* need to establish process around consistently backing-up<br />
* make it easy for the people to back-up, like a button<br />
<br />
* '''online database'''<br />
<br />
Questions to ask:<br />
<br />
* Is the data that you want to back up all in 1 places?<br />
* How does the backup work?<br />
<br />
Complete the Back-up Process<br />
- can you restore from the back up<br />
- can you test that the back-up in functional<br />
- if you use external hard drives, how to<br />
<br />
S.M.A.R.T. Mon (monitor) Tools - smartmontools<br />
- can ask the hard drive to tell you things like temperature, when the last read error was, let me know when the disk is going to fail<br />
<br />
* git (revision control)<br />
<br />
'''Databases'''<br />
* 2 common ones<br />
** mySQL<br />
** PostGres – postgresql.org<br />
<br />
Incremental Backups<br />
*Rdiff<br />
*Differential<br />
<br />
* it is really important that you understand how the backup that you are running is working, is it sync, mirrored, iterative, just tracking changes... etc<br />
<br />
Restoring<br />
<br />
* database backups<br />
** have a machine not on internet<br />
** recreate database & then push the backup to it and see if it works<br />
**you could also run tests to see if it works<br />
<br />
Tools that do autobackup testing - <br />
* test your restores<br />
* you tell them the kind of thing that you think you are backing up<br />
<br />
Everything time you bring in someone new, make sure they can restore from a back – test that someone could do it (tests if it is possible & likely)<br />
<br />
For developers – understanding the functional dependencies that the code relys on<br />
<br />
Backing up Social Media – what is necessary to backup?</div>Vivian