User's Manual

A Known issues and workarounds
Path failover issues are observed on Windows Server 2012
Symptom: On Windows Server 2012, path failover issues are observed, even after installing the
advanced path failover driver and rebooting the server twice. The installation file used was:
HP_StoreEver_High_Availability_Path_Failover_Driver_Windows_2012_2012_R2_Z7550-01470.exe
Workaround: The installer for the initial release of the advanced path failover driver has a defect
that results in an incorrect installation on Windows Server 2012. The defect in the installer has
been fixed.
Download and install the updated driver package.
1. Uninstall the advanced failover drivers.
a. Select Start→Programs→Control Panel.
b. Select the Advanced Failover Drivers entry and then click Uninstall/Change.
c. Follow the provided prompts to complete the driver removal.
2. Reboot the server.
3. Download the latest Advanced Failover Drivers for Windows Server 2012 from the HP website.
a. Navigate to http://www.hp.com/support/storage.
b. Click Tape Storage.
c. Click Enterprise Class Tape Libraries (for ESL G3) or Tape Libraries (for MSL6480).
d. Click HP StoreEver ESL G3 Tape Libraries (for ESL G3) or HP StoreEver MSL6480 Tape
Library (for MSL6480).
e. In the Download options tab, click Drivers, software & firmware.
f. For the ESL G3, select your product.
g. In the Operating System drop down, select OS Independent.
h. Click Driver — Storage Tape.
i. Click Obtain software for the High Availability Failover Driver for your operating system.
j. Click Receive for Free.
k. Follow the prompts to download the driver package.
4. Double-click the installer for your operating system to install the Tape Upper Bus Storage Filter
driver.
5. Restart when requested.
6. After the system restarts, the installer will continue installing the Tape Multi-Path Intermediate
Class driver.
The current implementation is failure tolerant only and not intended
to fix unstable SAN environments.
Symptom: Device connectivity lost after several closely spaced path failures. If several closely
spaced path failures occur on all of the available paths the operating system might not detect a
path change and report that to the driver causing a loss of connectivity with the device.
Workaround: Locate and repair the SAN faults. The driver is not always able to recover if both
the active path and the standby path have faults.
The current implementation of the Windows driver uses the first path
to a device that was successfully found.
Symptom: The device driver does not connect to the preferred path after a system boot or device
rescan.
Workaround: The driver prefers the first path in the hardware scan performed by the operating
system. If a particular path is preferred, load the HBA for that path in the lower numbered hardware
location.
69