Resuming Production After Failover; Synchronizing Data After Failover; Example Scenario; Returning Operations To Original Primary Site - HP StorageWorks P4000 User Manual
Remote copy user guide
Hide thumbs
Also See for StorageWorks P4000:
- User manual (350 pages) ,
- Maintenance manual (53 pages) ,
- Release notes (18 pages)
Table of Contents
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 StorageWorks 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
Time
1:00 p.m.
1:10 p.m.
1:30 p.m.
1:33 p.m.
2:00 p.m.
The following data needs to be synchronized once the primary volume is back online:
Original volume, which contains data from 1:00 to 1:30 p.m.
Acting primary volume which contains data from 1:33 to 2:00 p.m.
Returning operations to original primary site
After the original primary site is operational again, restore operations to that site. The steps to restore
operations depend upon the state of the original primary volume.
If the primary volume is working:
36
Using Remote Copy
Event
Regular hourly scheduled remote snapshot
starts.
Remote copy finishes.
Primary volume goes offline.
Scripted failover causes remote volume to
become the acting primary volume.
Original primary volume comes back on-
line.
What happens
RemoteSS_1 creates in remote manage-
ment group.
Copying is complete.
OrigPrimaryVol_1 is offline.
ActPrimaryVol_1 becomes primary and
active, and usable to application server.
OrigPrimaryVol_1 is online.
Table of Contents
