HP LeftHand P4000 Virtual SAN Appliance Software - Manual (Page 27)

Using failover to remote volume
If the primary volume is not available, you can use the wizard to promote the remote volume to
an acting primary volume.
1. In the navigation view, select the volume to convert.
2. Right-click the volume, and then select Failover/Failback Volume.
3. Click Next.
4. Select the reason you are failing over the volume.
Use the second choice if your primary volume is not available and you want to get an acting
primary volume into production.
5. Select To failover to the remote volume, and click Next.
The next window reminds you to disconnect any iSCSI sessions connected to the volume.
6. The final step is to make the remote volume into an acting primary volume.
This acting primary volume connects to application servers in order to maintain business
continuance or accomplish disaster recovery.
7. Click Finish.
The final window of the wizard displays a summary of the actions and a reminder to reconnect
your iSCSI sessions.
8. If you promoted a remote application-managed snapshot, use diskpart.exe to change the
resulting volume's attributes.
For more information, see the HP P4000 SAN Solution User Guide or online help.
Resuming production after failover
After failover occurs, three scenarios exist for resuming production:
•
Failback returns operations to the original primary site it is restored.
•
Convert the backup site to the new primary site.
•
Set up a new primary site and resume operations at that site.
The task flow for restoring or recovering data and resuming the original Remote Copy configuration
is different for each scenario.
Use these procedures when you are resynchronizing data between the acting primary volume and
the recovered, or newly configured, production site primary volume.
Synchronizing data after failover
After a failover, there are usually two snapshots or volumes that have conflicting data. Recovering
and synchronizing data depends on multiple factors, including the application involved.
Example scenario
The following example illustrates one process for synchronizing data. Remember that synchronization
is optional.
Table 6 Timeline of failover
What happens Event Time
RemoteSS_1 creates in remote
management group.
Regular hourly scheduled remote
snapshot starts. 1:00 p.m.
Copying is complete. Remote copy finishes. 1:10 p.m.
OrigPrimaryVol_1 is offline. Primary volume goes offline. 1:30 p.m.
Resuming production after failover 27