W2K3 change order of Tape Device

[svenix71]

Hi,
We have a problem with our Legato 7.3.2 Jumbo installation over a Windows 2003 Standard Edition SP1.
For some inexplicable reason, it seems that W2K3 changes the order of how it sees the tape devices, and of course, then the Legato it became to work wrong, as the libray was defined with other tape device order (using jbconfig).
There is a TID:

http://support.microsoft.com/?scid=kb;en-us;873337&x=10&y=15

in Microsoft Support, but yet we had applied we still have the same problem..
Has anyone information about this??

 

[Rif123]

I assume the order only changes when you reboot? Try to set up persistant bindings on your HBA if you are using that. You should find information about this in your HBA vendor's manual.

 

[605]

Thanks for sharing this info - the only solution i knew so far was to add "persistent bindings" in a SAN.

It would be easier if you could boot Windows without auto-reconfiguration.

 

[svenix71]

No, it changes order when it is working, not after a rebboting. Our HBA are Emulex LP1050DC and Emulex A8003A (HP model FC2242SR), we have HBA Anywhere utility but we are not sure if it has the option of Persistent binding..

 

[605]

To setup persistent bindings in HBAnyware, go to the controller's "Target Mapping" tab.

 

[wallace88]

The Microsoft article that you provided also tells you to add the Persistence registry entry after you install the MS hotfix... this is how you set up persistent binding in Windows.

Regardless, once windows is booted and the devices are discovered and assign a drive path, then there is no reason for the drive order to change. if this is what you are seeing, then this suggests that the devices are disappearing and reappearing n the SAN while Windows is still running. Check the SAN logs and the Windows event logs to search for evidence to this assumption. If so then there is some issue at the SAN level that needs to be addressed.

 

[svenix71]

Thanks for your recommendations,

We have implemented Persitent Binding in our HBA cards, hope this will solve the problem.
wallace88, as we already work with w2k3 sp1 , we didnt't install the hotfix but we added the Persistence binding configuration in the registry. After this, we had the issue again one more time...