Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00

there are no dependents on the legacy CFS mount point MNP packages. In case CFS
mount point MNP packages have not been configured, this step will ensure that there are
no dependents on the legacy CVM diskgroup MNP packages:
# cmgetconf -p <application_pkg_name> > <backedup_appl_config>
# cmdeleteconf -p <application_pkg_name>
• Use the cfsmntadm command to delete all the legacy disk group and mount point MNP
packages managed by the Site Controller from a node in the recovery site. Use the
cfsdgadm command if there are no CFS mounts configured.
# cfsmntadm delete <mount point>
or
# cfsdgadm delete <cvm_diskgroup_name>
• Configure all the CVM diskgroups and the mount points required by an application in a
single modular SMS CFS /CVM package. Add the EMS resource and apply the
configuration.
# cmapplyconf -P <modular_cfs_package_file>
• Edit the application's configuration file and change its dependency from legacy CFS
mount point or CVM disk group MNP packages to the newly created modular SMS
CFS/CVM package. Apply this package configuration.
cmapplyconf -P <backedup_application_config>
• Get the current configuration of the Site Controller. Modify the Site Controller configuration
with the new set of packages that must be managed on the recovery site. Leave the set
of packages that are being managed on the primary site as it is.
3. Start the Site Controller again on the primary site.
4. Halt the Site Controller package on the primary site. This will halt all the complex workload
packages that are running on the primary site.
5. Restart the Site Controller on the recovery site. The complex workload will start up on the
recovery site using the new modular SMS CFS/CVM packages.
6. Halt the Site Controller that is running on the recovery site in DETACH mode.
7. Repeat step 2 that was performed on the recovery site initially, on the primary site
8. Start the Site Controller again on the recovery site.
You can either continue the Site Controller package to run on the recovery site or move it back to
the primary site.
Upgrading the Site Controller package
When using Metrocluster with Continuous Access XP A.10.00 or later, the Site Controller Package
can be upgraded to use the Metrocluster modules. By upgrading the Site Controller Package, the
environment file parameters are included in the Site Controller Package configuration file. The
Metrocluster environment file need not be edited or distributed to all the nodes. For more information
about configuring Site Controller package in modular style see “ Configuring Site Controller
package using command line interface” (page 47).
To upgrade the Site Controller Package in a cluster:
1. Upgrade the Site Controller Package to the latest version of Metrocluster.
# cmmakepkg -u <pkg_name> -m dts/sc <output_pkg.ascii>
2. Add Metrocluster module to the Site Controller package configuration file.
# cmmakepkg -i <output_pkg.ascii> -m dts/mcxpca -t <path_to_env_file>
<migrated_output_pkg.ascii>
178 Legacy packages