Druva inSync Reviews

I use Druva inSync for a client's enterprise workload, including VMware backup, SQL backup, file system backup, and Salesforce and Microsoft 365 backup.

Druva is offered as a service so that we can access it from any enterprise-based browser or URL. We also have a single sign-on, which allows me to log in securely. Hence, I can easily access the system, configure it, perform day-to-day monitoring tasks, and check for any issues or configurations needed. Overall, it's a simple and easy-to-use tool with a high-speed and straightforward interface for management.

Druva inSync offers all the native features, such as recovery on the same server or an alternate location. It allows for installing an agent on any server trusted by the network. Its recovery feature is robust and reliable.

It's a pretty solid solution. Nowadays, nearly every major player, such as Veeam and Rubrik, offers a similar architecture—cloud-based and service-oriented. They all offer similar features.

All the features are pretty good. It has a simple interface. The simple user interface, once configured, requires nothing much to do. It gives you the status of all your daily jobs or workloads.

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.

I have been using Druva inSync for six years.

There's no limitation to scale up. It depends on the workload. The billing is based on the consumption we're using. If there are new workloads or servers to be added, we have to consider how many credits it will consume. They inform us if there's a shortfall, and then we have to purchase additional credits.

There should be around 600 servers.

Three people are using this solution.

Technical support is good.

Positive

It is easy, straightforward, and simple to implement. It was finished, maybe within a week. It was pretty fast and simple. Three people are required for the solution's deployment.

Druva inSync offers limited backup features for various workloads. Druva does not currently support some features due to its presence in the market. They need to introduce new features to accommodate different types of workloads. If a specific workload requires backup and isn't currently supported, reaching out to them can prompt implementation in upcoming quarters or within six months to a year.

We don't have everything we need. The features we require as customers are almost available. We've already submitted a request for features like Active Directory backup and endpoint backup.

It was existing data being backed up by another backup tool. Determining the total number of servers, including physical and virtual ones, was crucial. We calculated the total number of production servers requiring backup, encompassing physical and virtual servers and various applications like Oracle, SQL, or Hyper-V. Once we compiled the list, we organized a batch deployment process, deploying around 50-80 servers daily, mainly focusing on weekends to prevent network overload from backup data. We also identified which servers needed file systems, VMware, or SQL backups.

It offers backup as a service, eliminating the need to manage backup servers. However, a con could be its retention policy, which only applies to its cloud-based storage. If they provided separate retention options for local backups, it would be beneficial. Additionally, the inability to back up data to tape is a downside, particularly for organizations requiring tape backups. Another con is the limited support for various workloads, such as OS applications. Expanding the range of supported workloads would enhance Druva's utility.

Overall, I rate the solution an eight out of ten.

We are using Druva inSync as an endpoint backup in our company.

Druva inSync is very easy to use. Creating policies and automatically deploying the solution on a user's machine is also possible. With the restoration features, whenever you want to restore something, it quickly starts the process and restores your data. The solution is also used for deduplication.

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.

I have been using Druva inSync for three years. I don't remember the version of the solution I am using. I know that we use the cloud version of the solution. I am a user of the solution.

The solution is useful since it does not impact the system's performance. It works. Every time it is involved in syncing some data, it works in the background. It also reduces deduplication, so the most recent data can be there in Druva inSync.

Overall, I rate the solution an eight out of ten.

All the data is well encrypted. In addition, the data is split into pieces so that if an endpoint is attacked or compromised with any kind of ransomware, the compromised machine can be relocated or restored. All the data that was previously backed up can be restored from the cloud. 

It has a lot of security features. Druva currently offers only the cloud version on AWS. Being a cloud solution, Druva goes by a lot of security compliances and provides a security portfolio. People are very skeptical of the data security in cloud solutions, and Druva has given consideration to that. 

It has some good geo-location features. If a machine is lost, when the machine is switched on and connected to the internet, that machine can be geo-located and tracked. It also has got the geo-wipeout feature. If someone tries to take out the data from a lost machine, they won't be able to do that. The moment an IT admin comes to know that the machine is no longer with a user, he or she can auto-run the geo-wipeout feature so that the data cannot be read by any third party.

