geopg(1M) Man Page

This section discusses errors and omissions from the geopg(1M) man page.

Difference Between Activating and Starting a Protection Group Is Not Clearly Defined (6438452)

Problem Summary: The description of the geopg start command in thegeopg(1M) man page is unclear.

Workaround: The -e option defines the scope of the geopg start command. If you specify -e local, the geopg start command is run on the cluster partner where the command is given. If you specify -e global, the geopg start command is run on both clusters in the partnership.

When the geopg start command is run on the primary cluster, either by running the geopg start -e local command on the primary cluster or by running the geopg start -e global command, the Sun Cluster Geographic Edition software brings online resource groups on the primary cluster only by using the scswitch -Z -g command.

When the geopg start command is run on the secondary cluster of the partnership, either as a result of running the geopg start -e local command on the secondary cluster or by running the geopg start -e global command, resource groups are not be started on the secondary cluster. The resource group are put in the unmanaged state by using the scswitch -u command.

The geopg start command activates the protection group on both the primary and the secondary clusters, which starts the Sun Cluster Geographic Edition management of the resource groups. However, the resource groups start, or are brought online, only on the primary cluster.

Depending on the role of the protection group, activating the protection group might not start the resource groups that the protection group contains.

Incorrect Definition of TrueCopy cluster_dgs Property in geopg(1M) man Page (6454231)

Incorrect Information: The geopg(1M) man page indicates that tuning of the cluster_dgs property is allowable at any time.

Correct Information: You can tune the cluster_dgs property only when the protection group is offline on both partner clusters.