The best way to move all files, shares, permissions from Windows server 2012 to Windows server 2016
I am moving my files from one retiring server to a new server. Server1 to Server2. The only thing these servers do is provide File services for all of my users. My question is basically this, I want to keep my server name the same, did not want to lose my shares and their permissions, so that all my users connections and embedded links in databases and spreadsheets would not break.
I have millions of files and backing up to tape or disk and restoring to Server2 would keep the shares and permissions but would take forever and I cannot be down for a very long period of time. I could restore a full backup from tape/disk of Server1 to Server2 but the restore would take days.
I could also migrate from physical Server1 to a Virtual Server2 but I have no idea how long that would take with the amount of files that would be moving to the new server.
I am just looking for any suggestions on a better more efficient way to do this.
I have millions of files and backing up to tape or disk and restoring to Server2 would keep the shares and permissions but would take forever and I cannot be down for a very long period of time. I could restore a full backup from tape/disk of Server1 to Server2 but the restore would take days.
I could also migrate from physical Server1 to a Virtual Server2 but I have no idea how long that would take with the amount of files that would be moving to the new server.
I am just looking for any suggestions on a better more efficient way to do this.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am a fan of FreeFileSync. It can do everything you are looking to do with no down time really. You will need to make sure all the setting are set properly for what your needs are, compare the two systems, and than sync. What I like most about this tool is I can sync everyday until the day I want to switch over and 99.9% of the files are already transferred over. And best of all, it is a free tool.
So first, let me say now is the time to take the hit and "break" existing links. Don't try to keep the server name the same. Microsoft continues to evolve SMB and with various MitM attacks, and signing protocols, you will only be creating pain.
Set up a new server. Set up DFS. Point the target to the existing old share, and start getting shortcuts, shares, scripts and so forth updated using the DFS name instead of the old server name.
Set up DFS-R. Data will be synced to the new server lazily, but no real downtime.
When you are ready, update DFS-N and point the target to the new server.
Fix what breaks.
Retire old server.
Future migrations are easier because DFS is in place and not tied to a specific server anymore.
Celebrate.
Set up a new server. Set up DFS. Point the target to the existing old share, and start getting shortcuts, shares, scripts and so forth updated using the DFS name instead of the old server name.
Set up DFS-R. Data will be synced to the new server lazily, but no real downtime.
When you are ready, update DFS-N and point the target to the new server.
Fix what breaks.
Retire old server.
Future migrations are easier because DFS is in place and not tied to a specific server anymore.
Celebrate.
Fix what breaks.If one of the things that break is Excel files with UNC paths instead of an absolute path, use this process to fix them
https://www.experts-exchange.com/articles/31867/Updating-Excel-Links-in-Thousands-of-Files.html
One reason to move to DFS though. Excel (and office on general) handles embedded UNC links properly. The article reinforces what I mean about the drawbacks of just giving a new machine an old name. It doesn't work as expected.
Or wait for 2019.
Or wait for 2019.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You ask how much data. 10 TB
I wouldn't mix DFS with a migration. I suggested moving to DFS *before* migrating. It makes migrating SIGNIFICANTLY easier. Just my opinion.
Patrick, do us a favor and give more feedback. The suggestions fill pages, your feedback so far is one sentence.
ASKER
I am not familiar with DFS but I would like to use it to do the replication. I will need to find a good resource for helping me in setting up DFS on the servers and getting the replication started. Are you able to setup DFS on a server that already has data on it? Any suggestions on where I can get information that would assist me?
ASKER
Thank you all for your assistance.
But the painful part will be the time the syncing takes - millions of files will take days.