Forum Discussion
Storage Migration Service - IP Cutover
Hi all,
I've got SMS working in my lab to test functionality. I've successfully migrated from a 2008 R2 to 2019 - files and shares are all A-OK and cutover reported all complete with no errors.
It all looks good, but my understanding is the destination computer should also take on the source machines IP address, For example, the source file server has an IP of 10.0.0.10 and the destination server IP is 10.0.0.20. During cutover, the original should be given a whole new IP (Either assigned statically or via DHCP) and the destination then given 10.0.0.10 at the same time it is renamed, yes?
I think I saw this happen in in the Ignite video, but unless I'm missing something obvious I can't get this to work.
I'm on 1.57.0 of the extension and using the VL ISO of 2019 for orchestrator and destination server if that makes any odds.
Any advice greatly appreciated!
Thanks,
- NedPyle
Microsoft
HidMov Hi. If it's not working it would be a bug - it should work exactly like you understand it and how I demonstrate it; when cutover completes, the destination server should have all the source machine's IPs. If the event logs don't have a clear error, you will need to open an MS Support case and provide them with logs. I'm not allowed to accept them here due to MS GDPR privacy and retention rules, it has to go through our trusted support org before I can see them.
