Issues Resolved in DataCore SANsymphony 10.0 PSP19

Continuous Data Protection Threshold

The Continuous Data Protection (CDP) “Max History Log” threshold warning after being changed was reverting to the default (100%) setting.

Continuous Data Protection Maximum History Log Size Issue

The DataCore Management Console resets the maximum Continuous Data Protection (CDP) history log file size to zero.

Dynamic Data Resiliency with 3-Copy Virtual Disks Using the 'Auto Select' Preferred Server

After evacuation, if the DataCore Server that owns the 'Parent' storage source is demoted, the preferred server setting will remain on the now-demoted DataCore Server instead of moving to the newly promoted DataCore Server.

DataCore Management Console

The "About" box of the management console displays the incorrect version information.

DCSX Process

Collecting performance metrics for Virtual Disk Mirror paths would cause a crash in the DCSX.exe process.

Force-Online Operation Failure During Double Server Failures

The Force-Online functionality fails with an error when a reported double failure still allows access to one side of a virtual disk mirror.

License Capacity

The Management Console would allow licensed capacity for disk pool storage to be exceeded when adding multiple physical disks at the same time.

Latency Thresholds

Users with 10.0 PSP16 and prior versions configuring the latency monitor thresholds could not remove or reconfigure the latency values after upgrading the software to 10.0 PSP17 and later versions.

Move Storage Source Operation

The ‘Move Storage Source’ operation would terminate unexpectedly.

Partial IIS Role Installation

The DataCore Rest Support installation does not enable the required IIS roles if some of the roles are already partially enabled.

Preferred Snapshot Pool Setting

Deselecting the Preferred Snapshot pool setting at the Virtual Disk level failed.

SANsymphony Server Sync

After any double failure is reported, if one of the DataCore servers is stopped and then restarted before the in-band (mirroring) connection has been restored, the other DataCore server may incorrectly set the double failed virtual disk on its side as Read/Write, allowing the host to access out-of-sync data.

SANsymphony Labels Display Incorrect Data Units

SANsymphony labels display incorrect data units (MB, GB, TB, PB) instead of the binary units (MiB, GiB, TiB, PiB).

User Role Description

User role descriptions were not detailed and may have confused the users while applying those user role privilege settings.

Virtual Disk Mirror Path

When a Fibre Channel or an iSCSI link was disconnected/reconnected, the very next host I/O after the reconnection could cause the mirror status of a virtual disk to unexpectedly report as ‘failed redundancy’.

Virtual Disk

The virtual disk source's role in a 3-way virtual disk is unclear to the user.