SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
Persistent Binding Issue (again)
Author Message
Post Persistent Binding Issue (again) 
We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not control the tape
drives and Networker was confused as to which tape drive was which (the
persistent binding thorn in our sides). We opened cases with both EMC
and Dell (server/library vendor). The tape drivers even affected how
long Windows took to come up, or specifically the Networker Server
service was hanging on coming up which Windows was waiting on to finish
coming fully up. Turns out our resource database had also somehow gotten
corrupted. EMC was extremely helpful in getting us going again since it
was really more of a Networker issue than a Dell issue.. They had us
install the IBM tape drivers instead of the Dell drivers (I feel that
IBM (not DELL) is best qualified to supply the drivers since they are
IBM branded drives). EMC pointed us to a solution (esg92364), but it
appears to be out of date since IBM updated their driver package to now
use two different installation programs...

I was wondering if anyone on the list could shed some light on which
registry file we should apply following the installation of the IBM
tape/changer drivers... Below are the contents of the 4 registry files
that come in the ZIP package downloaded from IBM, the readme.txt file
that comes with it does not make any mention of the reg files or which
one does what. The KB solution (esg92364) should also be updated to
specify which install program to run (install_exclusive.exe or
install_nonexclusive.exe) that now comes in the ZIP package from IBM
with the tape drivers.

Regards,

Paul
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
Sorry, forgot to paste in the reg files on initial post...

We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not control the tape
drives and Networker was confused as to which tape drive was which (the
persistent binding thorn in our sides). We opened cases with both EMC
and Dell (server/library vendor). The tape drivers even affected how
long Windows took to come up, or specifically the Networker Server
service was hanging on coming up which Windows was waiting on to finish
coming fully up. Turns out our resource database had also somehow gotten
corrupted. EMC was extremely helpful in getting us going again since it
was really more of a Networker issue than a Dell issue.. They had us
install the IBM tape drivers instead of the Dell drivers (I feel that
IBM (not DELL) is best qualified to supply the drivers since they are
IBM branded drives). EMC pointed us to a solution (esg92364), but it
appears to be out of date since IBM updated their driver package to now
use two different installation programs...

I was wondering if anyone on the list could shed some light on which
registry file we should apply following the installation of the IBM
tape/changer drivers... Below are the contents of the 4 registry files
that come in the ZIP package downloaded from IBM, the readme.txt file
that comes with it does not make any mention of the reg files or which
one does what. The KB solution (esg92364) should also be updated to
specify which install program to run (install_exclusive.exe or
install_nonexclusive.exe) that now comes in the ZIP package from IBM
with the tape drivers.

Regards,

Paul
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \

------------------------------------------------------------------------
------------
File: DisableCPF.reg
-----------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcgbs2k3]
"FailoverDisabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcg2k3]
"FailoverDisabled"=dword:00000001


------------------------------------------------------------------
File: EnableCPF.reg
----------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcgbs2k3]
"FailoverDisabled"=-

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcg2k3]
"FailoverDisabled"=-


------------------------------------------------------------------
File: DisableDPF.reg
-------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3]
"FailoverDisabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3]
"FailoverDisabled"=dword:00000001

------------------------------------------------------------------
File: EnableDPF.reg
-----------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3]
"FailoverDisabled"=-

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3]
"FailoverDisabled"=-
----------------------------------------------------------------


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
Hello,
Can you give us more info
Which version of LTO and servers are you on.
What was the download url
is the patch you list on IBM site ?
I checked th IBM site and looked at couple of downloads available, i.e V
6.1.84 ( Height), from previous knowledge, you can just run installers
( i did not see two installe.exe here) and install will take care of
driver install, including registry, previous readme on the drivers files
indicated how to use persistent binding feature available with this
drivers. ( install drivers from cmd line, not device manager--so i was
told by ibm)
The problem you see with server taking long etc, has also happed to us, as
long as you can verify that the drivers have loaded and you use
appropriate method of persistent binding, you should be good.
If you have IBM support or your Lib vendor should be able to help you out
clarifying the registry etc
HTH



