How much disk space do you need when using SPMT to migrate file server content to SharePoint Online? The documentation recommends 150 GB. However, my experience has been that the agents run out of disk space if the source exceeds the available disk space.

I would have expected content to be packaged and uploaded in batches, so that agents don’t need to store all of the migrated content. If I look into the MigrationToolStorage folder on an agent, I can see that it creates separate pack directories. However, it keeps doing this until it runs out of space. The migration job then fails with the error “Temporary storage on your local computer is too low”. 

For the current migration job, I paused it just before the agent ran out of space. At that point, there were 30 separate pack folders on the agent, using 117 GB of storage. It took around 30 minutes after pausing for these folders to get processed and removed. My current plan is to keep pausing the migration job when disk space is low until all the data has been migrated. However, I would have expected SPMT to cater for this scenario automatically. 

The ethernet connection on the agent is running at a steady 380 Mbps, so it doesn’t appear to be a bottleneck. I have configured two agents, but only one appears to be used. This may be because I am only executing a single migration job.

​How much disk space do you need when using SPMT to migrate file server content to SharePoint Online? The documentation recommends 150 GB. However, my experience has been that the agents run out of disk space if the source exceeds the available disk space. I would have expected content to be packaged and uploaded in batches, so that agents don’t need to store all of the migrated content. If I look into the MigrationToolStorage folder on an agent, I can see that it creates separate pack directories. However, it keeps doing this until it runs out of space. The migration job then fails with the error “Temporary storage on your local computer is too low”.  For the current migration job, I paused it just before the agent ran out of space. At that point, there were 30 separate pack folders on the agent, using 117 GB of storage. It took around 30 minutes after pausing for these folders to get processed and removed. My current plan is to keep pausing the migration job when disk space is low until all the data has been migrated. However, I would have expected SPMT to cater for this scenario automatically.  The ethernet connection on the agent is running at a steady 380 Mbps, so it doesn’t appear to be a bottleneck. I have configured two agents, but only one appears to be used. This may be because I am only executing a single migration job.  Read More

​