Storage Foundation 5.1 and MSCS

If you want to use Storage Foundation 5.1 to manage dual path disk you may run into the following:  if you install SF first and the disk groups appear fine.  Then if you try to configure MSCS and it can’t see the  disk.  You may need to add the MSCS Option, so you can also add “VRTS STORAGE FOUNDATION OPTION MICROSOFT CLUSTER 5.1 WIN FOR OS TIER ENTERPRISE EDITION STE LIC” license key and it in should indicate that the MSCS option is available.  However, when you go back to Add/Remove programs to select this option, it does not appear as a choice in the add/remove SF options. The Proper way to manage MSCS using SFW is VERITAS Storage Foundation for Windows (SFW) management data by creating disk groups from physical disk.  These disk groups are further divided into volumes, which can be mounted from the cluster nodes. Symantec recommends that you have a minimum of two volumes on shared disk, one each for SQL Server data and registry replication information.  If you will be configuring an MSDTC service group, create additional volumes for MSDTC log and MSDTC registry replication.  These volumes must be accessible for all cluster nodes. Note:  If your storage devices are SCSI-3 compliant, and you wish to use SCSI-3  Persistent  Group Reservation (PGR), YOU MUST ENAB LE scsi-3 SUPPORT USING THE VERITAS Enterprise Administrator (VEA- Control Panel – System Setting). See the VERITAS Storage Foundation Administrator’s Guide for more information. For Windows Server 2003, Windows Disk Management Compatible Dynamic Disk Group creates a disk group that is compatible with the disk groups created with Windows Disk Management and with earlier versions of Volume Manager for Windows products. For Windows Server 2008, Windows Disk Management Compatible Dynamic Disk Group creates a type of disk group that is created by Windows Disk Management (LDM). After the above processes one must import the disk groups from the VEA console and create the dynamic volumes.