"Goslin, Paul" <pgoslin < at > CINCOM.COM>
Sent by: EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>
06/26/2008 10:18 AM
Please respond to
EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>; Please respond
to
"Goslin, Paul" <pgoslin < at > CINCOM.COM>


To
NETWORKER < at > LISTSERV.TEMPLE.EDU
cc

Subject
[Networker] Persistent Binding Issue (again)






Sorry, forgot to paste in the reg files on initial post...

We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not control the tape
drives and Networker was confused as to which tape drive was which (the
persistent binding thorn in our sides). We opened cases with both EMC
and Dell (server/library vendor). The tape drivers even affected how
long Windows took to come up, or specifically the Networker Server
service was hanging on coming up which Windows was waiting on to finish
coming fully up. Turns out our resource database had also somehow gotten
corrupted. EMC was extremely helpful in getting us going again since it
was really more of a Networker issue than a Dell issue.. They had us
install the IBM tape drivers instead of the Dell drivers (I feel that
IBM (not DELL) is best qualified to supply the drivers since they are
IBM branded drives). EMC pointed us to a solution (esg92364), but it
appears to be out of date since IBM updated their driver package to now
use two different installation programs...

I was wondering if anyone on the list could shed some light on which
registry file we should apply following the installation of the IBM
tape/changer drivers... Below are the contents of the 4 registry files
that come in the ZIP package downloaded from IBM, the readme.txt file
that comes with it does not make any mention of the reg files or which
one does what. The KB solution (esg92364) should also be updated to
specify which install program to run (install_exclusive.exe or
install_nonexclusive.exe) that now comes in the ZIP package from IBM
with the tape drivers.

Regards,

Paul
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \

------------------------------------------------------------------------
------------
File: DisableCPF.reg
-----------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcgbs2k3]
"FailoverDisabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcg2k3]
"FailoverDisabled"=dword:00000001


------------------------------------------------------------------
File: EnableCPF.reg
----------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcgbs2k3]
"FailoverDisabled"=-

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcg2k3]
"FailoverDisabled"=-


------------------------------------------------------------------
File: DisableDPF.reg
-------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3]
"FailoverDisabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3]
"FailoverDisabled"=dword:00000001

------------------------------------------------------------------
File: EnableDPF.reg
-----------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3]
"FailoverDisabled"=-

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3]
"FailoverDisabled"=-
----------------------------------------------------------------


"signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER




via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
Version of Tape drives is LTO 2
Server is 7.2.2 running on a quad processor Dell Power Edge 2650 running
Windows Server 2003 - SP2.

The download URL was posted on this list a few weeks ago... It's

ftp://ftp.software.ibm.com/storage/devdrvr/Windows/Win2003/Latest/

The filename I downloaded was IBMTape.x86_6193.zip (828KB).

It contains two install programs: install_exclusive.exe and
install_nonexclusive.exe (but NO INSTALL.EXE ! ~) like I said earlier,
the readme file makes no mention of the reg files.

The library is also from Dell (PV136T, a re-branded ADIC), we do not
have IBM support. EMC spec'd everything, the software, hardware, tape
drives, etc... Then they sent consultants to install / set it up,
problem is they did not leave us any documentation on how to
re-implement the persistent binding they put in place, which worked
flawlessly reboot after reboot. EMC should require their consultants to
document what they do.... Dell's solution is to use Dell Drivers (which
have not worked as well as the IBM drivers have in our past experience).


-----Original Message-----
From: Fazil.Saiyed < at > anixter.com [mailto:Fazil.Saiyed < at > anixter.com]
Sent: Thursday, June 26, 2008 12:04 PM
To: EMC NetWorker discussion; Goslin, Paul
Cc: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] Persistent Binding Issue (again)


Hello,
Can you give us more info
Which version of LTO and servers are you on.
What was the download url
is the patch you list on IBM site ?
I checked th IBM site and looked at couple of downloads
available, i.e V 6.1.84 ( Height), from previous knowledge,
you can just run installers ( i did not see two installe.exe
here) and install will take care of driver install, including
registry, previous readme on the drivers files indicated how
to use persistent binding feature available with this
drivers. ( install drivers from cmd line, not device
manager--so i was told by ibm) The problem you see with
server taking long etc, has also happed to us, as long as you
can verify that the drivers have loaded and you use
appropriate method of persistent binding, you should be good.
If you have IBM support or your Lib vendor should be able to
help you out clarifying the registry etc HTH



