Skip to main content



How can we help you?


Druva Documentation

Frequently asked questions

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

Are violations deleted once the non-compliant files no longer contain sensitive data?

No, the violations will not be deleted. The non-compliant file will move to the Resolved tab.

Is a new entry created with every completed snapshot for the same file that continues to violate a compliance policy?

A new entry is not created. The same entry with the updated count is displayed only when the file's modification time is changed. Additionally, no new entry is created after every completed snapshot for the same non-compliant file.

Can I map the same set of users across different compliance policies?

Yes, you can map a compliance policy with multiple profiles. Alternatively, you can map a single profile with multiple compliance policies.

What happens if administrator disables a few user accounts? Does inSync still index the user data?

After an administrator disables the users, inSync stops backing up data for the disabled users. Therefore, inSync does not index data for the users as soon as they are disabled.

Can I check data violations for preserved users?

As an administrator, you can see all the violations on historical data of preserved users. After you preserve a user, inSync stops backing up data for the preserved user and new compliance policies do not scan the historical data for violation checks.

What happens if a snapshot is scanned and a violation was reported, but the administrator removes that snapshot?

In such cases, inSync will report the violation. inSync will not delete any violation.

I have created a new custom sensitive data using different matching criteria and regular expressions. When will inSync scan files using the newly defined sensitive data?

inSync does a complete re-scan of the latest snapshot that is created after the new sensitive data was defined.  Thereafter, inSync scans only the incremental snapshots.

Why am I unable to download a non-compliant file?

File download fails if the file was compacted. In such case, inSync displays the following error message:

File-name cannot be downloaded as it has been compacted from Storage as per the retention policies of your organization.

What happens if the latest version of a file or email and its previous versions are in a different state?

For example, if the latest version of a file is marked as resolved whereas previous versions are in quarantine state, inSync will continue to display such files in the quarantined state. Therefore, the inSync end user will be able to download or restore the latest versions of the file but cannot download or restore previous versions of the file.

What happens when the inSync end user tries to download or restore quarantined files?

The following behavior is observed when a inSync end user tries to download or restore quarantined files:

  • Download of a single quarantined file will generate an empty file of size 0 byte
  • Restore of a single quarantined file will generate a temp file of size 0 byte

What happens when the inSync end user restores/downloads a folder which has one or more quarantined file?

The inSync end user will not be able to download or restore the quarantined files that are in the download folder. Rest all files will be downloaded or restored.

What happens if inSync administrator unquarantines a non-compliant file or email?

inSync cloud administrator or legal administrator can unquarantine a file or email violation. When you unquarantine a file or email, then inSync resolves the latest version as well as all the previous versions of the file or email. Additionally, inSync displays the violation in the Resolved tab.

Following is the impact of unquarantining a violation:

  • For administrators: Administrators can restore the non-compliant file or email to the user’s device. Administrator can also download the non-compliant file to a local computer.
  • For inSync end users: inSync end users can download or restore the non-compliant file or email through inSync Web or through inSync Client.

What file extensions are scanned by inSync to report Compliance violations?

Here is a list of file extensions (and their MIME types) that are scanned by inSync to report compliance violations.

By default, the following Google Workspace native files' MIME types are scanned by inSync to report compliance violations:

  • application/
  • application/
  • application/
Category MIME Types File extensions

Text Files

text/csv .csv
text/plain .txt 
text/tab-separated-values .tsv, .tab
Rich Text Format
application/rtf .rtf
text/richtext .rtx
Emails application/ .msg

MS Office Documents

application/msword .doc, .dot
application/msword2 .doc, .dot
application/msword5 .doc, .dot
application/ .doc, .dot
application/onenote .onetoc, .one, .onetoc2
application/ .xls, .xla, .xlt
application/msexcel .xls, .xla, .xlt
application/ .xlam
application/ .xls, .xla, .xlt
application/ .xls, .xla, .xlt
application/ .xls, .xla, .xlt
application/ .xlsm
application/ .xlsm
application/ .xls, .xla, .xlt
application/ .ppt, .pot, .pps. ppa
application/mspowerpoint .ppt, .pot, .pps. ppa
application/ .ppam
application/ .pptm
application/ .sldm
application/ .ppsm
application/ .mpp
application/ .docm



inSync does not scan documents saved in Strict Open XML Document format. 

application/vnd.openxmlformats-officedocument.presentationml.slide .sldx
application/vnd.openxmlformats-officedocument.presentationml.slideshow .ppsx



inSync does not scan documents saved in Strict Open XML Document format. 




inSync does not scan documents saved in Strict Open XML Document format. 

PDF Files application/pdf .pdf
application/x-pdf .pdf

Open Documents

application/vnd.oasis.opendocument.presentation .odp
application/x-vnd.oasis.opendocument.presentation .odp
application/vnd.oasis.opendocument.spreadsheet .ods
application/x-vnd.oasis.opendocument.spreadsheet .ods
application/vnd.oasis.opendocument.text .odt
application/x-vnd.oasis.opendocument.text .odt

Archive files

application/zip .zip
application/tar .tar
application/gzip .tar.gz
application/bzip2 .tar.bz2 

Note: To report compliance violations, inSync scans the files by MIME types and not by file extensions. The file extensions column lists the file extensions that are associated with a particular MIME type for referential purposes.  

Does inSync scan archive files for violations? 

Yes. inSync scans files and email attachments for the following archive file types: 

  • *.zip
  • *.tar
  • *.tar.gz
  • *.tar.bz2

You can enable scanning of archive files from compliance settings. For more information, see Modify Compliance Settings.

When enabled, inSync scans archive files for violations and displays the archive file under File Violations. Click the archive file name to view details of the violation and click the Download Details link to download the list of violated files in the archive.

For emails, inSync scans archive files in email attachments and reports violations, if any, on the Email Violations tab. Any action that you take is applied on the parent archive file. For example, if you resolve a violation, inSync resolves all the violations in the archive. 


  • inSync does not scan password protected archive files.
  • inSync scans archive files only up to 2 levels in the hierarchy.
    For example, if the archive file has the following structure: > File > File > File > file.txt
    inSync will only scan till > File
  • inSync supports a maximum of 50000 files in an archive for scanning. 
  • inSync scans an archive file of size maximum of up to 500 MB.
  • inSync scans a file inside an archive file of size maximum of up to 200 MB.
  • inSync scans a maximum of up to 50000 files in an archive file.