HP StoreEver High Availability Path Failover Linux Driver Release Notes Version 1.0.5-1 (5697-3326, June 2014)

ManualsBrandsHP ManualsStorageHP StoreEver MSL6480 Scalable Base Module

HP StoreEver High Availability Path Failover

Linux Driver Release Notes

Version: 1.0.5-1

HP Part Number: 5697-3326

Published: June 2014

Edition: 1

Summary of content (5 pages)

PAGE 1
HP StoreEver High Availability Path Failover Linux Driver Release Notes Version: 1.0.
PAGE 2
© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft® and Windows® are U.S.
PAGE 3
Description These release notes describe the features and other release information for the Linux Availability Path Failover driver. High Availability Path Failover uses capabilities in the LTO-6 tape drives and the libraries in which they are installed, combined with kernel mode drivers running on a host system to provide path failover when multiple paths are available to a tape drive or to a library.
PAGE 4
• Drivers to be used with HP LTO-6 FC drives and the ESL G3 and MSL6480 tape libraries in which they are installed. • Drivers create entries in the system log when they are first started and whenever any exceptional conditions occur. • Diagnostic information is available via the /sys file system. See the HP StoreEver Tape Libraries Failover User Guide for more information. Fixes N/A Issues and workarounds This section identifies important issues and workarounds for Advanced Path Failover.
PAGE 5
same time that a reservation or prevent media removal setting is in the process of being changed or if all paths are lost to an active control path drive in a multi-initiator environment and one host does not recover from the path failure it is possible to have a reservation or prevention setting that is no longer associated with a host. Note that this is not unique to the APF driver and is most likely to occur in traditional multi-path configurations.