"Goslin, Paul" <pgoslin < at > CINCOM.COM>
Sent by: EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>

06/26/2008 10:18 AM
Please respond to
EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>;
Please respond to "Goslin, Paul" <pgoslin < at > CINCOM.COM>

To
NETWORKER < at > LISTSERV.TEMPLE.EDU
cc
Subject
[Networker] Persistent Binding Issue (again)






Sorry, forgot to paste in the reg files on initial post...

We had an incident yesterday following the reboot of our
Networker Server with the monthly MS patches where we could
not control the tape drives and Networker was confused as to
which tape drive was which (the persistent binding thorn in
our sides). We opened cases with both EMC and Dell
(server/library vendor). The tape drivers even affected how
long Windows took to come up, or specifically the Networker
Server service was hanging on coming up which Windows was
waiting on to finish coming fully up. Turns out our resource
database had also somehow gotten corrupted. EMC was extremely
helpful in getting us going again since it was really more of
a Networker issue than a Dell issue.. They had us install the
IBM tape drivers instead of the Dell drivers (I feel that IBM
(not DELL) is best qualified to supply the drivers since they
are IBM branded drives). EMC pointed us to a solution
(esg92364), but it appears to be out of date since IBM
updated their driver package to now use two different
installation programs...

I was wondering if anyone on the list could shed some light
on which registry file we should apply following the
installation of the IBM tape/changer drivers... Below are the
contents of the 4 registry files that come in the ZIP package
downloaded from IBM, the readme.txt file that comes with it
does not make any mention of the reg files or which one does
what. The KB solution (esg92364) should also be updated to
specify which install program to run (install_exclusive.exe or
install_nonexclusive.exe) that now comes in the ZIP package
from IBM with the tape drivers.

Regards,

Paul
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \

--------------------------------------------------------------
----------
------------
File: DisableCPF.reg
-----------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcgbs2k3]
"FailoverDisabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcg2k3]
"FailoverDisabled"=dword:00000001


------------------------------------------------------------------
File: EnableCPF.reg
----------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcgbs2k3]
"FailoverDisabled"=-

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcg2k3]
"FailoverDisabled"=-


------------------------------------------------------------------
File: DisableDPF.reg
-------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3]
"FailoverDisabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3]
"FailoverDisabled"=dword:00000001

------------------------------------------------------------------
File: EnableDPF.reg
-----------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3]
"FailoverDisabled"=-

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3]
"FailoverDisabled"=-
----------------------------------------------------------------

To sign off this list, send email to
listserv < at > listserv.temple.edu and type "signoff networker" in
the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any
problems with this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS
at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER






via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
Hello,
If you are talking about persistent binding on ADIC, you can easily check
that by logging into the Adic Gui, let me know if you need help there.
I found the following reference to the reg file.
Adic even lets you save your config to a file or internally to a Memory
for later recovery ( that is if any one saved it to begin with)

"A potential loss of data may occur if you are using V6.1.5.4 or V6.1.4.8
of the device driver

with Data Path Failover enabled. This bug happens very rarely, but if
you are using either of

those versions, we recommend that you double-click DisableDPF.reg from
the driver install package

and reboot your system, or update your driver to the latest supported
level on the FTP site.
HTH


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On
Behalf Of Goslin, Paul
Sent: Thursday, June 26, 2008 5:19 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Persistent Binding Issue (again)

...
We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not control the tape
drives and Networker was confused as to which tape drive was which (the
persistent binding thorn in our sides).
...

Hi Paul,

Did you try Microsoft's hotfix for this problem?
KB #873337 (http://support.microsoft.com/kb/873337/) is probably just
what
you need.
There's also a Win2K version, and they're not supported (so: at your own
risk).

Best of luck, regards,

Alexander


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
Yes - we've tried that in the past and it apparently does not work...

-----Original Message-----
From: Alexander Kaasjager [mailto:A.Kaasjager < at > dataman.nl]
Sent: Friday, June 27, 2008 6:25 AM
To: EMC NetWorker discussion; Goslin, Paul
Subject: RE: [Networker] Persistent Binding Issue (again)

