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

Consider the following guidelines:
• The Site Controller package control log file can be specified using the following attribute
script_log_file in the Site Controller package configuration file.
Serviceguard defaults the Site Controller package logs to the default log destination. The
default log destination for a given Site Controller Package is /var/adm/cmcluster/log
<Site_controller_package_name>.log.
• HP recommends that you specify the Site Controller Package log file under the directory
specified for the dts/dts/dts_pkg_dir attribute in the Site Controller Package configuration
file.
• The Metrocluster storage preparation modules must log to the Site Controller package log file.
• The Site Safety Latch mechanism logs are saved in the /etc/opt/resmon/log/api.log
file.
Cleaning the site to restart the Site Controller package
The Site Controller package startup on a site can fail for various reasons. The Site Safety Latch will
be in a special state: INTERMEDIATE. In this state, the Site Controller package cannot be started
from either of the sites. A special tool called cmresetsc is provided to cleanup a site under this
condition. This tool cleans the Metrocluster environment in site for the Site Controller package. But,
it does not clean any of the managed packages for the Site Controller Package. Any issues in the
packages managed by Site Controller package must be fixed by the operator and the package’s
node switching must be enabled before restarting the Site Controller package.
When the Site Controller package fails, the following message appears in the Site Controller
package log file on the node where it was last running or was last started:
Check the package log files on all nodes of all other packages managed
by the Site Controller package to identify issues in those packages.
Steps to clean a site for a site aware disaster tolerant application as follows:
1. Clean the Site Safety Latch on the site by running the cmresetsc tool.
On a node from the site, run the following command:
# /usr/sbin/cmresetsc <Site_controller_package_name>
IMPORTANT: You must be the root user to run this command.
2. Check the package log file of the Site Controller Package on the node it failed on and fix any
reported issues.
3. Enable node switching for the Site Controller package on that node.
# cmmodpkg –e -n <node name> <site_controller_package_name>
4. Check the package log file on all nodes of the MNP packages managed by the Site Controller
package on the site.
5. Fix any issues reported in the package log files and enable node switching for the MNP
packages on the failed nodes.
# cmmodpkg -e -n <node 1 name> -n <node 2 name> <MNP Package name>
6. Restart the Site Controller package and enable global switching.
# cmrunpkg <site_controller_package_name>
# cmmodpkg -e <site_controller_package_name>
In addition to the cmresetsc tool, use the cmviewsc tool to view information on the Site Controller
package managed workload package. This tool is available in the /usr/sbin directory. Run the
following command to use the cmviewsc tool.
# /usr/sbin/cmviewsc [-v] [site_controller_package_name]
Troubleshooting Metrocluster SADTA 61