User's Guide

# cmdeploycl -s <site1_name> -n <node1> -n <node2> -s <site2_name> -n
<node3> -n <node4> -c <cluster_name> -q <quorum_server> -cfs
For example,
# cmdeploycl -s siteA -n node1 -n node2 -s siteB -n node3 -n node4 -c
site_cluster -q quorum.server.com -cfs
This creates a cluster with two sites with the CVM infrastructure configured via the SG-CFS-pkg
System Mutlti-node (SMNP) package. For additional information on cmdeploycl, see the cmdeploycl
man page, cmdeploycl (1m).
Setting up the Complex Workload Redundantly in the Metrocluster
For SADTA, the complex workload is configured redundantly in the cluster. A separate set of
packages must be used to configure the complex workload at each site. The data of the complex
workload must be replicated between the disk arrays at each site.
The storage device for a complex workload must first be configured at the site with the source disk
of the replication disk group. Then, a complex workload package stack should be created at this
site. It is only at this stage that an identical complex workload using the target replicated disk must
be configured with the complex workload stack at the other site.
The site from where the data is replicated is referred as Source Disk Site and the site to which the
data is replicated is referred as Target Disk Site in this section.
Following are the topics discussed in this section:
• “Configuring the Storage Device for the Complex Workload at the Source Disk Site” (page 347)
• “Configuring the Complex Workload Stack at the Source Disk Site” (page 351)
• “Halting the Complex Workload at the Source Disk Site” (page 352)
• “Preparing the Replicated Disk at the Target Disk Site” (page 352)
• “Configuring the Storage Device for Complex Workload at the Target Disk Site” (page 353)
• “Configure the Identical Complex Workload Stack at the Recovery SIte” (page 355)
• “Halting the Complex Workload on the Recovery Site” (page 355)
Configuring the Storage Device for the Complex Workload at the Source Disk Site
The shared storage device for storing the data of a complex workload can be configured using
CFS, CVM or SLVM. When using CFS, appropriate Cluster File Systems must be created over the
replicated disks. When using SLVM or CVM, appropriate SLVM volume groups or CVM disk groups
must be created with required raw volumes over the replicated disks. The procedures to create the
storage device differ when using CFS, CVM or SLVM.
Following are the topics discussed in this section:
• “Configuring the Storage Device using SG SMS CFS or CVM in a Modular Style Package”
(page 347)
• “Configuring the Storage Device using CFS in a Legacy Style Package” (page 348)
• “Configuring the Storage Device using SG SMS CVM in a Legacy Style Package” (page 349)
• “Configuring the Storage Device using VERITAS CVM” (page 350)
• “Configuring the Storage Device using SLVM” (page 350)
Configuring the Storage Device using SG SMS CFS or CVM in a Modular Style Package
By using modular style packages, Serviceguard enables you to manage all the CVM diskgroups
and the CFS mountpoints required by an application within a single package. This helps in
significantly reducing the number of packages to be managed by a cluster administrator.
Configuring Complex Workloads using Site Aware Disaster Tolerant Architecture 347