Located it and just pasting it directly here again for you
Persistent binding is another issusing I became ohhhhh so familiar with when it comes to windows.
If you allow me to digress from the topic a hair here, I will give you some helpful information.
I believe from previous mentioned posts in this thread your drivers are the IBM ultrium? Are you using drivers supplied by library mfg for these drives or the default windows drivers? Believe it or not, this matters
Persistent binding is nice. It, sets the device to bind in the same address everytime. At least this is how it is supposed to work in theory. But sometimes hardware changes happen, and those addresses change and Networker doesn't know there new address.
Depends on how active of a SAN network you have. We are constantly building ours out larger and larger. (In 1 datacenter we backup on average 130tb a week.) So our SAN is ever growing.
So, to tackle this whole issue, and to save yourself some headache in the long wrong, set Persistent Naming as well. It's another setting that EMC doesn't talk about as much, but until it comes into play because of drive addresses changing. The nice thing about using Persistent naming is, whether the address of the unit changes.. (ex: ADIC@2.1.1) persistent naming doesn't care because it bases it on the WWN of the drive.
If you use the windows driver MS has an article on it that I had sitting around here somewhere but can't locate at this moment, but if you use your mfg drivers, they are done by IBM. And they have there own way to set persistent naming with them as well.
I HIGHLY recommend you set the persistent naming. Here's an example of how I did my IBM driver. (I have IBM Ultrium drives as well that Dell provides.) Persistent naming is all set in the registry.
(note: the WWNN_ names has the letters in lower case, if you export this key to install and set on several servers like I did, make sure the letters stay in lower case or the device name you set won't stick and it will set it to whatever it wants.)
The last part of the key will correspond to the WWN name of your tape drive. I manually modified mine to tape names like Tape1, Tape2, etc. Because the IBM driver when persistent naming is set, creates the key and gives it a default name of Tape4801011 or something like that. IBM's idea of being cute using the hexdecial equiv of the letters IBM. I had usses with it using that name, so I manually modified it.
In here you will have:
PersistentDeviceName REG_SZ Data Value is the device name you want to give the device like Tape5
Now if your using the native Windows driver, as mentioned before, there is a similar way via the registry, to set and make the persistent naming stick as well. Also I used the persistent naming, so that every server no matter what always came up with the same tape device name no matter which server it was on.
I used that, but with MS persistent binding and not one provided by IBM drivers. I also used CLI instead of NMC. Nice thing about MS approach is that you can have persistent binding and have and old format names (you can have it with IBM as well using some reg hacks which has been discussed recently). I suspect 7.4.x might lack support for NMC inq when using IBM drivers, but that's just a guess.
According to the NetWorker V7.5 Release Notes, support for persistent device naming in Windows was introduced in NetWorker V7.5. Prior to this, support for persistently-named devices was available only on Linux.
I recently, like last week. Posted in another thread exactly how you use the IBM driver to set persistent naming because of the exact problem you just mentioned.
Windows 2003 SP1 and later provide persistent names for tape devices.If the following Registry entry is created:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Tape\Persistence [DWORD value of 1]
and the system is rebooted, device file \\.\Tape0 becomes something like \\.\Tape2147483646, which is persistent.This was tested with an EMC Disk Library, and was found to work correctly with a sampling of emulated tape drives, including Quantum SDLT320, Sony SDX-700C and STK T10000A drives.It did not work correctly with the IBM LTO3 drives with the IBM tape driver 6.1.9.3; the longer persistent names were not created.
Tape Driver
The IBM Tape Device Drivers Installation and User’s Guide August 2007 describes persistent naming support available in the IBM Tape Device Driver on AIX, HP-UX and Solaris (Windows is not mentioned in the Guide, but is supported.More on this in the next paragraph).
AIX – provides a persistent logical name, but it is based on SCSI ID, LUN ID and HBA number
HP-UX – provides an additional set of device special files with a prefix of ‘s’ for the driver-configured tape devices (ex., /dev/rmt/S55…)
Solaris – by modifying IBMtape.conf to specify the order in which /dev/rmt files will be created, based on SCSI target and LUN
Add a value in the registry called PersistentNaming and assign it a value 1 at: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k3
reboot
This provides device files of the form \\.\Tape4801105 that do persist when other devices are added or removed.NetWorker V7.5 can use these devices (NetWorker bug LGTsc17131 addressed and fixed an earlier problem that prevented use of these persistently-named device special files).
HacknDos1
1 Rookie
•
66 Posts
0
October 5th, 2009 10:00
Persistent binding is another issusing I became ohhhhh so familiar with when it comes to windows.
If you allow me to digress from the topic a hair here, I will give you some helpful information.
I believe from previous mentioned posts in this thread your drivers are the IBM ultrium? Are you using drivers supplied by library mfg for these drives or the default windows drivers? Believe it or not, this matters
Persistent binding is nice. It, sets the device to bind in the same address everytime. At least this is how it is supposed to work in theory. But sometimes hardware changes happen, and those addresses change and Networker doesn't know there new address.
Depends on how active of a SAN network you have. We are constantly building ours out larger and larger. (In 1 datacenter we backup on average 130tb a week.) So our SAN is ever growing.
So, to tackle this whole issue, and to save yourself some headache in the long wrong, set Persistent Naming as well. It's another setting that EMC doesn't talk about as much, but until it comes into play because of drive addresses changing. The nice thing about using Persistent naming is, whether the address of the unit changes.. (ex: ADIC@2.1.1) persistent naming doesn't care because it bases it on the WWN of the drive.
If you use the windows driver MS has an article on it that I had sitting around here somewhere but can't locate at this moment, but if you use your mfg drivers, they are done by IBM. And they have there own way to set persistent naming with them as well.
I HIGHLY recommend you set the persistent naming. Here's an example of how I did my IBM driver. (I have IBM Ultrium drives as well that Dell provides.) Persistent naming is all set in the registry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3
In here you create:
PersistentNaming REG_DWORD set value to 1
Reboot machine after setting this and then the following keys will be created.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3\WWNN_500308c09b
dc3004
(note: the WWNN_ names has the letters in lower case, if you export this key to install and set on several servers like I did, make sure the letters stay in lower case or the device name you set won't stick and it will set it to whatever it wants.)
The last part of the key will correspond to the WWN name of your tape drive. I manually modified mine to tape names like Tape1, Tape2, etc. Because the IBM driver when persistent naming is set, creates the key and gives it a default name of Tape4801011 or something like that. IBM's idea of being cute using the hexdecial equiv of the letters IBM. I had usses with it using that name, so I manually modified it.
In here you will have:
PersistentDeviceName
REG_SZ
Data Value is the device name you want to give the device like Tape5
Now if your using the native Windows driver, as mentioned before, there is a similar way via the registry, to set and make the persistent naming stick as well. Also I used the persistent naming, so that every server no matter what always came up with the same tape device name no matter which server it was on.
Hope you find this useful.
Paul
ble1
4 Operator
•
14.4K Posts
0
October 5th, 2009 05:00
tlemons1
1 Rookie
•
87 Posts
0
October 5th, 2009 07:00
According to the NetWorker V7.5 Release Notes, support for persistent device naming in Windows was introduced in NetWorker V7.5. Prior to this, support for persistently-named devices was available only on Linux.
tl
HacknDos1
1 Rookie
•
66 Posts
0
October 5th, 2009 10:00
I recently, like last week. Posted in another thread exactly how you use the IBM driver to set persistent naming because of the exact problem you just mentioned.
I will locate it and post link for ya...
cf13
7 Posts
0
October 6th, 2009 00:00
Simple changing device names, solved the problem.
psoni1
41 Posts
0
February 11th, 2010 07:00
I have the same problem and we are using IBM drivers ibmtp2k3.sys
[1] Is it necessary to first remove tape devices from device manager ?
[2] Do I have to reconfigure jukebox in NMC after applying this fix ? Will devices be scanned as //./Tape instead of //./Tape0 //./Tape1 etc ?
ble1
4 Operator
•
14.4K Posts
0
February 16th, 2010 05:00
tlemons1
1 Rookie
•
87 Posts
1
February 16th, 2010 07:00
Windows Driver
[Microsoft Knowledgebase article 873337]
Windows 2003 SP1 and later provide persistent names for tape devices. If the following Registry entry is created:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Tape\Persistence [DWORD value of 1]
and the system is rebooted, device file \\.\Tape0 becomes something like \\.\Tape2147483646, which is persistent. This was tested with an EMC Disk Library, and was found to work correctly with a sampling of emulated tape drives, including Quantum SDLT320, Sony SDX-700C and STK T10000A drives. It did not work correctly with the IBM LTO3 drives with the IBM tape driver 6.1.9.3; the longer persistent names were not created.
Tape Driver
The IBM Tape Device Drivers Installation and User’s Guide August 2007 describes persistent naming support available in the IBM Tape Device Driver on AIX, HP-UX and Solaris (Windows is not mentioned in the Guide, but is supported. More on this in the next paragraph).
In addition, persistent binding support in the IBM Tape Device Driver for Windows is described in the readme file for the driver (ftp://ftp.software.ibm.com/storage/devdrvr/Windows/Win2003/Latest/IBMTape.W200x.Readme.txt). This support began in v6.1.6.2. To use this feature:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k3
This provides device files of the form \\.\Tape4801105 that do persist when other devices are added or removed. NetWorker V7.5 can use these devices (NetWorker bug LGTsc17131 addressed and fixed an earlier problem that prevented use of these persistently-named device special files).
psoni1
41 Posts
0
February 17th, 2010 08:00
Thanks for the update.
Do I need to choose "Persistent Names = Yes" option while scanning for the devices in NMC after applying this fix ?
tlemons1
1 Rookie
•
87 Posts
1
May 20th, 2010 12:00
Yep.