I'm looking for a reliable, long-term solution for managing our file servers. We currently run a clustered setup that hosts shared drives and folder redirection, but every 4-5 years we end up migrating it, and the process is always fraught with issues. The last time we tried using the File Migration Service it worked well, but now the destination servers aren't recognizing the SMS service, even though it's running fine.
I know that robocopy is an option, but it doesn't update the paths, which causes problems with numerous applications and folder redirections. We operate around the clock, so minimizing downtime is critical.
What approaches can I take for file servers that will ensure high availability and allow for smoother OS upgrades in the future? Is using DFS a good idea? What else could work? Ideally, I want a solution that retains the same hostname for our clients and applications.
6 Answers
You should definitely consider setting up DFS-N. This way, you can keep your paths consistent when you update your target folders to the new server/share. It simplifies the migration process a lot!
DFS is definitely one option. Another is to utilize a file server that allows for hardware or OS upgrades without much downtime, like a VM with in-place upgrades or solutions like NetApp or Dell PowerScale.
I've always done it the manual way. I robocopy the data to a new server several days ahead, check for permission issues, and when it’s time to switch, I robocopy again for any changes. Then I just rename the new server to the old one and recreate the shares as needed.
There might still be a method to export some registry settings to help migrate shares and permissions, though it might come with some caveats regarding machine names and IPs. It's something to consider, but it could be a bit of a hassle. Honestly, the DFS route might be the best approach according to others.
That's exactly why DFS exists! Setting up DFS-N means your names won't change, and with DFS-R, you can replicate and move files easily to your new server. It's really a straightforward solution!
Storing files on a virtual disk could be a game-changer. It eliminates the hassle of migrations altogether!
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