Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA P6000 for Linux B.01.00.00

P6000 Continuous Access does not resynchronize the source and destination Vdisks upon

links recovery. This helps in maintaining data consistency.

2. Take a local replication copy of the destination Vdisks using HP P6000 Business Copy software

so that there is consistent copy available for recovery.

3. Change the Continuous Access link state to resume mode. This initiates the normalization upon

Continuous Access link recovery.

The above steps ensures that even though the primary site fails while copy is in progress, the

destination Vdisk can be used after restoring the data from the BC volume.

Planned maintenance

Node maintenance

If you take a node down for maintenance, package failover and quorum calculation is based on

the remaining nodes. Make sure that the nodes are taken down evenly at each site, and that

enough nodes remain on-line to form a quorum if a failure occurs. Planned maintenance is treated

the same as a failure by the cluster.

Metrocluster package maintenance

There might be situations when the package needs to be taken down for maintenance purposes

without moving the package to another node. The following procedure is recommended for normal

maintenance of the Metrocluster with Continuous Access EVA P6000 for Linux:

1. Disable packge switching.

# cmmodpkg -d <pkgname>

2. If SMI-S user credentials or ports are being changed, update the smis.conf file and

re-generate the caeva.map file. Distribute the updated caeva.map file to all the nodes of

the cluster.

3. If there are changes to the package attributes, edit the configuration file, and then apply the

updated package configuration.

# cmapplyconf -P <pkgname.config>

4. Start the package with the appropriate Serviceguard command.

# cmmodpkg -e <pkgname>

Failback

If the primary site is restored after a failover to the recovery site, you may want to fail back the

package to the primary site. Manually resync the data from the recovery site to the primary site.

After resynchronization is complete, halt the package on the recovery site, and restart it on the

primary site. Metrocluster performs a failover of the storage, which returns the SOURCE status to

the primary VDisks.

Administering Metrocluster with Serviceguard Manager

To administer Metrocluster or the packages configured under Metrocluster 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 Administration Tab and choose the available options

when required. Choose appropriate packages for the required option.

32 Administering Metrocluster