443 Posts

November 17th, 2008 19:00

Please note that a tape once labelled in Networker will always have the same label name. This will not change no matter how many times you relabel the tape. If you are having problems in relabelling a tape with the same name, remove the entry for the tape label from the list of volumes and then try to relabel.

455 Posts

November 17th, 2008 01:00

Check in your list of volumes if this name exists. If it does then either delete it if its not required or give this volume a new name.

You ca try a library reset.

181 Posts

November 17th, 2008 03:00

The Volume Means the Tape Bar code no , If i tried in another tape also the same problem occurs , And just let me know how to change he Volume Name .



Rajesh

2 Intern

 • 

2K Posts

November 17th, 2008 04:00

If you are using BarCode labelling, you do not need to change Volume Name. It is the same as barcode label. If this volume is in Volumes list, delete it from there.

181 Posts

November 17th, 2008 19:00

No , The thing is If we clicked in the devices , In the right pane you will getiing list of the tapes which has been labeld or unlabaled rite . In that till day before yesterday i have labeled a new tape and took backup and unforunately from yesterday onwards i am getting this error while labeling , All the settings is correct and i used the same settings before it was working fine . Can you justify what is the problem .


Rajesh

4 Operator

 • 

14.4K Posts

November 20th, 2008 00:00

To see why this has happened to you one needs to look in daemon.log for this tape and check if anything wrong has happened (I/O error, verification failure when tape was filled, etc). Without banging your head too much, simply delete the volume and label it again.

181 Posts

November 20th, 2008 19:00

Thnaks for your Help .

181 Posts

November 20th, 2008 19:00

Good Morning, I had all these stuff , But still it was showing the problem and the problem got reolved , What happened is I Just reinstall the Networker . After reinsall the networker , and had made some some changes in the drive . I want to know that Whether this problem is in the Networker or in the library . Why because now in most of the networker the problem is coming , As i reinstall the networker the problem is resolve , How can i predict this to be stable if this kind of problem occurs .


Rajesh

2 Intern

 • 

2K Posts

November 20th, 2008 22:00

Reinstall NW is not the solution especially if you retained the original res folder, than the resources were the same. When I experience such issues, I do make some changes to the jukebvox and drive prperties and several such issues get rectified. Ex.:

for drives, CDI not used. Uncheck element_tags etc.

4 Operator

 • 

14.4K Posts

November 20th, 2008 23:00

I agree - reinstalling NW was not solution here.

9 Posts

November 22nd, 2008 18:00

May i know is this problem has solved or not? if not, what is your NW version?
and do you has doing upgraded NW ?
No Events found!

Top