How to Remove a Replication Component From an Oracle Solaris ZFS Snapshot Protection Group

Language:

Note - You can also accomplish this procedure by using the Oracle Solaris Cluster Manager browser interface. First you must remove affinity and dependency from the replication logical hostname resource group and resource in case of zone cluster, as described below. Then click Partnerships, click the partnership name, click the protection group name, in the Data Replication Components section highlight the replication component name, and click Remove. After this is done, remove the Oracle Solaris Cluster private strings as described below in case either partner is a zone cluster. 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

Ensure that the following conditions are met:

The protection group is defined on the local cluster.
The protection group is deactivated on both partner clusters.
The replication component is managed by the protection group.

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.
If local partner is a zone cluster, remove the resource group affinity and resource dependency from logical hostname resource group and resource that is hosting the replication hostname in the global zone.
You would have set the affinity and dependency when creating the replication setup. Optionally, you can remove the logical hostname resource group and resource.

For example, suppose the logical hostname resource group in global zone is paris-lh-rg, and the resource is paris-lh-rs.

Type the following commands in the global zone of one node of the local partner to only remove the affinity and dependency:
```
# clrg set -p RG_affinities-=++paris:pg1-app-rg1-infr-rg paris-lh-rg 
# clrs set -p Resource_dependencies_offline_restart-=paris:pg1-srcpool1-stor-rs paris-lh-rs
```
Type the following commands in the global zone of one node of the local partner to remove the resource group and resource:
```
# clrs disable paris-lh-rs
# clrs delete paris-lh-rs 
# clrg delete paris-lh-rg
```
If the protection group and the replication component exists on the remote partner, then the replication configuration related to this replication component on the remote partner will be removed automatically.
If remote partner is a zone cluster, remove the resource group affinity and resource dependency from logical hostname resource group and resource that is hosting the replication hostname in the global zone of the remote partner. You would have set the affinity and dependency when creating the replication setup. Optionally, you can remove the logical hostname resource group and resource.

For example, suppose the logical hostname resource group in global zone is newyork-lh-rg, and the resource is newyork-lh-rs.

Type the following commands in the global zone of one node of the remote partner to only remove the affinity and dependency:
```
# clrg set -p RG_affinities-=++newyork:pg1-app-rg1-infr-rg newyork-lh-rg 
# clrs set -p Resource_dependencies_offline_restart-=newyork:pg1-targpool1-stor-rs newyork-lh-rs
```
Type the following commands in the global zone of one node of the remote partner to remove the resource group and resource:
```
# clrs disable newyork-lh-rs
# clrs delete newyork-lh-rs 
# clrg delete newyork-lh-rg
```
Remove the remote replication component.
Type the following command in one node of the local partner cluster.
```
# geopg remove-replication-component zfs-snap-replication-component zfs-snap-protection-group
```
zfs-snap-replication-component

Specifies the name of the replication component.

zfs-snap-protection-group

Specifies the name of the protection group.

If the replication component exists on the remote partner, then this command removes the replication component configuration from the remote partner automatically. This happens in an asynchronous manner.
If either partner is a zone cluster, you must remove the Oracle Solaris Cluster private string in the global zone of each partner that was created to store the SSH passphrase used by the replication setup.
For example, if paris is a global cluster and the other partner newyork is a zone cluster, and the replication component is repcom1, type the following command in one node of paris to remove the private string global:repcom1:local_service_passphrase.
```
$ clps delete global:repcom1:local_service_passphrase
```
Type the following command in the global zone on one node of newyork to remove the private string newyork:repcom1:local_service_passphrase.
```
$ clps delete newyork:repcom1:local_service_passphrase
```
(Optional) On each zone cluster partner, if no other existing replication components in the protection group use the zpool that was used by the removed replication component, delete the zpool's device group in the global zone of a zone cluster partner.
In this situation, only the SUNW.HAStoragePlus resource managing the zpool is in the application resource group. That zpool device group would have been created by the replication infrastructure when you had created the replication component that you just removed. The name of the such a zpool device group is same as the name of the zpool.

For example, type the following command in the global zone of a zone cluster partner newyork to delete the device group for the zpool targpool1:
```
$ cldg delete targpool1 
```
You are not required to perform this action as the presence of the zpool device group does not hamper any supported action on a zpool in the Oracle Solaris Cluster environment.