Maintaining 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
and
#cmviewconcl -v
4.Verify SRDF Links.
#symrdf list
On the target disk site, do the following:
1.Start the target disk site.
# cmruncl
The target disk site comes up with ccmonpkg up. The application packages are in halted state, and ccmonpkg is running.
2.Do not manually start application packages on the target disk site; this will cause data corruption.
3.Confirm target disk site status.
# cmviewcl
and
# cmviewconcl -v
Maintaining 3PAR Remote Copy data replication environment
While the package is running, a manual storage failover on Remote Copy volume group outside of Metrocluster with 3PAR Remote Copy software can cause the package to halt due to unexpected condition of the 3PAR Remote Copy virtual volumes. HP recommends that no manual storage failover be performed while the package is running.
If the Remote Copy replication was stopped due to link failures, you can manually start the replication even while the package is running. You do not have to manually start the replication if the auto_recover option is set for the Remote Copy volume group.
Viewing the Remote Copy volume group details
To associate the Remote Copy volume group name with the package, run the cmgetpkgenv command:
# cmgetpkgenv <pkg_name>
To list the various properties of 3PAR Remote Copy volume group, run the CLI command showrcopy command.
You can view the Remote Copy volume group details using HP 3PAR Management Console.
66 Administering Continentalclusters
