This error occurs when you initiate a label operation and select a specific device. It can mean one of the following:
1- Pool restrictions are preventing the tape from being labeled in the drive you want to use.
2- NetWorker is automatically attempting to label a tape but all devices for a particular pool are in use.
If all devices for a particular pool are in use, wait for one of the devices to become free so that the drive can be allocated for the label operation. Or Remove the device restriction on the Pool or enable the particular device on the Pool configuration.
It may be also that Networker thinks the drive is already loaded and therefore it cannot unload the device to perform an inventory operation on a volume.
Check the following:
1- All devices are enabled.
2- Run nsrjb -HHv -j (to check if you are able to run inventory or not )
1. All devices are enabled; the physical ones on the Legato serve and the rd=.... ones on the storage node.
2. nsrjb -HHv ends with success (the -j option is not accepted like that)
3. no tape is loaded in the drives; so no operation is going
4. The pool is defined so that tONLY he 4 rd=.... devices can be used; not the physical ones..... is this the way how legato makes a difference between a system being a Legato client or a storage node ?
You have not set the storage node field in the client configuration; the backup is trying to find a device on the backup server but since you have restricted the pool to use devices on the storage node only there are no valid devices available. Amend your client(s) to include the name of the storage node in the client's storage node field and it will work. You may find it is a good idea not to restrict the pool to those specific drives as it may cause confusion in the future!
You have the pool restrictions set up for the drives to the storage node and you say in the attachment but you do not mention if the NetWorker server has any drives in this selection. You highlight the volume you wish to label, but you do not mention if you also highlight a drive on the storage node also, if you do not do this NetWorker may attempt to use a drive on the NetWorker server as you have not explicitly stated which drive you want to use. As you are doing this through the GUI and most likely from the NetWorker server I guess you are trying to label a tape on one of the NetWorker server drives rather than the Storage node. You can remedy this by: -
1. Select the tape and any drive from the storage node via the GUI, then label.
2. From command line on the Storage node run nsrjb -s , at the prompt answer Y to label.
3. Change Read Hostname value of the jukebox resource to be the Storage node and attempt label as before via GUI.
1. I have removed and re-created the rd=.... devices using "configure drive". It did not change the failure of the label process
2. I have set persistant names= Y. but it did not chanhg the failure of the label process
3. In the pool restrictions, i have set that only the rd=... tape devices can be used for that pool; not the ones on the legato servers (\\.\Tape0)
4. I did not select which tapedrive to use in the label process. I let it to "automatic selection".
5. In the Storage node field of tab lobal (2 of 2), i have 2 lines:
s-olaf-zy1 (which is the name of the storage node)
nsrserverhost
6. I want to backup adrive which is local to the Storage node. The data is physically on a Lun on a SAN (NETAPP).
David, is this correct ?
In the TAB storage node, the Legato server only show the 4 physical drives while under the Storage node name I only see thr 4 rd=..... devices. Is this correct ?
OK - so automatic selection cannot work out we have pool restrictions for the devices as we are running the commands from GUI and trying to take action on the NetWorker server. Your client seems to be configured correctly, and to get this to work when you start the backup you can select/check/set Auto Media Management on the jukebox resource.
When you start the backup for the client NetWorker will know a volume needs to be labelled and do this automatically on the storage node (without having to pre-label the volumes manually).
Either do this or on the GUI highlight any drive on the storage node, then highlight the volume you want to label, right click and say label.
My previous post got corrupted when I gave you the commands - substitute the names in brackets for command line options: -
nsrjb -s (NetWorker server name) -b (pool name) -L -S (slot no of volume in jukebox) or -T (bar code of volume), then answer Y at prompt to label.
I have switched on "Auto Media Management" on the library and labeling a tape still fails with the same error. Labeling a tape should always be possible. No?
It sould be possible to do the labeling in the NMC on the storage node as well as on the NW server. I would think ?!
2. The error i get: "cannot allocate 1 devices needed for Label operation, number of available and usable devices=0, check pool restrictions or device availibility"
Did you try to label specifying the device to be used for it?
Are you able to mount tapes in any of those devices which are currently giving the error message? If not, what message/error do you get?
Do you have any specific label template for that pool?
Is it a new tape that you are trying to label or is it already from another pool? If it is from another pool that could be the reason why it won't mount the tape in that device as the other pool is not set to use those devices.
This happened to me and I discovered that some tapes were stuck in the tape drives which made it impossible for other tape operations to proceed. I logged into the tape library and moved the tapes to other slots and tried the operation that was failing with the same error.
Also with NW one can use the sji tools (that come with the NW installation of a NW SN) to talk to a library, for example sjirdtag to show the drives and the tape slots, showing what is located in each of them. You can also move around things or putting tapes into slots and drives and eject them back into a slot. Not handy to do this while NW is also operating, but more for problem solving to see if any scsi commands can even be run towards the library in question.
Bebo2k
544 Posts
0
March 27th, 2012 20:00
Hi Johan,
This error occurs when you initiate a label operation and select a specific device. It can mean one of the following:
1- Pool restrictions are preventing the tape from being labeled in the drive you want to use.
2- NetWorker is automatically attempting to label a tape but all devices for a particular pool are in use.
If all devices for a particular pool are in use, wait for one of the devices to become free so that the drive can be allocated for the label operation. Or Remove the device restriction on the Pool or enable the particular device on the Pool configuration.
It may be also that Networker thinks the drive is already loaded and therefore it cannot unload the device to perform an inventory operation on a volume.
Check the following:
1- All devices are enabled.
2- Run nsrjb -HHv -j (to check if you are able to run inventory or not )
Hope this helps you.
Thanks,
Ahmed Bahaa
CarlosRojas
1.7K Posts
0
March 27th, 2012 22:00
Hi Johan,
I think this could be a wrong configuration or even a device ID/ordering issue.
Based on the error message NW logically is trying to access a device that physically doesn't match with the information NW has in the RES folder.
Have you tried to manually remove those RD devices and re-created them again?
Do you have persistent naming in place for those devices?
Thank you.
Carlos.
Johans2
100 Posts
0
March 27th, 2012 22:00
Hi Ahmed,
1. All devices are enabled; the physical ones on the Legato serve and the rd=.... ones on the storage node.
2. nsrjb -HHv ends with success (the -j option is not accepted like that)
3. no tape is loaded in the drives; so no operation is going
4. The pool is defined so that tONLY he 4 rd=.... devices can be used; not the physical ones..... is this the way how legato makes a difference between a system being a Legato client or a storage node ?
Regards,
Johan
DavidHampson-rY
294 Posts
0
March 28th, 2012 01:00
Johan
You have not set the storage node field in the client configuration; the backup is trying to find a device on the backup server but since you have restricted the pool to use devices on the storage node only there are no valid devices available. Amend your client(s) to include the name of the storage node in the client's storage node field and it will work. You may find it is a good idea not to restrict the pool to those specific drives as it may cause confusion in the future!
Regards
David
masonb
445 Posts
0
March 28th, 2012 01:00
Johan,
You have the pool restrictions set up for the drives to the storage node and you say in the attachment but you do not mention if the NetWorker server has any drives in this selection. You highlight the volume you wish to label, but you do not mention if you also highlight a drive on the storage node also, if you do not do this NetWorker may attempt to use a drive on the NetWorker server as you have not explicitly stated which drive you want to use. As you are doing this through the GUI and most likely from the NetWorker server I guess you are trying to label a tape on one of the NetWorker server drives rather than the Storage node. You can remedy this by: -
1. Select the tape and any drive from the storage node via the GUI, then label.
2. From command line on the Storage node run nsrjb -s , at the prompt answer Y to label.
3. Change Read Hostname value of the jukebox resource to be the Storage node and attempt label as before via GUI.
Regards,
Bill Mason
Johans2
100 Posts
0
March 28th, 2012 01:00
Hi,
1. I have removed and re-created the rd=.... devices using "configure drive". It did not change the failure of the label process
2. I have set persistant names= Y. but it did not chanhg the failure of the label process
3. In the pool restrictions, i have set that only the rd=... tape devices can be used for that pool; not the ones on the legato servers (\\.\Tape0)
4. I did not select which tapedrive to use in the label process. I let it to "automatic selection".
5. In the Storage node field of tab lobal (2 of 2), i have 2 lines:
s-olaf-zy1 (which is the name of the storage node)
nsrserverhost
6. I want to backup adrive which is local to the Storage node. The data is physically on a Lun on a SAN (NETAPP).
David, is this correct ?
In the TAB storage node, the Legato server only show the 4 physical drives while under the Storage node name I only see thr 4 rd=..... devices. Is this correct ?
Still don't know where it goes wrong ....
Rgds,
Johan
masonb
445 Posts
0
March 28th, 2012 02:00
Johans,
OK - so automatic selection cannot work out we have pool restrictions for the devices as we are running the commands from GUI and trying to take action on the NetWorker server. Your client seems to be configured correctly, and to get this to work when you start the backup you can select/check/set Auto Media Management on the jukebox resource.
When you start the backup for the client NetWorker will know a volume needs to be labelled and do this automatically on the storage node (without having to pre-label the volumes manually).
Either do this or on the GUI highlight any drive on the storage node, then highlight the volume you want to label, right click and say label.
My previous post got corrupted when I gave you the commands - substitute the names in brackets for command line options: -
nsrjb -s (NetWorker server name) -b (pool name) -L -S (slot no of volume in jukebox) or -T (bar code of volume), then answer Y at prompt to label.
This should get your volume.
Regards,
Bill Mason
kciolek_emc
16 Posts
0
March 28th, 2012 03:00
What is the error you're seeing? Did you give access to the user for the remote storage node?
Under User Groups in NMC
User=administrator,host=remotestoragnode.
Sent from my iPhone
Ken Ciolek
Solutions Architect
EMCISA, EMCIE
Backup Recovery Systems (BRS)
EMC
2 Penn Plaza, 18th floor
New York, NY 10001
Mobile: 201-983-1537
Kenneth.CiolekJr@emc.com
Johans2
100 Posts
0
March 28th, 2012 03:00
William,
I have switched on "Auto Media Management" on the library and labeling a tape still fails with the same error. Labeling a tape should always be possible. No?
It sould be possible to do the labeling in the NMC on the storage node as well as on the NW server. I would think ?!
Rgds,
Johan
Johans2
100 Posts
0
March 28th, 2012 04:00
Hi,
1. The users system@storagenodename and administrator@storagenodename are in the administrators list of user groups
2. The error i get: "cannot allocate 1 devices needed for Label operation, number of available and usable devices=0, check pool restrictions or device availibility"
Rgds,
Johan
mridul_singh
57 Posts
0
April 3rd, 2012 05:00
Hi Johans,
Can you try the follwowing to lable the tape and provide the output:
nsrjb -vvv -L -b pool -f device -S slot#
where
pool=media pool
device=name if the device
slot#=slot from which tape is to be labelled
CarlosRojas
1.7K Posts
0
April 3rd, 2012 05:00
Hi Johans,
Did you try to label specifying the device to be used for it?
Are you able to mount tapes in any of those devices which are currently giving the error message? If not, what message/error do you get?
Do you have any specific label template for that pool?
Is it a new tape that you are trying to label or is it already from another pool? If it is from another pool that could be the reason why it won't mount the tape in that device as the other pool is not set to use those devices.
Thank you.
Carlos.
Johans2
100 Posts
0
April 3rd, 2012 05:00
Hi,
The problem is still not solved. Anyone who has an idea ?how to proceed ?
Johan
MS Robert
1 Message
0
December 11th, 2022 21:00
Hi all,
This happened to me and I discovered that some tapes were stuck in the tape drives which made it impossible for other tape operations to proceed. I logged into the tape library and moved the tapes to other slots and tried the operation that was failing with the same error.
Regards,
barry_beckers
393 Posts
0
December 19th, 2022 10:00
Also with NW one can use the sji tools (that come with the NW installation of a NW SN) to talk to a library, for example sjirdtag to show the drives and the tape slots, showing what is located in each of them. You can also move around things or putting tapes into slots and drives and eject them back into a slot. Not handy to do this while NW is also operating, but more for problem solving to see if any scsi commands can even be run towards the library in question.