Apparently you have to change the location attribute after the volume is 
removed... doing it before did not stick.  I will try again next week when I 
have a clone tape to remove.  



lphilpot wrote:
> 
> > 1.) Marked the tape full with "nsrjb -o full {barcode} 
> > 2.) Updated the location field with NW Admin Console
> > 3.) Brought tape library offline, and pulled tape
> > 4.) Inserted new volume into library
> > 
> 
> 
> > What is wrong with this process? 
> > 
> 
> Nothing that I can see. I've scripted a similar process that has worked 
> for years: 
> 
> 1. The script uses mminfo to report on which clones are to be pulled
> 2. I physically pull them from the libraries (no port either, I just open 
> them up)
> 3. Once the libraries are back online, the script reinventories the 
> slot(s) (nsrjb) and sets their location to a special "offsite" value 
> (mmlocate)
> 
> It does a few other QA and compliance things, but I've never had any 
> issues with it. However, that's using 7.2. We'll be going to 7.4 in the 
> next few months, so I'm all ears if there are issues with this 
> procedure...
> 
> 
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


+----------------------------------------------------------------------
|This was sent by Jonathan.Gill AT uconn DOT edu via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

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