Home » HP Manuals » Storage Devices » HP P4000 » Manual Viewer

HP P4000 9.0 HP StorageWorks P4000 Remote Copy User Guide - Page 55

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

Add to My Manuals
Save this manual to your list of manuals

Page 55 highlights

Figure 20 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. P4000 Remote Copy user guide 55

Section	Page
P4000 Remote Copy user guide	1
Contents	3
1 Understanding and planning Remote Copy	9
How Remote Copy works	9
Graphical representations of Remote Copy	10
Copying the primary snapshot to the remote snapshot	10
Graphical legend for Remote Copy icons	10
Remote Copy and volume replication	11
Uses for Remote Copy	11
Benefits of Remote Copy	12
Planning for Remote Copy	12
Planning the remote snapshot	12
Prerequisites for creating a remote snapshot	12
Logging in to primary and remote management groups	13
Designating or creating the remote volume	13
Using schedules for Remote Copy	13
Planning the Remote Copy schedule	13
Recurrence	13
Testing the copy time	13
Capacity	14
Retention policies	14
Best practices	15
2 Using Remote Copy	17
Working with remote snapshots	17
New for release 8.5 and greater	17
Creating a remote snapshot	17
Best practice	17
Getting there	17
Creating the primary snapshot	18
Creating primary snapshots for volume sets	19
Creating a remote volume	21
Designating an existing volume as a remote volume	21
Creating a new remote volume manually	21
Creating a remote volume while creating a remote snapshot	21
What the system does	22
Creating the first copy	22
Viewing a list of remote snapshots	24
Setting the remote bandwidth	24
Selecting remote bandwidth rate	24
Best practice	24
Setting the bandwidth	25
Canceling a remote snapshot	25
Editing a remote snapshot	25
Deleting a remote snapshot	25
Monitoring remote snapshots	26
Monitoring details from the Remote Snapshots feature	26
Viewing information in the Remote Snapshots tab	26
Viewing the status in the Remote Snapshot Details window	26
Scheduling remote snapshots	29
Best practices for scheduling remote snapshots	29
Creating the schedule	29
Creating the schedule for volume sets	30
Timing for a scheduled remote snapshot	31
What the system does	32
Pausing and resuming scheduled snapshots	32
Pause a schedule	32
Resume a schedule	32
Editing the schedule to remote snapshot a volume	33
Edit the remote snapshot schedule	33
Deleting the remote snapshot schedule	33
Failover and failback using Remote Copy	33
Planning failover	34
Using the Volume Failover/Failback Wizard	34
Converting a primary volume to a remote volume	34
Using failover to remote volume	35
Resuming production after failover	36
Synchronizing data after failover	36
Example scenario	36
Returning operations to original primary site	36
Synchronizing the data between the acting primary volume and the original primary volume	37
Creating a new primary volume at the original production site	37
Setting up a new production site	38
Making the backup site into the new production site	38
Rolling back primary and remote volumes	38
Using SmartClone to clone a volume from a snapshot	38
Rolling back a primary volume	38
Prerequisites	38
Rolling back a remote volume	39
Using remote snapshots for data migration and data mining	40
New for release 8.0	40
Creating a split mirror	40
Disassociating remote management groups	40
Best practice for disassociating management groups	40
3 Sample Remote Copy configurations	43
Using Remote Copy for business continuance	43
Achieving high availability	43
Configuration for high availability	43
How this configuration works for high availability	44
Best practices	46
Remote snapshots with volume replication	46
Example configuration	46
How it works	47
Achieving affordable disaster recovery	47
Configuration for affordable disaster recovery	47
How this works for affordable disaster recovery	48
Best practices	50
Select an optimum recurrence schedule.	50
Use remote snapshots in conjunction with local, synchronous volume replication	50
Example configuration	50
Using Remote Copy for off-site backup and recovery	50
Achieving off-site backup	51
Configuration for off-site backup and recovery	51
Configuration diagram	51
How this configuration works for off-site backup	51
Best practices	52
Example configuration	52
Achieving nondestructive rollback	52
Configuration for nondestructive rollback	52
How this configuration works for nondestructive rollback	53
Best practices	55
Roll back the primary snapshot and keep the remote snapshots as a backup.	55
Using Remote Copy for data migration or cloning	55
Achieving data migration	56
Configuration for data migration	56
How this configuration works for data migration	56
4 Support and other resources	59
Contacting HP	59
Subscription service	59
HP Insight Remote Support Software	59
New and changed information in this edition	60
Related information	60
HP websites	60
Typographic conventions	60
Customer self repair	61
HP product documentation survey	62
Glossary	63

Match case Limit results 1 per page

Figure 20 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:

Preserve the current state of the primary volume that you want to roll back by creating a one-time

(manual) remote snapshot of it.

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.

P4000 Remote Copy user guide