Overall Satisfaction with Druva inSync
We are using Druva In-Sync across the whole organization for device and SaaS backup (G Suite). This allows us to have personal devices backed up and restorable by the individual, as well as the admin. The G Suite backup covers our needs to keep our Google Drive data backed up without relying on Google's uptime SLA.
- Easy to manage by end users.
- Easy to restore by end users.
- Easy to manage by admin.
- Implementation of devices could be easier. Currently, you need to provide a spreadsheet with usernames and device serials/MAC addresses to implement in a batch
- Druva has reduced the cost of backup while also providing greater coverage than the previous product we used.
- Druva's bandwidth usage and CPU usage has been negligible to the end users.
- By backing up our SaaS storage, as well as our local devices, we have greatly improved our compliance as well as created a stronger DR solution.
We protect G Suite with Druva. It was super easy to implement and backed up all of our data very quickly.
Druva's compliance monitor has helped us understand our non-compliant data better and show us the users in the organization that are making non-compliant choices with data. This will help to tighten our compliance and train users to understand where they are making compliance mistakes.
- Code42 (formerly CrashPlan)
Code42 stopped supporting Windows servers, so we needed to move to another vendor that could support our Windows server in the cloud ASAP. Druva was able to do so and also cover our on-premise servers. The cost went up slightly to move to Druva, but we added a great deal more coverage with Druva (G Suite backup and compliance).
Do you think Druva Data Resiliency Cloud delivers good value for the price?
Yes
Are you happy with Druva Data Resiliency Cloud's feature set?
Yes
Did Druva Data Resiliency Cloud live up to sales and marketing promises?
Yes
Did implementation of Druva Data Resiliency Cloud go as expected?
Yes
Would you buy Druva Data Resiliency Cloud again?
Yes
COVID-19 Changes
We moved to WFH before implementing Druva, but since then we feel much more secure about our cloud backups. We previously relied on the cloud provider's SLA, but determined that was not enough and with WFH we rely on that cloud data even more so than in the past. Druva has also allowed us to back up more of our user's devices than our previous solution covered.
Druva InSync gives us a piece of mind that our data is backed and easy to restore, should be be hit with ransomware.
Not applicable, but I am sure that the feature set of inSync would make these issues much easier to deal with, should they occur
Using Druva inSync
75 - All users in the organization are using Druva for backup. This includes admin staff, membership coordinators, publications, insurance, accounting, and executives.
1 - I am the only admin for Druva in our organization and I find the admin console easy to use and understand. In fact, the fact that one person can manage it all was one of the main selling points for Druva.
- device backup
- cloud services backup
- easy restoration by the end users
- easy management
- We haven't dug very deep into the product yet, so I have nothing to share here. So far...
- Data governance is becoming a bigger issue and we hope to leverage that in Druva
Evaluating Druva inSync and Competitors
Yes - Code42 CrashpPlan. We replaced them because they dropped Windows Server backup coverage and we needed to have that for one server. Even though the server was now in the cloud, Code42 couldn't backup the Windows Server platform. Druva does so without a problem. Druva also allowed us to backup more device types than Code42.
- Price
- Product Features
- Product Usability
Product Features was the most important factor because we needed that server backed up. Once I saw the feature set and demo, price became the next factor and Druva was priced right for our organization.
I am happy with our process and selection. I don't think I would change anything. We looked at several products, had input from some partners, and decided on Druva based on their feature set and price.
Druva inSync Support
Pros | Cons |
---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
Support is part of the contract and I can't imagine not having it. Especially since this is a new product for us. I expect to use support several times in the coming year, whether it be fixing an issue or looking for help on using new features.
Not inSync related, but I was having a problem understanding how Druva Phoenix needed to be set up with our AWS FSx server and they were able to get on a virtual meeting with me and walk me through it in 15 minutes. Great support!
Using Druva inSync
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |
- Adding data to the backup scheme is easy for end users on their devices
- end use restores are also quite easy
- enabling the cloud backup was super easy
- deployment to the devices is cumbersome and difficult if you want the user data part of the deployment.
Yes - Keeps crashing on my iPhone Xs Max. I am going to try deleting it and reinstalling.