[980] in SIPB-AFS-requests
AFS 3.2 backup system
daemon@ATHENA.MIT.EDU (Marc Horowitz)
Wed Jun 23 00:09:05 1993
To: sipb-afsreq@athena.mit.edu
Cc: probe@athena.mit.edu
Reply-To: Marc Horowitz <marc@mit.edu>
Date: Wed, 23 Jun 93 00:08:36 EDT
From: Marc Horowitz <marc@athena.mit.edu>
I've set up the 3.2 backup system at work, and I think we should set
it up here at SIPB. This is a proposal for discussion.
1) I'm running fms now to determine how much we can actually store on
a tape.
2) There should be two volume sets. Both should include all backed up
volumes. One should be used for off-site backups, and one for on-site
backups.
3) This is the dump schedule I've set up for work. I think it would
work well for SIPB as well. I don't expect us to make daily backups
often, but this provides for that. We might also consider a cycle of
three full dumps instead of just two.
/full1
/tue1
/wed1
/thu1
/fri1
/week1
/tue2
/wed2
/thu2
/fri2
/week2
/tue1
/wed1
/thu1
/fri1
/week3
/tue2
/wed2
/thu2
/fri2
/full2
/tue1
/wed1
/thu1
/fri1
/week1
/tue2
/wed2
/thu2
/fri2
/week2
/tue1
/wed1
/thu1
/fri1
/week3
/tue2
/wed2
/thu2
/fri2
For the non-afs3.2-backup-aware, this means that we have two full
backups, run every 4 weeks, alternating. Every week, we have an
incremental based on the most recent full. The tapes are reused each
4 week period. There are also daily incrementals, but we don't need
to actually run them. If we do, the incremental tapes are reused
every two weeks. We could reduce this to one trivially.
So, does this make sense to everyone? (Who can understand it :-)
Marc
