Unsolved

This post is more than 5 years old

32 Posts

788

April 20th, 2006 00:00

export port

hi;

i realised that our library's export cartridge port isn't set. So i changed the first slot as export port from the hardware. now legato finds out the slot but it gives an error like "wrong slot adress etc." i think i must reconfigure library. should i simply run jbconfig ? is there anything else that i should do ?

thanks.

32 Posts

April 20th, 2006 01:00

IE cap is the first slot in our library. before, this slot was configured as MAP port. and if i try to deposit a cartridge from networker, it said like "no export slot was found". now it looks as export port in library. And in networker, i can't see this slot anymore. so is jbconfig enough to run, should i do anything in windows ?

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 20th, 2006 01:00

No, jbconfig will be enough (but you will need to delete previous instance of library first of course).

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 20th, 2006 01:00

I'm not sure how things were before and how do they look now, but usually IE cap is the last one and not first. Once you did this verify layout with sjirdtag command. Then go to library properties from NW and check following field:
- physical slots
- available slots

I think first one is read only and probably changed now (-1) which leads me to believe you do need new jbconfig now. Make sure that you call your library with the same name as before (and that you do not have any tape loaded during jbconfig procedure).

32 Posts

April 21st, 2006 05:00

thanks. it worked. after depositing i see the cartridge as unlabeled, as intented. i make an inventory for this slot. but i think it does by reading its barcode not by putting into drive and reading the label block of cartridge. because it finishes at once. if we put the cartridge into another drive outside the library and label it before depositing ?
it will read wrongly, am i right ?

32 Posts

April 21st, 2006 06:00

yes it's working as what manual says. because it's barcode is still in media database.

imagine that we withdraw the cartridge from library and then not delete the volume information.

and we deposit it to another library which has a different media database or another standalone drive. and label it there. then withdraw again.

then deposit to our first library. when i inventory, it reads the barcode and thinks it's the same cartridge before withdrawing for the first time.
i hope i am clear :)

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 21st, 2006 06:00

It really depends. If library will return uknown of unexpected barcode for slot tape will be loaded and label will be verified. If you do something like nsrjb -HvE and follow this with nsrjb -Iv -S slot range (or even only nsrjb -IEv) you might not see that. As manual says "If the bar code label is not unique or does not exist in the NetWorker media data-base, the volume name is read from the media. If a bar code label on the media has changed, then the NetWorker media database is updated with the new bar code label."

The rule of the thumb is that when you move your tapes without knowledge of NW you must run inventory.

I didn't understand your second question (drive outside the library, label and then deposit...).

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 21st, 2006 07:00

imagine that we withdraw the cartridge from library
and then not delete the volume information.

Delete from media database or nsrjb database? I assume first one as that is something one does see in practice.
EDIT: Actually it is first one after reading second part :)

and we deposit it to another library which has a
different media database or another standalone drive.
and label it there. then withdraw again.

Oh, that would be new backup server. OK...

then deposit to our first library. when i inventory,
it reads the barcode and thinks it's the same
cartridge before withdrawing for the first time.
i hope i am clear :)

Oh yes, that is correct and expected behaviour. However, if you would try to load that tape or label it again NW would complain as tape would labeled in second NW server. Also, while barcode and label would be the same (actaully, in its core label would not be same) volid would be different. This is how you can also see message for duplicate ids...

In such case you would get in trouble and if NW would insist of loading that tape over the night while backup is running you could get stuck.

Unless you really need to you should not share same tapes between different libraries because soon or later a mistake will happen (Murphy). If yes, then make sure that you delete the volume from the media db once that you remove it from one server and assign it to second one.
No Events found!

Top