Storage management limitations
This section lists the software limitations related to the storage management components; these components are available as part of the InfoScale Foundation, InfoScale Storage, and InfoScale Enterprise products.
Related information
Limitations
SFW does not support disks with unrecognized OEM partitions (3146848)Only one disk gets removed from an MSFT compatible disk group even if multiple disks are selected to be removedCannot create MSFT compatible disk group if the host name has multibyte charactersFault detection is slower in case of Multipath I/O over Fibre ChannelFlashSnap solution for EV does not support basic disksIncorrect mapping of snapshot and source LUNs causes VxSVC to stops workingSFW does not support operations on disks with sector size greater than 512 bytes; VEA GUI displays incorrect sizeDatabase or log files must not be on same volume as SQL ServerOperations in SFW may not be reflected in DISKPARTDisk signatures of system and its mirror may switch after ASR recoverySFW does not support growing a LUN beyond 2 TBSCSI reservation conflict occurs when setting up cluster disk groupsSnapshot operation fails when the Arctera VSS Provider is restarted while the Volume Shadow Copy service is running and the VSS providers are already loadedWhen a node is added to a cluster, existing snapshot schedules are not replicated to the new nodeRestore from Copy On Write (COW) snapshot of MSCS clustered shared volumes failsDynamic Disk Groups are not imported after system reboot in a Hyper-V environmentStorage Agent cannot reconnect to VDS service when restarting Storage AgentSFW does not support transportable snapshots on Windows Servervxsnapsql restores all SQL Server databases mounted on the same volumeWindows Disk Management console does not display basic disk converted from SFW dynamic diskDCM or DRL log on thin provisioned disk causes all disks for volume to be treated as thin provisioned disksAfter import/deport operations on SFW dynamic disk group, DISKPART command or Microsoft Disk Management console do not display all volumesRestored Enterprise Vault components may appear inconsistent with other Enterprise Vault componentsEnterprise Vault restore operation may fail for some componentsShrink volume operation may increase provisioned size of volumeReclaim operations on a volume residing on a Hitachi array may not give optimal resultsStorage migration of Hyper-V VM on cluster-shared volume resource is not supported from a Slave nodeIn a CVM environment, disconnecting and reconnecting hard disks may display an errorLimitations of SFW support for DMP