HP 3000 Enterprise Virtual Array - Manual (Page 35)

Storage System Description
35 Enterprise Virtual Array 3000 User Guide
Table 3 describes the failback default behavior and settings allowed for each
operating system. The table indicates when Secure Path is used in conjunction
with the operating system
.
Path B -
Failover/Failback
At initial presentation The units are brought online to
Controller B.
On dual boot or controller
resynch
If cache data for a LUN exists on a
particular controller, the unit will be
brought online there. Otherwise, the units
are brought online to Controller B.
On controller failover All LUNs are brought online to the
surviving controller.
On controller failback All LUNs remain on the surviving
controller. After controller restoration, the
units that are online to Controller A and set
to Path B are brought online to
Controller B. This is a one time occurrence.
If the host then moves the LUN using SCSI
commands, the LUN will remain where
moved.
Table 2: Failback Preference Settings (Continued)
Setting Point in Time Behavior
Table 3: Failback Settings by Operating System
Operating System Default Behavior Settings Allowed
Windows
®
Secure Path Autoback done by the host No Preference, Path A/B -
Failover Only.
Sun UNIX ® Secure Path Autoback done by the host No Preference, Path A/B -
Failover Only.
HP Secure Path Autoback done by the host No Preference, Path A/B -
Failover Only.
IBM AIX Secure Path Autoback done by the host No Preference, Path A/B -
Failover Only.
Tru64 UNIX Host follows the unit All settings allowed.
Recommended setting: Path
A/B - Failover/Failback.
VMS (7.3 and below) Attempts to move the unit to
the first path discovered
No Preference, Path A/B -
Failover Only.
VMS (7.3-1 and greater) Host follows the unit All settings allowed.
Recommended setting: Path
A/B - Failover/Failback.