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.
Sometimes a connection to an Office 365 location can be initiated only with the help of proxy settings.
To enable proxy mode for Hyper Migration please do the following:
1.Navigate to the Help tab, and select Proxy Mode.
2.On Connect to SharePoint pop up screen, enable the Use Proxy fucntion by selecting the check box and click the Proxy Configuration button.
3.In the Proxy configuration screen, enter all of your proxy configuration settings, or import the settings from Internet Explorer by clicking the Import Settings button. Click Save.
4.Finish setting up your connection and click Start Migration.
Note: The Proxy option is disabled after the restart of the tool.
To use it permanently or with scripts, please do the following:
1.Navigate to the location in Explorer where Essentials is installed (this location is C:\Program Files\Quest\Essentials by default).
2.Open Essentials.ini file using NotePad.
3.Add the following parameter at the end of the document:
4.Save the file.
5.Run Metalogix Essentials as usual, creating a new hyper migration or hyper backup job using proxy settings for the connection.
Auto Resume allows users to set automatic resume sessions in order to bypass issues caused by Office 365 throttling. This functionality works by analyzing a hyper backup or hyper migration at the medium stage, looking for errors that occurred during migration. Once a "is not responding" error is found, the next auto resume round is started, and only objects with the "is not responding" status are re-migrated.
The number of Auto Resume attempts can be specified in in the Profile Manager.
1.In the Essentials, select the Help tab, and then Profile Manager.
2.In Profile Manager, select Hyper Migration/Backup from the left hand tab.
3.On the right hand half of the Profile Manager window, find the "Number of Rounds" setting. This setting is set to 1 by default, which means that only one migration round will be launched and the auto-resume function is not enabled. Changing this number, to 5 for example, will cause the tool to run the first migration round, and then it will run auto resume attempts until the connection problem is solved, or up to 4 more times (for a total of 5 rounds). (This means if the connection problem is resolved by the second attempt, then auto resume will stop and have no need to run 2 more times)
NOTE: Auto Resume will only retry for throttling issues and will skip issues connected with permissions, authentication, lost internet connections, and non-supported objects, etc.
NOTE: You can use Admin Pool in combination with Auto-Resume or use only one of the functions to solve the problem with connections to Office 365.
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.
NOTE: Admin pool is not supported for connection by Claims.
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.
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
essentials -cmd fileSharesToOneDrive -trgtsite https:// quest-admin.sharepoint.com -trgtuser firstname.lastname@example.org -trgtepass WW4P5qweqMFmMSHasdasdvRnQP0C6EmQ == -trgtuser_1 email@example.com -trgtepass_1 WW4P5MFmMSHasdasdvRnQP0C6EmQ== -usermapping 'D:\fileshare-onedrive.csv' -overwritebehavior dont_copy - log 'output.xml' -noSplash