User guide

Table 10 Failback preference behavior (continued)
BehaviorPoint in timeSetting
If cache data for a LUN exists on a particular
controller, the unit will be brought online there.
On dual boot or controller resynch
Otherwise, the units are brought online to
Controller B.
All LUNs are brought online to the surviving
controller.
On controller failover
All LUNs remain on the surviving controller.
After controller restoration, the units that are
On controller failback
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 11 (page 38) describes the failback default behavior and supported settings when
ALUA-compliant multipath software is running with each operating system. Recommended settings
may vary depending on your configuration or environment.
Table 11 Failback settings by operating system
Supported settingsDefault behaviorOperating system
No Preference
Path A/B – Failover Only
Host follows the unit
1
HP-UX
Path A/B – Failover/Failback
No Preference
Path A/B – Failover Only
Host follows the unit
1
IBM AIX
Path A/B – Failover/Failback
No Preference
Path A/B – Failover Only
Host follows the unit
1
Linux
Path A/B – Failover/Failback
No PreferenceHost follows the unitOpenVMS
Path A/B – Failover Only
Path A/B – Failover/Failback
(recommended)
No PreferenceHost follows the unit
1
Sun Solaris
Path A/B – Failover Only
Path A/B – Failover/Failback
No PreferenceHost follows the unitTru64 UNIX
Path A/B – Failover Only
Path A/B – Failover/Failback
(recommended)
No Preference
Path A/B – Failover Only
Host follows the unit
1
VMware
Path A/B – Failover/Failback
No PreferenceFailback performed on the hostWindows
Path A/B – Failover Only
Path A/B – Failover/Failback
38 EVA6400/8400 operation