welcome: please sign in

Diff for "BackupInfo"

Differences between revisions 9 and 10
Revision 9 as of 2007-08-30 16:03:29
Size: 1665
Editor: netblock-68-183-71-43
Comment:
Revision 10 as of 2007-09-27 14:27:08
Size: 1669
Editor: MichaelOlson
Comment: Fix title of last section
Deletions are marked like this. Additions are marked like this.
Line 65: Line 65:
== Database Backups ==
Line 66: Line 68:
= Database Backups =

This page describes the procedure for accessing and using our off-site backups. Only admins can do this -- if you want to get some file or directory back from the dead and are not an admin, please contact the hcoop-sysadmin list for assistance.

1. Mounting the backup volume

1.1. Getting access

ssh FOO_admin@deleuze.hcoop.net

aklog -c megacz.com

cd /afs/megacz.com/hcoop-backup/

cd $DESIRED_BACKUP_DATE

1.3. Restoring the volume dump to a volume with a new name

cat $VOLNAME.dump.bz2.aescrypt | \
  ccrypt -cdk /etc/backup-encryption-key | \
  bunzip2 | \
  vos restore deleuze /vicepa $VOLNAME.restored

1.4. Mounting the newly restored volume onto the filesystem

fs mkm /afs/hcoop.net/.../tmp-mount $VOLNAME.restored

2. Restoring a particular file

# examine /afs/hcoop.net/.../tmp-mount

3. Unmounting the restored volume

fs rm /afs/hcoop.net/.../tmp-mount

4. Renaming the restored volume so it takes the place of the damaged/corrupted/erased volume

Do this if you want to restore an entire volume. This deletes the old volume and replaces it with the backup.

vos remove $VOLNAME
vos rename $VOLNAME.restored $VOLNAME

5. Removing the restored volume

If you only wanted to restore a few files from the volume, you should remove the local copy of the backup volume when done.

vos remove $VOLNAME.restored

6. Database Backups

cat databases.tar.bz2.aescrypt | \
  ccrypt -cdk /etc/backup-encryption-key | \
  bunzip2 | \
  tar -xvzf -

BackupInfo (last edited 2019-03-31 19:34:13 by ClintonEbadi)