I'm working on migrating a file server for the first time, and it's a sizable one at 2.7TB with five separate drives. I've completed all my seed copies and am currently handling the delta copies.
Original server details:
- Name: file.server.com
- IP: 192.168.1.5
New server details:
- Name: newfile.server.com
- IP: 192.168.1.10
From what I understand, once I finish the final delta copy, I just need to transfer the registry keys from the original server to the new one located at HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesLanmanServerShares. After that, I'll shut down the old server, rename the new server to file.server.com, and change its IP to 192.168.1.5. Am I missing any crucial steps?
4 Answers
I personally recommend switching to DFS during a migration like this. It can save you from dealing with all the hassle of cutovers in the future. Your current plan looks good though!
Your plan sounds solid! When I did my final Robocopy, I actually renamed the old server first to make sure no one was connected during the last copy. This method worked well for me, even when I moved about 14TB without any issues.
I've typically added the /mir /sec flags to my Robocopy command to ensure that security permissions are correctly replicated. Good luck with your migration!
Just to be safe, I like to double-check the SPNs on the old host and ensure that everything is correctly set up on the new host's Active Directory object. Missing SPNs can lead to some complications later.
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