Owner's manual

Setting Point in time
Behavior
At initial presentation The units are brought online to Controller
B.
On dual boot or controller resynch
If cache data fo
raLUNexistsona
particular co
ntroller, the unit will be
brought onlin
ethere. Otherwise,the
units are brou
ght online to Controller B.
On controller failover
All LUNs are brought online to the
surviving controller.
Path B - Failover/
Failback
On controller failback
AllLUNsremainonthesurviving
controller. After controller restoration,
the units that are online to Controller
A and set to Path B are brought online
toControllerB.Thisisaonetime
occurrence. If the host then moves the
LUN using SCSI commands, the LUN will
remain where moved.
Table 4 Failback Settings by Operatin g System
Operating system
Default behavior
Settings supported
Windows®
Auto failback done by the host No Preference, Path A/B - Failover
Only.
Sun Sola
ris®
Auto failback done by the host No Preference, Path A/B - Failover
Only.
HP-UX
Autoback done by the host
No Preference, Path A /B - Failover
Only.
IBM AIX
Auto failback done by the host No Preference, Path A/B - Failover
Only.
Tru64 UNIX
Host follows the unit
All set
tings allowed.
Recomm
ended setting: Path
A/B - Failover/Failback.
VMS (7.3-1 and greater)
Host follows the unit
All settings allowed.
Recommended setting: Pa th
A/B - Failover/Failback.
Linux
Auto failback done by the host No PreferencePath A/B - Failover
Only
Nove
ll NetWare
Auto failback done by the host No PreferencePath A/B - Failover
Only
Changing virtual disk failover/failback settin g
Changing the failover/failback setting of a virtual disk may impact which controller presents the disk.
Table 5 identifies the presentation behavior that results when the failover/failback setting for a virtual
dis
k is changed.
NOTE:
If the new setting causes the presentation of the virtual disk to move to a new controller, any snapshots
or snapclones associated with the virtual disk will also be moved.
4000/6000/8000 Enterprise Virtual Array user guide
35