What I like best about Druva Data Security Cloud is the combination of simplicity and strong security delivered through a fully cloud-native model.
In day-to-day use, the biggest advantage is how little overhead it requires. Once policies are configured, backups for endpoints, servers, and Microsoft 365 largely run on autopilot. There’s no infrastructure to maintain, no storage planning, and very little routine “backup babysitting,” which frees up IT time for more strategic work.
At the same time, it doesn’t sacrifice resilience. The built-in ransomware protection, immutable backups, and air-gapped cloud architecture provide a strong safety net against both cyber threats and accidental data loss. That balance—low operational effort with high recovery confidence—is a major differentiator compared to traditional backup systems.
Overall, the standout value is that it turns backup from a hands-on infrastructure burden into a managed, scalable service that just works consistently in the background. Review collected by and hosted on G2.com.
What I dislike most about Druva Data Security Cloud is that some areas feel less flexible than you would expect from an otherwise modern, cloud-native platform.
The biggest example is reporting and customization. While the default dashboards are useful, they don’t always go deep enough for more complex environments or compliance-driven reporting needs. In those cases, you often end up exporting data and building your own reports outside the platform, which adds extra steps and reduces efficiency.
Another limitation is the restore experience for large or complex recoveries. File-level restores are straightforward and fast, but larger restores or highly granular recovery scenarios can feel less intuitive and sometimes slower than expected. Visibility into progress and control over advanced restore scenarios could be improved.
Finally, broader application and integration depth is an area where there’s room for growth. Druva covers core workloads like Microsoft 365 and endpoints very well, but organizations with more specialized applications or deeper integration needs (for example with SIEM tools, ticketing systems, or niche enterprise apps) may find the ecosystem less extensive than they’d like.
Overall, these drawbacks don’t outweigh the benefits, but they do show up more clearly in complex or highly regulated environments where flexibility and deep customization matter. Review collected by and hosted on G2.com.







