Please share with the community what you think needs improvement with Druva inSync.
What are its weaknesses? What would you like to see changed in a future version?
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.
What do you like most about Druva inSync?
Thanks for sharing your thoughts with the community!