How to label volume with barcode? 3

[Pancevo1956]

nsrjb command gives:

Jukebox ADIC@4.4.1: (Ready to accept commands)
slot volume pool barcode volume id recyclable
1: A00014 Bekap servera full A00014 1284045165 no
2: A00013 Bekap servera full A00013 453063638 no
3: A00012 Bekap servera inkr A00012 2035997205 no
4: -* A00011 -
5: A00010 Bekap servera full A00010 3348009328 no
6: A00009 Default A00009 4021459 no

What I need is the command (or GUI in Networker Administrator 7.4) to label volume in slot 4 with label A00011.

 

[605]

From the GUI, this should not be a problems as the jukebox option "use barcode labels" has obviously been set.

Just select the volume, open the menu, select the label command and answer the questions.

From the command line, you must use the nsrjb command. But if you have the GUI available, i do not recommend it.

 

[denisfr]

Hello,

you can try (if the 'match bar code labels' or something like that is set for your jukebox) :

nsrjb -L -b "your_pool" -S 4

Denis

 

[Pancevo1956]

That was fine but last several days I have tried to put it back in right order but of no avail. I have tried the following:
1. reset the jb with nsrjb -HEv & nsrjb -IEvv
2. run nsrim -X & nsrck -L6

Then when Right click slot & inventory -> On the Bottom of the window -> there is a option of Force load & inventory label and that for each volume where barcode does not correspond volume.

And each morning same thing. 1 or 2 volumes are with label.
Is there anything else I can do?

 

[605]

This does not make sense. It looks like the media DB deletes/forgets the info about the volume for whatever reason.

Resetting the jukebox just scans the barcodes. It does not affect the media information about known tapes (at least it should not).

nsrck -L6 recovers the latest client files index inf and has nothing to do with the media. This command will not have any effect on the media info.

-----------------------

The problem you described initially pointed to the fact that the volume has a barcode but it will not be labeled at all. Now in the last sentence you say that "1 or 2 volumes are with label." - This does not seem to be logical.

 

[a060463xyz]

If some of your media will not be labeled there might be a problem with the barcode reader.
Maybe your barcodes are not fully compatible with your library or they are not placed correctly on the tape.
If you make an inventory and all barcodes are displayed correctly everything is ok with your barcodes.
Then you have to check for duplicate barcodes.
Networker will not label a type with an existing label.
Check your daemon.raw file after rendering it with nsr_render_log.

 

[605]

To a060463xyz:

Your concern about barcodes is correct in general. But did you notice that in this case, the barcode has been in fact been recognized?

Your statement "Networker will not label a type with an existing label." is definitively wrong. There are a lot of things to consider (depending on the current situation). However, if your statement would be right, the consequence would be that NW/the admin can not reuse a NW media.
And this is simply not true.

 

[denisfr]

Check to see if jukebox barcodes are the same than in networker database with this command :

sjirdtag 4.4.1

you'll see barcode as JB can read it

 

[a060463xyz]

to 605 :
Theres a difference between "relabel" and label a new Volume with an existing name :

relabeling works, in the second case networker issues a warning that there is already a volume in the media database with this name and asks you to choose a different name or to delete the old one.
I know there are some possibilities to generate identical names and networker is able to cope with it using the volumeid. But I dont want to confuse Pancevo1956 who seems to be not so familiar with networker.
I think some of us including me are not "native englisch speakers" so sometimes we might miss a bit. sorry

I have seen that the barcode is shown for slot4 but this can be due to some caching in nsrlcpd.
I f the barcode can not be read at the moment Networker wants to fetch the volume for labeling ...
But this shold generate a message in the daemon.raw so we have to check this file !

 

[Pancevo1956]

Instructor,

that is how it should be:

C:\Documents and Settings\Administrator>nsrjb

