There is room for improvement in Druva inSync. In the next release, I would like to see additional features and functionalities that focus more on AI functionality, similar to what other vendors offer.
Technical Consultant at a tech services company with 11-50 employees
Reseller
Top 5
May 19, 2025
Currently, there is not anything required for improvement as they are already enhancing their existing solutions. We have suggested improvements for geolocations and other matters. To make Druva inSync better, they can implement additional DLP. They have recently launched initiatives such as geolocation and password encryption, which cannot be removed.
Real-time alerts are crucial for better incident management. Additionally, the support team generally needs to be more proactive with technical and general suggestions. The documentation should be improved, with more advanced feature guides and video resources.
The last update made the interface look somewhat unfamiliar to users. Data recovery was technically flawless at some point. However, an update after a merger changed things. The current procedure for data encryption is not as straightforward as before, and we're facing some challenges. Specifically, one user encrypted their data, and since they have left the company, we cannot decrypt it. This has resulted in a loss of access to that data.
Backup & Recovery Administrator at a outsourcing company with 10,001+ employees
Real User
Top 10
Apr 12, 2024
Sometimes, they conduct scheduled maintenance. During these times, the services are unavailable. However, this is communicated to customers when they sign up for the Duo Service. It's already stated in the terms and conditions.
The solution takes a lot of time during restoration. I am not sure how its restoration works since it was end-to-end, which means it was between two clients, including the client and servers. Users may have a very good internet bandwidth, but the restoration is very slow from Druva inSync. The aforementioned details can be considered for improvement.
DVP IT at a financial services firm with 5,001-10,000 employees
Real User
Feb 1, 2022
Druva inSync Some resources are used to possibly minimize. The use of an encryption key at the user level would increase security. I would like to see security improved in the next release.
The backup time is very poor. The backup runs continuously. It goes on from morning till night. The system performance also becomes very poor when Druva inSync is running. When the backup starts, the systems become very slow. You cannot work while the backup is going on. After the backup is complete, the system performance picks up again. I raised this issue with Druva, but they are not able to resolve this issue. They should analyze the reason for this kind of problem. They have asked for too many error logs, but how do we get logs from the laptops of the users who are unavailable because they are not working from a centralized office, or they are at a customer site or are traveling? Such users can only communicate through emails. This problem is not related to just one user; it is related to every user. There are so many problems in the Druva inSync patches. Sometimes, the software gets uninstalled automatically, and we are not able to find it on the client system. The users say that they didn't uninstall the software. So, how do we find out who uninstalled the software? If the Druva inSync client is installed on the system, the users should not have the right to uninstall the patch. There should be a security system and an admin panel so that the Druva inSync software is locked when it is installed on the client system. Users should not uninstall it unknowingly. A user should be able to uninstall it only after providing a password set by the administrator. They have given many other restrictions, such as a user cannot restore the data from his laptop, or a user cannot remove the snapshot from his laptop. They can also provide a restriction for uninstalling Druva inSync.
Druva inSync is very high in price. A general customer cannot afford this solution. Even if the product is good, people cannot afford such a high cost just for taking the backup. This is a recurring investment, and the customers have to pay for it every year. Druva is also yet to develop the channel and the channel or partner commitment.
Technical manager at Optimistic Technology Solutions Pvt Ltd
Reseller
Jul 8, 2020
The user quota is an area that needs to be improved. Rather than have a quota of 50Gb per user, they could consider 60Gb to 70Gb. We could acquire more clients with that additional storage space available.
Founder, Owner at a tech vendor with 11-50 employees
Real User
Jan 30, 2020
If I could have an accelerator or something to back up the solution on the cloud, that would be helpful. Also, it would be helpful if the accelerator could give me a buffer of a couple of days for any kind of immediate recovery on an offsite. If I could have a day or two to recover on-prem. If I could use the rest on cloud and have my backup offloaded to another engine (and that engine could basically be offline while handling the rest of the backup) that would be great. Then I wouldn't have to use my computer
Technical Consultant at a tech services company with 11-50 employees
Consultant
Jul 16, 2019
This solution would benefit from the inclusion of an on-premise backup feature, as currently, they are offering everything in the cloud. We have seen that some customers prefer on-premise backup, so they need to think about this.
Druva inSync is a comprehensive data protection and governance platform that enables organizations to securely backup, recover, and manage their critical data.
With its cloud-native architecture, inSync offers scalable and efficient data protection across endpoints, cloud applications, and servers. It provides automated backups, ensuring that data is always protected and easily recoverable in case of any data loss or system failure.
In addition, inSync offers advanced data...
There is room for improvement in Druva inSync. In the next release, I would like to see additional features and functionalities that focus more on AI functionality, similar to what other vendors offer.
Currently, there is not anything required for improvement as they are already enhancing their existing solutions. We have suggested improvements for geolocations and other matters. To make Druva inSync better, they can implement additional DLP. They have recently launched initiatives such as geolocation and password encryption, which cannot be removed.
Real-time alerts are crucial for better incident management. Additionally, the support team generally needs to be more proactive with technical and general suggestions. The documentation should be improved, with more advanced feature guides and video resources.
The last update made the interface look somewhat unfamiliar to users. Data recovery was technically flawless at some point. However, an update after a merger changed things. The current procedure for data encryption is not as straightforward as before, and we're facing some challenges. Specifically, one user encrypted their data, and since they have left the company, we cannot decrypt it. This has resulted in a loss of access to that data.
Sometimes, they conduct scheduled maintenance. During these times, the services are unavailable. However, this is communicated to customers when they sign up for the Duo Service. It's already stated in the terms and conditions.
It would be good if bare metal backups were possible.
The solution takes a lot of time during restoration. I am not sure how its restoration works since it was end-to-end, which means it was between two clients, including the client and servers. Users may have a very good internet bandwidth, but the restoration is very slow from Druva inSync. The aforementioned details can be considered for improvement.
The product needs to improve its support.
The one area that needs to improve is the pricing.
The speed could be better.
Druva inSync Some resources are used to possibly minimize. The use of an encryption key at the user level would increase security. I would like to see security improved in the next release.
It is based on AWS and works very well in those environments however, it works very well in multi-cloud environments.
The backup time is very poor. The backup runs continuously. It goes on from morning till night. The system performance also becomes very poor when Druva inSync is running. When the backup starts, the systems become very slow. You cannot work while the backup is going on. After the backup is complete, the system performance picks up again. I raised this issue with Druva, but they are not able to resolve this issue. They should analyze the reason for this kind of problem. They have asked for too many error logs, but how do we get logs from the laptops of the users who are unavailable because they are not working from a centralized office, or they are at a customer site or are traveling? Such users can only communicate through emails. This problem is not related to just one user; it is related to every user. There are so many problems in the Druva inSync patches. Sometimes, the software gets uninstalled automatically, and we are not able to find it on the client system. The users say that they didn't uninstall the software. So, how do we find out who uninstalled the software? If the Druva inSync client is installed on the system, the users should not have the right to uninstall the patch. There should be a security system and an admin panel so that the Druva inSync software is locked when it is installed on the client system. Users should not uninstall it unknowingly. A user should be able to uninstall it only after providing a password set by the administrator. They have given many other restrictions, such as a user cannot restore the data from his laptop, or a user cannot remove the snapshot from his laptop. They can also provide a restriction for uninstalling Druva inSync.
Druva inSync is very high in price. A general customer cannot afford this solution. Even if the product is good, people cannot afford such a high cost just for taking the backup. This is a recurring investment, and the customers have to pay for it every year. Druva is also yet to develop the channel and the channel or partner commitment.
The user quota is an area that needs to be improved. Rather than have a quota of 50Gb per user, they could consider 60Gb to 70Gb. We could acquire more clients with that additional storage space available.
If I could have an accelerator or something to back up the solution on the cloud, that would be helpful. Also, it would be helpful if the accelerator could give me a buffer of a couple of days for any kind of immediate recovery on an offsite. If I could have a day or two to recover on-prem. If I could use the rest on cloud and have my backup offloaded to another engine (and that engine could basically be offline while handling the rest of the backup) that would be great. Then I wouldn't have to use my computer
This solution would benefit from the inclusion of an on-premise backup feature, as currently, they are offering everything in the cloud. We have seen that some customers prefer on-premise backup, so they need to think about this.