the only place where i have done persistent binding was when i was connecting tape drives to a media manager server (HP Omniback) back in windows 2000. Right now i have windows 2003 connected to IBM 3592 tape drives (emulated EDL 4100) backing up to Networker. I've never had problems with tape drives getting re-numbered in Win2k3. Are you setting up persistent binding for Clariion LUNs ? If you are running PowerPath it should not be an issue even if device gets re-numbered.
This is for tapes for backups through Networker only.
Even I generally do it on OS through Windows registry keys only. This is an EMC install site where we get tapes makred FULL abruptly and a lot of SCSI resets so I was evaluating all components.
EMC says that they do hardware ps as that ensures that the names are persistent when it loads the card before the OS, OS get persistent names only. They have done it additionally on OS since IBM recommends that for IBM tape drives it should be done on OS through Windows registry.
I believe doing Os registry is better as that ensures that if HBA is replaced you do nto get into redoing things on the new HBA and what if it gives a new name.
In this issue, we have tweaked some timeouts and CDI settings and are not facing many SCSI resets now.
dynamox
9 Legend
•
20.4K Posts
0
February 10th, 2010 21:00
amediratta
2 Intern
•
2K Posts
0
February 10th, 2010 22:00
This is for tapes for backups through Networker only.
Even I generally do it on OS through Windows registry keys only. This is an EMC install site where we get tapes makred FULL abruptly and a lot of SCSI resets so I was evaluating all components.
EMC says that they do hardware ps as that ensures that the names are persistent when it loads the card before the OS, OS get persistent names only. They have done it additionally on OS since IBM recommends that for IBM tape drives it should be done on OS through Windows registry.
I believe doing Os registry is better as that ensures that if HBA is replaced you do nto get into redoing things on the new HBA and what if it gives a new name.
In this issue, we have tweaked some timeouts and CDI settings and are not facing many SCSI resets now.