Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.10 - User Guide

Copyright Tool Overview
General Tool Configuration Profile Manager Proxy Mode Azure Turbo and CSOM Creating User Mapping Creating User and Template Reports Support and Troubleshooting Activation Modes of Migration
Home Tab Migration Analysis Tab Migrator Tab
Interface Connect to Resources Copy Sites Live Compare Hyper Mode Classic Mode Copy Alerts Orphaned Users Copy In-Place Tagging of SharePoint Items Incremental/Delta Copy Forms Migration Workflow Migration Save Site to XML
File Manager Tab Drives Tab
Interface Overview Migration Job Structure Connecting to Resources Copy Google Drive Copy File Share Copy My Sites to OneDrive for Business Copy Tenant Copy Box Copy Dropbox Nintex Deployment
Security Manager Tab Term Store Manager Tab Administrator Tab Backup Tab
Interface Overview Backup Job Structure Advanced Search Retention Policies Storage for Backup Import/Export Backup Archives Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Hyper vs Classic Backup Setup Hyper SharePoint Online Backup Hyper OneDrive Backup Hyper Office 365 Groups Backup Smart Backup Classic SharePoint Online Backup Classic OneDrive Backup Classic Office365 Groups Backup Classic Mailbox Backup Change Properties for Backup Admin Management Scheduling Backup Jobs Backup Project Conversion
Help Tab View Tab Architect Tab Public Folders for SharePoint Tab Scripts Appendix About

Requirements for Storage

Essentials uses the Apache Derby Database when creating a backup on File System Storage. It’s an open source relational database implemented entirely in Java. No extra tools or services are required to be installed. (


For Azure Storage, Essentials uses the Table Storage Service - a NoSQL key-value store for rapid development using massive semi-structured datasets. In order for this to work, you must have the Table Storage Service. (


For Amazon S3 storage, Essentials requires you to have the Amazon DynamoDB service. Amazon DynamoDB is a key-value and document database that delivers single-digit millisecond performance at any scale.



If you use Amazon S3 storage with Custom End points in Essentials with Amazon DynamoDBLocal service, then you do not require an amazon DynamoDB. This is because the DynamoDB databases are placed locally on the file system and synchronize with backup project located on Amazon S3 storage. (






Import/Export Backup Archives

This section provides an overview of importing and exporting backup archives.

Exporting Backup Archives

Metalogix Backup allows users to export/import projects to/from external archives.  

To export a Backup project:

1.In the Backup Navigator panel, navigate to the backup project that you would like to export, select the object that you would like to export and right click on it and select Export.
backup export1
Alternatively, you can select the object that you would like to export and click the export button in the Backup Navigator ribbon.
backup export2

2.In the provided window select a location where the export will be saved.  You may also select to split the export into multiple files and/or add a password to the export file.
backup export3

3.Press Finish to Start the Export.

Importing Backup Archives

Metalogix Backup allows users to export/import projects to/from external archives.  

To Import a Backup Archive from Local storage:

1.Select "Import from Local" from the Backup Ribbon.
import backup from local1

2.Select the type of Archive (ZIP would be generated using the Export Backup Archive feature) and give your project a Name.
import backup from local2

3.Press Finish to Import.

To Import a Backup Archive from Cloud storage:

1.Select Import from Cloud
import backup from cloud1

2.In the first window enter the Project Name, click Next.
import backup from cloud2

3.In the next window select your cloud storage provider where the backup is stored.

4.Press the ... button and enter the appropriate information to connect to your storage location (see the Connecting to Cloud Storage section for details on how to connect to your cloud storage location).
import backup from cloud3

5.Locate and select the archive to load within the appropriate container or bucket

§​The archive to select should follow the naming pattern "ARCHIVE-projectName".  Do not select its parent folder nor the archive folder that ends with _archiveData (i.e. ARCHIVE-projectName_archiveData).

6.Press Finish to Import.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating