Watching Our Backs - Revision history

Jlderidder at 22:24, 18 December 2012

2012-12-18T22:24:21Z

←Older revision		Revision as of 22:24, 18 December 2012
Line 26:		Line 26:


-	The script then logs in with the checkscripts database ~~on content.lib.ua.edu~~ to verify that it ran, the timestamp, and any errors.	+	The script then logs in with the checkscripts database to verify that it ran, the timestamp, and any errors.


	'''storeFileSums'''		'''storeFileSums'''

-	Following this script, another script named storeFileSums runs. This one goes through all the gathered checksums, compares them to the ones in the md5sums mysql database ~~on content.lib.ua.edu~~, verifies (again) that nothing has changed, and enters new checksums that are found, with a timestamp.	+	Following this script, another script named storeFileSums runs. This one goes through all the gathered checksums, compares them to the ones in the md5sums mysql database, verifies (again) that nothing has changed, and enters new checksums that are found, with a timestamp.

-	This database is backed up monthly, and regular copies kept on ~~libcontent1~~.lib.ua.edu.	+	This database is backed up monthly, and regular copies kept on libcontent.lib.ua.edu.

	Errors are sent to jlderidder@ua.edu and uadigitalservices@gmail.com.		Errors are sent to jlderidder@ua.edu and uadigitalservices@gmail.com.

-	This script also logs in with the checkscripts database ~~on content.lib.ua.edu~~ to verify that it ran, the timestamp, and any errors.	+	This script also logs in with the checkscripts database to verify that it ran, the timestamp, and any errors.


	'''Automated Script Verifications'''		'''Automated Script Verifications'''

-	Once a week, a script called "checkscripts" on ~~content~~.lib.ua.edu in /~~home/jlderidder~~/scripts/cya looks through the entries in the checkscripts database for the past week, and compares them with the list of entries of existing cron scripts and when they are due to run.	+	Once a week, a script called "checkscripts" on libcontent.lib.ua.edu in /srv/scripts/cya looks through the entries in the checkscripts database for the past week, and compares them with the list of entries of existing cron scripts and when they are due to run.
	The checkscripts database consists of 2 tables: "ran" and "scripts."		The checkscripts database consists of 2 tables: "ran" and "scripts."
	Ran contains an auto-incrementing primary key (num), scriptid (identifier for the script, again a number),		Ran contains an auto-incrementing primary key (num), scriptid (identifier for the script, again a number),
Line 59:		Line 59:
	'''Database Backups'''		'''Database Backups'''

-	Since the checksums are backed up in a MySQL database, and a second MySQL database manages the scripts, there's a cron script (called "backups") on both content.lib.ua.edu (in /home/jlderidder/scripts/cya; backups go into /contentdbs/backups/databases/) and ~~libcontent1~~.lib.ua.edu (in /srv/scripts/cya/; backups go into /srv/backups/ ) which backs up selected databases monthly. Both scripts delete backups over a year old.	+	Since the checksums are backed up in a MySQL database, and a second MySQL database manages the scripts, there's a cron script (called "backups") on both content.lib.ua.edu (in /home/jlderidder/scripts/cya; backups go into /contentdbs/backups/databases/) and libcontent.lib.ua.edu (in /srv/scripts/cya/; backups go into /srv/backups/ ) which backs up selected databases monthly. Both scripts delete backups over a year old.
	Currently the list of databases backed up on content.lib.ua.edu is this:		Currently the list of databases backed up on content.lib.ua.edu is this:
-	#checkscripts
-	#md5sums
	#mysql		#mysql

Line 69:		Line 67:
	#mysql		#mysql
	#Acumen		#Acumen
		+	#md5sums
	#metaview (the test database for Acumen)		#metaview (the test database for Acumen)
-		+	#steve_museum (used for [http://tagit.lib.ua.edu Tagit] social tagging of content)
		+	#transcribe (with trmediawiki below, used for [http://transcribe.lib.ua.edu Transcribe] user transcriptions of content)
		+	#trmediawiki

	These lists are subject to change.		These lists are subject to change.

Jlderidder at 19:40, 30 June 2011

2011-06-30T19:40:11Z

