I'm looking to migrate a file server from Windows Server 2016 to Server 2022. It's currently set up as a VM with a separate data disk from the operating system. I've heard some people suggest simply detaching the data disk and reattaching it to the new server. Others have mentioned using Storage Migration Service or Robocopy as alternatives. I'm curious about other methods and what people recommend to ensure minimal downtime. Thanks!
5 Answers
Honestly, I've done plenty of migrations using Robocopy—it’s tried and true. But I think the least hassle comes from making sure your OS is on a separate drive from your data. That way, you can just upgrade the OS without affecting everything else.
An in-place upgrade can work if you don’t mind a little downtime—about 30 minutes is typical. Just make sure everything is backed up beforehand in case things go sideways.
Setting up DFS can really save you some headaches in future migrations. If you have enough disk space, it’s a solid choice for zero downtime.
I've tried both Robocopy and just detaching and reattaching the virtual disk to the new VM, and both methods worked well for me. Just make sure to have a full, recent backup that's been tested—you never know what might happen during migration!
Don’t overlook DFS! It’s super easy to use. You can keep your data syncing for a month before you disconnect. This way, you can double-check everything without worrying about losing anything.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures