HP StorageWorks Continuous Access EVA Administrator Guide (T3687-96043, December 2005)

11. Add the hosts for the system with new hardware.
12. Create the non-D R group virtual disks.
13. Present all non-DR group virtual disks to their hosts.
14. Perform one of the following:
a. Ifthesourcearrayconfiguration was captu red with the SSSU, executeConfigName_step2 on
thesourcearray. ConfigName is a user-assigned name given to the SSSU script at the time of
cre ation. DR groups are re-created with the SSSU if they were performing as the source when
the configuration was captured. This step may take some time to complete.
b. If you are not using an SSSU script for recovery, re-create all DR groups on the source array ,
using the information recorded in the Table 6. Specify the repaired or replaced array for
the destination.
15. If, in t he previous step, you used the SSSU to re-create DR groups on the source array, you must
manually re-create any additional DR groups that had their source on the failed hardware. This is
necessary because the SSSU will not re-create the DR groups on the source array if they performed
as the destination when the configuration was captured. After you perform this step, all DR groups
reside on the source array.
16. If desired, set all affected DR groups from normal mode to failsafe-enabled mode.
17. Perform one of the following:
a. If the original array configuration was captured with the SSSU, execute Config N am e _step3
on the new hardware. ConfigName is a user-assigned name given to the SSSU script at the
time of creation.
b. If you are not using an SSSU script for recovery, present the destination virtual disks on the array
with new hardware to the appropriate hosts using the information you recorded in the Table 6.
18. If, in the previous step, you used the SSSU to p resent destination virtual disks to their hosts, manually
present any additional virtual disks that originally had their sources on the failed hardware to their
hosts on the array with new hardware. This is necessary because the SSSU will not present virtual
disks whose destinations were the current source array when the configuration was captured. After
performing this step, all destination virtual disks are presented to hosts.
19. If the repaired or replaced array is to be the source for the DR groups, fail over any D R groups
using the procedure Planned failover.
20. Issue operating system commands to restart host I/O on the source array. For specifics, see
Resuming I/O af ter failover.
21. (Optional) Set the DR groups to the desired Home setting.
R
ecovering from a disk group hardware failure
Disk group hardware failure occurs when a disk group loses more disks than a given Vraid type can
recover from, a loss of redundancy that results in an inoperative disk group. This condition can occur
from the loss of one disk for Vraid0 or, less likely, of two disks for Vraid1 and Vraid5. In each case, the
hardware must b e replaced, and the disk group data rebuilt. (For a complete description of disk group
failures, see the EVA best practices white p aper .) This section describes the symptoms and recovery of
an inoperative disk group at either the source or d estination array.
If an array only has one disk group, and that disk group fails, the array becomes inoperative. Reinitialize
the array to manage it (see Return operations to new hardware).
Ifyouhavemultiplediskgroupsandonefails,followtheprocedureDisk group hardware failure on the
source array or Disk group hardwa re failure on the destination array.
Failed disk group h ardware indicators
If disk group hardware fails, the replication manager displays the following:
HP StorageWorks Continuous Access EVA administrator guide
41