>>> Fred Donck writes:
FRED> AFS'ers, I have a 'small' problem :-( with the afs backup on
FRED> afs 3.3a.
FRED> Last night I ran a full backup on all three servers located
FRED> here. Two of them finished successfully, the third failed
FRED> with 200+ volumes still to go. How can I make sure that those
FRED> volumes are dumped. In other words how can I find out which
FRED> are the volumes that have/haven't been dumped to create a
FRED> dumpschedule for those that haven't been dumped.
If you run the dump command with the argument "-n", you will see a
list of what would have been dumped if you were actually performing a
dump. These volumes are listed in the order in which they would have
been dumped. So if you know that a specific number of volumes were
successfully dumped and 200+ volumes failed, then just count the
volumes on the list until you reach that specific number, and the
remaining volumes on the list are the ones that still need to be
dumped. If you write the output of the dump command to a file, you can
use a text editor to go directly to the line number (volume) where the
backups failed.
FRED> Or can I just restart the full backup (creating a new dump-id)
FRED> so that the still to be dumped volumes will come on tape ?
This would work, but it may just fail again at the same point.
...Mike
----
-------------------------------------------------------------------------------
Michael Wright UNIX/AFS System Administrator
Westinghouse Savannah River Company Email: [EMAIL PROTECTED]
Building 773-42A Phone: (803)725-1611
Aiken, SC 29808 FAX: (803)725-8829
-------------------------------------------------------------------------------
