Perform the following steps to install SFW HA server components
The systems that belong to the domain in which you have logged in are listed in the Available Systems list. Select one or more systems and click the right arrow to move them to the Selected Systems list. Click OK.
If you select "User entered license key" as your license type, the License Details panel appears by default. On the License Details panel, enter the license key and then click Add. You can add multiple licenses for the various product options you want to use.
For details, See About installing SFW or SFW HA.
Storage Foundation Options
Veritas Volume Replicator (VVR)
Veritas Volume Replicator (VVR) replicates data across multiple sites for disaster recovery.
FlashSnap allows you to create and maintain split-mirror, persistent snapshots of volumes and application components. FlashSnap supports VSS based snapshots to provide application data in a consistent state after the application is restored.
Replace Disk Management Snap-in with SFW VEA GUI
Replaces the Disk Management Snap-in in the Windows Computer Management console and the Server Manager console with the Veritas Enterprise Administrator GUI for Windows Server 2008.
DMP Device Specific Modules (DSMs)
Compellent array (VCOMPLNT)
Dell EqualLogic array (VEQLOGIC)
EMC Clarion (VEMCCLAR)
EMC Symmetrix/DMX (VEMCSYMM)
EMC VPLEX array (VEMCVPLX)
FUJITSU ETERNUS 2000 array (VFUJITSUAA)
Hitachi 95xx-AMS-WM (VHDSAP)
Hitachi TagmaStore/HP XP (VHDSAA)
HP 2000 array (VHPMSA2)
HP EVA-MSA (VHPEVA)
HUAWEI S5300/S2300 array (VHUAWEIAP)
IBM DS AP (VIBMAPDS)
IBM DS6000 (VIBMAP)
IBM DS4000/SUN 6000 (VENGAP)
IBM DS8000/ESS (VIBMAADS)
IBM XiV Storage System (VXIV)
NEXSAN SATA/SAS Beast, E60/E18 array (VNEXSAN)
SUN Array - (VSUN)
XioTech Array (VXIOTECH)
Symantec maintains a Hardware Compatibility List (HCL) for Veritas Storage Foundation and High Availability Solutions for Windows. The HCL provides information on HBAs and firmware that have been tested with each supported array. Check the HCL for details about your hardware before installing or using DMP DSMs.
Do not use a DMP DSM together with a third-party DSM for the same array. Only one DSM at a time can claim the LUNs in an array. According to Microsoft Multipath I/O (MPIO) documentation, if multiple DSMs are installed, the Microsoft MPIO framework contacts each DSM to determine which is appropriate to handle a device. There is no particular order in which the MPIO framework contacts the DSMs. The first DSM to claim ownership of the device is associated with that device. Other DSMs cannot claim an already claimed device. Therefore, to ensure that the DMP DSM claims the LUNs of an array, no other DSM should be installed for that same array.
Veritas Cluster Server Options
Global Cluster Option
Global Cluster Option (GCO) enables you to link the clusters located in different geographies.
This provides wide-area failover and disaster recovery.
Fast failover improves the failover time taken by storage resources during the service group failovers, in a clustered environment. Fast failover is particularly noticeable in clusters having multiple storage stacks configured, typically over 20 disk groups and over 150 volumes.
Note that the wizard fails to proceed with the installation, unless all the selected systems have passed the validation checks and are ready for installation. In case the validation checks have failed on any of the system, review the details and rectify the issue. Before you choose to proceed with the installation, select the system and click Re-verify to re-initiate the validation checks for this system.
Note that the Automatically reboot systems after installer completes operation check box is selected by default. This will reboot all the selected remote systems immediately after the installation is complete on the respective system. If you do not want the wizard to initiate this auto reboot, clear the selection of Automatically reboot systems after installer completes operation check box.
If you have installed SFW with Microsoft Failover Cluster, but if Microsoft Failover Cluster is not yet configured, you must register the Volume Manager Disk Group resource after configuring the Microsoft clustering software.