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 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
To make an application highly available, the application must be managed as a resource in an application resource group.
All the entities you configure for the application resource group on the primary cluster, such as application resources, installation, application configuration files, and resource groups, must be replicated to the secondary cluster. The resource group names must be identical on both clusters. Also, the data that the application resource uses must be replicated to the secondary cluster.
This section contains information about the following tasks:
Before You Begin
You can add an existing resource group to the list of application resource groups for a protection group. Before you add an application resource group to a protection group, ensure that the following conditions are met:
The protection group is defined.
The resource group exists on both clusters and is in an appropriate state.
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
When you bring a protection group online on the primary cluster, you should bring the application resources groups participating in that protection group online only on the same primary cluster. Setting the Auto_start_on_new_cluster property to False prevents the Oracle Solaris Cluster resource group manager from automatically starting the application resource groups. In this case, the start up of resource groups is reserved to the Geographic Edition software.
When the protection group is activated, application resource groups need to be online only on the primary cluster.
Set the Auto_start_on_new_cluster property to False as follows:
# clresourcegroup set -p Auto_start_on_new_cluster=False apprg
The application resource group does not have dependencies on resource groups and resources outside of this protection group unless the External_Dependency_Allowed protection group property is set to TRUE. To add several application resource groups that share dependencies while the External_Dependency_Allowed protection group property is set to FALSE, you need to add all the application resource groups that share dependencies to the protection group in a single operation. If you add the application resource groups separately, the operation fails.
The protection group can be activated or deactivated and the resource group can be either Online or Unmanaged.
If the resource group is Unmanaged and the protection group is Active after the configuration of the protection group has changed, the local state of the protection group becomes Degraded.
If the resource group to add is Online and the protection group is deactivated, the request is rejected. You must activate the protection group before adding an active resource group.
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.
This command adds an application resource group to a protection group on the local cluster. Then the command propagates the new configuration information to the partner cluster if the partner cluster contains a protection group of the same name.
# geopg add-resource-group resourcegrouplist protectiongroup
Specifies the name of the application resource group. You can specify more than one resource group in a comma-separated list.
Specifies the name of the protection group.
For information about the names and values that are supported by Geographic Edition software, see Appendix B, Legal Names and Values of Geographic Edition Entities, in Oracle Solaris Cluster Geographic Edition System Administration Guide.
If the add operation is unsuccessful on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration status is set to OK on the local cluster.
If the Configuration status is OK on the local cluster, but the add operation is unsuccessful on the partner cluster, the Configuration status is set to Error on the partner cluster.
After the application resource group is added to the protection group, the application resource group is managed as an entity of the protection group. Then the application resource group is affected by protection group operations such as start, stop, switchover, and takeover.
Example 2-9 Adding an Application Resource Group to a Protection Group
This example adds two application resource groups, apprg1 and apprg2, to tcpg.
# geopg add-resource-group apprg1,apprg2 tcpg
You can remove an application resource group from a protection group without altering the state or contents of an application resource group.
Before You Begin
Ensure that the following conditions are met:
The protection group is defined on the local cluster.
The resource group to be removed is part of the application resource groups of the protection group. For example, you cannot remove a resource group that belongs to the data replication management entity.
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.
This command removes an application resource group from the protection group on the local cluster. If the partner cluster contains a protection group of the same name, then the command removes the application resource group from the protection group on the partner cluster.
# geopg remove-resource-group resourcegrouplist protectiongroup
Specifies the name of the application resource group. You can specify more than one resource group in a comma-separated list.
Specifies the name of the protection group.
If the remove operation is unsuccessful on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration status is set to OK on the local cluster.
If the Configuration status is OK on the local cluster, but the remove operation is unsuccessful on the partner cluster, the Configuration status is set to Error on the partner cluster.
Example 2-10 Deleting an Application Resource Group From a Protection Group
This example removes two application resource groups, apprg1 and apprg2, from tcpg.
# geopg remove-resource-group apprg1,apprg2 tcpg