Druva inSync Reviews

I am using Druva inSync for taking backup of our mailboxes, our Teams, groups, Teams channels, SharePoint, and OneDrive. We are using it for taking our M365 backups.

Druva inSync is providing single item recovery, which is very helpful. You do not need to restore the complete mailbox, and it is providing a data lock feature, so your data will be safe. There is no chance of deletion of data. They will give you many options to restore in the same mailbox, to restore in a different mailbox, or to restore in a different folder.

Druva inSync is completely integrated with our Azure AD. There is no chance that you will have a duplicate account and there is no loss of license due to duplicity of mailbox. It is a nice tool that is fully integrated with the M365 universe.

Single item recovery is a key feature. Backup happens at the mailbox level, and backups are happening through the API, so it does not get throttled by Microsoft. It also provides a data lock feature, and the snapshot of daily reporting is also good.

Suppose a user has missed five or ten emails that they want to restore. Instead of restoring the complete mailbox in a different shared mailbox or in the same mailbox, which would create data duplicity and result in a long restoration time, Druva inSync gives you single item recovery. You can go to the backups and select a single item, then restore it to the user's mailbox. This is also applicable to calendars, which is a nice feature.

Reporting is quite good. You will have plenty of reports that you can use, such as daily backup, daily failures, and API-related reports. You can create groups which are Azure groups, and it also supports dynamic groups. You do not need to manually add users, so your sources will be dynamic.

Druva inSync is a very competitive product and cost-effective. If you want a smart product that is capable of restoring and doing backups, Druva inSync is one of the biggest providers.

Earlier, restorations were taking a day's time. Now it takes just hours or minutes based on the size. It saved time and space. Now it does not need restoration of the complete mailbox, only a few items, and there is no duplicity. We can restore in the same mailbox or we can restore in a shared mailbox.

We were using a different solution, which is Veritas. We moved to Druva inSync because of the pricing, the single item recovery, and other features that I mentioned.

Druva inSync has impacted our organization positively because our data restoration time is now very low, and there is no duplicity of restoration. We know what type of data we are going to restore and what our restoration point is. It is giving us a disaster recovery mechanism in terms of any malware or ransomware-related attack. We can restore the mailbox as quickly as possible, and we can even restore it as a PST file. It is giving a positive impact to the organization.

Druva inSync provides single item recovery which helps in restoring specific emails without needing to restore the entire mailbox, saving time and reducing data duplication. It is fully integrated with Azure AD, minimizing duplicacy of accounts and license loss. It allows restoration in the same or different mailbox or folder and supports dynamic groups. It also offers a data lock feature and snapshot of daily reporting, adding reliability to our operations.

Druva inSync's competitive pricing and effectiveness in data backup and restoration make it a leading choice, especially with its ability to work efficiently with M365.

This significantly reduces restoration time from days to just hours or minutes, meaning it saves both time and space as it does not require complete mailbox restoration.

The tool's integration features, competitive cost-effectiveness, and the ability to perform quick restorations highlight its value, complementing its pronounced impact on the organization's overall efficiency.

Druva inSync can improve if we can integrate a chatbot. Instead of going through the portal, if there were a chatbot and we could restore mailboxes and groups by chatting with the chatbot, that would be an added feature.

The restoration of notes is a limitation. Druva inSync is not capable of restoring notes. If users have something saved in notes, Druva inSync will not be able to restore it. If it could enhance the capability to restore notes, that would also be helpful.

If it were to enable chatbot functionality and by just saying to the chatbot to restore a mailbox or restore an item to the mailbox, that would enhance productivity. There is some limitation of restoration for certain folders. If those could be fixed, it would be a perfect product.

I have been using Druva inSync for the last seven years.

Druva inSync is stable.

It is scalable. You can integrate with M365, you can integrate with Azure, you can integrate with dynamic groups, all through APIs. It is a quite stable and scalable product.

Druva inSync has top-notch customer support and it comes free. You do not need to pay extra, and there is a chatbot facility available to connect with customer support. Their documentation is thorough and helpful.

We were using a different solution, which is Veritas. We moved to Druva inSync because of the pricing, the single item recovery, and other features that I mentioned.

We came to know that Druva inSync is the market leader, and we evaluated it. It satisfied all our needs, so we chose to use it.

If anybody is looking for a cost-effective and effective data backup and restoration solution, please go with Druva inSync. It is highly integrated and a recommended product for saving your mailbox data or saving your M365 data. I would rate this product a nine out of ten.

We collect reviews for software products. After visiting our site and downloading reports on Acronis and Druva inSync, I would like to know if you are working with those products.

The best features of Druva inSync from my perspective are what attract customers to the product. I appreciate the good features it offers, which are important for the community.

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.

I have six and a half years of experience with Druva inSync.

