cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup Tape writing behaviour

Hello All,

I have a question about tape retention. The question may be stupid and /i think i know the answer, but I am not sure.

In a situation where netbackup is writing a frontend(client to tape)  or SLP driven deduplication backup (disk to tape).. and for some reason the backup fails.

What happens to the data that has already been written on the tape? Is it retained as per the policy schedule retention that is defined or is it discarded?

Also what happens to such a tape where the backup that was writing to it failed before it could complete?

Is there a way of identifying such tapes? Maybe erasing them and putting them i nthe scratch pool?

Any help is fully appreciated.

 

Kind Regards,

Jay

 

5 Replies

Re: Netbackup Tape writing behaviour

If a job fails and has NOT spanned to another tape, then the tape is rewond to the beginning of the failed jobs, and an empty header is wriitten.  Therefore, the failed data is inaccessable and will be overwritten the next time the tape is used.

If the failed backup has spanned to another tape, then the same is true, but only for the tape that is being written at the time the job fails.  Previous tapes used for the failed backups and not 'updated'.

 

Re: Netbackup Tape writing behaviour

and if backup is multiplxed - e.g one good backup and one failed backup, the space used by the failed backup will be lost capacity until tape is returning to scratch status

Re: Netbackup Tape writing behaviour

Thanks for the replies.Is there any way to easily identify tapes which were part of failed backups? That is a scenario where backups have spanned multiple tapes and failed

Re: Netbackup Tape writing behaviour

No, not really. Nor can you recover that lost space, tape is linar medium. Best and only option is to wait for backups to expire. 

 

Re: Netbackup Tape writing behaviour

All media-id's used in the job will be in Job Details or in All Log Entries report.