HP LeftHand P4000 User Manual

HP P4000 Remote Copy User Guide

Abstract

This guide provides information about configuring and using asynchronous replication of storage volumes and snapshots across geographic distances.

For the latest version of this guide, see the HP website http://www.hp.com/support/manuals.

HP Part Number: AX696-96089 Published: September 2011 Edition: 5

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

1 Understanding and planning Remote Copy....................................................5

How Remote Copy works...........................................................................................................5

Graphical representations of Remote Copy..............................................................................5

Remote Copy and volume replication......................................................................................6

Uses for Remote Copy..........................................................................................................7

Benefits of Remote Copy.......................................................................................................7

Planning for Remote Copy.........................................................................................................7

Planning the remote snapshot................................................................................................8

Using schedules for Remote Copy...............................................................................................9

Planning the Remote Copy schedule.......................................................................................9

Best practices....................................................................................................................10

2 Using Remote Copy..................................................................................12

Working with remote snapshots................................................................................................12

Application-managed snapshots—New for release 8.5 and later.............................................12

Creating a remote snapshot................................................................................................12

Viewing a list of remote snapshots........................................................................................17

Setting the remote bandwidth..............................................................................................17

Canceling a remote snapshot..............................................................................................18

Editing a remote snapshot...................................................................................................18

Deleting a remote snapshot.................................................................................................18

Monitoring remote snapshots...................................................................................................19

Monitoring details from the Remote Snapshots feature.............................................................19

Scheduling remote snapshots...................................................................................................21

Best practices for scheduling remote snapshots...........................................................................22

Creating the schedule.............................................................................................................22

Creating the schedule for volume sets...................................................................................23

What the system does........................................................................................................24

Pausing and resuming scheduled snapshots................................................................................24

Editing the schedule to remote snapshot a volume.......................................................................25

Deleting the remote snapshot schedule......................................................................................25

Failover and failback using Remote Copy..................................................................................25

Planning failover................................................................................................................25

Using the Volume Failover/Failback Wizard...............................................................................26

Converting a primary volume to a remote volume...................................................................26

Using failover to remote volume...........................................................................................27

Resuming production after failover............................................................................................27

Synchronizing data after failover..........................................................................................27

Returning operations to original primary site..........................................................................28

Setting up a new production site..........................................................................................29

Making the backup site into the new production site...............................................................29

Rolling back primary and remote volumes..................................................................................29

Using SmartClone to clone a volume from a snapshot.............................................................29

Rolling back a remote volume..............................................................................................30

Using remote snapshots for data migration and data mining........................................................30

New for release 8.0...........................................................................................................31

Disassociating remote management groups................................................................................31

Best practice for disassociating management groups...............................................................31

3 Sample Remote Copy configurations...........................................................32

Using Remote Copy for business continuance.............................................................................32

Achieving high availability..................................................................................................32

Contents 3

Configuration for high availability........................................................................................32

How this configuration works for high availability...................................................................33

Best practices....................................................................................................................35

Achieving affordable disaster recovery.................................................................................36

Configuration for affordable disaster recovery........................................................................36

How this works for affordable disaster recovery.....................................................................37

Best practices....................................................................................................................39

Using Remote Copy for off-site backup and recovery...................................................................39

Achieving off-site backup....................................................................................................39

Configuration for off-site backup and recovery.......................................................................40

How this configuration works for off-site backup.....................................................................40

Achieving nondestructive rollback.........................................................................................41

Configuration for nondestructive rollback...............................................................................41

How this configuration works for nondestructive rollback.........................................................42

Best practices....................................................................................................................44

Using Remote Copy for data migration or cloning.......................................................................44

Achieving data migration....................................................................................................44

Configuration for data migration..........................................................................................45

How this configuration works for data migration....................................................................45

4 Support and other resources......................................................................47

Contacting HP........................................................................................................................47

Subscription service............................................................................................................47

HP Insight Remote Support Software..........................................................................................47

New and changed information in this edition.............................................................................48

Related information.................................................................................................................48

HP websites......................................................................................................................48

Glossary....................................................................................................49

Index.........................................................................................................55

4 Contents

1 Understanding and planning Remote Copy

