Known Issues in DataCore VASA Provider 3.1 - Preview
Capability Sets and Default Profiles
When accessing the Configure tab, the Capability Sets and Default Profiles may not display the contents for the virtual volumes. However, DataCore VASA Provider 3.1 supports these features when creating a policy.
DataCore VASA Provider Registration
After registering the DataCore VASA Provider via the DataCore Deployment Wizard, it may take some time before the Storage System is displayed in the vCenter > Manage > Storage Providers panel. Until the storage is brought online by a vCenter rescan, a message stating that "No Storage System" is displayed. Alternatively, stop and restart the DataCore VASA Provider Service to manually initiate a rescan, or manually unregister and re-register the Storage Provider to correct this.
If a DataCore VASA Provider is manually unregistered from the vCenter and then re-registered, it cannot be automatically unregistered from the vCenter when the DataCore VASA Provider is subsequently uninstalled.
Deleting Snapshots
A reference snapshot (a snapshot that is used to create a fast clone virtual machine (VM)) that was created before upgrading the DataCore VASA Provider might not successfully delete after upgrading the DataCore VASA Provider version to 3.1. The snapshot may not be removed from the underlying storage system (SANsymphony). Instead, the snapshot may appear as deleted in the vCenter user interface. It is recommended to consider this behavior while managing snapshots in your environment.
Deleting the entire VM will delete the snapshots successfully.
Failover and Failback Operation on Virtual Machines
On a vSphere 7 configuration, the failover or failback operation on multiple virtual machines (VMs) may fail for some of the VMs with a message stating "Virtual machine [vm-name] is not recovered. Internal error: Cannot find vVol configuration device [vvolId] for VM [vm-name] in the list of recovered vVol configuration devices."
As a workaround, trigger the operation again on the same instance.
Failover Operation in a High Availability Setup
In a High Availability DataCore VASA Provider setup, the failover operation from the Site Recovery Manager (SRM) may fail when the DataCore VASA Provider node of the replication destination is in standby mode. As a workaround, restart the DcsVasa service on both the active and standby nodes belonging to the replication destination.
Fast Clone with Replication Policies
Fast Clones with replication policies are not supported in the DataCore VASA Provider 3.1 version.
Migrating Storage or Hosts
If the migration of storage fails, pass-through disks may remain in the SANsymphony configuration. Contact DataCore Technical Support for assistance in removing these disks. If a timeout failure occurs when migrating storage or hosts, retry the operation.
Before migrating storage because of a pool failure, modify the Host Preferred Server setting from “Preferred All” to “Auto Select” in the DataCore Management Console.
Migrating Virtual Machines from VMFS to vVol
Virtual Machines (VM) on a VMFS datastore that contain VMware snapshots may fail migration to a vVol. Remove any VMware snapshots before proceeding with this procedure.
Migrating VMs on a mirrored VMFS datastore to a mirrored vVol may sometimes fail with a message stating "The operation is not allowed in the current state." Retry the operation. If the failure persists, see the Resolution section of this VMware Knowledge Base article for possible solutions.
Snapshot
- The names of snapshots created in vCenter are not reflected in the DataCore Management Console.
- DataCore does not support vCenter snapshots with dual storage policy virtual machines.
Storage Policy
For a storage policy based on the Storage Profile rule, the virtual machine (VM) compliance status may show as Compliant even though the data migration is still in progress at the storage side.
Test Failover with Multiple Virtual Machines
On a vSphere 7 configuration, the test failover operation on multiple virtual machines (VMs) may fail for some of the VMs with a message stating "Virtual machine [vm-name] is not recovered. Internal error: Cannot find vVol configuration device [vvolId] for VM [vm-name] in the list of recovered vVol configuration devices."
As a workaround, try running a test failover operation on a protection group containing less than three VMs.
Virtual Machine Storage Policies
Migration or cloning of virtual machines with different types of storage policies (Mirror Policies, Dual Policies, Single Policies) is not supported.