SOLVED
Home

Storage Migration Service stuck at renaming source computer

%3CLINGO-SUB%20id%3D%22lingo-sub-783708%22%20slang%3D%22en-US%22%3EStorage%20Migration%20Service%20stuck%20at%20renaming%20source%20computer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783708%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20doing%20a%20migration%20from%20a%202008%20r2%20server%20to%20a%202019%20server%2C%20and%2C%20all%20went%20well%20until%20the%20cut-over%20which%20got%20stuck%20at%2041%25%20renaming%20the%20source%20computer.%3C%2FP%3E%3CP%3EI%20looked%20at%20the%202008%20R2%20server%2C%20and%2C%20while%20the%20IP%20did%20change%20on%20it%2C%20its%20hostname%20didn't%2C%20so%20I%20manually%20changed%20it%2C%20rebooted%20it%2C%20added%20it%20back%20to%20the%20domain%2C%20rebooted%2C%20but%20the%20job%20is%20still%20stuck%20in%20the%20same%20state.%3C%2FP%3E%3CP%3EI%20can't%20cancel%20the%20job%2C%20delete%20it%2C%20make%20it%20go%20forward%2C%20I%20can't%20do%20anything%20really.%3C%2FP%3E%3CP%3EHas%20anyone%20else%20run%20into%20this%20before%3F%20I%20guess%20it's%20not%20really%20worth%20doing%20this%20in%20an%20automated%20way%2C%20as%2C%20if%20I%20had%20done%20the%20cut-over%20steps%20manually%20it%20would%20have%20taken%20me%20only%2010%20minutes%20since%20the%20actual%20data%20transfer%20did%20work%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20will%20try%20rebooting%20the%20orchestrator%20server%20(a%20third%202019%20server)%20to%20see%20if%20the%20job%20finally%20cancels%20or%20somethingt...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(I'm%20running%20the%20latest%20stable%20everything%20as%20of%20today%2C%20except%20for%20the%202008%20R2%20server%20which%20wasn't%20updated%20to%20the%20latest%2C%20didn't%20have%20time%20for%20that.%202019%20servers%20are%20up-to-date)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-783708%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783728%22%20slang%3D%22en-US%22%3ERe%3A%20Storage%20Migration%20Service%20stuck%20at%20renaming%20source%20computer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783728%22%20slang%3D%22en-US%22%3EWell%2C%20rebooting%20was%20the%20only%20thing%20that%20made%20the%20job%20stop.%3CBR%20%2F%3EI%20tried%20resuming%20the%20job%20afterwards%20thinking%20that%20it%20will%20realise%20that%20the%20rename%20source%20computer%20step%20had%20been%20done%2C%20but%20it%20didn't%20work%20anymore%2C%20presumably%20because%20it%20still%20had%20the%20previous%20name%20in%20the%20source%20device.%3CBR%20%2F%3EI%20guess%20rebooting%20your%20orchestrator%20server%20and%20then%20just%20deleting%20the%20job%20is%20the%20only%20way%20to%20go%20at%20this%20point.%20(and%20of%20course%2C%20completing%20the%20rest%20of%20the%20cut-over%20steps%20manually)%3C%2FLINGO-BODY%3E
adsfasdfasdfaswef
New Contributor

Hi.

 

I was doing a migration from a 2008 r2 server to a 2019 server, and, all went well until the cut-over which got stuck at 41% renaming the source computer.

I looked at the 2008 R2 server, and, while the IP did change on it, its hostname didn't, so I manually changed it, rebooted it, added it back to the domain, rebooted, but the job is still stuck in the same state.

I can't cancel the job, delete it, make it go forward, I can't do anything really.

Has anyone else run into this before? I guess it's not really worth doing this in an automated way, as, if I had done the cut-over steps manually it would have taken me only 10 minutes since the actual data transfer did work?

 

I will try rebooting the orchestrator server (a third 2019 server) to see if the job finally cancels or somethingt...

 

(I'm running the latest stable everything as of today, except for the 2008 R2 server which wasn't updated to the latest, didn't have time for that. 2019 servers are up-to-date)

1 Reply
Solution
Well, rebooting was the only thing that made the job stop.
I tried resuming the job afterwards thinking that it will realise that the rename source computer step had been done, but it didn't work anymore, presumably because it still had the previous name in the source device.
I guess rebooting your orchestrator server and then just deleting the job is the only way to go at this point. (and of course, completing the rest of the cut-over steps manually)
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
9 Replies