Remote Copy provides a powerful and flexible method for reproducing data and keeping that replicated data available for disaster recovery, business continuance, backup and recovery, data migration, and data mining.

How Remote Copy works

Remote Copy uses the existing volume and snapshot features with replication across geographic distances to create remote snapshots. The geographic distance can be local (in the same data center or on the same campus), metro (in the same city), or long distance (cross-country, global).

For example, the accounting department in the corporate headquarters in Chicago runs the corporate accounting application and stores the resulting data. The designated backup site is in Detroit. Nightly at 11:00 p.m., accounting updates are copied to the Detroit backup facility using Remote Copy. “Basic flow of Remote Copy” (page 5) shows the basic flow of Remote Copy.

Reproducing data using Remote Copy follows a three-step process:

1. At the production location, create a snapshot of the primary volume. This is called the primary

snapshot.

2. Create a remote volume at the remote location, and then create a remote copy of the primary

snapshot to the remote volume. The system copies data from the primary snapshot to the remote snapshot.

Figure 1 Basic flow of Remote Copy

NOTE: Both primary and completed remote snapshots are the same as regular snapshots.

Remote Copy can be used on the same site, even in the same management group and cluster.

Graphical representations of Remote Copy

The HP StorageWorks P4000 Centralized Management Console displays special graphical representations of Remote Copy.

How Remote Copy works 5

Copying the primary snapshot to the remote snapshot

When the primary snapshot is copying to the remote snapshot, the CMC depicts the process with a moving graphic of pages from the primary to the remote snapshot. The pages move in the direction of the data flow from primary to remote snapshot.

Figure 2 Icons depicting the primary snapshot copying to the remote snapshot

Graphical legend for Remote Copy icons

The Graphical Legend window available from the Help menu depicts the icons associated with Remote Copy.

Figure 3 Icons for Remote Copy in the Graphical Legend window

Remote Copy and volume replication

Remote Copy is an asynchronous replication of data. Network RAID is a synchronous replication of data. Using synchronous Network RAID on multiple storage systems within a cluster in combination

6 Understanding and planning Remote Copy

with asynchronous Remote Copy on a different cluster of storage systems creates a robust, high-availability configuration.

Uses for Remote Copy

Common uses for the Remote Copy application.

Table 1 Uses for Remote Copy

How it worksUse Remote Copy for

Business continuance and disaster recovery

Off-site backup and recovery

Split mirror, data migration, content distribution

Volume clone

Benefits of Remote Copy

• Remote Copy maintains the primary volume’s availability to application servers. Snapshots

on the primary volume are taken instantaneously, and are then copied to remote snapshots in the off-site location.

• Remote Copy operates at the block level, moving large amounts of data much more quickly

than file system copying.

• Snapshots are incremental, that is, snapshots save only those changes in the volume since the

last snapshot was created. Therefore, failback may need to resynchronize only the latest changes rather than the entire volume.

Remote Copy stores remote snapshots on a machine in a geographically separate location. The remote snapshots remain available in the event of a site or system failure at the primary site.

Remote Copy eliminates the backup window on an application server by creating remote snapshots on a backup server, either local or remote, and back up from that server.

Remote Copy makes a complete copy of one or more volumes without interrupting access to the original volumes. You can move the copy of the volume to the location where it is needed.

Remote Copy creates copies of the original volume for use by other application servers.

• Remote Copy is robust. If the network link goes offline during the process, copying resumes

where it left off when the link is restored.

Planning for Remote Copy

Remote Copy works at the management group, cluster, volume, and snapshot levels. Review

“Remote Copy, SAN/iQ, and storage systems” (page 8) for common configurations at these

levels.

Planning for Remote Copy 7

Table 2 Remote Copy, SAN/iQ, and storage systems

Remote Copy configurationStorage system level

Management groups

Clusters

Volumes

Snapshots

• Create remote snapshots in the same management

group or in a different management group than the primary volume.

• If using different management groups, the remote

bandwidth setting of the management group containing the remote volume determines the maximum rate of data transfer to the remote snapshot.

• Event notification tells you when copies complete or fail.

It also notifies you if a remote volume or snapshot is made primary or if the status of the connection between management groups containing primary and remote volumes changes.

• Create remote snapshots in the same cluster or in a

