| 5 | | '''Updated 2011-03-09''' |
| 6 | | * nebulous on ippdb00 is replicated on ippdb02. It is backed up twice a day from replicate at 0:30 and 12:30. Dumps can be found in /export/ipp001.0/ipp/mysql-dumps. Command for backup is started from ipp@ipp001 crontab. |
| 7 | | * Command for backing up gpc1, ippRequestServer, isp, ippadmin is /home/panstarrs/ipp/mysql-dump/ops_dump.csh (Manoa cluster). |
| | 4 | (Last update: 2011-04-06) |
| | 5 | * Backup scripts can be found here: https://svn.pan-starrs.ifa.hawaii.edu/repo/ipp/trunk/tools/mysql-dump. They are installed in ~ipp/mysql-dump. |
| | 6 | * nebulous on ippdb00 is replicated on ippdb02. |
| | 7 | The database on the replication slave database is backed up twice a day at 0:30 and 12:30 (see the local crontab). Dumping the complete database takes about 3 hours. |
| | 8 | Every day at 3:05 and 15:05 the last nebulous dump is copied on ipp001 by the neb_copy.sh script running on ipp001 (documentation is in the script). neb_copy.sh verifies that the copy is fine otherwise sends an e-mail (while in dev mode, only to me, i.e. serge). |
| | 9 | * gpc1 on ippdb01 is replicated on ippc02. |
| | 10 | The database on the replication slave database is backed up every 4 hours (at 0:05, 4:05, 8:05, 12:05, 16:05, and 20:05). Dumping the database takes about one hour (TODO: maybe shorter. When I looked at that ippc02 was doing another backup that I didn't want to stop). The script responsible for the dump (gpc1_dump) is also responsible for the copy onto ipp001 (it is then different from the previous one). |
| | 11 | Every 4 hours (at 1:30, 5:30, 9:30, 13:30, 17:30, and 21:30), gpc1 is verified, alternatively "installed" on gpc1_0 or gpc1_1, and distributed with its md5 checksum on the rsync server. |
| | 12 | * Backups of ippRequestServer, isp, ippadmin is /home/panstarrs/ipp/mysql-dump/ops_dump.csh (Manoa cluster). |
| 12 | | '''Updated (2009.10.14): The rsync server for the database dumps has changed from ipp0002 to ipp0012. The text below reflects this change.''' |
| 13 | | |
| 14 | | '''Updated: We have recently (2009.09.16) changed the dump scheme to only dump the specific databases of interest. The text below reflects this change.''' |
| 15 | | |
| 16 | | Thanks to efforts by Cindy & Gavin, regular dumps of the mysql databases being used by the processing system on Maui are now being made available via the rsync server on ipp0012.ifa.hawaii.edu. The three databases distributed are the gpc1 processing database, the isp processing database, and the ippadmin database describing the database schema. These are dumped every 4 hours, and are available from the rsync location: |
| 17 | | |
| 18 | | rsync://ipp0012.ifa.hawaii.edu/ippdb |
| 19 | | |
| 20 | | if you want all three, give a command like: |
| 21 | | |
| | 18 | if you want all three, give a command like: |
| 24 | | The databases have names of the form ippdb01-DBNAME.dump.gz, eg, the GPC1 processing information is in the file called ippdb01-gpc1.dump.gz. The GPC1 gzip file is currently 0.8GB, so be careful. They are also dumped every 4 hours, and the new one replaces the old name. If people are unable to retrieve these in less than the 4 hour period (~0.4 Mbit/sec), then we can adjust the naming to keep more than one old version around. |
| | 21 | The databases have names of the form ippdb01-DBNAME.dump.gz, eg, the GPC1 processing information is in the file called ippdb01-gpc1.dump.gz. The GPC1 gzip file is currently '''8GB''', so be careful. They are also dumped every 4 hours, and the new one replaces the old name. If people are unable to retrieve these in less than the 4 hour period, then we can adjust the naming to keep more than one old version around. |
| 32 | | |
| 33 | | |
| 34 | | |
| 35 | | |
| | 29 | * all backups for the past 5 days (~20 copies) |
| | 30 | * one backup per day for the previous ~10 days (~10 copies) |
| | 31 | * one backup every 10 days for the previous 100 days (~10 copies) |
| | 32 | * one backup every 100 days for the lifetime of the project (~15 copies) |
