📝 Note
​This article applies to

FAQs

Druva inSync solves business challenges related to endpoint data protection and governance, including data backup and restore, governance (visibility, control, and eDiscovery enablement), and DLP (Data Loss Prevention).

Druva inSync provides complete data loss prevention including data encryption on endpoint devices, geo-tracking of devices, remote wipe on laptops and mobile devices, and restore of user data, preferences, and system settings.

Druva inSync enables eDiscovery for data stored on endpoint devices. inSync offers a complete governance solution for endpoint data including a legal hold workflow that provides identification tools with federated search and audit trails, collection and preserve-in-place capability, and eDiscovery enablement with direct access to Druva from an eDiscovery platform.

Druva inSync is architected for data storage efficiency. inSync’s global, app-aware deduplication delivers up to 90% in storage and bandwidth savings, which has the added benefit of providing a better end-user experience with up to 6x faster incremental backups than any competitor. Druva accomplishes this by deduplicating blocks of data across all users in an enterprise, each subsequent user transfers and stores less data until maximum efficiency is achieved.

Druva inSync provides a complete set of tools to accomplish large-scale device refreshes and OS migrations across endpoint devices. Features include mass deployment support for SCCM and Casper, data and persona backup for capturing and restoring of user preferences and system settings, and wizard-based workflows to enable both user and IT-initiated device refreshes with minimal overhead and manual involvement.

With inSync’s unique Integrated Mass Deployment (IMD), delegated administration, and deep directory integration for AD save up to 75% in deployment time.

Druva inSync offers a complete set of privacy settings required by any global enterprise. inSync enables IT to set group policies that allow users to prevent administrator access to their data, for example, officers of the company. In the case of litigation, provisions can be made to enable legal department access only.

Druva inSync Cloud ensures data durability, which includes up to 3-way data redundancy across data centers. Send your data only once; redundancy is automatic and transparent at no additional cost.

Druva inSync offers a unique and highly secure 2-factor encryption scheme. By utilizing this model, no one except the customer can access their data, not even Druva. This enables companies to have complete data security and privacy: data cannot be handed over if subpoenaed or a government request is made to Druva. In addition, we feature a published vulnerability assessment, pen tests, data scrambling, and compartmentalization to ensure the greatest levels of data security and privacy for our customers.

The Druva inSync cloud is up to date with the latest in infrastructure and application security and compliance, currently complying with SOC 1 (SSAE 16, ISAE 3402, formerly SAS 70), SOC 2, SOC 3, ISO 27001, PCI DSS Level 1, ITAR, HIPAA, FedRAMP, FIPS, FISMA, and others. To learn more, please contact us directly.

If you are an existing customer, please refer to the SLA in your Master Customer Agreement (MCA).

Druva inSync has a global footprint with 30+ independent regions supported and complies with regional Data Privacy Acts (DPAs), including the latest EU data protection requirements. To achieve this, Druva inSync builds on top of extensively certified cloud infrastructure from AWS and Microsoft Azure with a set of data security and system controls, including enabling administrators to map users via profiles to regions, ensuring your data is only accessible by you and resides in the location required.

Druva inSync is built for the cloud and delivers unique innovations with it’s patented global deduplication engine, 2-factor encryption, and cloud-based storage architecture. Furthermore in the cloud, AWS provides innovations such as Cloudfront, Glacier, redundant data center architecture, and S3 object storage, providing customers not only cost efficiencies, but more effective ways to manage data over time.

Global deduplication delivers not only substantial storage savings but also tremendous bandwidth savings: as high as 90% with significantly faster incremental backups (up to 6x faster). These bandwidth savings, coupled with resource throttling on the client lowers the impact to network bandwidth and minimizes client resource consumption, creating a better overall user experience.

Druva is fully configurable via administrative profiles that map to groups of users. These profiles provide advanced settings, such as backup frequency, which can be set to happen as often as every few minutes, to provide continuous data protection. If authorized by IT, end users can modify their backup schedules as needed to best fit their requirements.

