Some protection groups do not require data replication. If you are using the Disaster Recovery framework to manage only resource groups, you can create protection groups that do not replicate data.
This section provides the following procedures:
How to Create a Protection Group That Is Configured Not to Use Data Replication
How to Add an Application Resource Group to a Protection Group That Does Not Use Data Replication
To create a protection group that uses data replication, see the appropriate Oracle Solaris Cluster guide for your data replication product:
Oracle Solaris Cluster Data Replication Guide for Oracle Data Guard
Oracle Solaris Cluster Data Replication Guide for ZFS Snapshots
Oracle Solaris Cluster Remote Replication Guide for Oracle ZFS Storage Appliance
Before You Begin
Before you create a protection group without data replication, ensure that the following conditions are met:
The local cluster is a member of a partnership.
The protection group that you are creating does not already exist.
You must be assigned the Geo Management rights profile to complete this procedure. For more information, see Disaster Recovery Framework Rights Profiles.
This command creates a protection group on the local cluster.
# geopg create -s partnership -o local-role \ [-p property [-p …]] protection-group
Specifies the name of the partnership.
Specifies the role of this protection group on the local cluster as either Primary or Secondary.
Specifies the properties of the protection group.
You can specify the following properties:
Describes the protection group.
Specifies whether to allow any dependencies between resource groups and resources that belong to this protection group and resource groups and resources that do not belong to this protection group.
Specifies a string that follows system-defined arguments at the end of the command line when the role-change callback command runs.
Specifies the path to an executable command. This path should be valid on all nodes of all partner clusters that can host the protection group. The script is invoked during a switchover or takeover on the new primary cluster when the protection group is started on the new primary cluster. The script is invoked on the new primary cluster after the data replication role changes from secondary to primary and before the application resource groups are brought online. If the data replication role change does not succeed, then the script is not called.
Specifies the timeout period for the protection group in seconds. You can change the timeout period from the default value depending on the complexity of your data replication configuration.
For more information about the properties you can set, see Appendix A, Standard Disaster Recovery Framework Properties, in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
Specifies the name of the protection group.
Log in to a node on the partner cluster to replicate the protection group to the partner cluster.
# geopg get --partnership <partnership-name> <protection group name>
For information about the names and values that are supported by Disaster Recovery framework software, see Appendix B, Legal Names and Values of Disaster Recovery Framework Entities, in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
For more information about the geopg command, refer to the geopg(8) man page.
This example creates a protection group that is configured to not use data replication.
# geopg create -s paris-newyork-ps -o primary example-pg
Next Steps
Go to How to Add an Application Resource Group to a Protection Group That Does Not Use Data Replication.
See Also
To delete a protection group, see Deleting Protection Groups and Data Replication Components in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
You must be assigned the Geo Management rights profile to complete this procedure. For more information, see Disaster Recovery Framework Rights Profiles.
# 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
# geopg show protection-group | grep -i external_dependency_allowed
If necessary, change the property value to TRUE.
# geopg set-prop -p External_Dependency_Allowed=TRUE protection-group
The Disaster Recovery framework requires that the application resource group be in the UNMANAGED state on the secondary cluster.
If the protection group is stopped on the primary cluster, the application resource group must also be unmanaged on the primary cluster.
If the protection group is active on the primary cluster, the application resource group must be in the UNMANAGED or ONLINE state on the primary cluster.
For instructions, see one of the following procedures:
# geopg add-resource-group application-resource-group protection-group
Specifies the name of an application resource group. You can specify more than one resource group in a comma-separated list.
Specifies the name of the protection group. The command adds an application resource group to a protection group on the local cluster. Then, if the partner cluster contains a protection group of the same name, the command propagates the new configuration information to the partner cluster.
For information about the names and values that are supported by the Disaster Recovery framework, see Appendix B, Legal Names and Values of Disaster Recovery Framework Entities, in Administering the Disaster Recovery Framework for Oracle Solaris Cluster 4.4.
After the application resource group is added to the protection group, the application resource group is managed as an entity of the protection group. The application resource group is now affected by protection group operations such as start, stop, switchover, and takeover.