Storage Migration failed files

%3CLINGO-SUB%20id%3D%22lingo-sub-1158886%22%20slang%3D%22en-US%22%3EStorage%20Migration%20failed%20files%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1158886%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20using%20the%20Windows%20admin%20center%20to%20transfer%20our%20old%202008r2%20file%20server%20to%20a%202019%20file%20server.%20Things%20look%20pretty%20good%20during%20the%20first%20scan.%20We%20migrated%206%20million%20files%20and%20only%20had%20around%20150%20failed%20files.%20When%20I%20look%20for%20the%20files%20that%20failed%2C%20I%20am%20running%20into%20a%20small%20problem%20with%20the%20logs.%26nbsp%3B%20The%20log%20is%20to%20large%20to%20open%20and%20times%20out.%20I%20have%20made%20the%20timeout%20change%20in%20the%20registry%20from%201%20minute%20to%2010%20but%20still%20having%20a%20problem.%20I%20even%20looked%20at%20the%20powershell%20script%20to%20export%20the%20storage%20migration%20service%20and%20proxy%20debug%20logs.%26nbsp%3B%20As%20I%20am%20trying%20to%20look%20at%20the%20logs%20on%20the%20orchestrator%20server%20I%20see%20a%20lot%20of%20the%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5Bverb%5D%20adding%20object%3D%20filename%20result%3Dsuccess%20intent%3D%20skipped%20or%20modify.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20do%20I%20need%20to%20search%20for%20to%20see%20the%20failed%20files.%26nbsp%3B%20I%20had%20clear%20the%20old%20logs%20and%20start%20a%20new%20scan%20and%20limited%20the%20log%20size%20so%20I%20can%20get%20it%20to%20a%20smaller%20manageable%20size.%20the%20scan%20is%20running%20and%20have%20am%20up%20to%20117%20files%20and%20am%20waiting%20till%20it%20finishes%20to%20try%20and%20get%20the%20error%20report%20but%20want%20to%20look%20at%20the%20current%20event%20viewer%20and%20see%20is%20I%20can%20find%20the%20failed%20files.%26nbsp%3B%20So%20if%20anyone%20can%20give%20me%20an%20example%20of%20what%20to%20look%20for%20in%20the%20events%20to%20find%20the%20failed%20files.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Regular Visitor

We are using the Windows admin center to transfer our old 2008r2 file server to a 2019 file server. Things look pretty good during the first scan. We migrated 6 million files and only had around 150 failed files. When I look for the files that failed, I am running into a small problem with the logs.  The log is to large to open and times out. I have made the timeout change in the registry from 1 minute to 10 but still having a problem. I even looked at the powershell script to export the storage migration service and proxy debug logs.  As I am trying to look at the logs on the orchestrator server I see a lot of the:

 

[verb] adding object= filename result=success intent= skipped or modify.

 

What do I need to search for to see the failed files.  I had clear the old logs and start a new scan and limited the log size so I can get it to a smaller manageable size. the scan is running and have am up to 117 files and am waiting till it finishes to try and get the error report but want to look at the current event viewer and see is I can find the failed files.  So if anyone can give me an example of what to look for in the events to find the failed files.

0 Replies