Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

RESYNC_WAIT_TIMEOUT expires and synchronization is still in progress, the package

fails to start with an error and will not start on any node in the cluster.

If the parameter RESYNC_WAIT_TIMEOUT is set to "no_timeout", then the package startup

waits for the resync until it either completes or fails.

NOTE: The RESYNC_WAIT_TIMEOUT value must not be greater than the value of

run_script_timeout parameter specified in the package configuration. Adjust the

run_script_timeout value as necessary to consider the RESYNC_WAIT_TIMEOUT

value in addition to the time taken for the full execution of each function in the package

startup.

m. To allow package to start up with non-current data, set AUTO_NONCURDATA to 1.

dts/3parrc/AUTO_NONCURDATA 1

The legal values for this parameter are “0” (default value) or “1”.

If AUTO_NONCURDATA is set to 1, Metrocluster software will allow the application to start

as long as the data is consistent; even though, it may not be current.

If AUTO_NONCURDATA is set to 0 (default value), Metrocluster software will not allow the

application to start if the data is not current. Require user intervention to bring the data

to current or to force the package to start on a node by creating FORCEFLAG in the

package directory (dts_pkg_dir).

n. Specify the time in seconds for Metrocluster to wait to determine that the Remote Copy

links are down. The default time in seconds to wait is 250.

dts/3parrc/PERIODIC_ASYNC_LINK_DOWN_TIMEOUT 250

For thefailover_policy parameter, Metrocluster failover packages can be configured to

use any Serviceguard defined failover policies. The site_preferred and site_preferred_manual

failover policies are introduced in Serviceguard specifically for Metrocluster configurations.

The site_preferred value implies that when a Metrocluster package has to fail over, it fails over

to a node within the same site. When there is no other configured node available within the

same site, the package fails over to a node of the remote site.

The site_preferred_manual failover policy provides automatic failover of packages within a

site, and manual failover across sites. To use either of these policies, the underlying cluster

must be configured with sites and each cluster nodes must be associated to a site. For

information on configuring the failover policy to site_preferred or site_preferred_manual, see

“Site Aware failover configuration” (page 11).

3. Validate the package configuration file.

# cmcheckconf -P pkgName.config

4. Apply the package configuration file.

# cmapplyconf -P pkgName.config

NOTE: After the modular Metrocluster 3PAR package is created, if the value of any

Metrocluster 3PAR parameter needs to be changed, then edit this package configuration file

and re-apply it.

Configuring a Metrocluster package using Serviceguard Manager

To configure a Metrocluster package using Serviceguard Manager:

1. Access one of the node’s System Management Home Page at http://<nodename>:2301.

2. Click Tools. If Serviceguard is installed, one of the widgets will have Serviceguard as an

option. Click Serviceguard Manager; link within the widget.

24 Configuring an application in a Metrocluster environment