Regarding cloud integrations for Druva inSync, I have experience with cloud integrations with Microsoft 365 and Google Workspace. I have faced some challenges with these integrations.

On a scale from one to 10, I would rate Druva's support at nine, with 10 being the highest.

Positive

Two or three people usually take part in deployment of Druva inSync. The typical deployment time for Druva inSync is two days maximum.

Druva inSync does provide return on investment in the end through cost reduction.

From my perspective, Druva inSync is reasonably priced. I am quite satisfied with the licensing cost.

I have been working with Druva inSync for six and a half years. I find Druva inSync's legal hold capabilities useful. Druva inSync's automation has reduced manual intervention in my data management processes. My overall review rating for Druva inSync is nine out of ten.

A typical use case for Druva inSync is that you can back up from any location, even from a hotspot. Regarding air gap, Druva inSync is completely immutable and highly secure. For availability, it has up to 11 nines uptime and 99.5%.

It is a good product for endpoints and Druva inSync servers, and it works effectively for data centers.

The organization has seen ROI from using Druva inSync through bandwidth saving, storage, and manpower optimization.

For managing compliance, users can search on Google and write compliance requirements that meet all standards.

The AI capabilities of Druva inSync are quite high compared to other products.

The solution provides significant ROI through bandwidth saving, storage, and manpower optimization.

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.

I have more than 1.5 years of experience working with Druva inSync.

The stability of Druva inSync is quite high and very stable, warranting a rating of 10.

The solution's suitability depends on the size of clients using Druva inSync, whether they are small, medium, or enterprise-sized businesses. If the use case fits the organization, then it is appropriate. The effectiveness depends on how the solution is presented and how it connects to specific needs.

The scalability of Druva inSync deserves a rating of 10.

The technical support from Druva inSync deserves a rating of 10.

Positive

The initial setup of Druva inSync is easy, generally taking just five minutes to deploy.

The deployment time is typically less than one hour, sometimes even less than one minute.

The organization has experienced ROI from Druva inSync through bandwidth saving, storage, and manpower optimization.

I am a technical consultant for Druva inSync. Based on my experience, I would recommend Druva inSync to others. On a scale of 1-10, I rate this solution a 10.

It removes the headache and hassle for users. However, there’s a critical issue, especially with endpoint users: any change made will immediately reflect, and another problem is that the backup only retains data for 30 days. 

Some users change files they might not remember or need to revert after a few weeks. According to system configuration and regulations, this limitation means that data from more than 30 days ago can't be retrieved, which is frustrating.

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.

I have been using Druva inSync since 2017.

There's some delay in the response. I’m getting support with full access and training, which is good. However, the training approach refers users to the portal and guidelines. While this is helpful, technicians or the technical team sometimes need specific information. They can't always find what they need through the general index or videos. The help or guide videos should be more targeted to specific issues. Currently, technicians have to go through all the training materials, which may be a waste of time for those who already know what they need. It’s challenging to find precise information quickly.

Neutral

From an advanced perspective, inSync seems to be the best solution for endpoints. However, its server-side and backend application support, including databases, is not as strong as Veeam's. Veeam is built explicitly for databases and more technical requirements, making it a more robust option.

The initial setup is straightforward. You simply deploy the agent to the end user and then configure it. If everything is scheduled with the end user, deploying it takes about ten to fifteen minutes, depending on the end user's connectivity for the backup.

Just install the agent, and it will detect and start downloading immediately.

It saves 75% time.

Pricing is average, but compared to the other solution, they need to revise their price list.

Some data can be decrypted, but some sensitive data remains highly encrypted, which takes time to access. To address this issue, we move to CompLoft.

Overall, I rate the solution a six out of ten.

We use it to back up endpoint data for our remote users who use laptops. With the work-from-home culture, backup is critical even when users are not in the office. 

Its primary function is back up, and it works very well. It's lightweight, easy to install and configure, and forget it, and it does its job automatically.

It works very well and fantastically. 

Data recovery is quick, and it also has a self-recovery feature. So, users do not need to contact IT administrators to recover lost or deleted files. They can do it on their own, eliminating waiting time.

The main advantage is the backup. In the event of a laptop crash, theft, or loss, we can instantly restore the user's data.

Druva has tied up with most of the major certifications like GDPR and things like that. So, it is a very safe and secure product.

One functionality I would like is the ability to manage multiple Office 365 tenants from a single console. Currently, Druva can manage only one Office 365 tenant per console. As a customer, I should be able to manage all Office 365 tenants from a single console. This is one product feature I am looking for.

We deployed it just three months ago. 

It's a very stable product and we haven't encountered any challenges.

It's a very scalable product. It's a SaaS-based, cloud-based model, so it's highly scalable.

There's no issue with the support. The support is excellent.

Positive

It is a very simple product and very easy to install and configure. Nothing really complex about installation.

The deployment took maybe two weeks because they have automated deployment scripts. So, two weeks is fine.

