HPE Storage Users Group

According to the HP 3PAR inform OS 2.3.1 Configuration Matrix (http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02634714/c02634714.pdf), you are supposed to apply the following hotfix to servers running Windows 2008 and R2: http://support.microsoft.com/kb/2406705

When installed you end up with mpio.sys version 6.1.7601.21720. However on servers where hotfix KB2522766 has been applied through Windows Update, you are unable to apply this update. Checking the mpio.sys driver you'll find that it has version: 6.1.7601.21731. (http://support.microsoft.com/kb/2522766)

The question is what to do, as we still experience the error described:
Example: I have 4 serveres running Windows clustering with 3PAR attached drives and D2D 4324 Tape devices. If we reboot the D2D, it will cause the clustering to fail and the server will loose connection to the drives.

Anyone, any ideas??

Generally the newer MPIO driver from Windows update is preferred/supersedes the older one in the matrix.

It is a best practice to keep your "tape" devices separated from your disk devices.... meaning on separate HBA ports. When you shutdown the VTL it's not only removing a LUN from your HBA but also a FC target, and I am guessing the errors/resets caused by this are disrupting the scsi bus/hba port enough to cause a failover.

Google for: TAPE and DISK on same HBA