Utilizing our 2-factor encryption scheme, Druva’s approach to encryption key management ensures data cannot be lost or corrupted, as only an encrypted token is stored per user. This model prevents others outside your organization from having access to your data, a known problem when both the key and data are stored in the cloud. With AWS’s data durability, the encrypted key data is safely stored, and as an added precaution, admin/user credentials can also be reset if required.

LEARN MORE ABOUT DRUVA’S SECURITY

For customers requiring their data to stay in the country of origin, in order to be in compliance with regional data regulations, Druva provides full customer control over regional data storage assignments per user via profile settings. Customer data stays where it’s intended and doesn’t move out of that region without the customer explicitly doing so.

Druva offers public, private, and hybrid cloud options.

Druva provides advanced out-of-the-box reporting capabilities, including a comprehensive, rich set of in-system reporting with exporting functionality.

Druva has no limitations on concurrency and provides enterprise-level scale into the 100’s of 1000’s of users, both on-premise and in the cloud.

inSync backs up system and app settings every 30 days. After every backup, the previous snapshot is replaced with the latest data. Hence, you can restore only from the latest snapshot and do not get to choose any older setting to restore. More importantly, system and app settings restore becomes available to the inSync user only when the user adds an additional device or replaces an old device. Thus, system and app settings restore is not a part of a normal restore view or process.

Once the user is deleted from the inSync Admin Console, data cannot be retrieved for the user.

The data is marked for deletion, and the compaction triggers after 7 days of user/device deletion. As the association between device and user is broken the data is lost.

The backed up empty folders will be skipped while restoring the data; however, if the empty folder has another nested empty folder, the parent folder will be restored but not the nested folder.
For example, a user has C:\Test\Test1, both the folders are empty, then Druva will not be backing up Test1. When you restore Test, it will only restore the Test folder, and Test1 will be skipped.

Druva inSync cloud stores the backed-up files/data in block storage. Druva inSync does not scan files/data is backed up.

If you decide not to purchase a license at the end of your Microsoft 365 backup trial, your backups will cease, and the data will be deleted from our systems. To remove the Druva->Office365 authentication, you can revoke access via the Druva console. If you only have one configuration, you might not see this option. Alternatively, you can manually delete the app in Azure to remove any access granted by the service account. For detailed instructions, please refer to our documentation.'

To review logs and determine why files were restored without user prompts, you can check the restore activity in the admin console under the reports section. Additionally, you can examine the User Audit Trails within the Audit Trails section. For more information, please visit these links: Restore Activity Report and View Audit Trails.

To find and manage excluded file types in Druva backups:

If you have "Include all files" but also specified "Exclude file types and folders," the listed file types will be excluded. There are two types of exclusions: local and global. For additional information, you can refer to these articles: Create a Profile and Defined File Types for Backup.

Yes, users can restore data using the inSync Web Console, which includes Google Workspace workloads. An admin must enable web restore via the profile settings. For instructions on how to enable web restore for users, please refer to the documentation.

To address throttling and continue backups with M365, you need to install auxiliary apps. Note that reducing the number of auxiliary apps is not part of the current workflow. If you need to do so, please contact Druva Support. This feature is available exclusively to customers with the M365 Advanced App. If you have the Druva Basic, Exchange Online+Public Folder, or SharePoint Online+OneDrive App, you can still manually install auxiliary apps.

You can adjust the User Backup Inactivity Alert through the Alerts Page. For guidance, see the reference article.

Applying a new template does not reset previously identified violations. Future scans will use the new template, but existing data related to past violations will remain.

To add storage regions to your account, submit a support case specifying the desired regions. inSync is the product name and comes in two versions: GovCloud and Public Cloud.

Our Discovery API identifies the mailbox type within 24 hours, so you can expect to see changes within the next 24 hours.

If you do not purchase a license at the end of your Microsoft 365 backup trial, your backups will no longer run and will be deleted from our end. To remove the Druva->Office365 authentication from the Druva interface, you can revoke access via the console. However, if you have only 1 configured, you might not see the option. Alternatively, you can manually delete the app within Azure to remove any access granted by the service account. Here is the documentation for more information : https://docs.druva.com/SaaS_Apps/Protect_Microsoft_365_Apps/010_Office_365%3A_Get_Started/Configure_Druva_inSync_for_Office_365