[444] in SIPB-AFS-requests
readonly and backup volumes and the backup software
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Mon May 6 22:38:54 1991
Date: Mon, 6 May 91 22:37:50 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: sipb-afsreq@ATHENA.MIT.EDU
It appears that the "vos backup" operation backs up a read-only copy
of a volume if it exists, rather than backing up the read-write copy.
I wanted to restore a file that existed a few hours ago in my sipb
volume. I made a mount point for sipb.mit.edu:user.jik.backup and
cd'd into it. The file wasn't there, despite the fact that vos
volinfo on the volume said it was created earlier tonight. I did the
same thing for sipb.mit.edu:user.jik.readonly, and the file wasn't
there either, and the volume was several months old.
So, I did "vos release" and then "vos backup" on my volume, after
which my newest files appears in both the readonly and backup volumes.
It seems to me therefore, that if we are not going to do automatic vos
releases on all of the volumes we back up each week, we have to delete
their readonly volumes.
Please let me know if I have made a mistake somewhere here.
jik
