Replicating a Sun ZFS Storage Appliance Protection Group Configuration to a Partner Cluster

After you have configured remote replication, resource groups, and resources on your primary and secondary clusters and you have created a protection group for those entities on the primary cluster, you can replicate the configuration of the protection group to the secondary cluster.

How to Replicate the Sun ZFS Storage Appliance Protection Group Configuration to a Partner Cluster

Before You Begin

Before you replicate the configuration of a Sun ZFS Storage Appliance protection group to a partner cluster, ensure that the following conditions are met:

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

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

• Application resource groups are online only on the primary cluster and in the unmanaged state on the secondary cluster.

Perform this procedure from phys-newyork-1, which is a 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.

1. Assume the root role or assume a role that is assigned the Geo Management RBAC rights profile.

   For more information about RBAC, see Geographic Edition Software and RBAC in Oracle Solaris Cluster Geographic Edition System Administration 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 Sun ZFS Storage Appliance software.

   ---

2. Ensure that the Auto_start_on_new_cluster property of the resource group is set to False.

   # clresourcegroup show -p Auto_start_on_new_cluster resource-group

   If necessary, change the property value to True.

   # clresourcegroup set -p Auto_start_on_new_cluster=True resource-group

3. Replicate the protection group configuration to the partner cluster.

   phys-newyork-1# geopg get -s ps-name pg-name

   -s ps-name

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

   pg-name

   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, modify the XML file for the expected configuration on the secondary cluster. Then 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 Software Installation Guide and the cluster(1CL)and clresource(1CL) man pages.

   ---

Example 1-9 Replicating a Sun ZFS Storage Appliance Protection Group to a Partner Cluster

The following example replicates the configuration of zfssa-pg from cluster-paris to cluster-newyork.

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

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 replicated component and application group that are configured almost identically to the replicated 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 adding the component to the protection group, see Debugging a Sun ZFS Storage Appliance Protection Group.