←Older revision		Revision as of 19:40, 30 June 2011
Line 44:		Line 44:
	Once a week, a script called "checkscripts" on content.lib.ua.edu in /home/jlderidder/scripts/cya looks through the entries in the checkscripts database for the past week, and compares them with the list of entries of existing cron scripts and when they are due to run.		Once a week, a script called "checkscripts" on content.lib.ua.edu in /home/jlderidder/scripts/cya looks through the entries in the checkscripts database for the past week, and compares them with the list of entries of existing cron scripts and when they are due to run.
	The checkscripts database consists of 2 tables: "ran" and "scripts."		The checkscripts database consists of 2 tables: "ran" and "scripts."
-	Ran contains an auto-incrementing primary key (num), scriptid (identifier for the script, again a number), datestamp (for when this script ran) and errors.	+	Ran contains an auto-incrementing primary key (num), scriptid (identifier for the script, again a number),
-	Scripts contains a numerical id (which corresponds to the scriptid in "ran"), scriptname, server, directory where the script resides, the cron job that calls it,	+	datestamp (for when this script ran) and errors.
-	and a textual description of when it runs ("runswhen") and what it does ("doeswhat") as well as names of any scripts that it precedes (preceeds) or succeeds (succeeds)	+
		+	Scripts contains a numerical id (which corresponds to the scriptid in "ran"), scriptname, server, directory
		+	where the script resides, the cron job that calls it, and a textual description of when it runs ("runswhen")
		+	and what it does ("doeswhat") as well as names of any scripts that it precedes (preceeds) or succeeds (succeeds)
	in order to work properly.		in order to work properly.
		+
	If any scripts did ''NOT'' run, which were scheduled, or any of them logged errors, this script sends emails to notify us of problems.		If any scripts did ''NOT'' run, which were scheduled, or any of them logged errors, this script sends emails to notify us of problems.
	Of course, this script also logs in with the checkscripts database to verify that it ran, and when.		Of course, this script also logs in with the checkscripts database to verify that it ran, and when.

Jlderidder at 18:55, 16 May 2011

2011-05-16T18:55:26Z

←Older revision		Revision as of 18:55, 16 May 2011
Line 15:		Line 15:
	corrupted item can be written to tape.		corrupted item can be written to tape.

-	On libcontent1, in /srv/scripts/md5/cya/, the script which calculates and checks sums is called "~~dirs~~". ~~([[Image:Dirs.txt]])~~	+	On libcontent1, in /srv/scripts/md5/cya/, the script which calculates and checks sums is called "md5check".
-	First it looks for new ~~content;~~ if there is any, it ~~calculates the sums~~ for that ~~content~~.	+
-	Second, it checks the checksums for ~~existing directories~~. If they have changed, it outputs an error.	+	First it looks for new holder areas (such as u0001, u0003, etc. in the archive). If there are any, it sets up a new location for checksums for that holder. Within each holder directory in the checksums area, there's a file for each collection. Each collection's file contains all the checksums for that collection.
-	Third, ~~it checks~~ the checksums for ~~existing files. If they have changed, it outputs an error~~.	+
-	~~If there are no errors~~, ~~it copies~~ the ~~sums /srv/scripts/md5/cya/backups~~ in ~~a tar.gz compressed form~~.	+	Second, md5check goes through each holder area in turn, checking collections one at a time. If the collection exists, it checks the checksums for each file. If they have changed, it outputs an error. While traversing the archive it notes new content, and generates checksums for those before going on to the next collection.
-	~~Backups older than a year are deleted.~~	+
-	~~Errors are sent to jlderidder@ua.edu and uadigitalservices@gmail.com.~~	+	Third, if any new collections were noted in the holder area, the script creates collection md5 files and generates checksums for the content before going on to the next holder area.
		+
		+	Fourth, the script goes through the new holder areas, finds new collections, notes any new content in existing collections.
		+
		+
	The script then logs in with the checkscripts database on content.lib.ua.edu to verify that it ran, the timestamp, and any errors.		The script then logs in with the checkscripts database on content.lib.ua.edu to verify that it ran, the timestamp, and any errors.

-	'''Checksum Backups'''

