Viking_ES
asked on
Questions on DFS/FRS
I want to use DFS and FRS to replicate all the important content on our main file server to an secondary file server. This secondary server would only be used when/if our main file server fails (by disabling referal to the secondary server and enabling it only when required).
Here's my problem: The main file server obviously contains all the files that should be replicated to the secondary file server(which is new) and is basically empty. When I create the links pointing to both servers, the content of the main server is moved in a directory called NTFRS_PREEXISTING_somethin g !!! After it's done moving the data to this folder everything gets eventually replicated in both server and the data is moved back in the main folder (on the main server). For obvious reasons, I cannot do this with our production data (I've only done tests so far) as it would take an unnacceptable period of time for the DFS/FRS mecanism to move hundreds of gigabytes of data inside this NTFRS_PREEXISTING folder and move it back in the original folder, during this process, users might loose access to their files. Is this normal behaviour? Do I really need to start with 2 empty DFS links so that DFS/FRS doesn't behave that way?
TIA.
Here's my problem: The main file server obviously contains all the files that should be replicated to the secondary file server(which is new) and is basically empty. When I create the links pointing to both servers, the content of the main server is moved in a directory called NTFRS_PREEXISTING_somethin
TIA.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.