Storage Migration Service Inventory completed with errors

[Kobus_Olivier]

Hi, I am running Windows Server 2019 Storage Migration Service Server to migrate a Windows Server 2012 R2 Server to Windows Server 2019. The Job, on 3 of my most important shares, says Completed with Errors"and due to the nature of the information I cannot ignore this and need to identify which folder have issues and errors. I cannot seem to find much in the Windows log files, any advise will be appreciated. Thank you.

[#2]

Hi. In the Transfer Details section for each server (a pull up from the bottom of the WAC screen), there is an option to save the Error log (as CSV) then open in Excel and look at the per-file errors. The codes will all be Windows Error codes as documented here:

https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes

If still not able to determine why certain files aren't transfering, let me know (I reserve the right to send you to MS Support for specific troubleshooting, naturally :grinning_face:).

Ned Pyle | Principal Program Manager, MS | @nerdpyle on twitter

[#3]

@Ned Pyle Happy to report back that I have found the directories\files that caused the issue. Another issue, after identifying the issue, correct it and the start the transfer again, it runs through every directory\file again (4TB) and it runs for 25+ hours ... Any idea? Thank you

[#4]

@Kobus_Olivier It's going to examine every file, antually, but it should not be transferring them all again - you will see the difference in the transfer details page and the saved CSV. We are working on some improvements in delta transfer perf, but most customers see reduced time between transfers if there aren't many changes. How many Cores do you have on the Orchestrator and Destination computer? 

[#5]

Hi, ok I understand. Both the server have dual core CPU’s with 8 GB RAM - what I am seeing now on the destination is that Windows Defender is hammering the CPU average of 60%. Is there any exclusions for Storage Migration Service? Thank you, Regard Kobus

[#6]

@Kobus_Olivier Re: defender... ouch. They have always told us to expect no more than 5-10% increased utilization. As atest, if you exclude folders where SMS is writing to (or temporarily disable real-time protection), do you see the performance improve?  

[#7]

@Ned PyleYes, I have disabled real time scanning and even seen and improvement. Still experiencing issues with about 22k files that have very explicit permissions (confidential data) where we cannot just go and alter these ..… Thank you for your help - appreciated.

[#8]

@Ned Pyle 

Hi, I'm trying to troubleshoot the "couldn't inventory some devices" during the "scan" phase of the storage migration.

I realize that it may be choking on long file names and 0kb files but how do you access this CSV?

I don't see it anywhere in the WaC console.

Thanks

[#9]

@Thom Edwards Hi. There is no CSV for Inventory, only for Transfer. If you are seeing an inventory failure the details are in the SMS event logs. 

[#10]

I found some bunk rights but what to do about the insanely long path names? I tried the registry key on the WAC server but the shares still fail to inventory for this reason.

Thanks so much.

[#11]

SMS supports long path names, as long as NTFS allows, you don't need to make registry changes. If it's failing there you need to open a support case, that's not supposed to be happening.

[#12]

@Ned Pyle 

Well I'm about to throw in the towel.  I started this huge 4TB 2008 R2 file server migration project about four weeks ago and I'm no further ahead.

• inventory scan fails on some files with vague error messages - checked rights and enabled log path names
• data transfer scan keeps getting stuck - doesn't timeout - spinning bagel for hours & hours - today it's stuck @ 44%
• hesitant to STOP the transfer as last time I did that it auto created a bunch of preexistingdata folders which ended up filling the destination volumes and the data transfer failing due to lack of space - i ended up restarting the entire process only to be stuck AGAIN

There is just no rhyme or reason why it keeps struggling.  It worked great on my tiny test server so perhaps this server is just too big not to fail.

Not sure where to go from here.

[#13]

HI. We've handled much bigger. I really recommend you not try to bang your head here further, open an MS support case. If we find a bug it's a free case, if it's something we can get working we will. Those support folks have access to me through an internal DL as well, you won't be hung out to dry.

[#14]

thanks sir, will do