cluster different from the primary volume.

• Primary volumes contain the data to be copied to the

remote snapshot.

• Data is copied to the remote snapshot via the remote

volume.

• The remote volume is a pointer to the remote snapshot.

The remote volume has a size of 0 bytes.

• After data is copied from the primary snapshot to the

remote snapshot, the remote snapshot behaves as a regular snapshot.

Planning the remote snapshot

Prerequisites for creating a remote snapshot

• Log in to both the management group that contains the primary volume and the management

group that contains the target cluster where the remote snapshot will be created.

• Designate or create a remote volume in that remote management group.

• Ensure there is enough space on the target cluster for the remote snapshot.

Logging in to primary and remote management groups

Log in to both the primary and the remote management groups before you begin, or you must log in to the remote management group while creating a remote copy.

Designating or creating the remote volume

Create a remote volume by using any of the following methods:

• Make an existing volume into a remote volume.

• Create a new remote volume while creating a remote snapshot.

• Create a new volume from the cluster Details tab window, and then select the Remote radio

button on the Advanced tab of the New Volume window. From the menu bar, select Tasks→Volume→New Volume.

For more information about these methods of creating remote volumes, see “Creating a remote

volume” (page 15).

8 Understanding and planning Remote Copy

Using schedules for Remote Copy

Scheduled remote snapshots provide fault tolerance for business continuance and disaster recovery, and a consistent, predictable update of data for remote backup and recovery.

Planning the Remote Copy schedule

Planning is critical. The following issues impact the amount of storage available in the system:

• Recurrence

• Capacity

• Retention

Recurrence

How often do you want the snapshots created? The recurrence frequency must account for the amount of time it takes to complete a remote snapshot. For example, if your recurrence schedule is set for a new snapshot every four hours, you should ensure that the time to copy that snapshot to the remote location is less than four hours.

Testing the copy time

One way to check the time required to copy a snapshot is to run a test of the actual process. To test this process, take two remote snapshots of the primary volume. Because the first remote snapshot copies the entire volume, it takes longer to copy. The second remote snapshot copies only changes made to the volume since the first remote snapshot was taken. You create the second remote snapshot after the time interval you intend to schedule. Because of that, the copy time for the second remote snapshot is more representative of the actual time required for copying subsequent remote snapshots.

To test the copy time:

1. Create a remote snapshot of the primary volume.

2. Wait for the copy to finish.

3. Create another remote snapshot of the primary volume.

4. Track the time required to complete the second remote snapshot.

NOTE: This is the minimum amount of time that you should allow between scheduled copies.

5. Check the remote bandwidth setting for the other management group by using the Edit

Management Group command. This setting affects the time required to copy a remote snapshot.

Capacity

Does the cluster that contains the remote volume have sufficient space to accommodate scheduled snapshots?

If the cluster does not have sufficient space available, the remote snapshot appears in the CMC and flashes red. On the Details tab of the remote snapshot, the status message displayed is Read

only, not enough space in cluster to start copy.

Retention policies

How long do you want to retain the primary snapshots? The remote snapshots? You can set different retention policies for the primary and remote snapshots. For example, you can choose to retain two primary snapshots and five remote snapshots. The number of snapshots retained refers to

Using schedules for Remote Copy 9

completed snapshots. Take the following characteristics of scheduled remote snapshots into account when planning retention policies.

• The SAN/iQ software never deletes the last fully synchronized remote snapshot.

Under some circumstances, such as unpredictable network speeds or varying snapshot size, a scheduled remote snapshot may create primary snapshots so frequently that the remote copy process cannot keep up with them. The retention policies for scheduled remote snapshots ensure that such factors do not cause primary and remote snapshots to become unsynchronized. Regardless of the retention policy defined for scheduled remote snapshots, up to two additional snapshots may be retained by the system at any given time. These two additional snapshots include the snapshot that is in the process of being copied and the last fully synchronized snapshot. A fully synchronized snapshot is one that has completed copying so that the remote snapshot matches its corresponding primary snapshot.

• Up to two additional snapshots may be retained at any given time.

