How to Replicate the Oracle Solaris ZFS Snapshot Protection Group Configuration to a Partner Cluster

Language:

Note - You can also accomplish this procedure by using the Oracle Solaris Cluster Manager b. Click Partnerships, then click the partnership name. In the Protection Groups section, click Get Protection Groups, and select the protection group to replicate. For more information about Oracle Solaris Cluster Manager, see Chapter 13, Using the Oracle Solaris Cluster Manager Browser Interface in Oracle Solaris Cluster 4.3 System Administration Guide.

Before You Begin

Before you replicate the configuration of an Oracle Solaris ZFS snapshot protection group to a partner cluster, ensure that the following conditions are met:

You have reviewed the information in Planning Remote Replication Using Oracle Solaris ZFS Snapshot.
You have performed the prerequisites mentioned in Prerequisites for Configuring Remote Replication Using Oracle Solaris ZFS Snapshot.
The protection group is defined on the remote cluster, not on the local cluster.
The application resource groups in the protection group configuration on the remote cluster exist on the local cluster.
Application resource groups are in unmanaged state on the local cluster.

Perform this procedure from one node on the local cluster.

Assume the root role or assume a role that is assigned the Geo Management RBAC rights profile.
For more information about RBAC, see Securing Geographic Edition Software in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.
Note - If you use a role with Geo Management RBAC rights, ensure that the /var/cluster/geo ACLs are correct on each node of both partner clusters. If necessary, assume the root role on the cluster node and set the correct ACLs.
```
# chmod A+user:username:rwx:allow /var/cluster/geo
```
The /var/cluster/geo directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Solaris ZFS snapshot software.
Ensure that the Auto_start_on_new_cluster property of the application resource group is set to False.
```
# clresourcegroup show -p Auto_start_on_new_cluster resource-group
```
If necessary, change the property value to False.
```
# clresourcegroup set -p Auto_start_on_new_cluster=False resource-group
```
If either partner is a zone cluster, configure an Oracle Solaris Cluster private string in the global zone of the local partner to store the local replication user's SSH passphrase.
For example, Suppose that the local partner is a global zone and the remote partner is a zone cluster. The replication component is repcom1. Type the following in one node of the local partner to configure the Oracle Solaris Cluster private string:
```
$ clps create -b global:repcom1:local_service_passphrase \
global:repcom1:local_service_passphrase
<Enter SSH passphrase at prompt>
```
For example, if the local partner is a zone cluster zc1 and replication component is repcom1, type the following in the global zone of one node of the local zone cluster partner to configure the Oracle Solaris Cluster private string:
```
$ clps create -b zc1:repcom1:local_service_passphrase \
zc1:repcom1:local_service_passphrase 
<Enter SSH passphrase at prompt>
```
Replicate the protection group configuration to the local partner cluster.
```
newyork-node-1# geopg get -s partnership protection-group
```
–s partnership

Specifies the name of the partnership from which the protection group configuration information is retrieved.

protection-group

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.

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

Note - The geopg get command replicates Geographic Edition related entities. To replicate Oracle Solaris Cluster resource groups, resource types, and resources, use the cluster export -t rg,rt,rs command to generate an XML cluster configuration file and modify the XML file for the expected configuration on the secondary cluster. Run the clresource create command with the –a option to apply the configuration updates. For more information, see How to Configure Oracle Solaris Cluster Software on All Nodes (XML) in Oracle Solaris Cluster 4.3 Software Installation Guide and the cluster(1CL)and clresource(1CL) man pages.
If local partner is a zone cluster, configure a logical hostname resource and resource group in the global zone of the local partner to host the replication hostname.
The names of the resource and resource group are not restricted to any specific format. After configuring the logical hostname resource and resource group, perform the following actions:
- Add a strong positive affinity from the logical hostname resource group to the zpool's infrastructure resource group.
  
  Note - Setting the strong positive resource group affinity will print a warning message, if the logical hostname resource group has the Auto_start_on_new_cluster=TRUE property while the zpool's infrastructure resource group has Auto_start_on_new_cluster=FALSE. This is allowed, since the Geographic Edition software will bring up the zpool's infrastructure resource group when required, thereby also bringing up the logical hostname resource group due to the affinity.
- Add a offline-restart resource dependency from the logical hostname resource to the zpool's infrastructure storage HAStoragePlus resource.
- Ensure that Auto_start_on_new_cluster is TRUE on the logical hostname resource group. This property is TRUE by default. In case the property is FALSE, set it to TRUE.
For example, suppose the local partner is a zone cluster zc1 and local replication hostname is newyork-lh. The zpool infrastructure resource group in zc1 is pg1-app-rg1-infr-rg. The storage resource is pg1-targpool1-stor-rs. Type the following commands in the global zone of one node of the local partner zc1:
```
$ clrg create newyork-lh-rg
$ clrslh create -g newyork-lh-rg -h newyork-lh newyork-lh-rs
$ clrg manage newyork-lh-rg
$ clrg set -p RG_affinities=++zc1:pg1-app-rg1-infr-rg newyork-lh-rg
(C538594) WARNING: resource group global:newyork-lh-rg has a strong positive affinity on
resource group zc1:pg1-app-rg1-infr-rg with  Auto_start_on_new_cluster=FALSE;
global:newyork-lh-rg will be forced to remain offline until its strong affinities are satisfied.
$ clrs set -p Resource_dependencies_offline_restart=zc1:pg1-targpool1-stor-rs newyork-lh-rs
$ clrg show -p Auto_start_on_new_cluster newyork-lh-rg 
=== Resource Groups and Resources === 
Resource Group:                               newyork-lh-rg
Auto_start_on_new_cluster:                      True
    **********
```
If the property is not True, type the following command :
```
$ clrg set -p Auto_start_on_new_cluster=True paris-lh-rg
```

Troubleshooting

If the validation is successful, the configuration status is set to OK, and the protection group is created on the local cluster. This protection group contains a remote replication component and application group that are configured almost identically to the replication component and application group on the remote cluster.

If the validation fails, the protection group is not created on the local cluster. Fix the cause of the error, and replicate it again.

If you have difficulties replicating the protection group configuration, see Debugging an Oracle Solaris ZFS Snapshot Protection Group.