-----Original Message-----
From: EMC NetWorker discussion
[mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of Goslin, Paul
Sent: Thursday, June 26, 2008 5:19 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Persistent Binding Issue (again)

...
We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not
control the tape
drives and Networker was confused as to which tape drive was
which (the
persistent binding thorn in our sides).
...

Hi Paul,

Did you try Microsoft's hotfix for this problem?
KB #873337 (http://support.microsoft.com/kb/873337/) is
probably just what you need.
There's also a Win2K version, and they're not supported (so:
at your own risk).

Best of luck, regards,

Alexander



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
...
We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not
control the tape
drives and Networker was confused as to which tape drive was
which (the
persistent binding thorn in our sides).
...


Did you try Microsoft's hotfix for this problem?
KB #873337 (http://support.microsoft.com/kb/873337/) is

Yes - we've tried that in the past and it apparently does not work...


Including the registry setting? It is somewhat below in the article,
I've
seen people read over it - unfortunately, that setting is exactly what
should solve it.
And is the Removable Storage service disabled?

Best of luck,

Alex


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
If you take a look at the Readme.txt file on IBM's ftp site (use the /Latest, not WHQL):

ftp://ftp.software.ibm.com/storage/devdrvr/Windows/Win2003/Latest/

4) Version 6.1.6.2 and later versions of the device driver have an option for enforcing file names for
tape drives that will persist across reboots of the operating system. For example, if your tape drive
has the name \\.\tape3 and the persistent naming option is used, then \\.\tape3 will be reserved for
use by that device after an operating system reboot. To take advantage of this feature, place a DWORD
value in the registry called PersistentNaming and assign it a value 1 at:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k3

and reboot your system.


This isn't "Persistent binding" because the issues in Windows aren't related to FC binding. Even if devices are correctly setup to persistent bind, they will still have reordering issues under Windows. The issue is the Window Plug & Play driver will dynamically assign storage devices names starting with \\.\Tape0, etc.. Once you modify this registry setting the devices will show up as \\.\Tape<SerialNumber> which will persist.

There is a similar fix on technet for non-ibm drivers. Again, it doesn't have anything to do with FC binding (the reason for confusion is that under unix persistent binding and persistent naming are the same, but not in windows)

For windows 2003:
http://support.microsoft.com/kb/873337

For Windows 2000:
http://support.microsoft.com/kb/889330/


----
Matthew Huff | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
www.otaotr.com | Phone: 914-460-4039
aim: matthewbhuff | Fax: 914-460-4139

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of Alexander Kaasjager
Sent: Friday, June 27, 2008 10:29 AM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] Persistent Binding Issue (again)

...
We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not
control the tape
drives and Networker was confused as to which tape drive was
which (the
persistent binding thorn in our sides).
...


Did you try Microsoft's hotfix for this problem?
KB #873337 (http://support.microsoft.com/kb/873337/) is

Yes - we've tried that in the past and it apparently does not work...


Including the registry setting? It is somewhat below in the article,
I've
seen people read over it - unfortunately, that setting is exactly what
should solve it.
And is the Removable Storage service disabled?

Best of luck,

Alex


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
Hello,
Along with steps to do the Persistent binding with the registry values and
utilizing IBM drivers, take a look at Persistent binding on the FC HBA
parameter, this should also be employed to avoid re-sequiencing.
Thanks



Matthew Huff <mhuff < at > OX.COM>
Sent by: EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>
06/27/2008 09:57 AM
Please respond to
EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>; Please respond
to
Matthew Huff <mhuff < at > OX.COM>


To
NETWORKER < at > LISTSERV.TEMPLE.EDU
cc

Subject
Re: [Networker] Persistent Binding Issue (again)






If you take a look at the Readme.txt file on IBM's ftp site (use the
/Latest, not WHQL):

ftp://ftp.software.ibm.com/storage/devdrvr/Windows/Win2003/Latest/

