This section contains procedures for the following tasks:
You can create protection groups that are not configured to use data replication. To create a protection group that does not use a data replication subsystem, omit the -d data-replication-type option when you use the geopg command. The geoadm status command shows a state for these protection groups of Degraded.
For more information, see Creating a Protection Group That Does Not Require Data Replication.
Before you create a protection group, ensure that the following conditions are met:
The local cluster is a member of a partnership.
The protection group you are creating does not already exist.
Protection group names are unique in the global Sun Cluster Geographic Edition namespace. You cannot use the same protection group name in two partnerships on the same system.
You can also replicate the existing configuration of a protection group from a remote cluster to the local cluster. For more information, see Replicating the Hitachi TrueCopy Protection Group Configuration to a Partner Cluster.
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.
Create a new protection group by using the geopg create command.
This command creates a protection group on all nodes of the local cluster.
# geopg create -s partnership-name -o local-role -d truecopy [-p property-settings [-p...]] \ protection-group-name |
Specifies the name of the partnership
Specifies the role of this protection group on the local cluster as either primary or secondary
Specifies that the protection group data is replicated by Hitachi TrueCopy
Sets the properties of the protection group
The properties you can set are the following:
Description – Describes the protection group
Timeout – Specifies the timeout period for the protection group in seconds
Nodelist – Lists the host names of the machines that can be primary for the replication subsystem
Cluster_dgs – Lists the device groups where the data is written
For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties.
Specifies the name of the protection group
For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities.
For more information about the geopg command, refer to the geopg(1M) man page.
The following example illustrates how to create a Hitachi TrueCopy protection group on cluster-paris, which is set as the primary cluster:
# geopg create -s paris-newyork-ps -o primary -d truecopy \ -p Nodelist=phys-paris-1,phys-paris-2 tcpg |
The following example illustrates how to create a Hitachi TrueCopy protection group, tcpg, for an application resource group, resourcegroup1, that is currently online on cluster-newyork.
Create the protection group without the application resource group.
# geopg create -s paris-newyork-ps -o primary -d truecopy \ -p nodelist=phys-paris-1,phys-paris-2 tcpg |
Activate the protection group.
# geopg start -e local tcpg |
Add the application resource group.
# geopg add-resource-group resourcegroup1 tcpg |
Before creating the protection group, the data replication layer validates that the horcmd daemon is running.
The data replication layer validates that the horcmd daemon is running on at least one of the nodes given in the Nodelist property. For more information about the horcmd daemon, see the Sun StorEdge SE 9900 V Series Command and Control Interface User and Reference Guide.
If the Cluster_dgs property is specified, then the data replication layer verifies that the device group specified is a valid Sun Cluster device group. The data replication layer also verifies that the device group is of a valid type.
The device groups specified in the Cluster_dgs property must be written to only by applications that belong to the protection group. This property must not specify device groups that receive information from applications outside of the protection group.
A Sun Cluster resource group is automatically created when the protection group is created.
This resource in this resource group monitors data replication. The name of the Hitachi TrueCopy data replication resource group is rg-tc-protection-group-name.
These automatically created replication resource groups are for Sun Cluster Geographic Edition internal implementation purposes only. Use caution when you modify these resource groups by using Sun Cluster commands.
Before modifying the configuration of your protection group, ensure that the protection group you want to modify exists locally.
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.
Modify the configuration of the protection group.
This command modifies the properties of a protection group on all nodes of the local cluster. If the partner cluster contains a protection group of the same name, this command also propagates the new configuration information to the partner cluster.
# geopg set-prop -p property-settings [-p...] \ protection-group-name |
Sets the properties of the protection group.
For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties.
Specifies the name of the protection group.
For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities.
For more information about the geopg command, refer to the geopg(1M) man page.
The following example illustrates how to modify the Timeout property of the protection group that was created in Example 10–2:
# geopg set-prop -p Timeout=400 tcpg |
When the geoadm status output displays that the Configuration status of a protection group is Error, you can validate the configuration by using the geopg validate command. This command checks the current state of the protection group and its entities.
If the protection group and its entities are valid, then the Configuration status of the protection groups is set to OK. If the geopg validate command finds error in the configuration files, then the command displays a message about the error and the configuration remains in the error state. In such a case, you can fix the error in the configuration, and issue thegeopg validate command again.
Before validating the configuration of a protection group, ensure that the protection group you want to validate exists locally and that the common agent container is online on all nodes of both clusters in the partnership.
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.
Validate the protection group's configuration.
This command validates the configuration of the protection group on the local cluster only. To validate the protection group configuration on the partner cluster, issue the command again on the partner cluster.
# geopg validate protection-group-name |
Specifies a unique name that identifies a single protection group
The following example illustrates how to validate a protection group.
# geopg validate tcpg |
During protection group validation, the Hitachi TrueCopy data replication layer makes the following validations:
The data replication layer confirms that the horcmd daemon is running on at least one of the nodes given in the Nodelist property of the protection group. The data replication layer also confirms that a path to a Hitachi TrueCopy storage device exists from the node on which the horcmd daemon is running.
For more information about the horcmd daemon, see the Sun StorEdge SE 9900 V Series Command and Control Interface User and Reference Guide
If the Cluster_dgs property is specified, then the data replication layer verifies that the device group specified is a valid Sun Cluster device group by using the scstat -D command. The data replication layer also verifies that the device group is of a valid type.
The data replication layer validates the properties of each Hitachi TrueCopy device group that has been added to the protection group.
If you want to delete the protection group everywhere, you must run the geopg delete command on each cluster where the protection group exists.
Before deleting a protection group, ensure that the following conditions are met:
The protection group you want to delete exists locally.
The protection group is offline on the local cluster.
You must remove the application resource groups from the protection group in order to keep the application resource groups online while deleting the protection group. See Example 10–7 and Example 10–10 for examples of this procedure.
Log in to a nodes on the primary cluster.
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.
Delete the protection group.
This command deletes the configuration of the protection group from the local cluster. The command also removes the replication resource group for each Hitachi TrueCopy device group in the protection group. This command does not alter the pair state of the Hitachi TrueCopy device group.
# geopg delete protection-group-name |
Specifies the name of the protection group
To also delete the protection group on the secondary cluster, repeat step 1 and step 2 on cluster-newyork.
The following example illustrates how to delete a protection group from both partner clusters.
The cluster-paris is the primary cluster. For a reminder of the sample cluster configuration, see Figure 2–1.
# rlogin cluster-paris -l root cluster-paris# geopg delete tcpg # rlogin cluster-newyork -l root cluster-newyork# geopg delete tcpg |
The following example illustrates how to keep two application resource groups, apprg1 and apprg2, online while deleting their protection group, tcpg. Remove the application resource groups from the protection group, then delete the protection group.
# geopg remove-resource-group apprg1,apprg2 tcpg # geopg stop -e global tcpg # geopg delete tcpg |