Backup Practices » History » Version 5
  Anchi Cheng, 08/19/2010 04:43 PM 
  
| 1 | 1 | Amber Herold | h1. Backup Practices  | 
|---|---|---|---|
| 2 | |||
| 3 | |||
| 4 | |||
| 5 | h2. Ideal setup:  | 
||
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | |||
| 10 | h2. Regular computer backup  | 
||
| 11 | |||
| 12 | |||
| 13 | |||
| 14 | To protect your program installation.  | 
||
| 15 | |||
| 16 | |||
| 17 | |||
| 18 | |||
| 19 | |||
| 20 | h2. Full backup of the databases every night  | 
||
| 21 | |||
| 22 | |||
| 23 | |||
| 24 | 4 | Anchi Cheng | The database are the metadata generated by Leginon and Project management system, leginondb and projectdb, respectively in the installation  | 
| 25 | 1 | Amber Herold | example.  | 
| 26 | |||
| 27 | |||
| 28 | |||
| 29 | |||
| 30 | |||
| 31 | h2. Full/Incremental/differential backup of the images  | 
||
| 32 | |||
| 33 | |||
| 34 | |||
| 35 | The image files located in [your storage disk] should be backup in full at least once  | 
||
| 36 | a month, and nightly in differential or incremental mode.  | 
||
| 37 | |||
| 38 | |||
| 39 | |||
| 40 | |||
| 41 | |||
| 42 | |||
| 43 | |||
| 44 | 5 | Anchi Cheng | h1. Current NRAMM setup:  | 
| 45 | 1 | Amber Herold | |
| 46 | |||
| 47 | |||
| 48 | Because our tape backup system is not on-site and the data have to transfer over slow  | 
||
| 49 | network to perform the task, we have not been able to backup in the ideal setting. Here is  | 
||
| 50 | what we currently do:  | 
||
| 51 | |||
| 52 | |||
| 53 | |||
| 54 | h2. Regular computer backup  | 
||
| 55 | |||
| 56 | |||
| 57 | |||
| 58 | TSRI Research Computing provides regular back up service that does full backup of the  | 
||
| 59 | computers every four weeks and incremental backup every night. The full backup expires in  | 
||
| 60 | 4 months and the incremental backup one month. We do this for the computers running  | 
||
| 61 | Leginon main program, the database server, as well as the web server.  | 
||
| 62 | |||
| 63 | |||
| 64 | |||
| 65 | |||
| 66 | |||
| 67 | h2. Regular backup & tar of the databases every night  | 
||
| 68 | |||
| 69 | |||
| 70 | |||
| 71 | On top of the TSRI backup, we also tar the database everynight and store it on the  | 
||
| 72 | institutional tape library.  | 
||
| 73 | |||
| 74 | |||
| 75 | |||
| 76 | |||
| 77 | |||
| 78 | h2. rsync to a tape library of the image storage disk  | 
||
| 79 | |||
| 80 | |||
| 81 | |||
| 82 | As our image storage disks total 15T byte, we currently use rsync function to update a  | 
||
| 83 | copy on our institutional tape library. It creates new files, updates old files, but does  | 
||
| 84 | not remove old files on the tape if it is removed on the storage disk. We do not think  | 
||
| 85 | this is the best solution since it is not possible to retrieve old files that have been  | 
||
| 86 | modified on a later time.  | 
||
| 87 | 2 | Amber Herold | |
| 88 | |||
| 89 | ______  | 
||
| 90 | |||
| 91 | [[Next Steps|< Next Steps]]  | 
||
| 92 | 3 | Amber Herold | |
| 93 | |||
| 94 | |||
| 95 | ______  |