Can anyone help with this error

Mark cheers for the reply mate.

Thenew SN i implement is 2k8X64 so RSM is disabled by default.

I have also disabled the media changer as the doco you sent.

I went and re-visited my other SN and confirmed RSM was disabled (win2k3) i have also disabled the medium changer on this SN as well.

If there is anything else you can suggest my ears are wide open.

ha, and thanks for the quck responce.

Awesome stuff mate.

NetWorker servers and storage nodes on Windows 2003 must have RSM disabled for the tape drives and the robotic arm of the autochanger or alternately disable the RSM service.

To disable the Removable Storage service:

1. From Control Panel > Administrative Tools select Services.
2. Right-click on Removable Storage and select Properties.
3. Select Disabled.
4. If the service status is Started, stop the service.
5. Click Ok.

If it is not possible to disable the RSM service, disable RSM on the tape drives and robotic arm.

To disable RSM for the robotic arm:

1. Right-click My Computer select Manage.
2. Select Manage RSM Libraries.
3. Right-click the tape drive and select Properties.
4. Click to uncheck Enable library.
5. Click Ok.

To disable RSM for tape devices:

1. Right-click My Computer select Manage. Select Device Manager in System Tools.
2. Select Changers.
3. Right-click the changer and select Properties.
4. Select disable from the drop down list for each device.
5. Click Ok.

If this does not resolve the issue, let us know.

disabling the Autochanger in 2k3 Device Manager is most likelly not the best option. The autochanger needs to send the serial number to announce it's part of the library. If you disable this then all the drives can only be configured as stand alone.

Do you have persistent binding set on your drives as from the error it looks like the drive paths are changing...

Scott

Here is a procedure I used last time I configured this which was about 2 years back so I expect there is a more up-to-date version of the driver to use - we were on 7.4.3 at the time:

This procedure assumes zoning has already been actioned.

0. We would not need to do this normally, but as we have installed the driver in exclusive mode we will first be required to uninstall the current driver:

       a. My Computer, right click, Manage.

       b. Device Manager>Tape drives

       c. right click on each entry and choose Uninstall

       d. Still in Device Manager right click on server name and choose Scan for hardware changes

       e. Drives will come up with under Other Devices with a question mark over the icon.  Right click on each device, Properties, Update driver.

       f. Choose not to use Windows update, install from specific location, Don't search I will choose, Have Disk, browse to directory in 1 and select ibmtpbs.inf, Open then finish.

       g. Drive will now be listed under Tape Devices.

1. If another device driver is installed then we can install IBM driver 6.1.8.9 (Non exclusive) from the install executable - this is in the directory C:\temp\IBMTape.x86_6189_LTO2-4 Tape Drive_Cert and the correct executable to run is install_nonexclusive.exe - just double click it.  (Verify in Device Manager that the tape drives now have driver version 6.1.8.9)

2. Start>Run>regedit to start the Registry Editor.    Update registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3,    add DWORD   "PersistentNaming" value 1    (note that this DWORD varies with earlier versions of the driver but for the current driver 6.1.8.9 this is the correct entry)

3. Reboot server

4. Run inquire will give drive paths in SCSI path order

5. Open regedit again and verify we have string values (REG_SZ) under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3\Enum called 0, 1, 2... etc corresponding to the number of drives.  Next find the newly created registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3 (note this is a different key to the one just checked) which correspond to the drives which will look like:

       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3\SERNUM_00000000000000000000001187192881

- the last 10 digits correspond to the serial number of the drive.  Under each of these keys update the string value (REG_SZ) called PersistentDeviceName by right clicking and choosing modify and amend this value to Tape0, Tape1... etc sequentially in the order the serial numbers appear in the inquire output, firstly for the ADIC drives, then continue the sequence for the EDL drives (indicated in the inquire output as Virtual Devices)

6. Reboot

7. Run inquire to verify that the drives now have a value Tape0, Tape1 etc etc.

We did receive a document at the time from EMC support which had a totally different procedure for configuring persistent binding that didn't work!  This one did.

I agree with David, you need to have persistent binding set in  Windows environment.    It is a pain, especially when you have more than 1 storage node.    The device name will change from \\.\TapeX format to \\.\TapeXXXXXXXX  (ours is something like \\.\Tape4801101.)

The easiest way to verify this, is to run the inquire command, when the system is running properly.  The next time you see the error, run it again, and see if the numbers line up.   If not, then you need to set persistent binding.

Hello,

I have a Data domain and two LTO, Networker 8.2

Can anyone tell me how to enable persistent binding and naming in windows server 2012R2?

Do we need to enable it from Windows registry and HBA software level ?how to do it for the both cases.

Is it necessary to first remove tape devices from device manager ?

Do I have to reconfigure jukebox in NMC after enabling persistent binding or before doing it ?

Regards.

Please open a new conversation for your persistent binding question.  This is because your question is not related to this original jukebox issue from 2011

Thank you.