Because the SAN/iQ software never deletes the last fully synchronized snapshot, a remote copy schedule may retain n+2 copies for a retention policy of n (the currently copying remote snapshot plus the last fully synchronized snapshot). Using the example above, if you have a retention policy for your remote copy schedule of two primary and five remote snapshots, the software may retain up to four primary and seven remote snapshots for a period of time.

“Snapshot retention policy and maximum number of retained snapshots” (page 10) shows

the maximum retained snapshots with respect to a specific retention policy.

Table 3 Snapshot retention policy and maximum number of retained snapshots

Maximum number of snapshots retainedScheduled remote snapshot retention policy

n + 2 of primary snapshots x + 2 of remote snapshotsn of primary snapshots x of remote snapshots

n of hours for primary snapshots x of hours for remote

snapshots

n of days for primary snapshots x of days for remote snapshots

n of weeks for primary snapshots x of weeks for remote snapshots

n + 2 primary snapshots older than nx + 2 remote snapshots older than x

• A remote snapshot is deleted only after its corresponding primary snapshot is deleted.

Additionally, a remote snapshot is deleted only after its counterpart primary snapshot. You cannot retain fewer remote snapshots than primary snapshots when setting your retention policies.

NOTE: Over the course of time, through deletion of primary snapshots, if you accumulate more

remote snapshots than primary snapshots, the remote snapshots become regular snapshots when their corresponding primary snapshots are deleted. You can identify them as remote snapshots by their names, since the naming convention is established as part of creating the remote snapshot schedule.

Best practices

• Retain at least two primary snapshots to ensure that only incremental copying is required for

remote snapshots.

• Review your remote copy schedule to ensure that the frequency of the remote copies correlates

to the amount of time required to complete a copy.

Use the checklist in “Scheduled Remote Copy planning checklist” (page 11) to help plan scheduled remote snapshots.

10 Understanding and planning Remote Copy

Table 4 Scheduled Remote Copy planning checklist

Scheduled snapshot

CharacteristicConfiguration category

Start time

Recurrence

Primary setup

Remote setup

• Start date (mm/dd/yyyy) for the schedule to begin

• Start time (mm:hh:ss) for the schedule to begin

• Recurrence is a yes or no choice. Do you want to take

a remote snapshot one time in the future and not have it recur, or do you want a remote snapshot to be taken on a regular schedule?

• Frequency (minutes, hours, days, or weeks) determines

the interval between recurring, scheduled, remote snapshots.

Select one of the following options:Retention

