On Nov 6, 2007, at 10:13 AM, MIchael Leone wrote:

Stan Horwitz <stan AT temple DOT edu> wrote on 11/06/2007 10:04:32 AM:

So I'd have to pipe the volume ID into nsrjb, get the slot number that

way, concat the the info with the previous report, and then email
it out?

Yes, but the idea to just refer to the tapes volume name on an "nsrjb
-w" command makes a lot more sense. That way, you allow NetWorker to
figure out where the tape is by just giving nsrjb the name of the
tape you want to remove from the tape library.

I'll see what I can do. This server isn't ready to be fully  put in

production yet, hence the tech doesn't get there every day to remove any auto-ejected tapes. When it goes into production, of course, he'll stop

there every day and remove the tape, so auto-ejecting shouldn't be a

problem. Until then, I guess I'll have to tell him to stop there every day

to remove the tape.

As long as there is only 1 tape per day, this should work. If the job goes

to 2 tapes (and it will), tho, I won't be able to auto-eject all the

volumes made for that day. When that happens, it will be easier to have

the email tell him which slots to eject when he gets to the site.

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER