IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Version 21 and Version 22 of DatabaseBackups


Ignore:
Timestamp:
Jul 12, 2011, 9:37:43 AM (15 years ago)
Author:
Serge CHASTEL
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DatabaseBackups

    v21 v22  
    66 * nebulous on ippdb00 is replicated on ippdb02.
    77
    8    The database on the replication slave is backed up twice a day at 0:30 and 12:30 (see the local crontab). Dumping the whole database takes about 3 hours.
     8   The database on the replication slave is backed up twice a day at 0:30 and 12:30 (see the root crontab on ippdb02). Dumping the whole database takes about 3 hours.
    99
    10    Every day at 03: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).
    11  * gpc1 on ippdb01 is replicated on ippc02.
     10   Every day at 09:05 and 16: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 to ps-ipp-ops.
     11   The log file can be found at /export/ippdb02.0/mysql-dumps/neb_dump.log
    1212
    13    The database on the replication slave 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).
     13 * gpc1 on ippdb01 is replicated on ippdb03 and ipp001.
     14
     15   The database on ippdb03 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. The script responsible for the dump (gpc1_dump) is also responsible for the copy onto ipp001 (it is then different from the previous one). This script is run as the ipp user (look at the ipp crontab on ippdb03).
    1416
    1517   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 (once a day between 0:00 and 4:00), and distributed with its md5 checksum on the rsync server.
     18
     19   The log file can be found at /export/ippdb03.0/mysql-dumps/gpc1_dump.log
    1620
    1721 * Backups of ippRequestServer, isp, ippadmin is /home/panstarrs/ipp/mysql-dump/ops_dump.csh (Manoa cluster).