Duality replication is a unique thing about this solution. Everybody's data is not backed up if the data is common. Similar data is not backed up from other machines.

The data backup also happens very smoothly. The bandwidth choking is very less. When the data is getting backed up, the users do not even get to know. There is no impact even when the users are not using high-speed bandwidth. 

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.

I have been using Druva inSync for nearly two years.

None of our customers have got any problem with Druva inSync. I have not found any customers complaining after the first installation. 

However, Druva Phoenix has a lot of issues and requires a lot of development, and people prefer Veritas or other solutions over Druva Phoenix.

There could be two aspects of scalability. The first aspect is where an individual user's data goes high. They provide a license that comes with 50 GB of data. If the users need more than 50 GB of data, they can switch to the next version of the license.

The second aspect is where the number of users increases. If a customer has 100 users today, and after a few months, wants to add 100 more users, the customer can just simply buy additional licenses.

Their technical support is okay so far. We do rigorous POC. Whatever customer queries are there, we answer them before the sale is done. After the sale is done, the customers normally do not have too many questions.

It is not a very tough job. It wasn't much of an effort.

Druva has got a technical distributor in India who implements it for us. All transactions are done through this distributor. This distributor does 10% to 15% of implementation, and the remaining part is done by the customer. If required, we also send our engineer to the customer. 

It is an expensive product for the middle class or SMB customers in India. A lot of top-level big companies also cannot afford this solution. 

During the license period, one can download the entire data from the cloud without paying any additional cost. This way the data can be easily recreated from the stored data when a machine is lost or the data is compromised.

I would recommend this solution. It is a good solution from the customer's point of view. Customers are very happy with this solution.

To adopt this solution, the mentality of valuing users' data is required in the customers. They should give a lot of value to users' data. In addition, they should be able to afford a backup for users' data. SMB customers can't afford this solution. Only profitable, big organizations can afford this solution. We mostly promote the Enterprise edition of this solution, and we are focusing on endpoint backup and cloud backup, but for both of these, the price is too high. We suggest trying this solution for the backup for 100 or 200 users from maybe the top management. People don't mind spending that much money on top management.

The eastern part of India is not a very strong business area. In addition, people are not very comfortable with moving the data to the cloud. They still think that storing data on-premises is more secure. We have spent the past year educating the customers.

I would rate Druva inSync an eight out of ten.

We use the tool as a backup on the client-side. 

The tool has good features. The backup is also accurate. 

The product needs to improve its support. 

I have been using the tool for a year. 

I would rate the product's stability a ten out of ten.

I would rate the product's scalability a ten out of ten. 

The tool's deployment took two months to complete. 

The product is fairly priced, I would rate its pricing five out of ten. 

I would rate the product an eight out of ten. 

We will be using it to backup Office 365. It's for Exchange, OneDrive, and Teams, that is, it's for SaaS backups.

It is simple to implement and use. It's very flexible.

The speed could be better.

It's not yet active, but it will be going in place within the next six months. We reviewed it over six months ago.

It's a stable and reliable product.

Technical support staff were very friendly and responsive, and I didn't have a problem with them.

The initial setup is straightforward.

It takes less than half an hour to deploy. The part that takes the longest is the one where you're defining your policies. It's a couple of clicks, and you're done. It's very quick if you've got the correct permissions; then it's just a matter of connecting your environment to the backup environment.

We did it ourselves.

It can be done by one person if you've got all of the required permissions. If you've got your Office 365 permissions, you don't need anybody else if the person deploying it will be the same person who is going to manage the Druva environment as well. If not, two people will be required.

Out of all the solutions we evaluated, Druva inSync was the most affordable.

There are additional costs if you want extra storage. Other than that, there aren't any additional costs.

Their site explains the different features you get with the different types such as Elite, Enterprise, and Basic.

We evaluated Veeam and Barracuda.

With Veeam, the problem was that it wasn't a SaaS solution. We would still have to build the infrastructure. There were one or two requirements that we didn't meet as well.

We wouldn't be able to do self-service backups and restores and would have to still get an admin to do it.

Do a POC of what you have, once you have a clear understanding of the needs you're trying to meet.

