Enhancements in DataCore SANsymphony 10.0 PSP22

Improved Disk Pool Capacity Optimization

Improved internal disk pool capacity optimization behavior for Zvol based storage allows SANsymphony to automatically detect and utilize additional underlying storage capacity more efficiently during dynamic growth operations.

Improved Logstore Handling for Mirror Recovery Protection

Improved Logstore handling for mirrored virtual disks to ensure reliable bitmap logging and correct recovery behavior. Mirror operations are now blocked when a server is offline without a Logstore, and Logstore is automatically created during server start/stop if missing. This prevents unexpected full recoveries and incorrect recovery direction scenarios.

Improved ZFSin Performance

ZFSin has been enhanced to reduce latency and improve performance stability during mirror recovery following a server restart. Optimized startup memory allocation and improved write-buffer management help deliver more consistent recovery performance under heavy write workloads.

Visibility for Witness Contact Failures

The System Health tab in the DataCore Management Console now shows a Warning status for a virtual disk when it fails a witness contact request, with a status of "Witness contact failed, Offline." Previously, this condition was recorded only in the trace logs and was not visible to the user. The status clears automatically once witness contact is restored and the virtual disk becomes healthy again.

Extended Support for Proxmox Snapshot Deletion

SANsymphony has extended support for Proxmox by adding support for the SCSI WRITE SAME (10) command. This allows Proxmox to zero out disk space more efficiently when deleting a snapshot, significantly reducing the time required to complete the operation.

Visibility for Auto-recovery Changes

A message is now written to the Event Log in the DataCore Management Console whenever auto-recovery is enabled or disabled for a virtual disk, stating whether the mirror recovery mode has been set to automatic or manual. Previously, this change was recorded only in the trace logs and was not readily visible, which made it difficult to determine why a virtual disk was reporting a status of "Log recovery paused" or "Full recovery paused".