Best Practices; Roll Back The Primary Snapshot And Keep The Remote Snapshots As A Backup; Using Remote Copy For Data Migration Or Cloning; Achieving Data Migration - HP StoreVirtual 4000 User Manual

Figure 18 Nondestructive rollback from the remote snapshot

Best practices

Roll back the primary snapshot and keep the remote snapshots as a backup.

To ensure that Remote Copy continues to operate, roll back the primary volume as follows:
1. Preserve the current state of the primary volume that you want to roll back by creating a
one-time (manual) remote snapshot of it.
2. Roll back the volume.
Before roll back, scheduled remote snapshots fail. After the primary volume is rolled back,
scheduled creation of remote copies will resume correctly.
Completed remote snapshots remain intact.

Using Remote Copy for data migration or cloning

Remote Copy allows migration of data from one application server to another without interrupting
the production application server. This capability supports a number of uses such as data mining
or content distribution.

Achieving data migration

You can use Remote Copy to make a complete copy (clone) of one or more volumes without
interrupting access to the original volumes. This type of data migration allows you to copy an entire
data set for use by a new application or workgroup.
To copy data from one location to another, simply create a one-time remote snapshot of the volume.
To make the remote snapshot a read/write volume, make it into a primary volume.
Using Remote Copy for data migration or cloning 45