Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

Maintaining the EMC SRDF Data Replication Environment
Normal Startup
The following is the normal Continentalclusters startup procedure. On the source disk site:
1. Start the source disk site.
# cmruncl -v
The source disk site comes up with ccmonpkg up. The application packages are down, and
ccmonpkg is up.
2. Manually start application packages on the source disk site.
# cmmodpkg -e <Application_pkgname>
3. Confirm source disk site status.
# cmviewcl -v
and
# cmviewconcl -v
4. Verify SRDF Links.
# symrdf list
On the target disk site, do the following:
1. Start the target disk site.
# cmruncl -v
The target disk site comes up with ccmonpkg up. The application packages (bkpkgX) stay
down, and ccmonpkg is up.
2. Do not manually start application packages on the target disk site; this will cause data
corruption.
3. Confirm target disk site status.
# cmviewcl -v
and
# cmviewconcl -v
Normal Maintenance
There might be situations where a package has to be taken down for maintenance purposes without
having the package move to another node. The following procedure is recommended for normal
maintenance of the Continentalclusters with EMC SRDF data replication:
1. Shut down the package with the appropriate command. Example:
# cmhaltpkg <pkgname>
2. Distribute the package configuration changes. Example:
# cmapplyconf - P <pkgconfig> (Primary cluster)
# cmapplyconf -P <bkpkgconfig> (Recovery cluster)
3. Start up the package with the appropriate Serviceguard command. Example:
# cmmodpkg -e <pkgname> (Primary cluster)
CAUTION: Never enable package switching on both the primary package and the recovery
package.
4. Halt the monitor package.
# cmhaltpkg ccmonpkg
308 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF