I assume it has no problems with you changing the location field even
though that location may not yet exist? I guess I'm trying to determine
if it matters whether you change the location for the tapes before or
after you actually move the library and or set up the new storage node.
Seems like it wouldn't make any difference as long as you were careful
to obtain the names of the tapes before you moved it. Otherwise, if you
waited, the location will no longer point to where it was. You couldn't
then run 'nsrjb -C' since they'd no longer be there and they'd list out
as '_*' in the new mount listing. Likewise, running mminfo to get the
names of the volumes that were in the old location would work but only
if you did it first; othwerwise, the old value might now be empty so
there would no longer be a way to automate the process of generating the
names of the volumes to feed to the mmlocate command.
George
Andrew McGeorge wrote:
>
> George,
>
> here is what I do.
>
> nsrjb -C
>
> to get a list of all tapes in the library.
>
> Use mmlocate on the list to alter the location of the tapes to the new
> storage node.
>
> Move library.
>
> Inventory.
>
> regards
> Andrew McGeorge
>
> -----Original Message-----
> From: George Sinclair [mailto:George.Sinclair AT NOAA DOT GOV]
> Sent: 27 March 2003 3:53:AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] Bar code reader and inventory question?
>
> I think your guess seems reasonable. I know from experience that in
> cases where the volume is no longer listed as being in a given library,
> e.g. it was previously removed and placed on shelf, NetWorker will not
> re-load it into the drive if you inventory it with bar coding turned on
> even though the library may have been moved. It appears that the only
> time it DOES re-load it is if it was previously listed in a given
> library and either the library has changed names or the drives, as you
> suggested, have changed. So, perhaps, tapes loaded in a given library
> are not simply seen by their bar codes but are additionaly seen by their
> bar codes at that particular location, not just one or the other, but
> both. So, until you remove the volume from the library, it's bar code to
> internal label matchup is volatile in the sense that it's bound to that
> location and will have to be re-loaded every time the location changes
> until it's removed from the library. At that point, it's golden.
>
> George
>
> Matts Nilsson wrote:
> >
> > Hi George,
> > I'm partially guessing here, so be patient with me.
> > What I know is that the tape will only be loaded in
> > drive if NetWorker can not match the barcode label to
> > a volume. That is, if the barcode is unknown, NW will
> > try to read the tape to see if it contains a label.
> > After that NW knows the status of the tape.
> >
> > Now I'm guessing: When you move a tape or
> > drive/library to a storage node, the tape isn't known
> > at that location. It is known in a library attached to
> > the NW server, but not at the storage node.
> > As I said, I'm guessing, so PLEASE correct me if I'm
> > wrong!! :)
> >
> > // Matts
> >
> > --- George Sinclair <George.Sinclair AT NOAA DOT GOV> skrev:
> > > Hi,
> > >
> > > I have a question about the bar code reader and how
> > > NetWorker determines
> > > if it has to re-load the volume to know what it's
> > > label is.
> > >
> > > I've noticed that if you have the bar code reader
> > > value turned on for
> > > the jukebox then NetWorker will only load the
> > > barcoded tape during an
> > > inventory the first time. After that, it no longer
> > > needs to load it to
> > > inventory it. Makes sense. It also makes sense that
> > > if you turn off the
> > > library, and or move tapes around then as long as
> > > the affected tapes
> > > have been previously inventoried, NetWorker should
> > > not have to re-load
> > > them to inventory them, BUT why is it that if you
> > > move the library to a
> > > different server then NetWorker has to re-load the
> > > tapes from scratch
> > > during the first inventory on that server, but once
> > > again, only the
> > > first time. This happens whenever we move the
> > > library to a new storage
> > > node server. Is this normal behavior? Maybe the fact
> > > that the SCSI
> > > cables were unhooked and the control port has
> > > changed causes this?
> > >
> > > Thanks.
> > >
> > > George
> > >
> > > --
> > > Note: To sign off this list, send a "signoff
> > > networker" command via email
> > > to listserv AT listmail.temple DOT edu or visit the list's
> > > Web site at
> > > http://listmail.temple.edu/archives/networker.html
> > > where you can
> > > also view and post messages to the list.
> > >
> > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
> >
> > _____________________________________________________
> > Gå före i kön och få din sajt värderad på nolltid med Yahoo! Express
> > Se mer på: http://se.docs.yahoo.com/info/express/help/index.html
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
> ========================================================================================
> This email message and attachments are confidential to our organisation and
> subject to legal privilege. If you have received this email in error, please
> advise the sender immediately and destroy the message and any attachments. If
> you are not the intended recipient you are notified that any use,
> distribution, amendment, copying or any action taken or omitted to be taken
> in reliance of this message or attachments is prohibited. You can read our
> Privacy Policy here: <http://www.asbbank.co.nz/privacystatement.stm>
> =========================================================================================
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
