Backup schedule

From UGCS
Jump to: navigation, search

General Notes

Each tape should have a label on the back with its name (usually UGCS_#). In the corner, it should also have the date it was purchased written in.

On the tape sleeve (the plastic case), you should put a piece of masking tape and identify what is on the tape. Please also write the tape number so the tapes and their cases stay matched. If the tape contains incremental backups, note which parent dumps it was taken from. I know the backup databases store this, but it's helpful to have written on the tape (otherwise you'll get very confused if you get out of the routine)

/afs/.ugcs/ugcs-admin/sysadmin-utils/dumptree will show you all of the AFS backups in a nice hierarchal structure.

To see what tape a dump is on, find its dumpid (with dumptree) and then run

backup dumpinfo -id <id> | head

Don't forget the |head otherwise it will list all the volumes in the dump (usually >3000) and you won't see anything.

Desired Schedule

  • We would like to backup everything off-site at least once a month. This means running the Bacula offsite jobs for everything manually. You should also do the /OffSiteQuarterly/month# dump.
  • Bacula automatically does dumps to persephone's disk once a day. You will have to manually manage the disk space, however- it fills up every few months or so.
  • We would like to get daily AFS dumps to something on-site. This means you should run the jobs in a schedule in the backup shell in the root screen session. See /afs/.ugcs/ugcs-admin/sysadmin-utils/make-dump-schedule.py to automate generating the schedule (so you can just copy-and-paste).
Personal tools