• Maximum number of snapshots (#)

• Set period of time (minutes, hours, days, or weeks)

The management group that contains the remote snapshotManagement group

The remote volume for the remote snapshotsVolume

Select one of the following options:Retention

• Maximum number of snapshots. This number equals

completed snapshots only. In-progress snapshots take additional space on the cluster while copying. Also, the system will not delete the last fully synchronized snapshot. For space calculations, figure n+2 where n=maximum number of snapshots.

• Set period of time (minutes, hours, days or weeks)

Using schedules for Remote Copy 11

2 Using Remote Copy

For information about how Remote Copy works and how to plan capacity for Remote Copy, see

“Understanding and planning remote copy” (page 5).

Working with remote snapshots

Remote snapshots are a core component of Remote Copy. Remote Copy uses the existing volume and snapshot capabilities to copy data across geographic distances.

Application-managed snapshots—New for release 8.5 and later

You can create remote application-managed snapshots that use the Application Aware Snapshot Manager to quiesce the application before creating the remote snapshots. Because the application is quiesced, the data in the snapshot is consistent with the application's view of the data. That is, no data was in flight or cached waiting to be written when the application created the snapshot.

This option requires the use of the Application Aware Snapshot Manager. For more information about the requirements for application-managed snapshots, see the HP P4000 SAN Solution User Guide or online help.

Creating a remote snapshot

You can either create a one-time remote snapshot or set up a schedule for recurring remote snapshots. Many of the characteristics for either case are the same.

Create a remote snapshot by using the following steps:

1. Log in to the primary management group.

2. Log in to the remote management group.

3. Create a primary snapshot of the primary volume manually to create a single remote copy

snapshot. When setting up a schedule to create a remote snapshot of a volume, the software automatically creates a primary snapshot, which is then copied to the remote volume.

4. Either create a remote volume on a remote management group, or select an existing remote

volume.

5. Create the remote snapshot.

Best practice

The best way to prepare for remote snapshots is to create the management group and volumes that will be remote before taking the snapshot. Although the interface allows you to create volumes and snapshots as you go, that may be a distraction at the time a crucial snapshot is needed.

Getting there

Navigate to the New Remote Snapshot window where remote copy procedures start.

1. In the navigation window, log in to the management group that contains the primary volume

or snapshot for which you are creating the remote snapshot.

2. Log in to the remote management group.

3. In the navigation window, select the primary volume (or snapshot).

To copy an existing snapshot to a remote management group, select that snapshot at this step.

4. Click Snapshot Tasks, and then select New Remote Snapshot.

Creating the primary snapshot

1. In the Primary Snapshot Setup box, click New Snapshot.

12 Using Remote Copy

If you selected a snapshot to start the process, you do not need to create a new snapshot.

2. (Optional) If you are using the Application Aware Snapshot Manager and want to quiesce

the application before creating the snapshot, select Application-Managed Snapshot. The system fills in the Description field and and the snapshot inherits the server assignment of

the volume.

3. Enter a name for the snapshot or accept the default.

TIP: Make the beginning of volume and snapshot names meaningful, for example,

“Snap1Exchg_03.”

4. (Optional) Enter a description of the snapshot.

5. Click OK to return to the New Remote Snapshot window.

The information for the primary snapshot is pre-filled. For example, the text for Snapshot Name changed from “Create Primary Snapshot” to “HdqtrsLogs_SS_1”.

6. In the Remote Snapshot Setup box, select the remote management group and volume.

If you need to create a volume, click New Remote Volume.

7. In the Snapshot Name box, enter the name for the remote snapshot.

8. (Optional) Enter a description for the remote snapshot.

9. Click OK in the New Remote Snapshot window.

The remote copy of the primary snapshot to the remote volume begins.

Figure 4 Remote copy in progress

Working with remote snapshots 13

Creating primary snapshots for volume sets

When you create an application-managed snapshot of a volume in a volume set, the software recognizes that the volume is part of a volume set, and prompts you to create a snapshot for each volume in the volume set. The result is a snapshot set that corresponds to the volume set. To see any associated snapshots, select a snapshot, click the Details tab, and look at the Snapshot Set field.

For information about the requirements for application-managed snapshots, see the HP P4000 SAN Solution User Guide..

NOTE: After you create snapshots for a volume set, typically you do not want to delete individual

snapshots from the snapshot set. You want to keep or delete all snapshots for the volume set. If you need to roll back to a snapshot, you want to roll back each volume in the volume set to its corresponding snapshot. The system gives you the option to automatically delete or roll back all associated volumes.

To create primary snapshots for volume sets:

1. Select a volume that is part of a volume set for the snapshot.

2. Log in to the management group that contains the volume for which you want to create a

snapshot.

3. Right-click on the volume and then select New Remote Snapshot.

4. Click New Snapshot.

5. Select Application-Managed Snapshot.

The software fills in the Description field and disables the Assign and Unassign Servers button automatically. You can assign servers after the snapshot is created.

6. Enter a name for the snapshot or accept the default.

7. Click OK.

The New Snapshot—Associated Volumes window opens with a list of all volumes in the volume set.

8. (Optional) Edit the Snapshot Name for each snapshot.

NOTE: Be sure to leave the Application-Managed Snapshots check box selected. This option

quiesces the application before creating the snapshots. If you deselect the option, the system creates a point-in-time snapshot of each volume listed.

9. (Optional) Edit the Description for each snapshot.

10. Click Create Snapshots to create a snapshot of each volume.

The Primary—Remote window opens with the list of the snapshots you just created. The first snapshot is already selected.

11. In the Remote Snapshot Setup box, select the remote management group and volume for the

selected snapshot.

NOTE: If you need to create a volume, select New Remote Volume.

12. In the Snapshot Name field, enter the name for this remote snapshot or accept the default.

13. (Optional) Enter a description for this remote snapshot.

14. Click Update Pending Table Below to add this remote snapshot setup to the list at the bottom

of the window. The system selects the next volume in the Select Primary Snapshot list at the top of the window.

15. Select or enter the Volume Name, Snapshot Name, and Snapshot Description for this remote

snapshot.

14 Using Remote Copy

IMPORTANT: All remote snapshots must be set up to use the same remote management

group.

16. Click Update Pending Table Below to add this remote snapshot setup to the list at the bottom

of the window.

17. Continue until each snapshot at the top of the window is set up.

A green check mark shows the snapshot is set up.

18. Click Create Remote Copies.

The remote copy of the primary snapshots to the remote volumes begins.

Creating a remote volume

You can create a remote volume by using the following methods:

• Designate an existing primary volume as a remote volume.

• Create a new remote volume manually.

• Create a new remote volume during creation of a remote snapshot.

• Use the Management Groups, Clusters, and Volumes wizard in the “Getting Started” launch

pad. See the HP P4000 SAN Solution User Guide for details on working through the wizards.

Designating an existing volume as a remote volume

When you select an existing volume to become a remote volume, the following occurs:

• A snapshot is created of the volume to preserve the data from the primary volume.

• The volume becomes a 0-byte remote volume.

Creating a new remote volume manually

Create a remote volume as you would any other volume. Be sure to select the storage systems at the remote site. Because management groups and clusters are logical entities, name them to reflect their remote functionality.

In this method, the primary volume is ready. Create a remote volume at the remote site to receive the snapshot, and then either take the snapshot and create a remote copy, or create the schedule to take remote snapshots.

Creating a remote volume while creating a remote snapshot

If you are using the New Remote Snapshot window, you can create a needed cluster and volume as you work through the window.

1. In the Remote Snapshot Setup box, select a management group to contain the remote snapshot.

NOTE: You must be logged in to the management group you select.

2. Click New Remote Volume.

The Management Groups, Clusters, and Volumes wizard opens. The wizard uses the information you entered to fill The New Remote Snapshot window when

you exit the wizard.

3. (Optional) Enter a description of the remote snapshot and click OK.

The system creates the remote copy.

Working with remote snapshots 15

NOTE: There may be a delay in remote copy time.

What the system does

The system creates the remote snapshot in the cluster that contains the remote volume, and then copies the primary snapshot onto the remote snapshot. The process of copying the data may take some time.

The remote snapshot appears below the remote volume in the navigation window when the copy completes.

NOTE: If you create a remote snapshot of a volume while a remote snapshot is in progress, the

second remote snapshot does not begin copying until the first remote snapshot is complete.

Creating the first copy

Creating the first copy of data is the first step when setting up a Remote Copy solution. Three methods for creating the first copy are described below.

Copy data directly to the remote site over the WAN.

Use this method if you are implementing the Remote Copy solution before you accumulate much data in the primary site, and your hardware is already installed in the remote site.

With this method, you create the primary management group and the remote management group in their respective locations, and then create the initial copy of the data directly over the WAN using Remote Copy.

Use the storage systems intended for the remote site to configure the remote management group onsite and copy data locally, and then ship the remote storage systems to the remote site.

Use this method if you initially have all the storage systems for the Remote Copy solution at the primary site.

1. Configure both the primary and remote management groups.

2. Create the first copy of the data locally over the gigabit Ethernet.

3. Ship the storage systems for the remote site and install the remote management group just as

you configured it in the primary site.

4. Allow adequate time between the arrival of the storage systems and the first remote copy

operation.

NOTE: The subsequent snapshots from the primary volume to the remote volume are

incremental.

Use the PrimeSync method of Remote Copy to configure a temporary management group, create the first copy locally, ship the temporary storage system, and then copy locally to the remote target.

Use this method if you have the primary (Site A) and remote site (Site B) configured and operational.

1. While at the primary Site A, use available storage systems to create a new temporary

management group, cluster, and volume. This management group, cluster, and volume are the PrimeSync that you will set up at the

primary Site A.

2. Make a remote snapshot of the primary Site A volume, and then copy it to the temporary

PrimeSync management group over gigabit Ethernet. See “Creating a remote snapshot”

(page 12).

3. Ship the storage systems to the remote Site B.

4. Power them on and discover them in the CMC to display the temporary PrimeSync management

group, cluster, and volume.

16 Using Remote Copy

5. Copy the remote snapshot from the temporary PrimeSync management group to the existing

remote Site B management group.

6. Disassociate the temporary PrimeSync management group from the remote Site B management

group. For more information, see “Disassociating remote management groups” (page 31).

7. Delete the temporary PrimeSync management group.

8. Set up the desired Remote Copy relationship, such as configuring a schedule to create remote

snapshots of the volume from the primary Site A to remote Site B management group. PrimeSync ensures that the proper relationship is established between the original primary

volume and the remote site. Subsequent remote snapshots from the primary site to the remote site are incremental.

NOTE: Use the initial snapshot that you used for the temporary PrimeSync management group

copy, to create the second Remote Copy or the schedule to create remote snapshots of the volume. You are now setting up the Remote Copy that goes from primary site A directly to remote site B which maintains that relationship going forward.

For more information on PrimeSync, see the “Application Note: SAN/iQ Remote Copy PrimeSync — Creating Initial Copy” at

http://www.hp.com/support/manuals.

Select Storage→Disk Storage Systems and then select HP LeftHand P4000 SAN Solutions.

Viewing a list of remote snapshots

View a list of remote snapshots associated with management groups, clusters, volumes, or snapshots.

1. In the navigation window, select a cluster to view its list of remote snapshots.

2. Click the Remote Snapshot.

The report in the Remote Snapshot tab lists management groups and all the snapshots. The other columns show status information about the remote snapshots. For more information, see

“Monitoring remote snapshots” (page 19).

Setting the remote bandwidth

The remote bandwidth sets the maximum rate for data transfer between management groups. The copy rate is equal to, or less than, the rate set.

To control the maximum rate of data transfer to a remote snapshot, set the remote bandwidth on the management group that contains the remote snapshot which is the remote management group. When setting the remote bandwidth, you can choose from a list of common network types, or calculate a custom rate, based on your particular requirements.

Selecting remote bandwidth rate

You may either select a preset speed from a list of standard network types or calculate a custom speed based on your specific requirements. Remember that the speed is the maximum rate at which data copies.

• Defaults setting— When setting remote bandwidth, selecting Defaults allows you to choose

from a list of common network types.

• Custom setting— The custom setting for remote bandwidth defaults to 32,768 KB, or about

4 MB. Use the calculation tool to identify a desired bandwidth setting. For example, if you have a T1 line, and you want to set the remote bandwidth to 12% of that capacity, you can use the calculation tool to find the correct value, 189 KB.

Working with remote snapshots 17

Figure 5 Calculating a custom value for setting remote bandwidth

Best practice

Set the bandwidth speed the same in both directions unless you have an asymmetrical WAN link. To set the bandwidth:

1. In the navigation window, select either the remote or primary management group.

2. Click Management Group Tasks, and then select Edit Management Group.

3. Select the remote or primary management group.

4. Click Edit Remote Bandwidth.

5. Change the bandwidth setting as desired.

Canceling a remote snapshot

When you cancel a remote snapshot that is in progress, the remote snapshot is deleted, but the primary snapshot remains.

1. In the navigation window, select the remote snapshot.

2. Click the Remote Snapshot tab.

3. Select the remote snapshot to cancel from the list, if it is not already selected.

4. Click Remote Snapshot Tasks, and then select Cancel Remote Snapshot.

5. Click OK.

Editing a remote snapshot

To change the description and change the server assignment of a remote snapshot:

1. Log in to the management group that contains the remote snapshot.

2. Select the remote snapshot in the navigation window.

3. Click Snapshots Tasks, and then select Edit Snapshot.

4. Change the desired information, and then click OK.

Deleting a remote snapshot

CAUTION: Do not delete individual snapshots that are part of a snapshot set. To see associated

snapshots, select a snapshot, click the Details tab, and then view the Snapshot Set field. For information about snapshot sets, see the HP P4000 SAN Solution User Guide. HP recommends that you keep or delete all snapshots for a volume set. If you need to roll back to a snapshot, you want to roll back each volume in the volume set to its corresponding snapshot. The system gives you the option to automatically delete or roll back all associated volumes.

1. Log in to the management group that contains the remote snapshot.

2. Select the remote snapshot in the navigation window.

18 Using Remote Copy

+ 39 hidden pages