Backup Practices » History » Revision 4
Revision 3 (Amber Herold, 04/23/2010 01:26 PM) → Revision 4/5 (Anchi Cheng, 08/19/2010 04:43 PM)
h1. Backup Practices h2. Ideal setup: h2. Regular computer backup To protect your program installation. h2. Full backup of the databases every night The database are is the metadata generated by Leginon and Project management system, leginondb and projectdb, respectively named "dbemdata" in the installation example. h2. Full/Incremental/differential backup of the images The image files located in [your storage disk] should be backup in full at least once a month, and nightly in differential or incremental mode. h2. Current NRAMM setup: Because our tape backup system is not on-site and the data have to transfer over slow network to perform the task, we have not been able to backup in the ideal setting. Here is what we currently do: h2. Regular computer backup TSRI Research Computing provides regular back up service that does full backup of the computers every four weeks and incremental backup every night. The full backup expires in 4 months and the incremental backup one month. We do this for the computers running Leginon main program, the database server, as well as the web server. h2. Regular backup & tar of the databases every night On top of the TSRI backup, we also tar the database everynight and store it on the institutional tape library. h2. rsync to a tape library of the image storage disk As our image storage disks total 15T byte, we currently use rsync function to update a copy on our institutional tape library. It creates new files, updates old files, but does not remove old files on the tape if it is removed on the storage disk. We do not think this is the best solution since it is not possible to retrieve old files that have been modified on a later time. ______ [[Next Steps|< Next Steps]] ______