Replicating the Hitachi TrueCopy or Universal Replicator Protection Group Configuration to a Secondary Cluster

After you have configured data replication, resource groups, and resources on your primary and secondary clusters, you can replicate the configuration of the protection group to the secondary cluster.

How to Replicate the Hitachi TrueCopy or Universal Replicator Protection Group Configuration to a Secondary Cluster

Before You Begin

Before you replicate the configuration of a Hitachi TrueCopy or Universal Replicator protection group to a secondary cluster, ensure that the following conditions are met:

• The protection group is defined on the remote cluster, not on the local cluster.

• The device groups in the protection group on the remote cluster exist on the local cluster.

• The application resource groups in the protection group on the remote cluster exist on the local cluster.

• The Auto_start_on_new_cluster property of the resource group is set to False. You can view this property by using the clresourcegroup command.

  # clresourcegroup show -p auto_start_on_new_cluster apprg

  Setting the Auto_start_on_new_cluster property to False prevents the Oracle Solaris Cluster resource group manager from automatically starting the resource groups in the protection group. Therefore, after the Geographic Edition software restarts and communicates with the remote cluster to ensure that the remote cluster is running and that the remote cluster is the secondary cluster for that resource group. The Geographic Edition software does not automatically start the resource group on the primary cluster.

  Application resource groups should be online only on primary cluster when the protection group is activated.

  Set the Auto_start_on_new_cluster property to False as follows:

  # clresourcegroup set -p Auto_start_on_new_cluster=False apprg1

1. Log in to phys-newyork-1.

   You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Geographic Edition Software and RBAC in Oracle Solaris Cluster Geographic Edition System Administration Guide.

   phys-newyork-1 is the only node on the secondary cluster. For a reminder of which node is phys-newyork-1, see Example Geographic Edition Cluster Configuration in Oracle Solaris Cluster Geographic Edition System Administration Guide.

2. Replicate the protection group configuration to the partner cluster by using the geopg get command.

   This command retrieves the configuration information of the protection group from the remote cluster and creates the protection group on the local cluster.

   phys-newyork-1# geopg get -s partnershipname [protectiongroup]

   -s partnershipname

   Specifies the name of the partnership from which the protection group configuration information should be retrieved and the name of the partnership where the protection will be created locally.

   protectiongroup

   Specifies the name of the protection group.

   If no protection group is specified, then all protection groups that exist in the specified partnership on the remote partner are created on the local cluster.

   ---

   Note - The geopg get command replicates Geographic Edition related entities. For information about how to replicate Oracle Solaris Cluster entities, see Replicating and Upgrading Configuration Data for Resource Groups, Resource Types, and Resources in Oracle Solaris Cluster Data Services Planning and Administration Guide.

   ---

Example 2-15 Replicating the Hitachi TrueCopy or Universal Replicator Protection Group to a Partner Cluster

This example replicates the configuration of tcpg from cluster-paris to cluster-newyork.

# rlogin phys-newyork-1 -l root
phys-newyork-1# geopg get -s paris-newyork-ps tcpg