Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.3 - User Guide

Metalogix Essentials for Office 365 User Guide
Administrator Architect Backup
Interface Overview Common Functions
Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Global and SharePoint Administrators Hyper Backup Creating a Full Backup Creating an Update Backup Creating an Exchange Online Mailbox Backup Creating an Office 365 Group Backup Creating a OneDrive for Business Backup Backup Resume Backup Search Restore from Backup Scheduling Backup Jobs Retention Policies Import/Export Backup Archives Moving the Backup Location Backup Project Conversion
Drives
Interface Overview Common Functions
Connecting to Drives Copy Google Drive Copy File Share Copy My Sites to OneDrive for Business Copy Tenant Copy Box Copy Dropbox OneDrive Management Progress Tab Hyper Migration Path Length Overflow
File Manager Informant Migrator
Interface Common Functions
Connect to SharePoint and OneDrive for Business Global and SharePoint Administrators Copy Sites Live Compare Copy Lists and Libraries Copy, Move, and Tag SharePoint Content Copy Alerts Pre-Migration Report Azure Turbo Mode In-Place Tagging of SharePoint Items Incremental Copy Nintex Workflow Migration Orphaned Users Copy Preserving Content Authorship and Approve/Reject Statuses Save Site to XML Using Scripts and Integration With Windows Task Scheduler
Profile and Global Variables Public Folders for SharePoint Reporting and Re-Mapping Users and Templates Security Manager Term Store Manager Scripts Wizards Appendix

Admin Pool

The Admin Pool functionality uses a set of global administrators for hyper migration and hyper backup operations in order to provide a solution for Office 365 throttling issues.

This functionality allows you to provide a list of admins from within wizards, instructing Essentials to use these global admin accounts when running the hyper migration or hyper backup. The more admin accounts you provide, the more users used to send requests to Office 365, thereby reducing the pressure on the target service.

In order to add more administrators you must use the +Admin button from within the Hyper Migration or Hyper Backup wizards. This button appears in place of the Connect button, after the first global administrator has been approved. You will see a list of users from within the wizard once the admin user has been authenticated.Admins pool 1

info

NOTE: Admin pool is not supported for connection by Claims.

Tracking

You can track the admin pool in detail from within the migration logs. First, you will see the list of provided global administrators. Next, in each request, you can see the ID for each administrator used in the current request.Admins pool 2

info

NOTE: Site Collection Administrators are required to perform a hyper migration to SharePoint site (Box to SharePoint or File Share to SharePoint options) or a hyper backup of SharePoint only site.

The admin pool feature can be used in migration via the user interface, or via script. You can generate a script or create a scheduled task

Script:

essentials -cmd fileSharesToOneDrive -trgtsite https:// quest-admin.sharepoint.com -trgtuser admin1@quest.com -trgtepass WW4P5qweqMFmMSHasdasdvRnQP0C6EmQ  == -trgtuser_1 admin2@quest.com -trgtepass_1 WW4P5MFmMSHasdasdvRnQP0C6EmQ== -usermapping 'D:\fileshare-onedrive.csv' -overwritebehavior dont_copy - log 'output.xml' -noSplash

 

Backup Project for File Share/Network and Cloud Storages

This section provides an overview of the organization of Hyper Backups withing your explorer when you use local drives or network drives as your backup storage.

 

The Backup project itself will have a name starting with the prefix 'HBACKUP', for example 'HBACKUP-SPOSite'.
hyper backup 2

Your Backup project folder will contain 3 sub-folders and 1 .project file.
hyper backup 3

Folder Contents

Database folder

This folder contains Databases with information about all the backup files, items, metadata, structure, permissions etc. Saving backup info in the database folder gives you the ability to use all the advantages of storing and searching inside of the database for fast and flexible work with backup.

 

DATAstore folder

All backup content is located in this directory location.  All files have non-original names and can not be opened without the Essentials tool. This feature provides extra security for your backup projects.
hyper backup 4

METAstore folder

Hyper Backup stores all of your content’s metadata, such as permissions, core properties, files metadata, columns etc., in this location
hyper backup 5

.project file

This file provides the tool required in order to read the backups, with information about the hyper backup project.

 

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. (https://db.apache.org/derby/)

 

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. (https://docs.microsoft.com/en-us/azure/storage/tables/table-storage-quickstart-portal)

 

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.

(https://aws.amazon.com/dynamodb/)

 

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. (https://docs.aws.amazon.com/en_us/amazondynamodb/latest/developerguide/DynamoDBLocal.html)

 

 

 

 

 

Hyper Backup Tab

Hyper Backup Tab

Hyper Backup Tab is where all hyper backups jobs are saved and displayed.

hyper backup 6

Column Title

Description

Icon

Indicates whether the migration was successful.

A green check-mark indicates a successful migration.

A white pause icon indicates that the migration was paused or not finished because of windows crash

A red pause icon indicated that backup job is finished but some of the items failed to backup .

Hyper Backup Type

Indicates the type of backup that was used.

Started

Indicates when the migration was started for each user.

Source User

Indicates the source user, SPO path or Backup snapshot  

Target User

Indicates the source user, SPO path or Backup snapshot  

Summary Record

Is a summary of the content that was migrated - this includes the successful, warning, and failed states for migrated content, as well as size and duration information

Duration

Indicates the time spent on the backup or restore

 

Related Documents