Changes between Version 11 and Version 12 of DatabaseBackups

Timestamp:

Apr 7, 2011, 12:19:20 PM (15 years ago)

Author:

Serge CHASTEL

Comment:

--

DatabaseBackups

@@ -32 +32 @@
 '''Note:''' The validity of the ippdb01-gpc1.dump.gz file can be asserted via its MD5 checksum (stored in ippdb01-gpc1.md5 and distributed in the same place rsync://ipp0012.ifa.hawaii.edu/ippdb/ippdb01-gpc1.md5)
 
-For reference, all of the various ipp mysql databases are now being dumped to /data/ipp001.0/ipp/mysql-dumps, and these above are linked into the 'distribution' subdirectory, which is made visible via the rsync server.  We are moving to a system of keeping a sampling of the old databases with the following timescales:
+= Other =
+
+== For reference ==
+All of the various ipp mysql databases are now being dumped to /data/ipp001.0/ipp/mysql-dumps, and these above are linked into the 'distribution' subdirectory, which is made visible via the rsync server.  We are moving to a system of keeping a sampling of the old databases with the following timescales:
 
  * all backups for the past 5 days (~20 copies)
@@ -40 +43 @@
 
 (currently, we are keeping all of the old copies with a linear spacing...)
+
+== Monitoring ==
+
+Log files (the best is to check in the relevant crontab though):
+
+ * gcp1:
+{{{
+ippc02:/export/ippc02.0/mysql-dumps/gpc1_dump.log
+ipp001:/home/panstarrs/ipp/mysql-dump/gpc1_install.log
+}}}
+
+ * nebulous:
+{{{
+ippdb02:/export/ippdb02.0/mysql-dumps/neb_dump.log
+ipp001:/home/panstarrs/ipp/mysql-dump/neb_copy.log
+}}}
+