Backups - Revision history

S23adhik: /* /users Backup */

2026-09-01T19:32:55Z

/users Backup

@@ Line 4: / Line 4: @@
 == /users Backup ==
 On Tequila I made a dedicated destination dataset called backup/csc0_backups (backups is a big pool);
@@ Line 21: / Line 23: @@
 zfs send -R -i csc0@base csc0@snap_$(date +%Y%m%d) | ssh root@tequila zfs recv -F backup/csc0_backups
 == MySQL ==

S23adhik at 04:40, 24 August 2026

2026-08-24T04:40:15Z

← Older revision		Revision as of 23:40, 23 August 2026
Line 2:		Line 2:

	Miscellaneous backups (including backups of home directories for expired accounts) are stored in /users/backup (accessible on any system that NFS-mounts [[User-data\|/users]]).		Miscellaneous backups (including backups of home directories for expired accounts) are stored in /users/backup (accessible on any system that NFS-mounts [[User-data\|/users]]).

			== /users Backup ==
			/users primary is held on ranch, whilst it's backup is held on tequila via incremental zfs snapshots

			On Tequila I made a dedicated destination dataset called backup/csc0_backups (backups is a big pool);

			zfs create backup/csc0_backups

			Then on ranch I ran a snapshot, and sent it over;

			zfs snapshot -r csc0@base

			zfs send -R csc0@base \| ssh root@tequila zfs recv -F backup/csc0_backups

			In the future we need to setup incremental sends on ranch

			zfs snapshot -r csc0@snap_$(date +%Y%m%d)

			zfs send -R -i csc0@base csc0@snap_$(date +%Y%m%d) \| ssh root@tequila zfs recv -F backup/csc0_backups

	== MySQL ==		== MySQL ==

Ztseguin: /* MySQL */

2017-02-02T05:19:45Z

MySQL

