Storage Migration Service 2008 R2 Physical to 2019 VM

%3CLINGO-SUB%20id%3D%22lingo-sub-2307509%22%20slang%3D%22en-US%22%3EStorage%20Migration%20Service%202008%20R2%20Physical%20to%202019%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2307509%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20using%20SMS%20to%20try%20and%20migrate%201.93TB%20and%20219%2C531%20source%20files%20from%20a%202008%20R2%20Server%20to%20an%202019%20VM%20server%20that%20is%20fully%20updated.%20The%20problem%20that%20I%20am%20running%20into%20is%20it%20is%20showing%20around%209%2C216%20failed%20files.%20So%20what%20I%20am%20trying%20to%20figure%20out%20is%20what%20can%20I%20do%20to%20Identify%20the%20failed%20files%20and%20what%20to%20do%20for%20next%20steps.%3C%2FP%3E%3CP%3EI%20have%20used%20the%26nbsp%3BStorage%20Migration%20Service%20Helper%20script%20to%20pull%20the%20logs%20from%20the%20Orchestrator%20and%20looked%20the%20logs%20but%20have%20been%20unable%20to%20identify%20which%20files%20have%20failed.%26nbsp%3B%20What%20other%20tools%20can%20I%20use%20to%20help%20me%20Identify%20the%20problem%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

I am using SMS to try and migrate 1.93TB and 219,531 source files from a 2008 R2 Server to an 2019 VM server that is fully updated. The problem that I am running into is it is showing around 9,216 failed files. So what I am trying to figure out is what can I do to Identify the failed files and what to do for next steps.

I have used the Storage Migration Service Helper script to pull the logs from the Orchestrator and looked the logs but have been unable to identify which files have failed.  What other tools can I use to help me Identify the problem?

0 Replies