Two to three people were required for both deployment and maintenance. 

The pricing is a bit on the higher side compared to other products in the market.

I would rate the pricing a seven out of ten, with one being very cheap and ten being very expensive. 

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

The user data on laptops is very critical. You should have an endpoint backup product on the user's machine to help you recover data in situations like loss of internet connectivity. This is one of the key products that any organization or endpoint should have.

I recently installed 800 users for inSync for SaaS and Salesforce. Druva inSync is good for endpoint backups.

We get control over authentication policies and create an agentless backup by generating a token for that. An email and a password are not necessary for that, and we can generate and install it on the system. The solution is also easy to use.

It would be good if bare metal backups were possible.

The solution is stable. We deployed the central piping eight to nine months ago. We perform monthly checkups, and there have been no issues to date. All the backups have been done. If the backup is failing, the solution will also alert you that a particular agent cannot back up, along with a reason, such as it being offline for a few hours.

The solution can be scaled. We have deployed agents across five to six companies.

I have a regional distributor for that and a group to which I haven't been added. If I have a query, I just call them directly, and they help me. They told me to create a case and send them the details before helping me out. The technical support is good.

The initial setup is very straightforward. You can explain how to do it remotely. If you have good knowledge about the interface, you can explain to a remote client how to perform the setup. You also have a status update of any patches. For example, it tells us if an agent is not updated.

If you know the interface well, the solution will take approximately half an hour to deploy, including explaining everything, creating a policy, building a profile policy, etc. If you call the client, you can explain what they need. After creating a policy and a profile, you can add an agent and apply that policy to the agent.

The pricing is good. The pricing changed since Commvault Metallic came out. They pitched unlimited backup, and that's the main reason Druva changed their prices. Also, Druva told us to merge our endpoint and SaaS licenses, which is good for people who are getting an endpoint backup since they will also get a SaaS backup.

I talked with my client, who has a private cloud hosted in someone else's environment. He wants to take a backup for that, and I need an image backup for bare metal backup. But it's impossible on the cloud, and Phoenix is not doing it either. Even if we installed the deployment on an agent, it won't take it. However, Arcserve does it, so we're pushing for Arcserve for the same client.

I prefer to go slow when setting up the solution because clients will have many doubts. The solution won't start up in ten minutes. If you take half an hour with the client and explain every step, setting up the solution will be very easy.

I rate Druva inSync an eight out of ten. After COVID, many people have been traveling remotely, and that's not an easy task for offices. If you don't have a lot of data in your systems, you can go with Druva since backups can be done in a cloud-based manner, and everything is secure.

Our primary use case is for backing up our endpoints. This helps clients who have critical data on their desktops.

One of the most valuable features is it is available on the cloud, so I do not need to make a firewall. Second, the backup speed is outstanding. The third thing is that the section policy is very good and gives you a lot of flexibility and granularity regarding what you need to back up.

The one area that needs to improve is the pricing.

I have been working with Druva inSync for the past six months.

We have not experienced any issues with stability at this point.

It is a very scalable product.

We have not had any issues with technical support so that is excellent.

The setup is straightforward and easy to install. The maintenance as well is simple.

It is very light and does not take up a lot of resources on your hardware. The deployment takes around one day to complete.

The pricing is thirty-five dollars per year or three dollars per month per user.

We were using the on-premise solution. And we compared it with the other option which was available. Most of the options that were available were still on premises. And then we had to just have a setup office, and make sure those firewalls and everything is up and running. And then, internally also, it becomes a security threat on one machine, all the data is there, all the confidential data is there. Or we have, what happens, I have the login, the admin or login, and I have the backup of all the machines, but nobody else can access the data. 

I would recommend individuals go ahead and buy it. It is easy to use, buy, and manage. I would rate Druva inSync a ten out of ten.

Our primary use case includes Office 365, endpoints, Teams, SharePoint, and Salesforce. However, we have not supported any mobile devices.

The way they handle the backups is pretty good. Reporting is also a huge positive, especially the Excel reports and the reporting tool.

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.

I have been working with Druva inSync for six years.

Druva inSync is not very stable. We have faced several issues, such as abrupt backup failures, internal errors, and unexplained removal of features like Cloud Cache. The documentation on their website is also not very clear.

Druva inSync is very much scalable. I would rate it an eight out of ten for scalability.

I am not very happy with the support. They tend to rely on bookish knowledge and often require a lot of follow-ups. I would rate their support a six out of ten.

Neutral

The initial setup is not very easy. It requires a lot of skills and backend preparations. It's not a finished product and definitely needs a lot of improvement.

Druva inSync is a good solution despite numerous cons. Currently, it is enjoying a good market share due to limited alternatives for endpoint and laptop backup solutions. However, it is not a finished product and needs significant improvements.

I'd rate the solution seven out of ten.

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.