If you are using NetWorker for this library you should really be doing all the functions via the Software. You can withdraw/deposit tapes via NetWorker from command line or GUI. This then means that NetWorker is aware of the changes and updates its information for the volumes going in or out.
On Windows it is usual to disable the Auto-changer under devices as this stops windows locking the robot (unless you have configured a RSM jukebox). NetWorker send SCSI commands directly to the robot on the address therefore it does not have to be enabled. If it is not enabled it will not show within Inquire - so please be aware of this.
Try doing the procedure via NetWorker - if backups etc are working without issue then you should be able to achieve what you need without using the Control Panel on the library.
CDI is really for the tape drives and their error reporting, it is not important for the robotics.
It does sound from your description that Windows is holding onto the arm for some reason as when you disable it within Device Manager you can perform the operations OK (as even when NetWorker is not running it's still locked). There is no adverse effect to leaving this disabled (apart from the inquire command will not report the arm) within the environment for "normal running". Just remember if you think there is an issue with the robotic communication you will have to enable to get it reported in inquire or use sji commands (like sjirdtag b.t.l ) to confirm communication is still good.
You do not mention how the library is connected (via direct SCSI cable or Fibre) the only other thing it could be if Fibre connected is something else is zoned to see the robot, but this would make it unlikely that disabling the changer on the host you are using the Library from would have any effect.
So disable within Device Manager and you should be good.
ethor1
2 Posts
0
June 17th, 2010 00:00
Thanks for the reply guys.
@William. Does it mean that I should leave the autoloader in disabled state?
That is what I have been doing:
1) Once backup completes, unmount tape from drive
2) Once tape is unloaded, withdraw/deposit the media
3) Once this is done, go to the control panel of the library and eject the magazine/IE slot
Step 3 is where the problem occurs (intermittently). Control Panel says the host is busy.
I've tried disabling all networker services but it still complains host is busy.
Only way to 'release' this is to disable the library in device manager. Then only will I be able to eject the magazine.
Sometimes it works. Sometimes it doesn't.
I've tried this with CDI enabled but the problem is still there.
hari_prakash
22 Posts
0
June 17th, 2010 00:00
Hi Edward,
Have you tried with Windows native drivers as well?
HTH.
masonb
445 Posts
1
June 17th, 2010 00:00
Edward,
If you are using NetWorker for this library you should really be doing all the functions via the Software. You can withdraw/deposit tapes via NetWorker from command line or GUI. This then means that NetWorker is aware of the changes and updates its information for the volumes going in or out.
On Windows it is usual to disable the Auto-changer under devices as this stops windows locking the robot (unless you have configured a RSM jukebox). NetWorker send SCSI commands directly to the robot on the address therefore it does not have to be enabled. If it is not enabled it will not show within Inquire - so please be aware of this.
Try doing the procedure via NetWorker - if backups etc are working without issue then you should be able to achieve what you need without using the Control Panel on the library.
Regards,
Bill Mason
masonb
445 Posts
0
June 17th, 2010 01:00
Edward,
CDI is really for the tape drives and their error reporting, it is not important for the robotics.
It does sound from your description that Windows is holding onto the arm for some reason as when you disable it within Device Manager you can perform the operations OK (as even when NetWorker is not running it's still locked). There is no adverse effect to leaving this disabled (apart from the inquire command will not report the arm) within the environment for "normal running". Just remember if you think there is an issue with the robotic communication you will have to enable to get it reported in inquire or use sji commands (like sjirdtag b.t.l ) to confirm communication is still good.
You do not mention how the library is connected (via direct SCSI cable or Fibre) the only other thing it could be if Fibre connected is something else is zoned to see the robot, but this would make it unlikely that disabling the changer on the host you are using the Library from would have any effect.
So disable within Device Manager and you should be good.
Regards,
Bill Mason