Skip to main content

 

Druva Documentation

Access legal hold data using WebDAV

inSync Cloud Editions: File:/tick.png Elite Plus File:/tick.png Elite File:/cross.png Enterprise File:/cross.png Business

Overview

You can access the user's legal hold data from endpoints such as computers and mobiles, and from cloud applications by using WebDAV. 

You can also access MAPI-based backup of emails through WebDAV. Following are the advantages:

  • inSync now supports multiple file formats - PST, MAPI  to export email data through WebDAV, providing IT and legal teams with flexible options to collect data on legal hold.
  • Every email backed up using MAPI is made available through WebDAV in the EML file format, calendar events are available in ICS file format, and contacts are available in VCF file format. VCF file format. 
  • A broad range of eDiscovery tools can support ingesting the EML file format which is the format in which inSync exposes MAPI and Exchange Online emails through WebDAV.  
  • This enhancement is available only with Elite and Elite Plus editions of inSync Cloud.

To know more about Messaging API (MAPI) that inSync uses to optimize efficiency for Outlook backups, see FAQs on how inSync backs up Outlook PST files. To know how the MAPI-based backed up data is arranged, see How the MAPI-based backup of emails data is arranged?

Step 1 of 2: Obtain WebDAV access details

To access legal hold data by using WebDAV, you must obtain the WebDAV access details. The WebDAV access details include your credentials and URLs to the storage where user data resides. If the users’ data is backed up on multiple storages, multiple WebDAV URLs are created.

 Note: inSync Cloud administrators can also access WebDAV using an API token. To know more, see Access WebDAV using API token as an authentication mechanism.

To obtain the WebDAV access details

  1. Click the relevant legal hold policy.
  2. Click Data Access. The data access URL and authentication details appear in the WebDAV Access Details area.

 

Access WebDAV using API token as an authentication mechanism

Only inSync Cloud administrators can access WebDAV using an API token. API token can only be generated by an inSync Cloud administrator and used to access WebDAV using any of the methods described in Step 2 of 2: Select a method for WebDAV access.

To log on to WebDAV, specify the email address of the inSync Cloud administrator who generated the API token as the Username and API token as Password when prompted for it.

Email address of the inSync Cloud administrator who generated the token is displayed in the Generated by field in the Access token for inSync APIs area.

To generate an API token:

  1. On the inSync Management Console menu bar, click wheel.png > Settings. The Settings page appears.
  2. Click the inSync APIs tab. The Access token for inSync APIs page appears.
  3. Click Copy Token. The token is copied to your clipboard.
    The Copy Token button is available only when the authentication token is valid. 
  4. If the token has expired, then click Create New Token and run the following steps:
    1. In the Expire on field, specify the expiry date of the authentication token.
    2. Click Done.

Note:

  • API token is associated with the email address of the inSync Cloud administrator, who generated the token.
  • If inSync Cloud administrators use SSO for login, use API token to log on to WebDAV.
  • inSync Cloud administrator who enabled the SSO can access WebDAV using both, API token and inSync username and password.
  • inSync Legal administrators cannot use API token to log on to WebDAV.

Step 2 of 2: Select a method for WebDAV access

You can access WebDAV by using the following methods:

Access WebDAV by using HTTP connectors within eDiscovery tools

inSync Client collects the EDRM-recommended metadata attributes of data that is backed up from devices of users who are on legal hold. inSync then provides WebDAV access to the preserved data and associated metadata. eDiscovery HTTP connector can be used to collect the preserved data and metadata attributes, parse through the data, and help data custodians to analyze and act on them.

For more information about creating a legal hold policy and accessing the WebDAV using AccessData, see Create legal hold using inSync. For more information about how AccessData can be integrated with Druva Druva inSync to mine data under inSync’s legal hold, see Using Druva Druva inSync with AccessData.

For more information about creating a legal hold policy and accessing the WebDAV using Recommind, see Create legal hold using inSync. For more information about how Recommind can be integrated with Druva Druva inSync to mine data under inSync’s legal hold, see Using Druva inSync with Recommind.

Access WebDAV by using a mapped network drive

