Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy and Universal Replicator Oracle Solaris Cluster 3.3 3/13 |
1. Replicating Data With Hitachi TrueCopy and Universal Replicator Software
2. Administering Hitachi TrueCopy and Universal Replicator Protection Groups
Strategies for Creating Hitachi TrueCopy and Universal Replicator Protection Groups
Creating a Protection Group While the Application Is Offline
Creating a Protection Group While the Application Is Online
Ensuring Data Consistency for Hitachi Universal Replicator in Asynchronous Mode
Understanding Data Consistency in Geographic Edition
Using Consistency Group IDs to Ensure Data Consistency
Requirements to Support Oracle Real Application Clusters With Data Replication Software
How to Create a Protection Group for Oracle Real Application Clusters
How the Data Replication Subsystem Validates the Device Group
How to Modify a Hitachi TrueCopy or Universal Replicator Protection Group
Validating a Hitachi TrueCopy or Universal Replicator Protection Group
How to Validate a Hitachi TrueCopy or Universal Replicator Protection Group
How to Delete a Hitachi TrueCopy or Universal Replicator Protection Group
Administering Hitachi TrueCopy and Universal Replicator Application Resource Groups
Administering Hitachi TrueCopy and Universal Replicator Data Replication Device Groups
Validations Made by the Data Replication Subsystem
How the State of the Hitachi TrueCopy or Universal Replicator Device Group Is Validated
Determining the State of an Individual Hitachi TrueCopy or Universal Replicator Device Group
Determining the Aggregate Hitachi TrueCopy or Universal Replicator Device Group State
Validating the Local Role of the Protection Group Against the Aggregate Device Group State
How to Modify a Hitachi TrueCopy or Universal Replicator Data Replication Device Group
Activating a Hitachi TrueCopy or Universal Replicator Protection Group
How to Activate a Hitachi TrueCopy or Universal Replicator Protection Group
Deactivating a Hitachi TrueCopy or Universal Replicator Protection Group
How to Deactivate a Hitachi TrueCopy or Universal Replicator Protection Group
Resynchronizing a Hitachi TrueCopy or Universal Replicator Protection Group
How to Resynchronize a Protection Group
Checking the Runtime Status of Hitachi TrueCopy and Universal Replicator Data Replication
Displaying a Hitachi TrueCopy or Universal Replicator Runtime Status Overview
How to Check the Overall Runtime Status of Replication
Displaying a Detailed Hitachi TrueCopy or Universal Replicator Runtime Status
3. Migrating Services That Use Hitachi TrueCopy and Universal Replicator Data Replication
A. Geographic Edition Properties for Hitachi TrueCopy and Universal Replicator
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.
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
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.
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]
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.
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