Jukebox ADIC@4.4.1: (Ready to accept commands)
slot volume pool barcode volume id recyclable
1: A00014 Bekap servera full A00014 1284045165 no
2: A00013 Bekap servera full A00013 453063638 no
3: A00012 Bekap servera inkr A00012 2035997205 no
4: A00011(R) Bekap servera full A00011 494321839 yes
5: A00010 Bekap servera full A00010 3348009328 no
6: A00009 Default A00009 4021459 no
7: A00008 Bekap servera full A00008 2532214991 no
8: A00007 Bekap servera full A00007 4124237071 no
9: A00006 Bekap servera full A00006 13815515 no
10: A00005 Bekap servera inkr A00005 1267268219 no
11: A00004 Bekap servera full A00004 2052774395 no
12: A00003 Bekap servera full A00003 469828135 no
13: A00002 Bekap servera inkr A00002 4228721222 no
14: A00001 Bekap servera inkr A00001 3663559846 no
15: A00015 Bekap servera full A00015 91047738 no
16:

etc


while it was error I have:
On my Gui barcode volume x has barcode y, whilest volume y
has barcode x.

or


C:\Documents and Settings\Administrator>nsrjb

Jukebox ADIC@4.4.1: (Ready to accept commands)
slot volume pool barcode volume id recyclable
1: A00014 Bekap servera full A00014 1284045165 no
2: A00013 Bekap servera full A00013 453063638 no
3: A00009 Default A00002 4021459 no
4: A00011 Bekap servera full A00011 494321839 no
5: A00010 Bekap servera full A00010 3348009328 no
6: -* A00009 -
7: A00008 Bekap servera full A00008 2532214991 no
8: A00007 Bekap servera full A00007 4124237071 no
9: A00006 Bekap servera full A00006 13815515 no
10: -* A00005 -
11: A00004 Bekap servera full A00004 2052774395 no
12: A00003 Bekap servera full A00003 469828135 no
13: A00009 Default A00002 4021459 no
14: -* A00001 -
15: A00015 Bekap servera full A00015 91047738 no
16:
17:
18:
19:
20:
21:
*not registered in the NetWorker media data base

 

[Pancevo1956]

That what is in log file:"...NetWorker media: (critical) Waiting for 1 writable volumes to backup pool 'Default' tape(s) on myserver.emaminus.local" which indicates that something went wrong, because it will wait indefinately for that particular volume.

When I perform the above commands plus on GUI select inventory then ticked "force load and verify label", the system seems to be OK and functinal. It finishes the daily backup, and everything seems to be Ok for 3 days. Then same story as it was at the beginning.
a060463xyz said "relabeling works, in the second case networker issues a warning that there is already a volume in the media database with this name and asks you to choose a different name or to delete the old one."
It did not ask me to chose different name or to delete old one.

denisfr:

inquire
...
scsidev@4.4.1:ADIC Scalar 24 310A|Autochanger (Jukebox), \\.\Changer0
.....

Then sjirdtag 4.4.1 gives:

"Tag Data for 4.4.1, Element Type DATA TRANSPORT:
Elem[001]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00009 >
Elem[002]: tag_val=0 pres_val=1 med_pres=0 med_side=0
Tag Data for 4.4.1, Element Type STORAGE:
Elem[001]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00014 >
Elem[002]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00013 >
Elem[003]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00012 >
Elem[004]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00011 >
Elem[005]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00010 >
Elem[006]: tag_val=0 pres_val=1 med_pres=0 med_side=0
Elem[007]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00008 >
Elem[008]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00007 >
Elem[009]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00006 >
Elem[010]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00005 >
Elem[011]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00004 >
Elem[012]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00003 >
Elem[013]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00002 >
Elem[014]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00001 >
Elem[015]: tag_val=1 pres_val=1 med_pres=1 med_side=0
VolumeTag=<A00015 >
Elem[016]: tag_val=0 pres_val=1 med_pres=0 med_side=0
Elem[017]: tag_val=0 pres_val=1 med_pres=0 med_side=0
Elem[018]: tag_val=0 pres_val=1 med_pres=0 med_side=0
Elem[019]: tag_val=0 pres_val=1 med_pres=0 med_side=0
Elem[020]: tag_val=0 pres_val=1 med_pres=0 med_side=0
Elem[021]: tag_val=0 pres_val=1 med_pres=0 med_side=0
Tag Data for 4.4.1, Element Type MEDIA TRANSPORT:
Elem[001]: tag_val=0 pres_val=1 med_pres=0 med_side=0
Tag Data for 4.4.1, Element Type IMPORT/EXPORT:
Elem[001]: tag_val=0 pres_val=1 inp_enab=1 exp_enab=1 access=1 full=0 im
p_exp=1"