-	~~After~~ this script ~~completes~~, another ~~one in the same directory, on the same server~~ runs. This one ~~is called "storesums" and that's just what it does. Existing sums are checked against those stored~~ in ~~a MySQL database (~~md5sums) on ~~another server (~~content.lib.ua.edu)~~; if any have~~ changed, or new ~~sums were created, these are added to~~ that ~~database; no existing sums~~ are ~~overwritten (and of course~~, a ~~datestamp~~ is kept ~~for each checksum)~~.	+	'''storeFileSums'''
		+
		+	Following this script, another script named storeFileSums runs. This one goes through all the gathered checksums, compares them to the ones in the md5sums mysql database on content.lib.ua.edu, verifies (again) that nothing has changed, and enters new checksums that are found, with a timestamp.
		+
		+	This database is backed up monthly, and regular copies kept on libcontent1.lib.ua.edu.
		+
		+	Errors are sent to jlderidder@ua.edu and uadigitalservices@gmail.com.
		+
	This script also logs in with the checkscripts database on content.lib.ua.edu to verify that it ran, the timestamp, and any errors.		This script also logs in with the checkscripts database on content.lib.ua.edu to verify that it ran, the timestamp, and any errors.
		+

	'''Automated Script Verifications'''		'''Automated Script Verifications'''
Line 55:		Line 66:
	#Acumen		#Acumen
	#metaview (the test database for Acumen)		#metaview (the test database for Acumen)
		+

	These lists are subject to change.		These lists are subject to change.

Jlderidder at 21:44, 30 July 2010

2010-07-30T21:44:26Z

←Older revision		Revision as of 21:44, 30 July 2010
Line 15:		Line 15:
	corrupted item can be written to tape.		corrupted item can be written to tape.

-	On libcontent1, in /srv/scripts/md5/cya/, the script which calculates and checks sums is called "dirs".	+	On libcontent1, in /srv/scripts/md5/cya/, the script which calculates and checks sums is called "dirs". ([[Image:Dirs.txt]])
	First it looks for new content; if there is any, it calculates the sums for that content.		First it looks for new content; if there is any, it calculates the sums for that content.
	Second, it checks the checksums for existing directories. If they have changed, it outputs an error.		Second, it checks the checksums for existing directories. If they have changed, it outputs an error.

Jlderidder at 15:52, 28 July 2010

2010-07-28T15:52:00Z

←Older revision		Revision as of 15:52, 28 July 2010
Line 32:		Line 32:

	Once a week, a script called "checkscripts" on content.lib.ua.edu in /home/jlderidder/scripts/cya looks through the entries in the checkscripts database for the past week, and compares them with the list of entries of existing cron scripts and when they are due to run.		Once a week, a script called "checkscripts" on content.lib.ua.edu in /home/jlderidder/scripts/cya looks through the entries in the checkscripts database for the past week, and compares them with the list of entries of existing cron scripts and when they are due to run.
		+	The checkscripts database consists of 2 tables: "ran" and "scripts."
		+	Ran contains an auto-incrementing primary key (num), scriptid (identifier for the script, again a number), datestamp (for when this script ran) and errors.
		+	Scripts contains a numerical id (which corresponds to the scriptid in "ran"), scriptname, server, directory where the script resides, the cron job that calls it,
		+	and a textual description of when it runs ("runswhen") and what it does ("doeswhat") as well as names of any scripts that it precedes (preceeds) or succeeds (succeeds)
		+	in order to work properly.
	If any scripts did ''NOT'' run, which were scheduled, or any of them logged errors, this script sends emails to notify us of problems.		If any scripts did ''NOT'' run, which were scheduled, or any of them logged errors, this script sends emails to notify us of problems.
	Of course, this script also logs in with the checkscripts database to verify that it ran, and when.		Of course, this script also logs in with the checkscripts database to verify that it ran, and when.

Jlderidder at 15:44, 28 July 2010

2010-07-28T15:44:40Z

←Older revision		Revision as of 15:44, 28 July 2010
Line 42:		Line 42:
	Currently the list of databases backed up on content.lib.ua.edu is this:		Currently the list of databases backed up on content.lib.ua.edu is this:
	#checkscripts		#checkscripts
-	#InfoTrack ( see [[Tracking_for_the_long_term]])
	#md5sums		#md5sums
	#mysql		#mysql

Jlderidder at 15:43, 28 July 2010

2010-07-28T15:43:11Z

←Older revision		Revision as of 15:43, 28 July 2010
Line 49:		Line 49:
	#InfoTrack ( see [[Tracking_for_the_long_term]])		#InfoTrack ( see [[Tracking_for_the_long_term]])
	#mysql		#mysql
		+	#Acumen
		+	#metaview (the test database for Acumen)

	These lists are subject to change.		These lists are subject to change.

Jlderidder at 21:33, 15 July 2009

2009-07-15T21:33:43Z

←Older revision		Revision as of 21:33, 15 July 2009
Line 26:		Line 26:
	'''Checksum Backups'''		'''Checksum Backups'''

-	After this script completes, another one in the same directory, on the same server runs. This one is called "storesums" and that's just what it does. Existing sums are checked against those stored in a MySQL database on another server (content.lib.ua.edu); if any have changed, or new sums were created, these are added to that database; no existing sums are overwritten (and of course, a datestamp is kept for each checksum).	+	After this script completes, another one in the same directory, on the same server runs. This one is called "storesums" and that's just what it does. Existing sums are checked against those stored in a MySQL database (md5sums) on another server (content.lib.ua.edu); if any have changed, or new sums were created, these are added to that database; no existing sums are overwritten (and of course, a datestamp is kept for each checksum).
	This script also logs in with the checkscripts database on content.lib.ua.edu to verify that it ran, the timestamp, and any errors.		This script also logs in with the checkscripts database on content.lib.ua.edu to verify that it ran, the timestamp, and any errors.

Line 42:		Line 42:
	Currently the list of databases backed up on content.lib.ua.edu is this:		Currently the list of databases backed up on content.lib.ua.edu is this:
	#checkscripts		#checkscripts
-	#InfoTrack [[Tracking_for_the_long_term]]	+	#InfoTrack ( see [[Tracking_for_the_long_term]])
	#md5sums		#md5sums
	#mysql		#mysql

	And the list of databases currently backed up on libcontent1.lib.ua.edu is this:		And the list of databases currently backed up on libcontent1.lib.ua.edu is this:
-	#InfoTrack [[Tracking_for_the_long_term]]	+	#InfoTrack ( see [[Tracking_for_the_long_term]])
	#mysql		#mysql

Jlderidder at 21:32, 15 July 2009

2009-07-15T21:32:53Z

←Older revision		Revision as of 21:32, 15 July 2009
Line 42:		Line 42:
	Currently the list of databases backed up on content.lib.ua.edu is this:		Currently the list of databases backed up on content.lib.ua.edu is this:
	#checkscripts		#checkscripts
-	#InfoTrack	+	#InfoTrack [[Tracking_for_the_long_term]]
	#md5sums		#md5sums
	#mysql		#mysql

	And the list of databases currently backed up on libcontent1.lib.ua.edu is this:		And the list of databases currently backed up on libcontent1.lib.ua.edu is this:
-	#InfoTrack	+	#InfoTrack [[Tracking_for_the_long_term]]
	#mysql		#mysql

Jlderidder at 20:33, 15 July 2009

2009-07-15T20:33:35Z

←Older revision		Revision as of 20:33, 15 July 2009
Line 35:		Line 35:
	Of course, this script also logs in with the checkscripts database to verify that it ran, and when.		Of course, this script also logs in with the checkscripts database to verify that it ran, and when.

-	Then, since any server can go down, and multitudes of error possibilities exist, a third script on a third server (libapp.ua-net.ua.edu) runs to verify that the checkscripts script ran as it should. Again, this one sends us any errors, and it logs in with the checkscripts database.	+	Then, since any server can go down, and multitudes of error possibilities exist, a third script on a third server ("checkscriptcheck" in /home/jlderidder/cya on libapp.ua-net.ua.edu) runs to verify that the checkscripts script ran as it should. Again, this one sends us any errors, and it logs in with the checkscripts database.

	'''Database Backups'''		'''Database Backups'''