In a previous article (see https://www.data-protector.org/wordpress/2013/05/persistent-binding-hp-lto-tape-drives-windows/) I reported about “tape persistence” for Windows.
In general there is noch change to adopt this for Windows 2012 and the registry keys are the same. However, a requirement is to activate “Target Persistent Binding” for the Fibre Channel HBA. In case of a QLogic adapter you may use the tool “QConvergeConsole” (SANSurfer) for the configuration. For Emulex (HBAAnywhere) the configuration is nearly the same. After configuration and activation on the HBA, adding the registry keys and a final reboot, the tape drives and the changer can be used “persistent”. Comment: all tested with HP libraries/drives.
Example:
Registry:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hplto] "AutoRun"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Tape] "Persistence"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MChgr] "Persistence"=dword:00000001
Hallo Daniel,
wie kann ich denn identische persistent names für Changer und Drives auf zwei Servern erreichen, die dieselbe MSL6480 ansprechen? Ziel: Backup mit DP-Cell#1, RecoveryTest mit DP-Cell#2. Recovery.IOS mit Cell#1 erzeugt. EADR scheitert nach dem Boot von der Recovery.ISO beim Zugriff auf die TapeLib über Cell#2, weil die Changer-Devices verschieden sind.
Viele Grüße
Jochen
Hi Jochen,
gar nicht 🙂 oder zumindest ist mir das nicht bekannt, da Windows laut meines Wissens, die Namen beim ersten Mal festlegt.
Schaue Dir mal die Dokumentation zum EADR genauer an, es gibt die Möglichkeit für das EADR die devices entsprechend zu ändern.
Grüße
Daniel
I\’ll try to make this as brief, but inclusive as possible to get your opinion on what I should try for debugging. The problem is my back-up software (IBM TSM) does not register the first of my 6 FC LTO6 drives as LTO6, only generic tape. My environment is – MSL6480/w 6 HHFC LTO6 drives, HP(brocade) 8-8 FC switch, HP(Emulex) AJ763B HBA, DL380pG8 running TSM on Windows 2012R2. My starting point was that configuration, and TSM saw all drives as LTO6 with no problem. I did set the persistence flag at that point.
Now the problem – I added a D6000 with a P421 SAS controller and noticed after several reboots the tape drives were changing SCSI IDs (this could have been happening before and I did not notice). So I installed the Emulex OneCommand Manager and mapped the WWN to SCSI addresses. I also updated the driver for the FC card to 2.76.3.1. Now I have the problem that TSM sees the first tape drive as \\\’generictape\\\’. All the other functions are working normally. IBM support says must be hardware since it worked before the changes and HP support says it must be TSM since all addresses are correct through the OS. What do I look for, and who do I press for answers. (Side note, I thought I would be good in having all HP HW, but the fingers are still pointing 😉
H Chris,
unfortunately I do not have experience with TSM. From hardware point of view the drives should properly configured when looking into the Windows Device Manager. If this is the case, you need to continue with the IBM Support.
Best regards
Daniel