There are so many offerings out there, and some of them give you more than what you require. If you know what you want and you have clear requirements, then you can actually simplify your choices.

I would rate Druva inSync at eight on a scale from one to ten.

With Druva inSync you can restore at the file level, and you can also import the backup record into the extension level of your files.

It is not resource-hungry by default, and the backup and restoration processes are very simple.

You can configure it at any time.

The main benefit of this solution is that it automatically scans the files for ransomware after the backup is complete.

It protects during the backup from ransomware to ensure it is virus-free at many configuration levels. You can configure according to your requirements.

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.

We have been using Druva inSync for three or four years.

Druva inSync is a stable solution, which is why we use it.

Druva inSync is scalable.

We can add 10, 20, 30, 50 users on a yearly basis. But not nearly as much. Because we have a limited number.

We have not contacted technical support, as we have not had any issues.

The installation and configuration are both very simple.

We don't need much to install and maintain this solution.

There are no licensing fees.

I would recommend this solution to others who are interested in using it.

I am very happy with this solution, I would rate Druva inSync a nine out of ten.

We use it only for the backup process. We have approximately 200 licenses.

It has a straightforward installation.

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.

I have been using Druva inSync for three years.

Their technical support is fine, but they take too much time to resolve a problem. Sometimes, they take three to seven days to resolve a problem.

The initial setup was straightforward. It took us just a day.

The pricing of Druva inSync is very high as compared to other cloud backup solutions. 

I would not recommend this solution to others. I am not happy with this solution. We got this solution for the cloud backup of our organization. If the cloud backup is not running and the user backup is not going to the cloud, then what is the point of using this solution?  If users are having problems with their day-by-day work while Druva inSync is taking backups, what is the point of installing this software? We are planning to move to another solution next year. 

I would rate Druva inSync a two out of ten.

The recovery aspect of the solution is its most valuable feature.

The aspect of recovery and requiring very little effort for implementation as well as the simplicity of configuration are all very useful. It's difficult if you need a specialist to deploy the services. It doesn't make sense if you have a solution that is on the cloud, and you're trying to simplify everything including the solution itself, and it's difficult to deploy. With this solution, you don't have to worry about that.

The solution saves you money because you don't have to get a specialist, which can come at a great cost. 

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

I've been using the solution for eight to nine months.

It's widely accepted as a solution and it's very stable. They have documentation, etc., which is easy to understand.  There's also always development and improvement happening on the tech. It's not a solution that is sold and then there are no improvements. The constant updates gives me confidence that if a company is constantly working to improve itself, it's always working on its stability and reliability.

The scalability doesn't offer us any challenges, and I don't foresee any challenges in the future either.

I'm not sure how it would be for a bigger organization with a larger setup, however. My scalability needs wouldn't match, for example, a regular enterprise-level organization. We have about 100-110 users on the solution on a daily basis currently.

I've personally never been in touch with technical support. Someone for the technical side of our organization would handle that.

We did use a different solution for a virtualized server environment. This is our first experience with Druva for desktop/laptop backups, but we have used other solutions for server backups. We've used free versions as well as paid versions.

The initial setup was very straightforward. It was nice and simple. 

I'm not sure how long deployment took. I would estimate that it took, for the complete deployment, from the server-side, etc., half a day or so. For us, the process was quite comfortable, but I believe it could have been even easier.

Only one person is needed for deployment and you do not need anyone to handle the maintenance. There's a person required, obviously, to check on things from time to time but there are no specialists required. 

We had assistance with implementation help from a consultant. The consultant and the rest of our admin staff handled everything.

We did evaluate other options. At one point in time, there were other solutions in the market, but Druva was financially more viable for us. Mostly, this was in terms of the hardware required for deployment. The fact that it is on cloud-based, and didn't require us to prepare any hardware was financially a huge selling point. 

Druva has a tie with Azure. We did not directly choose Azure as our cloud and we've not engaged in the procurement of a cloud. 

Druva can be used on the desktop, for laptop backups, and on your virtualized environment backup.

I would recommend the solution to others.

I'd rate the solution ten out of ten as it currently serves my purpose.