Hey everyone! I've recently taken on a project to migrate a 1 TB shared file from one file server to another. Both servers are in the same domain, but the second one is located at a branch office. My goal is to ensure minimal to no downtime during the migration and to preserve all existing file permissions. I want the staff to be able to access the files just as they did before the move, which I think could be managed with DFS (Distributed File System) namespaces. After I finish the migration, I plan to delete the files from the old server, but it'll still remain active. I'm considering setting up DFS on both servers, creating a namespace with the same name as the shared file on server one, and using Robocopy for the initial file transfer. After that, I would use DFS replication for incremental updates before removing the old server from the DFS setup. Once everything is good, I'd back up the old files and wipe them out. Has anyone gone through something similar? Any tips or alternative suggestions? Also, I'll definitely enable bandwidth throttling. Anything else I should be on the lookout for?
5 Answers
By the way, what kind of network are you working with? Is it 10 Gigabit? And are your drives SSDs or HDDs? That will influence your overall speed and performance, so just keep that in mind!
I have to laugh at some of this. If migrating files is such a simple task, why are you getting paid for it? You sound like you might be overthinking. It’s just a file transfer! Just make sure you've got a plan and everything should be fine.
If bandwidth isn’t a concern between the sites, you could consider using a physical method. Get a TB USB drive, copy the files to it using Robocopy, then physically ship it to your branch server. Once there, plug it in and copy everything over again. It’s a bit of work but can save a lot of time on the network. After that, just keep running Robocopy for any catch-up copies until you're ready to cut over.
Honestly, using Robocopy is probably your best bet here. It's robust and designed for this kind of file transfer. Just make sure you use the right switches, like /sec and /mir, to get everything copied over correctly. If you're worried about staff access, setting up DFS first with that namespace is a smart move. That way, once the files are migrated, they won’t even notice a change on their end. Good luck!
I’ve actually managed to migrate a whopping 19 TB over a WAN link before and had no downtime. Sure, it took a few days and required rerunning scripts a couple of times, but it worked like a charm! Just remember to have your initial copy, keep it up to date, and then do one final sync before you switch everything over to the new server. Absolutely essential to test that everything is syncing properly first!
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