Testing Failover At The Recovery Site; Actual Failover At The Recovery Site - HP StoreVirtual 4000 Deployment Manual

IMPORTANT:
multiple volumes on the same remote Management Group.
Volumes ignored by the HP P4000 SRA
Remote snapshots within the same HP P4000 SAN Solution management group are ignored. These
snapshots are not considered disaster recovery copies since they are usually created to clone a
volume in the HP P4000 SAN Solution, and copies that reside on the same SAN are not useful for
disaster recovery.

Testing failover at the recovery site

SRM performs test failovers at the recovery site when requested. When test failovers are requested,
the HP P4000 SRA will perform the steps listed.
1. Select the replicated volumes.
2. Identify the latest complete Remote Copy snapshot.
3. Delete any temporary writable space on that snapshot to ensure an unedited snapshot is
presented to ESX servers.
Use this snapshot to create a smart clone.
4. Configure authentication for ESX servers to directly mount smart clones.
5. When testing stops, to conserve space on the SAN, delete the temporary writable space that
was used during the test.

Actual failover at the recovery site

In the event of a disaster, the SRM can perform actual failover when requested to. When actual
failover is requested the HP P4000 SRA will perform the steps listed.
1. Select the replicated volumes.
2. Identify and remove any incomplete remote copies that are in progress and present the most
recent completed Remote Copy as a primary volume.
3. Convert remote volumes into primary volumes and configure authentication for ESX servers to
mount them.
If an actual failover does not run completely for any reason, the failover can be called many times
to try to complete the run. If, for example, only one volume failed to restore and that was due to
a normal snapshot being present, the snapshot could be manually deleted and the failover be
requested again.
Reprotect at the recovery site
After a failover, the SRM can perform reprotect when requested to. When actual reprotect is
requested the HP P4000 SRA will perform the steps listed.
1. On the original protected site (which will become recovery site after reportect is executed)
a. Pause any schedules going from primary volume to remote.
b. Remove any ESX Server assignment.
c. Change primary volume to backup
2. On the original recovery site (which will become protected after reprotect is executed)
• Create remote schedule with the primary volume as the target or un-pause remote
schedules.
3. Delete any SRA created snapshots and schedules.
A volume in the protected site should not have two or more schedules going to
How the HP P4000 SRA Works with VMware SRM 5 5