Changes between Version 36 and Version 37 of DatabaseBackups

Timestamp:

Mar 30, 2015, 11:25:19 AM (11 years ago)

Author:

bills

Comment:

--

DatabaseBackups

@@ -4 +4 @@
 (Last update: see [http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/wiki/DatabaseBackups?action=history history])
  * Backup scripts can be found here: https://svn.pan-starrs.ifa.hawaii.edu/repo/ipp/trunk/tools/mysql-dump. The README file and each script contain documentation. They are installed in ~ipp/mysql-dump.
- * nebulous on ippdb00 is replicated on ippdb02.
+ * nebulous on ippdb00 is replicated on ippdb02, ippdb06, and ippdb08
 
+NOTE: Backups of the nebulous database are no longer perfomed. This section is no longer applicable.
    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. 
 
@@ -15 +16 @@
  * gpc1 on ippdb01 is replicated on ippdb03 and ipp001. 
 
-   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).
-
-   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.
+   The database on ippdb03 is backed up every 12 hours (at 4:05 and 16:05). Dumping the database takes about six hours. 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).
 
    The log file can be found at /export/ippdb03.0/mysql-dumps/gpc1_dump.log
+
+   On ipp001, every 12 hours (at 1:05 and 13:05), gpc1 is verified and distributed with its md5 checksum on the rsync server. Note that the dump no longer needs to be injested onto the mysql instance on ipp001 because it is a replicant.
 
    The backup file can be ingested to create a replication slave of the master (ippdb01). The master coordinates are dumped just before the actual mysqldump and are written to /export/ippdb03.0/mysql-dumps/mysql-gpc1-coordinates-ippdb03-*.txt (take the coordinates that corresponds to the dump). Use those coordinates after the mysqldump has been ingested (there are other coordinates in the mysqldump file but they cannot be used to create a replication slave). Documentation about use of master coordinates can be found [http://svn.pan-starrs.ifa.hawaii.edu/trac/ipp/wiki/MySqlReplication there].