That seems to be OK?

 

[605]

It looks weird. I would assume that there is a kind of problem with the media index which i can not really define. As such it is hard to propose a solution. However, if this is a new problem (if the system was running fine for some months) i think there is no software issue but a DB problem.

One potential solution could be to delete the media from the media DB and to rescan it later.
Another solution could be to recover the last well known instance of the media DB first.

Sorry, but i do not really know any better solution.

 

[a060463xyz]

One of my customers had a similiar error with an NEO2000 jukebox, the barcode reader unit had a defekt, after a replacement everything was ok.

As a work arround I would disable the barcode reader and label the media manually.

 

[Pancevo1956]

Another solution could be to recover the last well known instance of the media DB first. " Instructor how to do that?

a060463xyz you are right. The problem started after the hardware problem, where transiever went bad from FC switch to the jukebox.

 

[a060463xyz]

i doubt that a recover of your media db will solve the problem but you can do that with mmrecov.
I will describe this process later.

If your Problem occured because some Tapes are labeled with the wrong barcode label it is sufficient to delete them from the media db and relabel them accordingly.
But first you have to look for valid save sets and clone them. You need two tape drives for cloning.

1. Locate the wrong media
mminfo -avr "volume,barcode" -q "family=tape"
gives you a list of all your tape media.
Those where the volume name does not match the barcode will cause you problems.
Notate those volumes and create a list of the savesets of these volumes :

mminfo -r "ssid" -q "volume=badname1" > output.txt
now for every tape with not matching barcode label :
mminfo -r "ssid" -q "volume=badname2" >> output.txt

Now label a Tape manually for a clone Pool e.g "Default Clone" and run :

nsrclone -b "Default Clone" -S -f output.txt

after this delete all the wrongly labeled tapes from the media db. Now a relabelling with the barcode name should work.





Now Description of mmrecov process (be carefull) :

lacate a boostrap backup with a known good media db.
stop networker.
relocate your /nsr/mm directory.
restart networker, now you have an empty media db.
load your Tape with bootstrap backup in a tape
e.g nsrjb -ln -f \\.\Tape0 volumename

now start mmrecov

 

[605]

a060463xyz described the procedure to restore the media db correctly.

However, considering your last statement, it really seems to be a HW related problem.

 

[Pancevo1956]

Instructor, the problem with hardware was solved and it works. Now, the problem is with I guess media db. I did not have courage to run recover, but I did delete bad tapes and relabel them again with barcodes.

My backup seems to be working but up to the end it stops, because the mounted volume becomes 100% full. There was three empty volume and the system did not dismount full volume and replace it with empty one of the same pool. Why? Log reported"Media event cleared. waiting for 1 writable volumes to backup pool 'MYpool' on myownserver".

Instead, I have done it manually. I put an empty tape belonging to the same pool. Still, networker does not carry on with backing up the rest of clients, but generates message "Media Info: Suggest manually labeling a new writable volume for pool 'Mypool'. What I was done wrong?
Are that problem related to the possibly damaged media db?

 

[605]

This most likely has nothing to do with the media DB but with the jukebox configuration. Is Auto Media Management enabled? - if not, you must label the tapes manually.

 

[Pancevo1956]

No, it is not enabled! What if I enabled now and repeat all the procedure? How to label manually? I have barcode reader.

 

[605]

Outch. The major issue for AMM is to handle labeling processes automatically instead of labeling media in advance.
Of course you can enable it now. NW will then label a media automatically when needed.

You will find more details in the NW Admin Guide.