J.Hinchcliffe's blog

Frist - see my blog on just how it Writes to tape.
www-secure.symantec.com/connect/blogs/understanding-how-netbackup-writes-tape

Now with that understanding your question about jobs wanting a tape drive.

A recent discussion showed that some NetBackup users think that "ALL_LOCAL_DRIVES" can only be used for windows clients.
It can be use for unix as well.

All local drives will work on UNIX just like it does on windows.

On windows clients it seems obvious that all local drives will be drives like C: and E: and F:

Understanding how NetBackup writes to tapes and what happens when images expire will help you better manage your tapes.

Tapes are linear - meaning that they write from the front to the back.

if we look at a tape.
BOT|day1image|day2image|blankspace|EOT

now the day1image expires on the tape - the assigned date does not change and you have this.

I set up Media ID Generation - had it just the way I wanted it!
I even tested it and it worked GREAT.

Then when my NetBackup operator put in new tapes for the library - the ID's were wrong!!!

I checked again and I yes I had a rule for it.
And I tested it and it worked.

So they tried again - and again it failed.

I know I am not the best typist or speller...
But does anybody know who to report typographical errors in documentation or the software?

Point in question -
NOM/Alerts/Select Condition
for High Frozen Media -
Description
"Action is taken if, Number of frozed medias exceeds predefined threshold value."