Windows OS

Before you begin

If you are using a self-signed certificate, before you access WebDAV, you must first install the self-signed certificate as a Trusted Root Certificate. However, we recommend that you install and use a certificate signed by a Trusted Certificate Authority (CA). Using a self-signed certificate might involve potential security risks.

Procedure

To access WebDAV by using a mapped network drive

  1. Ensure that WebClient service is running on your computer.
  2. Click the Start menu.
  3. Right-click Computer > Map network drive. The Map Network Drive window appears.
  4. On the Map Network Drive window, provide the appropriate information for each field.
  5. On the Enter Network Password window, provide the username and password of the cloud administrator or legal administrator, and then click OK.

Mac OS

Before you begin

If you are using a self-signed certificate, before you access WebDAV, you must first install the self-signed certificate by using the Keychain Access utility in Mac. By using the same utility, you can then update the Trust setting for this certificate and mark it as a certificate that is always trusted for all users. However, we recommend that you install and use a certificate signed by a Trusted Certificate Authority (CA). Using a self-signed certificate might involve potential security risks.

Procedure

To access WebDAV by using a mapped network drive
  1. Open Finder.
  2. On the menu bar, click Go > Connect to Server. The Connect to Server window appears.
  3. In the Server Address, type the WebDav URL. For example: https://restore-c1-cloud.druva.com/webdav/Legal Hold Policy 1. Access_WebDAV_mapped_network_drive_Mac.png
  4. Click Connect.
  5. On the Enter Network Password window, provide the username and password of the cloud administrator or legal administrator, and then click Connect.

Access WebDAV by using a web browser

You can use a web browser to access the legal hold data via WebDAV, and then download the legal hold data to your computer. If the download fails or is interrupted, then you can resume the download by using download manager add-ons that are available for your web browser. The download manager resumes the download from right where it was interrupted.

To access WebDAV by using a web browser

  1. Open a web browser.
  2. In the address bar, type the WebDAV URL and press Enter.
    Note: If you are using a self-signed certificate, an untrusted certificate alert appears. Depending on the browser that you are using, you can click Proceed anywayI Understand the Risks, or Continue to proceed. However, we recommend that you install and use a root certificate signed by a Trusted Certificate Authority (CA) because using a self-signed certificate might involve potential security risks.
  3. Type the username and password.
  4. Click Ok

How legal hold data is arranged

After the WebDAV authentication, the legal hold policy folders appear. The hierarchy of the legal hold policy folders is as follows:

LegalHoldFolder.jpg
  • A legal hold policy folder contains folders for users that are on legal hold.
  • Each user folder contains device folders. 
    Note: Device names containing "/" and "," are replaced by %2F and %2C respectively. 
  • Each device folder contains backed up folders.
  • Each backup folder contains files and folders included in the backup.

Before a user is put on legal hold, inSync has backed up data multiple times. Over a period of time, the user can modify or rename folders and files at multiple occasions. Therefore, inSync appends a version number to the backed up folders and file names.

inSync checks for the last period (.) in the file or folder name and appends the version number before the period. This preserves the file extensions when versions are appended during backups.

Example:
Version v1 getting appended to Jellyfish.png will appear as:

Jellyfish,v1.png

If you have periods (.) in the folder names, version is appended before the last period in the folder name. This may result in the versions getting appended in the middle of the folder name with periods.

Example:
Folders Field.Reports and Transaction.Summary.Stats when appended with version v2 will appear as:

  • Field,v2.Reports
  • Transaction.Summary,v2.Stats

The version number indicates the snapshot number in which the folder or file is modified or renamed. A snapshot is a “point in time image” of the backup folders and indicates the state of the backup folders, which at a particular point in time.

If you view all backup data, then different versions of the same folders and files appear. For example: 

  • My Documents,v1/Jellyfish,v2.png
  • My Documents, v1/Jellyfish,v3.png 

Where, v2 and v3 are the second and the third version of the same file. This means that the user has modified Jellyfish.png twice.

If you view the last backup data of users, only the latest versions of the folders and files appear. This means that you will see only one version of the folders and files. For example:

  • My Documents, v1/Jellyfish,v3.png

