Answer the question
In order to leave comments, you need to log in
How to replace the file server?
We have a file server based on Windows 2003 with a bunch of balls. Works 24x7
It is required to replace the entire server with a new one, based on Windows 2012 with a "hot" or with minimal downtime.
I tried to somehow synchronize the balls using robocopy. The process is very long and takes 3 days. During this time, the information is already outdated and you can do it endlessly.
Again, the transfer itself will take time, there is no way to transfer the ball itself and without stopping the server. And I would not like to.
Vopnikla idea - to use DFS.
I admit, I have been using DFS for a long time and I treat it as something crooked and buggy.
Hence the question, does it make sense for me to move in this direction? Who uses DFS tell me whether it is possible to configure DFS on a combat server and not break the existing structure?
Or are there other transfer options?
UPD. The idea of just dragging the balls one by one to another server will not work. It needs to stay the same. That is, the name of the server or the path to the ball is immutable
Answer the question
In order to leave comments, you need to log in
You need DFS replication - it's balls replication technology. It will copy the share and keep it up to date on another server. In this case, the paths on the main server will not change the server.
And if so:
1. We raise a new server
2. We raise balls on it
3. We copy everything to it
4. We indicate on the DC that Server1 (where everything lives now) now answers here (respectively new)
As a result, users will contact the same server, but in fact a new one will answer them.
"Old" balls from sin translate into RO.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question