Issues Resolved in DataCore SANsymphony 10.0 PSP22

Capacity Optimization Could Not Be Disabled on a Disk Pool

Capacity Optimization could not be disabled on a disk pool.

Capacity Optimization Could Not Be Fully Disabled on a Server

Capacity Optimization could not be fully disabled on a server.

Collapse All Option Fails in DataCore Management Console

When selecting Collapse All in the DataCore Management Console, only the currently selected node was collapsed instead of all expanded nodes.

DataCore Management Console and PowerShell Commands Could Become Unresponsive

In some cases, a large number of storage-related events within a server group could cause the DataCore Management Console and PowerShell cmdlets to become unresponsive.

DataCore Executive Service Could Fail to Start

The DataCore Executive Service could fail to start if the Microsoft iSCSI Initiator service was not running or had stopped unexpectedly.

DataCore Management Console Login Failure for Users Without Assigned Roles

Logging into the DataCore Management Console with a user account that has no roles assigned could fail.

Delayed Mirror Path Recovery in System Managed Mirroring

System Managed Mirroring could take longer than expected to restore mirror paths after network connectivity was restored, resulting in delayed mirror recovery.

Duplicate IQN from Server Name Prefix Not Detected

Servers in a server group could generate identical IQNs when their hostnames shared the same first 15 characters, leading to communication issues between ports.

Disk Pools Could Display Incorrect Critical Status

When a server ran low on available Capacity Optimization space, disk pools could display critical status indicators even when sufficient regular storage capacity remained available.

Evacuate-on-Fail PowerShell Script Could Fail When Hosts and Servers Shared the Same Name

The EvacuateOnFail.ps1 script could fail when VMware hosts and SANsymphony servers had identical names.

Maximum History Log Size Could Not Be Modified

The maximum history log size value could not be modified in the DataCore Management Console.

Mirrored Pool Recovery Events Not Visible

When a physical disk in a mirrored pool enters recovery, recovery events are not visible in the DataCore Management Console, making it difficult for users to identify the start and completion of the recovery process.

System Health Bandwidth Tab Icons Not Displayed

Icons were not displayed for components such as Front-End Ports, Mirror Ports, Disk Pools, and Physical Disks in the System Health > Bandwidth tab of the DataCore Management Console.

Unexpected Removal of Virtual Disk Mappings During VMware Host Migration

In rare cases when using SANsymphony's vCenter integration, migrating or removing a VMware host could unintentionally remove virtual disk mappings to other hosts that were sharing the same virtual disk, resulting in loss of access across all ESX hosts.

Unexpected Loss of Automatic Log Store Configuration

A DataCore Server configured to automatically select a Disk Pool for the log store could unexpectedly change to a "No Log Store" configuration.

Logging Database Backup Files Could Consume Excessive Disk Space

Archived SANsymphony logs were not being removed, eventually filling up the local boot drive.

Incorrect License Information After Failed Activation

After a failed license activation, the DataCore Management Console (DMC) could display incorrect expiration dates, or licensed capacity and configuration could revert to Trial mode.

Pool Configuration Failure After Mirrored Disk Removal

Removing a mirrored pool disk when the physical disks were missing from the system could cause the configuration to become invalid, preventing the DataCore Server from starting.

Virtual Disk Monitor Threshold Settings Unavailable in the DataCore Management Console

Virtual disk monitor thresholds could not be configured in the DataCore Management Console after applying BZ Model license keys.

Virtual Disk Deletion During Reclamation May Cause System Crash

Deleting a virtual disk while its SAUs were still being reclaimed could cause a system crash.

Virtual Disk Template Read-Only Setting Not Enforced

The Read-Only setting on a virtual disk template did not prevent the template from being modified in the DataCore Management Console.

Virtual Disk Becomes Inaccessible After Resize

After resizing a mirrored virtual disk, mirror paths from one direction could change to a Not Present state resulting in loss of host access on one side.

Replication Interrupted by Reclamation on Destination Virtual Disk

Automatic or manual reclamation on the destination virtual disk could cause unexpected interruptions to asynchronous replication transfers from the source virtual disk.

Rename Option Not Available for ESXi Hosts After vCenter Unregistration

After unregistering a vCenter Server from SANsymphony, ESXi hosts that were previously managed through vCenter incorrectly displayed the Rename option in the DataCore Management Console. Attempting to rename the host resulted in an error.

Repeated Errors When Adding Physical Disks with Capacity Optimization Enabled

When Capacity Optimization is enabled, repeated errors were generated when adding a physical disk to a pool.

System Health Shows “Unknown” After 3-Way Virtual Disk Evacuation

After evacuating a 3-way virtual disk, system health incorrectly displayed “Unknown” for one of the virtual disk sources.

Failover Sometimes Fails When a Disk Pool Fails and Mirror Paths Are Unavailable

Microsoft Cluster nodes did not fail over when a Disk Pool failed and mirror paths were unavailable at the same time.

Delayed or Missing Recovery for CDP-Enabled Virtual Disks After Deleting a Persistent Rollback

Deleting Persistent Rollbacks would sometimes cause an unexpected virtual disk recovery that might not start or might start only after a significant delay. The storage source of the rollback would report as 'not ready'.

Hosts Not Notified When a Virtual Disk Is Resized

After a virtual disk was resized, larger or smaller, connected hosts were not reliably notified of the new size and could continue sending I/O based on the old size. This could cause I/O failures, particularly after a virtual disk was reduced in size.

DataCore Management Console Instability When Upgrading Nodes One at a Time

In large server groups, after upgrading from PSP19 or PSP20, the DataCore Management Console could become unresponsive or very slow for the DataCore Servers still waiting to be upgraded.

Misleading Disk Path Messages Logged During Routine Rescans

Messages stating that disk paths had disappeared, and then reappeared, were recorded in the Event Log in the DataCore Management Console, even though no mirror paths were lost.

Disk Pools Using 4 KiB Sector Size Support

A Disk Pool created for 4 KiB sector size support could go unexpectedly offline if one or more of the physical disks in the pool were suddenly unavailable or manually removed.