There are significant disadvantages that need addressing. Failure reports are limited. Alert notifications for Druva inSync, Druva endpoints, and Druva M365, which are managed by backup profiles, cannot be configured to send automated or real-time alerts. We have to depend on manual checks and go to the console directly. I had a customer who recently purchased Datadog. Even when filtering the logs, we see many "backup completed with errors" messages. However, when I go to the console, I cannot find anything. After researching, I discovered that backups showing as never backed up could involve many users or workloads that have not yet been backed up. They might be new joiners where backup has not started or has not been configured. However, since they were added to Azure AD, Druva provisioned them through the user provisioning process. If they have never been backed up, the system shows them as backed up with errors, which is disappointing. Druva's argument is that they want to flag them as errors because they have never been backed up, but customers should not be bothered by workloads that have not been backed up. Reporting is another area where we are really struggling. If we need three months of data, we cannot get that report. We have received many requests from customers asking for reports showing backup frequency. For example, if backing up five times a day, they want a report showing exactly how many times it is actually getting backed up. There is no way to see that report. When downloading the last user backup status report or rollout report, we cannot see a single entry for all five backups for that particular endpoint. There is no way to tell customers that a backup is running five times a day and will generate five snapshots unless we manually visit each client and check the backup schedules. Those reporting limitations are really disappointing. Documentation is not concise and clear. One of our clients got downsized and decommissioned everything due to compliance requirements. Some companies cannot pass FDA licenses and certifications, so they downsize and lay off staff. This client stopped their on-premises DFS file share in Windows and moved to Azure. We configured Druva Data Security Cloud backup for Azure file share, which completed successfully. During the cleanup process, the Azure team saw many keys in Azure Key Vault, deleted those keys, and performed a soft delete. The moment they did the soft delete, backup started failing. I worked with support, but Druva support had no idea because it was not documented anywhere that Quantum Bridge VM requires Azure Key Vault services for private machines or private shares behind private subnets not exposed to the public internet. Support searched logs, took extensive logs, and checked with the engineering team. It took around ten days to resolve the issue. They found that because the Azure team deleted the keys from Key Vault, the Quantum Bridge VM provisioned in the private subnet could not connect to the public internet, and therefore provisioning failed. However, this is not documented in Druva documentation. I also received a request for AWS FSx backup for NetApp ONTAP. I searched and could not find any documentation. I was forced to create a ticket with Druva support. We have a CSM, and since we newly bought Druva Cloud Ranger, Druva appointed a CSM for this. I sent an email, and the CSM said they are looking internally, but externally or as a Druva user, I cannot find any documentation. These things are very disappointing and should not happen with an enterprise backup tool.
If a customer is using legacy infrastructure, such as in-house servers or in-house data centers, that is where Druva Data Security Cloud does not perform well as a backup solution. I think it is one area where they can improve. Legacy infrastructure is mainly used by schools, universities, and government institutions. Because they have some critical data that they cannot put on the cloud, it makes sense that this is a limitation.
I think Druva's deduplication technology is great, but the way they charge for source storage means the storage size can suddenly become much larger, and I would have been much happier if they were to give deduplication advantages on endpoints and M365 as well, which they don't. I think the best improvement Druva could make is better training for customers and partners, as their on-ground support from a technology point of view is much better with Veeam and Commvault than with Druva. There is room for improvement in their response time and first-level support quality, as some changes are happening in the team in India, which might be the reason for this.
Sr. Executive Engineer at a outsourcing company with 51-200 employees
Real User
Top 5
Apr 15, 2026
Druva Data Security Cloud is a very strong SaaS-based backup and recovery platform, but based on real-world experiences, there are a few areas where it could be improved. One area is performance during very large-scale initial backups or restores. Some environments can experience slower sync times when onboarding a large dataset. Another area for improvement is flexibility in policy customization and advanced configuration. While the platform is very simple and centralized, some organizations with complex environments may want deeper control over backup policies and encryption. Cost visibility is also something that could be improved.
Desktop Analyst at a outsourcing company with 1,001-5,000 employees
Real User
Top 10
Apr 3, 2026
When considering how Druva Data Security Cloud could be improved, I would suggest several enhancements. I would prefer to see improvements in Druva Data Security Cloud that include the use of end-to-end encryption, secure communication protocols, and strong authentication to prevent unauthorized access to our data and interception. It would also be helpful to regularly update firmware, enable access controls, and store data in secure platforms such as Druva Data Security Cloud to ensure backup compliance and protection against data loss or cyber threats. Better features for our organization would include enhanced reporting and analytics and more customizable alerting, which would help improve monitoring, along with proactive issue resolution. Additionally, deep integrations with more third-party tools and faster large-scale restore performance would further strengthen efficiency and user experience.
I believe Druva Data Security Cloud could be improved as the user interface could be a little more clear, the SSO setup was a little confusing, and the ticket creation procedure could be simpler. I would also add that there is not enough transparency on pricing.
In future updates, I would like to see more AI feature functionality in Druva Data Security Cloud, as that is definitely one of the improvements needed.
Technical Consultant at a tech services company with 11-50 employees
Reseller
Top 5
Sep 18, 2025
They could integrate an EDR tool during backup. By integrating with that tool, they could easily rectify cyberattacks, miscellaneous attacks, and ransomware. It can prevent ransomware when data is in transit, not just at rest. They can improve their product quality for Salesforce as they don't have the capability to run that business without Technobind. They should consider supporting additional workloads in their tenant. They need multiple tenants where they can provide protection. For example, if a customer is using ESG cloud, they should plan for backup support and other data centers such as Control-S and many more.
Multi Property IT Manager at John Q. Hammons Hotels, Inc.
Real User
Top 20
Nov 1, 2024
I suggest improvements in the time it takes to restore data. Also, the reports we can generate have limited features. There is a limitation in the advanced reporting features, such as understanding how many files are in the backup, which users are actively using it, and how many files have been backed up properly.
Druva Data Security Cloud is a cloud-based platform offering comprehensive data security and management for businesses. It provides features focused on data backup, recovery, archiving, and governance across cloud workloads (like Microsoft 365, Google Workspace, and Salesforce), endpoints (such as laptops and mobile devices), and virtual machines (VMs). Key functionalities include centralized management via a web-based console, automated backups and quick recovery, data archiving for...
There are significant disadvantages that need addressing. Failure reports are limited. Alert notifications for Druva inSync, Druva endpoints, and Druva M365, which are managed by backup profiles, cannot be configured to send automated or real-time alerts. We have to depend on manual checks and go to the console directly. I had a customer who recently purchased Datadog. Even when filtering the logs, we see many "backup completed with errors" messages. However, when I go to the console, I cannot find anything. After researching, I discovered that backups showing as never backed up could involve many users or workloads that have not yet been backed up. They might be new joiners where backup has not started or has not been configured. However, since they were added to Azure AD, Druva provisioned them through the user provisioning process. If they have never been backed up, the system shows them as backed up with errors, which is disappointing. Druva's argument is that they want to flag them as errors because they have never been backed up, but customers should not be bothered by workloads that have not been backed up. Reporting is another area where we are really struggling. If we need three months of data, we cannot get that report. We have received many requests from customers asking for reports showing backup frequency. For example, if backing up five times a day, they want a report showing exactly how many times it is actually getting backed up. There is no way to see that report. When downloading the last user backup status report or rollout report, we cannot see a single entry for all five backups for that particular endpoint. There is no way to tell customers that a backup is running five times a day and will generate five snapshots unless we manually visit each client and check the backup schedules. Those reporting limitations are really disappointing. Documentation is not concise and clear. One of our clients got downsized and decommissioned everything due to compliance requirements. Some companies cannot pass FDA licenses and certifications, so they downsize and lay off staff. This client stopped their on-premises DFS file share in Windows and moved to Azure. We configured Druva Data Security Cloud backup for Azure file share, which completed successfully. During the cleanup process, the Azure team saw many keys in Azure Key Vault, deleted those keys, and performed a soft delete. The moment they did the soft delete, backup started failing. I worked with support, but Druva support had no idea because it was not documented anywhere that Quantum Bridge VM requires Azure Key Vault services for private machines or private shares behind private subnets not exposed to the public internet. Support searched logs, took extensive logs, and checked with the engineering team. It took around ten days to resolve the issue. They found that because the Azure team deleted the keys from Key Vault, the Quantum Bridge VM provisioned in the private subnet could not connect to the public internet, and therefore provisioning failed. However, this is not documented in Druva documentation. I also received a request for AWS FSx backup for NetApp ONTAP. I searched and could not find any documentation. I was forced to create a ticket with Druva support. We have a CSM, and since we newly bought Druva Cloud Ranger, Druva appointed a CSM for this. I sent an email, and the CSM said they are looking internally, but externally or as a Druva user, I cannot find any documentation. These things are very disappointing and should not happen with an enterprise backup tool.
If a customer is using legacy infrastructure, such as in-house servers or in-house data centers, that is where Druva Data Security Cloud does not perform well as a backup solution. I think it is one area where they can improve. Legacy infrastructure is mainly used by schools, universities, and government institutions. Because they have some critical data that they cannot put on the cloud, it makes sense that this is a limitation.
I think Druva's deduplication technology is great, but the way they charge for source storage means the storage size can suddenly become much larger, and I would have been much happier if they were to give deduplication advantages on endpoints and M365 as well, which they don't. I think the best improvement Druva could make is better training for customers and partners, as their on-ground support from a technology point of view is much better with Veeam and Commvault than with Druva. There is room for improvement in their response time and first-level support quality, as some changes are happening in the team in India, which might be the reason for this.
The solution should allow non-IT users to be able to search more specifically.
Druva Data Security Cloud is a very strong SaaS-based backup and recovery platform, but based on real-world experiences, there are a few areas where it could be improved. One area is performance during very large-scale initial backups or restores. Some environments can experience slower sync times when onboarding a large dataset. Another area for improvement is flexibility in policy customization and advanced configuration. While the platform is very simple and centralized, some organizations with complex environments may want deeper control over backup policies and encryption. Cost visibility is also something that could be improved.
When considering how Druva Data Security Cloud could be improved, I would suggest several enhancements. I would prefer to see improvements in Druva Data Security Cloud that include the use of end-to-end encryption, secure communication protocols, and strong authentication to prevent unauthorized access to our data and interception. It would also be helpful to regularly update firmware, enable access controls, and store data in secure platforms such as Druva Data Security Cloud to ensure backup compliance and protection against data loss or cyber threats. Better features for our organization would include enhanced reporting and analytics and more customizable alerting, which would help improve monitoring, along with proactive issue resolution. Additionally, deep integrations with more third-party tools and faster large-scale restore performance would further strengthen efficiency and user experience.
I believe Druva Data Security Cloud could be improved as the user interface could be a little more clear, the SSO setup was a little confusing, and the ticket creation procedure could be simpler. I would also add that there is not enough transparency on pricing.
In future updates, I would like to see more AI feature functionality in Druva Data Security Cloud, as that is definitely one of the improvements needed.
They could integrate an EDR tool during backup. By integrating with that tool, they could easily rectify cyberattacks, miscellaneous attacks, and ransomware. It can prevent ransomware when data is in transit, not just at rest. They can improve their product quality for Salesforce as they don't have the capability to run that business without Technobind. They should consider supporting additional workloads in their tenant. They need multiple tenants where they can provide protection. For example, if a customer is using ESG cloud, they should plan for backup support and other data centers such as Control-S and many more.
I suggest improvements in the time it takes to restore data. Also, the reports we can generate have limited features. There is a limitation in the advanced reporting features, such as understanding how many files are in the backup, which users are actively using it, and how many files have been backed up properly.