Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.4 - 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

Refresh Azure Logs Policy

The 'Refresh Azure Logs Policy' functionality allows the user to set a schedule for refreshing logs when Hyper Migration via Azure Turbo Asynchronous Mode was used. This function will update all finished jobs on the schedule that you set.

Note: Jobs with a state of In Progress will not be updated.

To enable auto refresh post migration logs do the following.

1.On the Hyper Migration tab, select that "Refresh Azure Logs Policy" button.
refresh azure logs policy1

2.Once the Refresh Azure Logs Policy window opens, set the times when you would like the azure logs to refresh. You can set 2 daily occurrences.
refresh azure logs policy2

Hyper Migration Report

Users can create an Excel sheet report of the Hyper Migration tab. The report will be a replica of the Hyper Migration jobs seen in the User Interface, providing users with source and target, and the state of the migration.

In order to create a report, click the Excel icon in the Hyper Migration sub panel:
 
Hyper Migration Report 1

 

This will generate a report which looks like the following:

Hyper Migration Report 2

Post Migration Logs

Once a Migration is completed, users have the option to View Logs, which provide an overview, for all users, of the content that was part of the migration, and whether it did or did not migrate successfully. This window can be accessed by selecting "View Log" from the summary window, which pops up upon the completion of a migration.
Drives Post Migration Logs 2

Individual logs are also available when you double click on a user in the Hyper Migration tab (see the Hyper Migration section for more details).

Drives Post Migration Logs

For details on the various possible post migration log states, please see this section.

Post Migration Log States

The states of Post Migration logs can vary as follows:

·Successfully Copied During All Copy Rounds: This section of the log shows all the files and folders were successfully copied during all migration rounds (first attempts and resume(s) afterwards). Files and Folders added to this record node were successfully migrated to the target and were, as a result, excluded from further Resume operations.

·Failed During Current Round: This section of the log shows all files and folders failed to copy during the current migration round (last attempt to copy content to target). Files and Folders added to this record node were not successfully migrated to the target (this could be a result of connection issues, Office 365 not responding, etc.). These items are available for a Resume operation, and Essentials will attempt to recopy them on the next migration round once Resume is selected.

·Warnings During All Copy Rounds: This section of the log shows all files and folders were skipped during all migration rounds (first attempts and resume(s) after this). Files and Folders added to this record node were not copied successfully, and therefore were not migrated to the target because of various condition (filters, file already exist, etc.). These items are excluded from further Resume migration operations.

·Not Started During Current Round. This section of the log shows all files and folders not copied during the current round (last attempt to copy content to target). Files and Folders added to this record node were not copied successfully and therefore were not migrated to the target because the copy job was not finished due to a tool/Operating system/Virtual Machine crash, or the operation was canceled by the user. However, the content was received from the source and added to the database. These items are available for Resume, and Essentials will attempt to recopy them on the next migration round once Resume is selected.

·In Progress During Current Round. This section of the log shows all files and folders locked and processed during the current migration round (last attempt to copy content to the target). Files and Folders added to this record node have not finished and have not attained a failed or successful status. These items are not available for Resume migration as they are part of the current progress information if the migration is still running.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating