Storage Migration Services
3 TopicsStorage Migration Services cutover stuck at 91%
Hi, I'm using the Storage Migration Services to move an on prem 2012 R2 server to an Azure hosted 2019 server. I've successfully done the first two steps and I'm doing the cutover and the cutover process has been hung at 91% for several hours. I've confirmed that the new destination server has been successfully been renamed and that the old source has also been renamed. I can successfully ping and connect (RDP) to both servers. But the cutover process is still hung. I checked the event logs in the Storage Migration Services and I see this message logged over and over: 12/19/2022-15:25:53.777 [Info] GetResponseFromHost(fsserver01) returned status: 5. Is reachable: False [d:\os\src\base\dms\proxy\cutover\cutoverproxy\CutoverUtils.cs::IsHostReachable::640] But I'm able to successfully connect to the fsserver01 server with no issues. Is there anything I can do to have the Storage Migration Service complete the cutover? Thanks Nick548Views0likes0CommentsWAC 2103.02 - Storage Migration Service Error Logs
Running a migration service and tried all the suggested corrections to obtain the error logs -- increased the processing time to 10 minutes validated all the SMB services are active etc. The error log still 'errors' out - I can download User/Group logs with no issue. Anyone got an idea of what / where to start digging into the next?906Views0likes0CommentsStorage Migration Services - Check if the source device is online - we couldn't access
Hi, I am transferring files from a Windows 2008 R2 servers to a Server 2019 server. It transfers about 6,000 files, then stops with this error: Check if the source device is online - we couldn't access it. I have rechecked the prerequisites and they are fine. I am a domain admin, and in the local admin group on both servers. The 2019 server is build is 10.0.17763. From the event log: Couldn't transfer all of the files in the endpoint on the computer. Job: Jobname Computer: source computer Destination Computer: computer Endpoint: something State: Failed Source File Count: 0 Source File Size in KB: 0 Succeeded File Count: 0 Succeeded File Size in KB: 0 New File Count: 0 New File Size in KB: 0 Failed File Count: 0 Error: 40961 Error Message: Transfer failed Guidance: Check the detailed error and make sure the transfer requirements are met. This could be because the orchestrator computer couldn't reach a source or destination computer, possibly due to a firewall rule, or missing permissions. Any help would be appreciated! Thanks961Views0likes1Comment