Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy for Linux B.01.00.00, July 2013

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. You are require to interfere 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 the failover_policy parameter, in Metrocluster failover packages you can use any

of the 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 needs to fail over, it

fails over to a node in the same site as the node it last ran. If a configured node is not available

within the same site, the package fails over to a node on another site.

The site_preferred_manual failover policy enables automatic failover of packages within

a site and manual failover across sites.

Configure a cluster with sites to use either of these policies. For information on configuring

the failover policy to site_preferred or site_preferred_manual, see “Site Aware

Failover Configuration” (page 8).

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.

3. On the Cluster’s Home Page, click the Configuration Tab, and then select Create A Modular

Package option.

Configuring Metrocluster Packages 17