HP XP Racks - Manual (Page 34)

SQL Options tab (SQL Server only):
• SQL instance
• If a backup server is used, it should also be configured in the same way as the database server
(except for the Replica Options tab).
• For a cluster configuration, Shared Data Path is set in the Cluster Options tab of the Setup Applic-
ation dialog box.
• Consult “ About concealing/revealing replica volumes ” on page 64 and “ Precautions for replica
operations ” on page 372 for additional requirements and information.
Related topics
• Adding an instance of Application Agent , page 61
• Creating an application replica , page 388
Setting up redundant pair management server configurations
Redundant pair management server configurations allow remote copy operations even when a remote
pair management server is unavailable (whether due to maintenance or hardware failure). Redundancy
can be defined in a variety of configurations, such as N:1 (N-to-one) and 1:M (one-to-many).
Pair management servers can be selected and registered (as a primary/secondary pair) during copy
group creation. Once registered, a pair of primary/secondary pair management servers is known
as a node. Nodes can be added or deleted as necessary without having to disband and reconstruct
the copy group.
This module includes the following topics:
• About redundant pair management server configurations , page 34
• Registering redundant pair management server nodes (while creating a copy group) , page 35
• Registering redundant pair management servers manually , page 36
• Adding pair management server nodes , page 36
• Deleting pair management server nodes , page 36
• Identifying a pair management server associated with a copy group , page 37
About redundant pair management server configurations
You can set up multiple pair management servers in any of four redundant configurations.
WARNING!
N:M and 1:M configurations are intended for use in disaster recovery. N:M and 1:M configurations
cannot be used to create or restore application replicas.
Table 1 Pair management server configurations
Description Name
A configuration in which the same configuration definition file that defines the primary
volume on the primary site is managed by multiple servers, and the configuration
definition file that defines the secondary volume on the secondary site is managed by
a single server.
N:1
(N-to-one)
Getting started 34