Storage Migration Service

Question

I am looking to migrate data from an old file server into a new one using the Storage Migration Service but there are a few things that I am wondering before I proceed. I did a little digging but couldn't find any definitive information.

My main concern is downtime. When using the Storage Migration Service, will this cause any disruption on the old server? I do not want our users to have trouble accessing their file shares during the process. I understand there will be some down time during the actual cutover phase, as the servers will need to be rebooted but what about the scanning or transfer phase?

Also, what happens if files are being moved around by users during/after the transfer phase? Will those changes update dynamically? If not, will there be an option to do a final sync up before the cutover? I am looking to keep the service disruption to a minimal so if you can provide any additional information that may help, I'd greatly appreciate it.

Answer 1

Hi Jeff,
For storage migration you can refer to this:
https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview
Based on my understanding, you can do the migration while the production goes on. There would be downtime during the cutover but normally it won’t take long.
For live migration you can refer to this:
https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/live-migration-overview

Thanks for your time.
Best Regards,
Danny

-----------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.