Hardware manual

Group Administration Data recovery
13–13
2. On the secondary group:
a. Promote the replica set to a recovery volume. Make sure
you keep the ability to demote the recovery
volume, in case you decide to cancel the role switch. See Promoting an inbound replica set to a recovery
volume.
Users can now access volume data by connecting to the rec
overy volume. See Connecting initiators to
iSCSI targets on page 8
-7.
b. Replicate the recovery volume to the primary group. See Replicating a recovery volume to the prim
ary
group.
c. Make the inbound replica set promotion permanent. See Making an inbound replica set promotion
permanent.
3. On the primary group, convert the failback replica set
to
an inbound replica set. See Converting a failback
replica set to an inbound replica set.
The partner role switch is complete.
Making an inbound replica set promotion permanent
After promoting an inbound replica set to a recovery volume, you can make the promotion permanent, resulting in
a new standard volume, template volume, or thin clone volume. You might need to perform this task if the original
volume is destroyed or if you are switching roles in a replication configuration.
Note: After making an inbound replica set promotion permane
nt, you can no longer demote the volume to the
original inbound replica set.
Restriction: Before you
can make a template replica set promotion permanent, you must permanently promote all
the attached thin clone replica sets.
1. Click
Volumes, then expand Volumes, then select the recovery volume, then click Make promote
permanent
.
2. In the Convert Recovery Volume – Vo
lume Settings dialog box:
• Enter a new volume name, up to 63 alphanumeric characters (including periods, dashes, and colons). A
volume name must be unique in a group.
• Enter an optional description.
• Select the storage pool.
Then, click
Next.
3. In the Convert Recovery Volume – iSCSI Access dialog box, specify:
• Access control credentials for the recovery volume. Specify a CHA
P user name, IP address, or iSCSI
initiator name. See About iSCSI target access controls on page 8
-1.
• Permission, either read-only or read-write.
• Whether to allow initiators with different iSCSI qualified
names (IQNs)
access to the volume. See
Multi-host access to targets on page 8
-6.