DataCore SANsymphony SDS Pros and Cons

The ability to pool the storage to leverage thin-provisioning is a huge saving in space and costs.

DataCore has helped provide flexible, highly available, high-performance storage that otherwise would have been outside our price range.

DataCore's ability to seamlessly move virtual volume data between storage pools as well as their synchronous mirroring has made maintenance and disaster recovery planning achievable.

Supporting of Automated-Storage-Tiering (AST) is a good feature that saves money.

The features I have found most valuable are the active-active, or so-called grid technology, and the integration into our VMware-vCenter.

Good security with this solution.

I'd have to say that the biggest improvement gained by using SANsymphony has to be the performance of the product.

During the maintenance periods, on any part of the storage or VMware migration, we have had no downtime.

The most valuable feature for us is that we can adjust the size of the storage very easily, without stopping production.

It is a well-proven, automated management tool in all dynamic provisioning, auto-tiering, great performance, parallel I/O​, cache speed mechanism, etc.

Oracle OLTP benchmark to test how it improves the performance while using flash drive NVMP.

Having an enterprise "Storage Dashboard" that can show capacity, usage, performance, and any issues would be very beneficial.

The cost is becoming prohibitive since they moved to a subscription model.

DataCore needs a more efficient and better way to keep track of metrics and counters so that we can do baseline analysis to measure performance.

We are waiting for container support (on the roadmap), as well as a user-friendly full web-administration capability, and an improved API.

I think an easier way to open a service call, right through the DataCore GUI, would be an improvement, especially when there is an urgent issue.

I would like for it to improve into a more ergonomic management console and a translation into the French language. It should have some process for a shutdown of a VM properly in case of a problem.

There is no way of quickly matching the exact size of a vDisk to a disk pool.

I think the performance reporting can be improved by adding historical statistics into a database for the purpose of comparing.

The alert system could have more features.

Unified storage (all block, objects, and files) should be in a single storage pool with unified storage concepts, hence providing the user with whatever they want.