Overview

You can export SharePoint site data snapshots from Druva Cloud to another S3 bucket or S3-compatible storage. Bulk export helps you stay compliant by maintaining a secondary copy of your backed-up data outside Druva Cloud.

Choose from two export options:

On-demand: Initiate an export whenever needed
Scheduled: Set up periodic exports based on your compliance requirements

For a quick overview of scheduled export, watch this video.

Feature Availability

To enable this feature, please contact support.

Type of Bulk Exports

The Druva Cloud platform supports two methods for SharePoint Online bulk export:

Feature	One-Time Export	Periodic Export
Use Case	Full archive of all historical data.	Periodic export of the latest SharePoint snapshots outside Druva Cloud.
Data Exported	All versions of all files. E.g., if a file was updated 10 times across 10 snapshots, all 10 versions are exported.	Incremental only — exports new or updated file versions since the last export.
Trigger	Manual — initiated via Support Ticket.	Automated — scheduled via Org app export profiles. Contact support to activate this feature for your instance.

Prerequisites

Ensure you have the following details for successful bulk export of the backed-up data.

AWS credentials
S3 Bucket name
S3 Bucket region

Option 1: Periodic Bulk Export

Configuring a periodic bulk export is a three-step process, as shown in the image below.

Log in to the Druva console and download the CloudFormation template.
Open your AWS account and use the downloaded template to create a stack. This step automatically provisions the required permissions, including the creation of an IAM role.
Return to the Druva admin console, enter the stack details, and verify the connection.

Detailed Setup Instructions

For complete step-by-step guidance, refer to the instructions below:

Step 1: Copy or download CloudFormation template

On the Druva Console, click SaaS Apps > Microsoft 365.

In the top menu bar, click Settings > Bulk Export Settings.
Click Configure SaaS Apps Bulk Export.
Copy or download the CloudFormation template.

📝NOTE:
The CloudFormation template is valid only for 15 mins. If the template expires, click Generate new template.

Step 2: Execute template and create stack

Go to the AWS CloudFormation console and click Create Stack (new resources). Click Create Stack (existing resources) when you want to reconfigure the stack with new bucket details.

To create a stack, perform the following steps:

Step 2.1: Specify template

Prepare the template. Ensure that the Template is ready option is selected.
Enter the template source location.
1. Amazon S3 URL: Enter the URL copied from the Druva console in the Amazon S3 URL field.
2. Upload a template file: Upload the CloudFormation template downloaded from the Druva console.
Click Next.

Step 2.2: Specify stack details

Enter stack name.
Enter the S3 bucket name where you want to bulk export backed-up data.
Click Next.

Step 2.3: Configure stack options

This step is optional. Keep the settings unchanged and click Next.

Step 2.4: Review

Review the details of your stack, select the acknowledgment and click Create stack.

The stack is created successfully.

Go to the Outputs tab to view the stack details that are used to verify access in the Druva console.

Step 3: Enter details and verify access

In the Druva console, enter stack details and verify access.

You can find these details on the Outputs tab of the generated stack.
1. Enter IAM Role ARN.
  This is the ARN of the role that has access to your AWS environment for bulk export.
2. Select Region.
  You can find the Bucket region on the Properties tab of the S3 Bucket.
3. Enter Bucket Name.
  This is the name of the S3 bucket provided to bulk export backed-up data.
4. (optional) Enter Bucket Path.
  If you do not specify the Bucket Path, the default path that is at the root level is used.
  For example, <provided-bucket-path>/<Bulk Export Data>/<M365/Gsuite>/<Workload>/<Site URL Name>/<data> Sample path: demo/Bulk Export Data/Microsoft 365/SharePoint/sites_demo_site/
  
  📝NOTE:
  ‘/’ from the SharePoint site URL will be replaced with underscores.
Click Verify Access.
❗IMPORTANT
The access is verified based on the specified IAM Role ARN, Bucket name, and Bucket path. Ensure to use the same details that are specified in the CloudFormation stack else the verification will fail.

📝NOTE:
You cannot save the configuration until the access is verified.

Click Save.
After you save the configuration, the Bulk Export Settings window is displayed.

Once the connection is verified, log in to the Druva Cloud Platform console and schedule periodic exports as needed.

Scheduling Periodic Bulk Export

To schedule a bulk export, start by updating the org app backup profile to enable the Bulk Export settings (see image below). If you want to schedule selected sites for bulk export, create a dedicated org app backup profile and an auto-configuration rule for those sites tailored to your requirement.

❗IMPORTANT

The bulk export feature license must be enabled on the backend for your instance. If it's not already activated, please contact Support to request access.

For more information on org app backup profile and auto configuration rule refer to the Backup Profiles for Org Apps.

Field	Description
Schedule and Retention	Specify the export frequency. Once a week - Default setting The latest backed-up snapshot is bulk exported for the first time. The subsequent bulk exports are incremental. The following graphic explains what is bulk exported in the first and subsequent exports.
Enable Export of Site Data	Select this checkbox if you want to automatically bulk export the latest snapshot of SharePoint sites to a specific off-site location. This setting is disabled by default.

Edit Bulk Export configuration

If you want to update the bucket details later, click Edit to edit the configuration. The Edit SaaS Apps Bulk Export window is displayed. For information about how to configure bulk export, see Configure Bulk Export.

If you want to update the bucket path specified in the existing bulk export configuration, you have to edit the configuration and verify the path. There is no need to rerun the stack.

Option 2: One-Time Export

If you need to perform a one-time export of SharePoint data, the process is managed by the Support team. This section outlines the steps and prerequisites to ensure a smooth export experience.

Step 1: Define Your Export Scope

Before contacting support, decide what data you want to export:

Export all SharePoint sites
Export specific SharePoint sites: You'll need to provide the Site ID for each site you want to export.

📝NOTE:

Exports are triggered only for sites where bulk export is enabled in the associated profiles.

Step 2: Support Team License Activation

After your request is approved, the support team will activate the one-time export license on the backend.

Step 3: Configure the Org App Profile

Once the license is active:

Update an existing profile to enable bulk export settings. — or —
Create a new org app profile

Step 4: Export Execution and Monitoring

After configuration is complete:

The support team will manually run a script to download the data.
You can track the export progress and view results under the Live Activities section of the Druva dashboard.

Monitor Bulk Export

You can monitor the status of bulk export from the Live Activities tab. This tab provides an overview of the live bulk export activities.

To view live activities:

On the inSync Management Console menu bar, click SaaS Apps > Microsoft 365 > Jobs.
Go to the Live Activities tab.
The Live Activities tab displays ongoing bulk export jobs with details such as name, email, profile, type, status, and start time.

You can filter the activities list based on the bulk export status.

Click any activity to view its details.