4) Version 6.1.6.2 and later versions of the device driver have an option
for enforcing file names for
tape drives that will persist across reboots of the operating system.
For example, if your tape drive
has the name \\.\tape3 and the persistent naming option is used, then
\\.\tape3 will be reserved for
use by that device after an operating system reboot. To take advantage
of this feature, place a DWORD
value in the registry called PersistentNaming and assign it a value 1
at:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k3

and reboot your system.


This isn't "Persistent binding" because the issues in Windows aren't
related to FC binding. Even if devices are correctly setup to persistent
bind, they will still have reordering issues under Windows. The issue is
the Window Plug & Play driver will dynamically assign storage devices
names starting with \\.\Tape0, etc.. Once you modify this registry setting
the devices will show up as \\.\Tape<SerialNumber> which will persist.

There is a similar fix on technet for non-ibm drivers. Again, it doesn't
have anything to do with FC binding (the reason for confusion is that
under unix persistent binding and persistent naming are the same, but not
in windows)

For windows 2003:
http://support.microsoft.com/kb/873337

For Windows 2000:
http://support.microsoft.com/kb/889330/


----
Matthew Huff | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
www.otaotr.com | Phone: 914-460-4039
aim: matthewbhuff | Fax: 914-460-4139

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On
Behalf Of Alexander Kaasjager
Sent: Friday, June 27, 2008 10:29 AM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] Persistent Binding Issue (again)

...
We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not
control the tape
drives and Networker was confused as to which tape drive was
which (the
persistent binding thorn in our sides).
...


Did you try Microsoft's hotfix for this problem?
KB #873337 (http://support.microsoft.com/kb/873337/) is

Yes - we've tried that in the past and it apparently does not work...


Including the registry setting? It is somewhat below in the article,
I've
seen people read over it - unfortunately, that setting is exactly what
should solve it.
And is the Removable Storage service disabled?

Best of luck,

Alex


"signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


"signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER




via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Persistent Binding Issue (again) 
Hi Paul

Unless you've purchased (from IBM) the license/key that allows the
multipathing feature of the IBM tape drive, you'll need to execute:

DisableCPF.reg
DisableDPF.reg

Hope this helps.
tl
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On
Behalf Of Goslin, Paul
Sent: Thursday, June 26, 2008 11:19 AM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Persistent Binding Issue (again)

Sorry, forgot to paste in the reg files on initial post...

We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not control the tape
drives and Networker was confused as to which tape drive was which (the
persistent binding thorn in our sides). We opened cases with both EMC
and Dell (server/library vendor). The tape drivers even affected how
long Windows took to come up, or specifically the Networker Server
service was hanging on coming up which Windows was waiting on to finish
coming fully up. Turns out our resource database had also somehow gotten
corrupted. EMC was extremely helpful in getting us going again since it
was really more of a Networker issue than a Dell issue.. They had us
install the IBM tape drivers instead of the Dell drivers (I feel that
IBM (not DELL) is best qualified to supply the drivers since they are
IBM branded drives). EMC pointed us to a solution (esg92364), but it
appears to be out of date since IBM updated their driver package to now
use two different installation programs...

I was wondering if anyone on the list could shed some light on which
registry file we should apply following the installation of the IBM
tape/changer drivers... Below are the contents of the 4 registry files
that come in the ZIP package downloaded from IBM, the readme.txt file
that comes with it does not make any mention of the reg files or which
one does what. The KB solution (esg92364) should also be updated to
specify which install program to run (install_exclusive.exe or
install_nonexclusive.exe) that now comes in the ZIP package from IBM
with the tape drivers.

Regards,

Paul
--
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \

------------------------------------------------------------------------
------------
File: DisableCPF.reg
-----------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcgbs2k3]
"FailoverDisabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcg2k3]
"FailoverDisabled"=dword:00000001


------------------------------------------------------------------
File: EnableCPF.reg
----------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcgbs2k3]
"FailoverDisabled"=-

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmcg2k3]
"FailoverDisabled"=-


------------------------------------------------------------------
File: DisableDPF.reg
-------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3]
"FailoverDisabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3]
"FailoverDisabled"=dword:00000001

------------------------------------------------------------------
File: EnableDPF.reg
-----------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3]
"FailoverDisabled"=-

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3]
"FailoverDisabled"=-
----------------------------------------------------------------