Where, v3 is the latest version of the file.

For more information about viewing all backup data, see View snapshots of backup data

 

How the cloud apps data is arranged

Arrangement of Exchange Online data

If a user with Exchange Online device is put on legal hold, the data is arranged in WebDAV as follows:

  • Exchange Online emails are available in .eml file format. The emails are grouped based on year > month > date for ease of accessibility.
  • Exchange Online calendar is available in .ics file format, in the following directory structure:

    Exchange Online/Calendars/<Calendar Name>/<Calendar Name>/<Event ID>.ics

  • Exchange Online contacts are available as .vcf file format, in the following directory structure:

    Exchange Online/Contacts/<Contact Folder>/<Contact Folder>/<Contact ID>.vcf

Arrangement of G Suite data

Gmail data

If a user with G Suite device is put on legal hold, then the Gmail data is arranged in WebDAV as follows:

  • Gmails are available in .eml file format, in the following directory structure:

    Gmail/Mails/<Year>/<Month>/<Date>/<date_time_received-subject_of_email>.eml

    Notes:

    • The emails are grouped based on year > month > data for ease of accessibility. ​
    • The subject of email can be up to 30 characters.
    • If an email has multiple attachments, inSync creates an .eml file for the email and separate.eml files for every attachment after backing up the Gmail data. You can then view and access the .eml files through WebDAV.
  • Contacts are available in .vcf file format, in the following directory structure:

    Gmail/Contacts/<Contact Folder>/<Contact ID>.vcf

  • Calendar events are available in .ics file format, in the following directory structure:

    Calendars/<Calendar Name>/<Calendar Name>/<Event ID>.ics

Google Drive data

If a user with G Suite device is put on legal hold, then the Google Drive data is arranged as follows:

Google Drive/Documents/<Files>

How the MAPI-based backup of emails data is arranged?

inSync displays the emails of end users who are on legal hold and whose data is backed up by using MAPI or Exchange Online through WebDAV in the following structure:

  • inSync exposes only the emails, contacts, and calendar events through WebDAV. Each MAPI data item is displayed in the following file formats:
    • Every email is displayed in .eml file format.
    • Every contact is displayed in .vcf file format.
    • Every calendar event is displayed in .ics file format.
      Note: If the MAPI calendar event size is greater than 128 KB, calendar event is displayed in .eml file format.
  • The data items are grouped based on year > month > date for ease of accessibility.
  • inSync maintains the original folder hierarchy of MAPI messages, and displays the data as follows:
    • The WebDAV URL of the folder shows the folder's display name and the inode number.
    • inSync retains and exposes the mtime attribute for all MAPI-backed up emails, calendar events, and contacts that are exposed through WebDAV.  

      However, the following most commonly used attributes are available in the EML file itself:

      • To
      • From
      • Cc
      • Bcc
      • Date Sent
      • Time Sent
      • Subject
      • Date Received
      • Time Received
      • Attachments
      • Name or Unique Identifier of the attachment
      • Message ID
      • Text or Message Body
      • SHA1 Hash
    • On WebDAV, the data is arranged per the following convention: 

      <device-name>/<fset name>/<pst name>/<actual folder hierarchy>/<time based folder hierarchy>/<message>

      Where,

      • <fsetname>: The name of the MAPI fset, which can be Outlook Advanced or Outlook All PSTs based on the configuration. For example, Outlook Advanced,v2 in the following illustration.
      • <pst name>: The name of the PST as seen in the Outlook settings. 
      • <actual folder hierarchy>: The folder such as Inbox, Outbox, Sent Items, and so on as well as the version information. For example, Calendar-13iCalendar-13iCalendar-13iCalendar-13i,v2 in the following illustration.
      • <time based folder hierarchy>: The folder in YYYY/MM/DD format based on the time the message was received. For example, 2016,v2/March,v2/10,v2 in the following illustration.
      • <message>: The file format based on the message type, such as, .eml, .vcf, or .ics format.
        For example, .ics files that are displayed in the following illustration: