Storage Foundation issues
This section lists the known issues related to the Storage Foundation (SFW) component.
Related information
Storage management issues
In Microsoft Azure environment, InfoScale Storage cannot be used in cluster configurations that require shared storageIn a Microsoft Azure environment SFW fails to auto discover SSD media type for a VHDIncorrect message appears in the Event Viewer for a hot relocation operationA volume state continues to appear as "Healthy, Resynching"After a mirror break-off operation, the volume label does not show on the Slave nodeCVM cluster does not support node names with more than 15 charactersFor CSDG with mirrored volumes, sometimes disks incorrectly shows the yellow warning iconSSD is not removed successfully from the cache poolOn fast failover enabled configurations, VMDg resource takes a longer time to come onlineOn some configurations, the VSS snapshot operation may fail to add volumes to the snapshot setUsing Failover Cluster Manager you cannot migrate volumes belonging to Hyper-V virtual machines to a location with VMDg or Volume Manager Shared Volume resource typePerformance counters for Dynamic Disk and Dynamic Volume may fail to appear in the list of available countersVSS snapshot of a Hyper-V virtual machine on SFW storage does not work from NetBackupIn some cases, when 80 or more mirrored volume resources fail over to another node in CVM, some volume resources fault causing all to faultIn CVM, if subdisk move operation for CSDG fails because of a cluster reconfiguration, it does not start again automaticallyStale volume entries under MountedDevices and CurrentControlSet registries not removed after the volume is deletedSome arrays do not show correct Enclosure ID in VDIDIn some cases, EV snapshot schedules failIn CVM, Master node incorrectly displays two missing disk objects for a single disk disconnectDRL plex is detached across CVM nodes if a disk with DRL plex is disconnected locally from the node where volume is onlineError while converting a Microsoft Disk Management Disk Group created using iSCSI disks to an SFW dynamic disk groupSnapshot schedules intermittently fail on the Slave node after failoverIn VEA GUI, Tasks tab does not display task progress for the resynchronization of a cluster-shared volume if it is offlineSnapback operation from a Slave node always reports being successful on that node, even when it's in progress or resynchronization fails on MasterFor cluster-shared volumes, only one file share per Microsoft failover cluster is supportedAfter cluster-shared volume resize operation, free space of the volume is not updated on nodes where volume is offlineIssues due to Microsoft Failover Clustering not recognizing SFW VMDg resource as storage classIf fast failover is enabled for a VMDg resource, then SFW volumes are not displayed in the New Share WizardVolume information not displayed for VMDg and RVG resources in Failover Cluster ManagerFailover of VMDg resource from one node to another does not mount the volume when disk group volume is converted from LDM to dynamicvxverify command may not work if SmartMove was enabled while creating the mirrored volumeAfter installation of SFW or SFW HA, mirrored and RAID-5 volumes and disk groups cannot be created from LDMSome operations related to shrinking or expanding a dynamic volume do not workVEA GUI displays error while creating partitionsFor dynamic disk group configured as VMNSDg resource, application component snapshot schedules are not replicated to other nodes in a cluster if created using VSS Snapshot Scheduler WizardIn Microsoft failover cluster, if VxSVC is attached to Windows Debugger, it may stop responding when you try to bring offline a service group with VMDg resourcesIn some cases, updated VSS components are not displayed in VEA consoleStorage reclamation commands do not work when SFW is run inside Hyper-V virtual machinesUnknown disk group may be seen after deleting a disk groupWrong information related to disk information is displayed in the Veritas Enterprise Administrator (VEA) console. Single disk is displayed as two disks (harddisk and a missing disk)SFW Configuration Utility for Hyper-V Live Migration support wizard shows the hosts as Configured even if any service fails to be configured properlySystem shutdown or crash of one cluster node and subsequent reboot of other nodes resulting in the SFW messaging for Live Migration support to failChanging the FastFailover attribute for a VMDg resource from FALSE to TRUE throws an error messageA remote partition is assumed to be on the local node due to Enterprise Vault DNS alias checkAfter performing a restore operation on a COW snapshot, the "Allocated size" shadow storage field value is not getting updated on the VEA consoleMessaging service does not retain its credentials after upgrading SFW and SFW HAEnterprise Vault (EV) snapshots are displayed in the VEA console log as successful even when the snapshots are skipped and no snapshot is createdOn a clustered setup, split-brain might cause the disks to go into a fail stateTakeover and Failback operation on Sun Controllers cause disk lossMicrosoft failover cluster disk resource may fail to come online on failover node in case of node crash or storage disconnect if DMP DSMs are installedThe Veritas Enterprise Administrator (VEA) console cannot remove the Logical Disk Management (LDM) missing disk to basic onesAfter breaking a Logical Disk Manager (LDM) mirror volume through the LDM GUI, LDM shows 2 volumes with the same drive letterUnable to failover between cluster nodes. Very slow volume arrivalVDS errors noticed in the event viewer logAn extra GUI Refresh is required to ensure that changes made to the volumes on a cluster disk group having the Volume Manager Disk Group (VMDg) resource gets reflected in the Failover Cluster Manager ConsoleDR wizard cannot create an RVG that contains more than 32 volumesFor a cluster setup, configure the Veritas Scheduler Services with a domain user accountIf an inaccessible path is mentioned in the vxsnap create CLI, the snapshot gets created and the CLI failsIf snapshot set files are stored on a Fileshare path, then they are visible and accessible by all nodes in the VCS clusterSharing property of folders not persistent after system rebootMicrosoft Disk Management console displays an error when a basic disk is encapsulatedResults of a disk group split query on disks that contain a shadow storage area may not report the complete set of disksExtending a simple volume in Microsoft Disk Management Disk Group failsSFW cannot merge recovered disk back to RAID5 volumeRequest for format volume occurs when importing dynamic disk groupLogging on to SFW as a member of the Windows Administrator group requires additional credentialsCertain operations on a dynamic volume cause a warningAvoid encapsulating a disk that contains a system-critical basic volumeSharing property of folders in clustering environment is not persistentEntries under Task Tab may not be displayed with the correct nameAttempting to add a gatekeeper device to a dynamic disk group can cause problems with subsequent operations on that disk group until the storage agent is restartedASR fails to restore a disk group that has a missing diskMirrored volume in Microsoft Disk Management Disk Group does not resynchronizeExpand volume operation not supported for certain types of volumes created by Microsoft Disk ManagementMirrorView resource cannot be brought online because of invalid security fileKnown behavior with disk configuration in campus clusters