type "signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post Article 873337 
We had an incident yesterday following the reboot of our Networker
Server with the monthly MS patches where we could not control the tape
drives and Networker was confused as to which tape drive was which (the
persistent binding thorn in our sides). We opened cases with both EMC
and Dell (server/library vendor). The tape drivers even affected how
long Windows took to come up, or specifically the Networker Server
service was hanging on coming up which Windows was waiting on to finish
coming fully up. Turns out our resource database had also somehow gotten corrupted.

I have been reading this thread and I see these symptoms quite a bit with Windows servers.

My question is....if you set Persistent Binding at the HBA level WHY would you also need to change the registry setting in windows?

This has been an ongoing battle over what should/shoudn't be done when it comes to windows and Persistent bindings....

View user's profile Send private message
Post Persistent Binding Issue (again) 
Because persistent binding means absolutely nothing in Windows in regards to tapes

Windows has a higher level api called Windows Plug and Play Driver that assigns device names like //./Tape0. It has nothing to do with fiber channel or other lower level drivers, so no matter what you do at the FC or SCSI level, the PnP driver will assign a arbitrary name.

To force those names to be consistent (which is important with tape drives), you need to set registry settings. Once that is done, the Plug and Play driver will create names like //./.Tape6455534 based on your SerialNumber of the tape drive.



----
Matthew Huff | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
http://www.ox.com | Phone: 914-460-4039
aim: matthewbhuff | Fax: 914-460-4139


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU]
On Behalf Of kicktothehead
Sent: Friday, June 26, 2009 10:09 AM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Persistent Binding Issue (again)

I have been reading this thread and I see these symptoms quite a bit
with Windows servers.

My question is....if you set Persistent Binding at the HBA level WHY
would you also need to change the registry setting in windows?

This has been an ongoing battle over what should/shoudn't be done when
it comes to windows and Persistent bindings....

+----------------------------------------------------------------------
|This was sent by bbosader < at > verizon.net via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------


type "signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.edu if you have any problems with
this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post persistent binding issue (again) 
I usually term persistent binding in windows as "tending to order
tape drive device links based on scsi bus/device order". With an
emphasis on "tending". In most cases, you'll get OS names that follow
the persistent binding--even more so when you have multiple devices
behind a single scsi id (like with a bridge or VTL), but there is no guarantee.
I midly disagree with Matthew, since the device order isn't
*entirely* arbitrary (scsi id 0 tends to get Tape0, scsi id 1 tends
to get Tape1--if for no other reason than PnP discovers devices in
bus/scsi order), but if you want perfectly reliable, its not.
And if you need to replace a tape drive, and your changer doesn't
forge WWNN and serial number, then it'll find the new device in a
different order, and that order will almost certainly change after a reboot.

There is a very quick cutover to using the windows consistent device
names (which they also term "persistent") or the IBM version of this
for LTO drives. Unless there is a reason you can't use it (version of
NetWorker that is too old to support that feature--I think 7.4.2 was
the first rev), I'd suggest you do.

--Dave

Date: Sat, 27 Jun 2009 12:54:08 -0400
From: Matthew Huff <mhuff < at > OX.COM>
Subject: Re: Persistent Binding Issue (again)

Because persistent binding means absolutely nothing in Windows in
regards to tapes

Windows has a higher level api called Windows Plug and Play Driver
that assigns device names like //./Tape0. It has nothing to do with
fiber channel or other lower level drivers, so no matter what you do
at the FC or SCSI level, the PnP driver will assign a arbitrary name.

To force those names to be consistent (which is important with tape
drives), you need to set registry settings. Once that is done, the
Plug and Play driver will create names like //./.Tape6455534 based on
your SerialNumber of the tape drive.




===================================
David Gold
Sr. Technical Consultant
Cambridge Computer Services, Inc.
Artists in Data Storage
Tel: 781-250-3000
Tel (Direct): 781-250-3260
Fax: 781-250-3360
dave < at > cambridgecomputer.com
www.cambridgecomputer.com

===================================
----------------------------------------------------------------------------
*Any ideas, suggestion or comments are mine alone, and are not of my company*


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB