A while back I wrote about the SharePoint Migration Tool. Today I will share my experiences of the SharePoint Migration Manager.
Why SharePoint Migration Manager?
Table of Contents
SharePoint Migration Manager is almost the same as the SharePoint Migration Tool.
When you look at the task settings for example, you wouldn’t really notice any difference.
Architecturally however there is a large difference. The SharePoint migration manager uses agents to do exactly the same as the migration tool.
You can have multiple agents sharing the load of the migration.
And as agents are progressing the tasks you can see fro each task how much progress has been made.
You can even run multiple migration tasks at the same time, but once you start using the SharePoint migration manager in real environments you will find that things don’t always turn green as shown below. In this post I’m hoping to help a bit with the more challenging situations.
Quite often you will find that some migrations work and some migration don’t work. It might sometimes feel like just random behaviour.
But there are a lot of factors that can be important.
- Resources available to the agents ( disk space, CPU power, memory, network speed)
- Stability of the infrastructure
Time to have a look at some of the failures that may occur. When you click on the Download failure report a zip file is downloaded with a variety of csv files in it.
When things go seriously wrong there will be a FatalError_R1.csv file. this file will contain a reason for the migration manager to completely stop a migration task.
Some examples of errors that I found during some of the migration are:
- ScanSharePoint Access Failure – Web issue. URL: https://myorg.sharepoint.com/sites/staff/Shared Documents User: firstname.lastname@example.org
- Temporary storage on your local computer is too low.
Both these error messages are quite annoying and not completely clear.
The itemFailureReport_R1.csv is another one of those files to have a look at. you might get errors like this:
- Scan File Failure:Path contains invalid characters. Valid path doesn’t start or end with space. Other invalid characters are <, ?, >, *, |, “, :, \, /
- Scan File Failure:Unauthorized access to source folder
- Failed to Read the file:Could not retrieve file’s metadata
- Packaging Failure:Unauthorized access to source file
For these file related issues you will need to adjust file names and make sure that your migration account has access to the files.
On the fatal errors however we have to use a different trick.
Temporary storage on your local computer is too low
The Temporary storage on your local computer is too low error is very uinclear. My system has plenty of space and it doesn’t look like this is a problem, until I found the following article with a great solution:
The problem is the space in %appData%\Microsoft. this is most likely on your C-Drive and the idea is to use a different storeage space somewhere.
So you would need to delete the MigrationToolStorage folder in %Appdata%/Microsoft and then run the following two commands to create a link to a different storage with more space.
cd %appdata%\Microsoft mklink /J MigrationToolStorage Z:\SomeOtherFolder
This solution isn’t just more stable it also makes the migration tool run a lot faster as my alternative storage is a lot faster than using the system drives.
Alternatively you can also go to the Agent settings and change the working folder to a different drive so that the migration manager uses that folder instead.
Ok, that is a great solution. Hopefully this will help someone else too.