← Older revision		Revision as of 00:19, 2 February 2017
Line 5:		Line 5:
	== MySQL ==		== MySQL ==

			We don't currently backup MySQL. See the historical version of this page for previous backup strategy.
	As of January 2010, backups of [[MySQL]] databases are run weekly and stored in /users/backup/mysql, a git repository accessible only to members of [[Systems_Committee\|syscom]] (for obvious reasons). In there is a .sql file containing a backup of each database present in the MySQL database.

	This backup is run automatically from /etc/cron.weekly/mysql-backup on [[Machine_List#caffeine\|caffeine]]. A git repository was chosen because the SQL dumps are by default text files which are easily handled by git (notably, git handles deltas for this format extremely well). As a result, it is possible to retrieve an old backup of a database or view differences from week to week by using the regular git tools. git stores compressed deltas for all previous revisions, so this has the effect of storing many old copies of databases at minimal storage cost.

	[[Category:Software]]		[[Category:Software]]

Ztseguin: Update LDAP and Kerberos backups

2017-02-02T05:13:38Z

Update LDAP and Kerberos backups

← Older revision		Revision as of 00:13, 2 February 2017
Line 1:		Line 1:
			We take [[LDAP]] and [[Kerberos]] backups twice daily. Backups on auth1 occur at 4am and on auth2 they occur at 4pm. On each machine, backups are stored in /backup/{ldap,krb5} (in the case of auth1, this is /backup exported from the [[NetApp]]).
	We take nightly [[Kerberos]] and [[LDAP]] backups. The backups are stored on [[Machine_List#artificial-flavours\|artificial-flavours]] in /var/backups/krb5 and /var/backups/slapd respectively. These are executed as cronjobs in /etc/cron.daily.

	Miscellaneous backups (including backups of home directories for expired accounts) are stored in /users/backup (accessible on any system that NFS-mounts [[User-data\|/users]]).		Miscellaneous backups (including backups of home directories for expired accounts) are stored in /users/backup (accessible on any system that NFS-mounts [[User-data\|/users]]).

Jbroman: add to Software category

2010-03-23T00:06:43Z

add to Software category

← Older revision		Revision as of 19:06, 22 March 2010
Line 8:		Line 8:

	This backup is run automatically from /etc/cron.weekly/mysql-backup on [[Machine_List#caffeine\|caffeine]]. A git repository was chosen because the SQL dumps are by default text files which are easily handled by git (notably, git handles deltas for this format extremely well). As a result, it is possible to retrieve an old backup of a database or view differences from week to week by using the regular git tools. git stores compressed deltas for all previous revisions, so this has the effect of storing many old copies of databases at minimal storage cost.		This backup is run automatically from /etc/cron.weekly/mysql-backup on [[Machine_List#caffeine\|caffeine]]. A git repository was chosen because the SQL dumps are by default text files which are easily handled by git (notably, git handles deltas for this format extremely well). As a result, it is possible to retrieve an old backup of a database or view differences from week to week by using the regular git tools. git stores compressed deltas for all previous revisions, so this has the effect of storing many old copies of databases at minimal storage cost.

			[[Category:Software]]

Jbroman: MySQL backups

2010-01-25T01:28:28Z

MySQL backups

← Older revision		Revision as of 20:28, 24 January 2010
Line 2:		Line 2:

	Miscellaneous backups (including backups of home directories for expired accounts) are stored in /users/backup (accessible on any system that NFS-mounts [[User-data\|/users]]).		Miscellaneous backups (including backups of home directories for expired accounts) are stored in /users/backup (accessible on any system that NFS-mounts [[User-data\|/users]]).

			== MySQL ==

			As of January 2010, backups of [[MySQL]] databases are run weekly and stored in /users/backup/mysql, a git repository accessible only to members of [[Systems_Committee\|syscom]] (for obvious reasons). In there is a .sql file containing a backup of each database present in the MySQL database.

			This backup is run automatically from /etc/cron.weekly/mysql-backup on [[Machine_List#caffeine\|caffeine]]. A git repository was chosen because the SQL dumps are by default text files which are easily handled by git (notably, git handles deltas for this format extremely well). As a result, it is possible to retrieve an old backup of a database or view differences from week to week by using the regular git tools. git stores compressed deltas for all previous revisions, so this has the effect of storing many old copies of databases at minimal storage cost.

Jbroman: added note about /users/backup

2010-01-19T22:59:52Z

added note about /users/backup

← Older revision		Revision as of 17:59, 19 January 2010
Line 1:		Line 1:
	We take nightly [[Kerberos]] and [[LDAP]] backups. The backups are stored on [[Machine_List#artificial-flavours\|artificial-flavours]] in /var/backups/krb5 and /var/backups/slapd respectively. These are executed as cronjobs in /etc/cron.daily.		We take nightly [[Kerberos]] and [[LDAP]] backups. The backups are stored on [[Machine_List#artificial-flavours\|artificial-flavours]] in /var/backups/krb5 and /var/backups/slapd respectively. These are executed as cronjobs in /etc/cron.daily.

			Miscellaneous backups (including backups of home directories for expired accounts) are stored in /users/backup (accessible on any system that NFS-mounts [[User-data\|/users]]).

Jbroman: here be cronjobs

2010-01-19T14:26:34Z

here be cronjobs

← Older revision		Revision as of 09:26, 19 January 2010
Line 1:		Line 1:
	We take nightly [[Kerberos]] and [[LDAP]] backups. The backups are stored on [[Machine_List#artificial-flavours\|artificial-flavours]] in /var/backups/krb5 and /var/backups/slapd respectively.		We take nightly [[Kerberos]] and [[LDAP]] backups. The backups are stored on [[Machine_List#artificial-flavours\|artificial-flavours]] in /var/backups/krb5 and /var/backups/slapd respectively. These are executed as cronjobs in /etc/cron.daily.

Jbroman: backups of KDC/LDAP are back in place

2010-01-19T14:25:24Z

backups of KDC/LDAP are back in place

← Older revision		Revision as of 09:25, 19 January 2010
Line 1:		Line 1:
	We ~~used to~~ take nightly [[Kerberos]] and [[LDAP]] backups. The backups are stored on [[Machine_List#artificial-flavours\|artificial-flavours]] in /var/backups/krb5 and /var/backups/slapd ~~respectively. However, these backups appear to have stopped in July and October of 2009,~~ respectively.		We take nightly [[Kerberos]] and [[LDAP]] backups. The backups are stored on [[Machine_List#artificial-flavours\|artificial-flavours]] in /var/backups/krb5 and /var/backups/slapd respectively.

Jbroman: fixed link

2010-01-19T14:13:51Z

fixed link

← Older revision		Revision as of 09:13, 19 January 2010
Line 1:		Line 1:
	We used to take nightly [[Kerberos]] and [[LDAP]] backups. The backups are stored on [[Machine_List#artificial-flavours artificial-flavours]] in /var/backups/krb5 and /var/backups/slapd respectively. However, these backups appear to have stopped in July and October of 2009, respectively.		We used to take nightly [[Kerberos]] and [[LDAP]] backups. The backups are stored on [[Machine_List#artificial-flavours\|artificial-flavours]] in /var/backups/krb5 and /var/backups/slapd respectively. However, these backups appear to have stopped in July and October of 2009, respectively.