Known Issues in DataCore SANsymphony 10.0 PSP15 Update 2

Asynchronous Replication

Creating a replication on a destination disk already served via loopback might fail and leave both sides on standby or only one side with successful replication. As a workaround, if only one side knows about the replication, perform a forced split and start over. If both are stating standby - activate the one that should be active.

Capacity Optimization on Disk Pools

Capacity Optimization cannot be enabled on a disk pool configured with a sector size of 4KB. To support capacity optimization on disk pools, the ZFS driver creates Zvols with a sector size of 512B, which are added as physical disks to the disk pool. But the disk pool requires that all physical disks in the pool have the same sector size. As a workaround, configure the disk pool with a sector size of 512B to enable capacity optimization on the disk pool.

DataCore Executive Service

On rare occasions after an upgrade, the DataCore Executive Service (DCSX.exe) may fail to start after the reboot. Follow the steps below as a workaround:

  1. Open the "Services" panel in Windows Services Manager.

  2. Start DCSX.exe manually and ensure that the DCSX.exe is still set to "Auto-start".

  3. Once started, open the DataCore Management Console on any server in the group.

  4. Right-click the server in question and select "Start" from the pop-up menu to start virtualization on that server.

DataCore Management Console

If the Server Group is configured to use Vcenter Integration, do not upgrade the servers to SANsymphony 10.0 PSP15 Update 2. Contact DataCore Technical Support for more information.

Disk Pool Deletion

After deleting a disk pool, the DataCore Management Console may display an error: "Something went wrong.". As a workaround, restart the DataCore Management Console.

Disk Tier Value

An incorrect disk tier value “0” may display in the DataCore Management Console and the corresponding row in the allocation map may not display when the first physical disk in a pool mirror disk pair fails. This is a user interface issue and does not impact the auto-tiering operation. The disk tier value becomes unavailable for the time frame when the first physical disk in a pool mirror disk pair fails/becomes offline. This is a temporary issue and the correct tier value automatically displays once the failed/offline physical disk recovers or once the mirror set is split. A fix for this issue will be provided in a future release.

Host Access

When reverting a full snapshot to a Backup (third) copy of a 3-way Mirrored virtual disk (vDisk), the action may result in the loss of host access to the vDisk. As a workaround, before performing a Revert from a full snapshot to a vDisk, check which mirror a vDisk copy is. This should not be performed against the mirror copy serving as the Backup copy at this time. In such a case, repeating the process should result in the restoration of host access to the vDisk.

Initiator IP Ignored for iSCSI Connections

When configuring an iSCSI connection via either the DataCore Management Console or PowerShell Cmdlets, you can specify the initiator IP but it will be ignored.

Mirrored Virtual Disks

On a three-way mirrored Virtual Disk (vDisk) configuration, the log recovery does not start following a replace or split-and-unserve on the mirror. As a workaround, rescan the ports.

Performance Recording

  • When recording a large number of counters on a local performance recording database, the database may become full and stale data may not be deleted as fast as new data is recorded. When this occurs, reading and recording performance data will stop until deletion operations are complete, and event log messages will be posted. Consider reducing the number of counters being recorded if this occurs.
  • Some counters may show differing values in recorded performance and live performance (Physical disk % Idle Time, Average Queue Length).

Purge on Pools with Mirrored Encrypted Virtual Disks

When a diskpool contains a mirrored encrypted virtual disk (vDisk), purging the failed disks in this pool may result in data corruption. Follow the steps below as a workaround:

  1. Disable "Auto Recovery" for the encrypted mirror vDisk.

  2. Purge the failed disk.

  3. Click "Replace" on the out-of-sync side.

  4. Enable "Auto Recovery" for the vDisk.

ReFS-formatted Virtual Disks

Formatting a virtual disk (vDisk) with Microsoft ReFS (Resilient File System) that is mapped over a loopback port will fail with an error stating the drive is not accessible.

Removing DataCore Servers from a Server Group

If after removing a DataCore Server from a server group, the removed server is still displayed in the DataCore Management Console, re-connect to the original server group by either using the ‘Server Group Connections’ Window or the ‘Connect to Server Group’ option in the Common Actions menu option.

Replication Issues in SANsymphony on Hyper-V Parent OS May Cause Standby Mode to Get Stuck

When SANsymphony is installed on the Hyper-V parent OS and asynchronous replication is configured for virtual disks, replication may get stuck in standby mode. To temporarily avoid this issue, install SANsymphony on a virtual machine (VM) instead of the parent OS.

Replication Transfer State

After exiting the test mode, if the device is not removed from the Windows Disk Management tool at the destination (standby) side, the Replication Transfer displays in the stuck state (the data was not transferring to the Replicated Virtual Disks (vDisks)) and few of the vDisks display an error such as destaging failure. As a workaround, manually refresh the Disk Management tool at the standby side.

Smart Deployment Wizard

  • The Smart Deployment Wizard (SDW) did not start the DataCore Executive Service (DCSX.exe) in the SDW-Clustered Virtual Machines Deployment Scenario after deploying the SANsymphony. As a workaround, check if the DCSX.exe is running in the target server. If not, start it manually and click "re-run" to continue the deployment in the SDW.

  • The Smart Deployment Wizard (SDW) failed to create the NFS share. Intermittently, SDW may fail to create the NFS share for the NAS Clustered configuration menu option and it does not report this failure. As a workaround, create the NFS share manually from Windows server>Failover cluster manager.

SMPA Disk Pools

Preserved space for an authorized SMPA disk pool may be reset to 0% when the authorized node changes. An example of this would be if the authorized node is stopped.

Snapshot Issues

The Events tab of the Snapshot in the DataCore Management Console may not display the operation completion message of a snapshot update procedure. However, the message does reflect in the DCS trace messaging and may be viewed by the support personnel if necessary. As a workaround, contact DataCore Technical Support for assistance with the trace messaging analysis.

Snapshot Split Error

When attempting to split a full snapshot, an error is displayed stating that the snapshots are not fully migrated as the migration map percentage is stuck. As a workaround, update the snapshot and retry splitting the snapshot.

SNMP Output

After deleting the virtual disks (vDisks) and rebooting the servers, the name of some objects may display with extra spacing. This should be a non-functional problem as the object ID remains the same.