>> There was no problem when I tried to do Monthly Full backup for all *.backup,
>> however, when I tried to do the next incremental backup, BUTC show me the
>> following msg:
>>
>> ----------
>> Volume home.user1.backup (536881785) not dumped - has not been
>> re-cloned since last dump
>>
>> Dump of volume mail.spool.beast.backup (536881785) failed
>>
>> Please select action to be taken for this volume
>> r - retry, try dumping this volume again
>> o - omit, this volume from this dump
>> a - abort, the entire dump
>> ----------
>>
>> To finish dump, Do I have to type 'o' key for every failed volume? :-(
> Yes. 8-(
> The word "failed" is a bit misleading here. It shouldn't complain
> if the account is untouched since last time, but it does.
> Unfortunately.
Note! The message you're seeing is not
"not dumped - has not been modified since last dump"
but more importantly
"not dumped - has not been re-cloned since last dump"
The first message is an informational message, the second indicates
that you're trying to dump a volume before vos backupsys has been run,
and hence backing it up isn't going to provide anything useful.
If your backups are overlapping your vos backupsys runs, this could
explain why you're seeing this message. You should make sure vos
backupsys has completed before attempting backups.
Our site runs backupsys at 4AM, and then runs backups the following
evening. Every once in a while our backups run long and overlap the
start of the next backupsys run and we see the message you've
mentioned.
Kevin Hildebrand
University of Maryland, College Park
