I have taken the following information from one of HP's Technical Whitepapers on the "HP StorageWorks P2000 Array System Remote Snap Software" (You can download from HP here)
If the local site fails, the applications need to switch to the remote site. To bring up the remote site, do the following:
1. Convert the remote volume (destination volume) to an external view volume
- NOTE : During the conversion to an external view volume, the volume is rolled back, or synced, to a replication snapshot. By default, the volume syncs to the latest replication snapshot, but you can choose any of the previous replication snapshots. Any data that has not been replicated is lost. A destination volume can be converted to an external view via SMU or CLI.
2. The new external view volume, which now resides on the remote site, can be mapped to a LUN and used as you would use the original volume.
3. Switch the applications to this external view volume and continue using the application.
Once the failure has been addressed at local site, complete the following steps:
1. At the local site make the original source volume a destination volume using the set replication-external view CLI command or by selecting Destination Volume Overview > Provisioning > Set Replication External view from the SMU page.
Important: A destination volume cannot be mapped, so be sure to unmap source volume before attempting to make it a destination volume.
2. Replicate any data written to the remote volume to the original source volume. This can be performed in a single replication or in multiple replications. Host access to the original volume should be halted. This ensures that all data has been transferred properly.
3. After all the data is replicated back to the local site, convert the source volume at the local site to the external view volume and then convert the remote volume to the destination volume. To set an external view volume to a destination volume on the system that owns the external view volume, set the external view to the other volume in the replication set.
4. Re-establish the replication set to the remote site. Continue using the scheduler for running remote replications in regular intervals.
I hope that this is has been helpful in understanding the steps invlolved for Disaster Recovery on the P2000 using the Remote Snap software, if you wish to read more then please download the Whitepaper here.
Regards
Technical ISS Solutions Team



