Code42 vs. Druva inSync

A side-by-side product comparison mapped to critical enterprise requirements

Like all business purchases, endpoint backup should be evaluated against a comprehensive list of critical requirements outlined by your buying team. This involves setting and prioritizing the product methodologies, features, and functionality that are most significant to your business.


If you're comparing Code42 against Druva inSync, you should consider the fundamental differences in the security, reliability, usability, scalability, and performance of each product in your requirements and gap analysis.


View the comparison chart to learn about these product differences - and what they mean for your business.

Enterprise Software Requirements Download pdf

Reliability

Code42

Druva inSync

Business Implications

Backup frequency is 15-minutes by default, configurable down to one minute.
(Source)

Backup frequency is 4-hours by default, configurable down to 20 minutes.
(Source)

Businesses deploy automatic endpoint backup to ensure that recovery point objectives and recovery time objectives are met. Code42’s automatic backup interval provides better protection against data loss by ensuring file changes are backed up at least every 15 minutes—compared to Druva’s default, and most commonly used, 4-hour backup interval which exposes users to several hours of data loss.

Back to Top
Security

Code42

Druva inSync

Business Implications

Encryption keys are owned solely by the customer and stored separately from data.
(Source)

One key is split and shared between the customer and the cloud.
(Source)

Code42 customers have ownership of their encryption keys—and therefore their data. Owning encryption keys and holding them separately from data limits exposure to data privacy breaches and blind subpoenas. Code42 cannot be compelled to provide access to your file contents because files are unreadable without your encryption keys. In contrast, Druva’s 2-factor encryption is a non-standard form of data security. Druva simply uses a username and password to protect a shared key to all data.

Encryption keys are unique to each user’s archive.
(Source)

A common “enterprise key” gives access to all user data.
(Source)

Protecting each user with a unique encryption key provides stronger data security than a common key method. A common encryption key drastically increases the amount of data that would be exposed if a key is compromised. Consider this: if a single user’s key is compromised under a unique encryption method, only that user’s data would be accessed. In contrast, Druva’s use of a common key—protected only by a user’s credentials—means the entire organization’s data could be accessed following the loss of a single computer or the compromise of a poor password. Druva uses a common encryption key method because it utilizes global deduplication. Druva claims global deduplication results in storage savings, but is that savings worth the risk to your data when Code42 eliminates storage concerns by offering affordable, unlimited cloud storage?

Back to Top
Usability

Code42

Druva inSync

Business Implications

Device CPU is configurable by percentage, and throttling can be applied contingent upon whether a user is present or away from the device.
(Source)

Device CPU priority is configurable by “Low,” “Normal” and “High” pre-sets only, and throttling is not available to account for times when a user is present or away.
(Source)

Endpoint backup must support user productivity—not inhibit it. Granular CPU customization helps organizations safeguard against paused backups by ensuring the software does not slow user devices. Code42’s present/away settings prioritize backup resources at the most favorable time for the user.

Code42 provides flexible cloud deployment options—public, private, hybrid—all available via the same software.
(Source)

Druva offers separate software for inSync Cloud and inSync On-Premise deployments.
(Source)

Code42’s flexible cloud architecture uses the same software for all deployment models, meaning there is no need to manage secondary client applications. By contrast, Druva offers separate inSync software for on-premises deployments and public cloud deployments— increasing the burden of IT management and making it more difficult for customers to mix, manage or change deployment types.

Secure, full-text file search and indexing within an individual’s archive.
(Source)

File search is conducted across all user archives but pertains to metadata only.
(Source)

Unlike Druva, Code42’s file indexing and search is not limited to metadata and file names. Code42 supports full-text indexing to enable designated admins to search all information and content in a file. The ability to perform a keyword search significantly increases the speed at which admins can identify files that are connected to legal and incident response situations, and eliminates the need to restore all of a user’s data in order to locate specific files.

Back to Top
Performance and Scalability

Code42

Druva inSync

Business Implications

File restores are requested from a user-aligned backup archive.
(Source)

File restores are requested from a global backup archive.
(Source)

Druva’s use of global deduplication slows restore speeds—especially at scale in a large enterprise. Because files or data blocks are not grouped by user, Druva’s backup system must search the entire data store (rather than a user-aligned archive) in order to locate requested data. This process slows the file restore process and forces the end user to wait at the most critical time—when a lost file is needed.

Laser-focused dedication to enterprise endpoint backup.
(Source)

Divided between endpoint backup, server backup, mobile backup and sync/share technologies.
(Source)

It’s a SaaS world—and the result is businesses can more easily implement the technologies that best meet their objectives. Today, most choose a best-of-breed strategy to ensure maximum performance and adoption. A “Swiss army knife” approach to an enterprise technology may offer some advantages for IT and end users, but when a vendor spreads its capabilities too thin, rather than striving for expertise in a core competency, its technology often falls short in critical areas. Code42 is fully dedicated to our core competency—seamlessly backing up end-user data so enterprises can view, analyze and restore files, and remediate and recover from any data incident.

47,000 business customers.
(Source)

4,000 business customers.
(Source)

Code42 is a trusted partner to more than 47,000 businesses of all sizes, including some of the largest enterprises in the world. Our proven track record—including multiple instances of 75,000+ user deployments—gives enterprises confidence that we can and will scale to support the demands of their business, allowing them to achieve certainty of data recovery and visibility.

Back to Top