Error Message

N/A

Issue is due to Microsoft Failover Clustering not recognizing SFW VMDg resource as storage class.

The following issues are observed because of this limitation in a Microsoft Failover Clustering environment:

■ Unable to configure file shares on volumes that are managed using SFW. If you create disk groups and volumes using SFW and then try to configure a VMDg, RVG, or Volume Manager Shared Volume resource in a Microsoft failover cluster, the Failover Cluster Manager snap-in (Microsoft Failover Clustering GUI) does not display the SFW volumes. As a result, you cannot configure file shares on those volumes. For more information, refer to Microsoft KB2795993 and KB2796000.

■ Unable to perform storage related operations on SFW VMDg resource from Microsoft Failover Cluster Manager If you create disk groups and volumes using SFW and configure a VMDg resource in a Microsoft failover cluster, then the Failover Cluster Manager snap-in does not list any storage related operations for the VMDg resource. This is seen when the VMDg resource is part of Available Storage group. The storage operations are enabled if the resource is part of a role. (2999555, 3000675) For more information, refer to Microsoft KB2795997.

■ Unable to configure SQL when databases reside on volumes managed using SFW If you try to install SQL in a Microsoft Failover Clustering environment and provide SFW volumes for SQL data directories, the SQL installation fails with the following error: The volume that contains the SQL data directory does not belong to the cluster group. (3008299) Note that these issues are restricted to file shares and Microsoft applications supported on Windows Server 2012. You can however use SFW and configure custom applications in a Microsoft Failover Clustering environment. This issue does not affect configuration and failover operations for custom applications in Microsoft Failover Clustering.

As a workaround, you can use Powershell cmdlets or Windows Explorer to configure file shares. Then, using Microsoft Failover Clustering, you can enable continuous availability.

Microsoft has acknowledged this as an issue and Veritas is actively working with Microsoft to get this fixed in Microsoft Failover Clustering. For more information, refer to the following Microsoft KB article: https://support.microsoft.com/kb/2804526

 

Applies To

Storage Foundation for Windows 6.0.2

Storage Foundation for Windows 6.1

Windows Server 2012

Windows Server 2012  R2