Unsolved
This post is more than 5 years old
2 Intern
•
132 Posts
0
5860
January 3rd, 2010 21:00
Error Message: Duplicate volume name `000020L4'. Select a new name or remove the original volume.;
Hi guys,
I would like to change the tape/volume pool, so I did label the tape/volume, the system shows an error which is duplicate volume name while the there is no duplicate I tired with many tapes/volumes some of them got labeled while some showed the same error.
This the error I got:
cancellation: none;
completion code: ;
error message: \
Duplicate volume name `000020L4'. Select a new name or remove the original volume.;
last update: 1262580496;
messages: ;
name: YE-SAH-JB01;
operation instance: 101;
operation source: GUI jb op;
progress: failed;
prompt response: ;
prompt: ;
start time: 1262580358;
status: failed
Please help.
I am using networker 7.4.4 that running on windows 2003 SP2


Imranullah
2 Posts
0
January 4th, 2010 01:00
masonb
445 Posts
0
January 4th, 2010 02:00
There are a few situations which can cause this type of error message within NetWorker. If you are 100% that your drive ordering is correct now, it could be it was wrong inthe past when you originally labelled these tapes and got the bar code from one written on the inside of a different tape. These usually only effect 2 or 3 tape volumes which are all linked. If the data on all 2 or 3 tapes is still required (i.e. not recyclable) then just mark them as manual recycle and wait until all 2 or 3 are recyclable. Then delete them from the Media Database (and Client file indexes when prompted) and relabel manually into a pool you need.
To check if you definitley have this use the following: -
If within the jukebox output the bar code is different to the volume label? if so most likely historical Ordering issue. You should be able to link the volumes affected by looking for each bar code and seeing what the volume label is.
Within the daemon.log file search for "Expected" you should see reports which say Expected volume xxxyyy got aaabbb" or NULL (but there can be other reasons for NULL being reported).
Only delete the volume if you are sure you do not want any data written on it!
If you are 100% sure the drive ordering is correct tyry running nsrjb -HEvv for the jukebox followed by nsrjb -IEvv and see what the output then shows if you have lots of tapes reprting as unlabelled. Then try and mount one tape volume in the drive and see if it mounts correctly. Ensure the barcode and volume label match. If you can do the mount successfully for a tape you wish to label then attempt the label operation and see what you get - for NetWorker to label the tape it must be recyclable and then you will be prompted to overwrite the label - this should work.
Regards,
Bill
Hakan_Engman
57 Posts
0
January 4th, 2010 06:00
Hi,
Just wanted to add to the list of solutions. I in some rare situvations when this occures you need to erase the volume based on the
volume id instead of the "barcode" name. ( Used when you try to delete from the GUI.)
If you issue a mminfo -avr "volume,volumeid" and find the tape that you want to remove/recycle.
then erase that volume_id in the mediadatabase with
nsrmm -d -V
I know that this process has changed, but I'm totally sure if it's 7.5 version that changes the procedure, but you end up with
duplicate tapes when:
1: You have a tape, both physical and a database record in the mediadb.
2: You or NetWorker issue a "recycle volume" for that tape.
3. The label process failes for some reason(drive error, loss of SAN conn) then the physical tape has a volume id written on the media that is the old one.
and the lable process has entered a new barcod/volume id record in the mediadatabase.
Next time you or networker tries to use the tape, you get a mis-match between the physical tape content and the mm db. And you get the "duplicate error."
Check if you have issues in the logs with tapedrives.
Cheers,
Håkan
DarkPanda
12 Posts
0
January 25th, 2010 21:00
Hi Guys,
I am encountering the same problem too. I am using NW7.4.4. as well.
Is this a bug?
If we do a manual recycle and relabel, will the symptoms come back again?
coganb
736 Posts
0
January 26th, 2010 01:00
Hi,
The most important thing to consider is your drive ordering. If this is not correct, then this problem will keep coming back again. This is not a bug, it's that the OS is presenting the drives to Networker in a different order from before.
-Bobby