When you activate a protection group, it assumes the role that you assigned to it during configuration.
For more information about configuring protection groups, see How to Create and Configure a Sun StorEdge Availability Suite 3.2.1 Protection Group.
You can activate a protection group in the following ways:
Globally, meaning you activate a protection group on both clusters where the protection group is configured
On the primary cluster only
On a secondary cluster only
When a protection group is activated on a primary or secondary cluster, the outcome depends on the type of data replication you are using. If you are using Sun StorEdge Availability Suite 3.2.1 software, data replication can only be started from the primary cluster. So, when you activate a protection group on the secondary cluster, the activation will not start data replication.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.
Activate the protection group.
This command activates the protection group on the local cluster.
When you activate a protection group on the primary cluster, its application resource groups are also brought online.
# geopg start -e scope [-n] AVS-protection-group |
Specifies the scope of the command
If the scope is Local, then the command operates on the local cluster only. If the scope is Global, the command operates on both clusters that deploy the protection group.
The property values, such as Global and Local, are not case sensitive.
Prevents the start of data replication at protection group startup
If you omit this option, the data replication subsystem starts at the same time as the protection group and the command performs the following operations on each device group in the protection group:
Verifies that the role configured for the replication resource is the same as the role of the protection group on the local cluster.
Verifies that the role of the volume sets associated with the device group is the same as the role of the protection group on the local cluster.
If the role of the protection group on the local cluster is secondary, unmounts the local volumes defined in all volume sets associated with the device group.
If the role of the protection group on the local cluster is primary, enables the autosynchronization feature of the Sun StorEdge Availability Suite 3.2.1 remote mirror software. Also, resynchronizes the volume sets associated with the device group.
Specifies the name of the protection group
The geopg start command uses the scswitch -Z -g resource-groups command to bring resource groups and resources online. For more information about using this command, see the scswitch(1M) man page.
The geopg start command performs the following actions if the role of the protection group is primary on the local cluster:
The command executes a script defined in the RoleChange_ActionCmd.
The command brings the application resource groups in the protection group online on the local cluster.
If the application resource group is a failover type resource group that shares affinities with one of the device groups in the same protection group, the command adds strong, positive affinities and failover delegation between the application resource group and the lightweight resource group.
The application resource group must not have strong, positive affinities with failover delegation. Otherwise, the attempt to add strong, positive affinities with failover delegation with the lightweight resource group will fail.
The command creates strong dependencies between the HAStoragePlus resource in the application resource group and the HAStoragePlus resource in the lightweight resource group for this device group.
If the command fails, the Configuration status might be set to Error, depending on the cause of the failure. The protection group remains deactivated, but data replication may be started and some resource groups may be brought online. You should run geoadm status to get the status of your system.
If the Configuration status is set to Error, revalidate the protection group by using the procedures described in How to Validate a Sun StorEdge Availability Suite 3.2.1 Protection Group.
The following example illustrates how to activate a protection group globally:
# geopg start -e global avspg |
The following example illustrates how to activate a protection group on a local cluster only. This local cluster might be a primary cluster or a secondary cluster, depending on the cluster's role.
# geopg start -e local avspg |
You can deactivate a protection group in the following ways:
Globally, meaning you deactivate a protection group on both the primary and the secondary cluster where the protection group is configured
On the primary cluster only
On the secondary cluster only
The result of deactivating a protection group on primary or secondary cluster depends on the type of data replication you are using. If you are using Sun StorEdge Availability Suite 3.2.1 software, data replication can only be stopped from the primary cluster. So, when you deactivate a protection group on the secondary cluster, this deactivate command will not stop data replication.
Log in to one of the cluster nodes.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.
Deactivate the protection group.
This command deactivates the protection group on all nodes of the local cluster.
When you deactivate a protection group, its application resource groups are also taken offline.
# geopg stop -e scope [-D] protection-group-name |
Specifies the scope of the command
If the scope is local, then the command operates on the local cluster only. If the scope is global, the command operates on both clusters where the protection group is deployed.
The property values, such as global and local, are not case sensitive.
Specifies that only data replication should be stopped while leaving the protection group online
If you omit this option, the data replication subsystem and the protection group are both stopped. If the role of the protection group on the local cluster is primary, omitting the -d option also results in the following actions:
Removal of resource group affinities and resource dependencies between the application resource groups in the protection group and the internal resource group
Taking the application resource groups offline and putting them in an unmanaged state
Specifies the name of the protection group
If the role of the protection group is primary on the local cluster, the geopg stop command disables the autosynchronization of each device group and places the volume sets into logging mode.
If the geopg stop command fails, execute the geoadm status command to see the status of each component. For example, the Configuration status might be set to Error depending upon the cause of the failure. The protection group might remain activated even though some resource groups might be taken offline. The protection group might be deactivated with data replication running.
If the Configuration status is set to Error, revalidate the protection group by using the procedures described in How to Validate a Sun StorEdge Availability Suite 3.2.1 Protection Group.
The following example illustrates how to deactivate a protection group on all clusters:
# geopg stop -e global avspg |
The following example illustrates how to deactivate a protection group on the local cluster:
# geopg stop -e local avspg |
The following example illustrates how to stop only data replication on a local cluster:
# geopg stop -e local -D avspg |
If the administrator decides later to deactivate both the protection group and its underlying data replication subsystem, the administrator can reissue the command without the -d option:
# geopg stop -e local avspg |
The following example illustrates how to keep two application resource groups, apprg1 and apprg2, online while deactivating their protection group, avspg.
Remove the application resource groups from the protection group.
# geopg remove-resource-group apprg1,apprg2 avspg |
Deactivate the protection group.
# geopg stop -e global avspg |