Table 1 1 Failback preference behavior (continued)
Setting
Table 12 (page 38)
ALUA-compliant multipath software is running with each operating system. Recommended settings
may vary depending on your configuration or environment.
Table 12 Failback settings by operating system
Operating system
HP-UX
IBM AIX
Linux
OpenVMS
Sun Solaris
Tru64 UNIX
VMware
Windows
38
EVA6400/8400 operation
Point in time
On dual boot or controller resynch
On controller failover
On controller failback
describes the failback default behavior and supported settings when
Default behavior
Host follows the unit
Host follows the unit
Host follows the unit
Host follows the unit
Host follows the unit
Host follows the unit
Host follows the unit
Failback performed on the host
Behavior
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.
All LUNs are brought online to the surviving
controller.
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.
Supported settings
1
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
1
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
1
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
(recommended)
1
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
(recommended)
1
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback
No Preference
Path A/B – Failover Only
Path A/B – Failover/Failback