Prerequisites and restrictions on package Easy Deployment in a
Metrocluster environment
Prerequisites and restrictions in a Metrocluster CAEVA environment
•Prerequisites:
–The replication pair must have been created already.
–The supported version of evainfo tool is installed.
–The Metrocluster version in all nodes of the cluster is Metrocluster CAEVA A.05.01 PHSS_41660 or superseding patch.
–The /etc/dtsconf/caeva.map file should have been created and distributed. This file is created using smispasswd and evadiscovery tools that are a part of MC CAEVA.
–The SMIS servers are up and reachable.
•Restrictions:
–The node name in Command View (EVA array management tool) should be same as the node name in the cluster configuration.
–The active management server should be listed in CAEVA.map file.
–If the physical disks are configured with
–The source vdisks in a DR group should be presented to all primary site nodes.
–The destination vdisks in a DR group should be presented to all recovery site nodes.
Prerequisites and restrictions in a Metrocluster SRDF environment
•Prerequisites:
–The replication pair must have been created already.
–The supported version of SYMCLI should have been installed.
•Restriction:
–If the physical disks are configured with
Prerequisites and restrictions in a Metrocluster XPCA environment
•Prerequisite:
–The device group pair must have been already created.
•Restrictions:
–A device group configuration with a HORCMPERM file is not currently supported.
–All physical devices must belong to exactly one replication pair (DEVICE GROUP).
–The device group monitor will not be configured as a part of Easy Deployment.
–If the physical disks are configured with
34
