Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

File Replication Service and Distributive File System 1

Status
Not open for further replies.

nic06

MIS
Jun 8, 2006
11
US
We have a folder (lets call it "test") located on the c:\ drive of one server (lets call it server A). We need the data inside this folder to show up on server B. When server A makes changes to any data inside the test folder the changes need to update on server B. Currently there is no folder on server B, but one can be created. We are running Windows server 2000 and 2003. I Have been looking into the File Replication service(FRS) offered by Microsoft and that led me to the Distributive File System (DFS). The DFS seems more complicated than what we are trying to do, but it seems we can't use the FRS without the DFS and a root. Does anyone have any input on the best way to go about doing this? Do we have to use the DFS to do this? Does anyone know of any resources on a how to guide in implementing both the DFS and FRS? I can't seem to find any step-by-step guides for the File replication service. Thank you, any input is greatly appreciated.
 
DFS is exactly what you need and yes, it uses the FRS to accomplish the task. We use it for exactly what you describe...server A is the "master" and server B holds only a copy of what's in the folder on A. If you change A, B gets changed but you can't change B by itself.

It's really a straightforward project...a good set of instructions can be found here:
I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
I have a root created on one server and am trying to create a new root replica on a different server. Do the two servers have to have the same domain?
 
They don't have to be in the same domain, but you will have to have a trust setup between the two domains in order for it to work.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
Do you know how I go about doing that? Do you know of any resouces I can view to see how to do it? Thanks!
 
The two domains are not connected at all. There is no tree or forest structure. Can the trust still be set-up?
 
Can you "see" the other network? In other words, how are these two networks physically connected?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
Domain A and Domain B cannot see eachother. They are not connected at all. They have the same name and password, but other than that they are not connected at all.
 
I am trying to setup an explicit trust but I get the error, "The DomainName domain cannot be contacted. If this domain is a Windows domain, the trust cannot be set up until the domain is contacted. Click Cancel and try again later. If this is an interoperable non-Windows Kerberos realm and you want to set up this side of the trust, click OK."
 
If the other domain is not physically connected in some way, you're not going to be able to set up a trust.
 
One of the Domains is in one state and the other is in a different US state. How can these two domains be physically connected?
 
Yeah, if you want to setup a trust between two domains, they have to be able to see each other.

You could setup a VPN between the sites, or a private frame/MPLS network, etc. No matter what, if you need these two servers to share information, they have to be able to see each other directly.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
Back to the beginning, I am confused on how the DFS is what to use. In the DFS we need to set up a root and link the folder on server A that we want server B to see to the root. This way server B, C, D, etc just goes teh root file on server and can see any shared foldes. We want server B to be able to go to a folder on server B not to a root on server to be able to access the folder. If we create a replica of teh root and put it on server B that just makes it so server now has that root folder on it. They can then access the shared folder but only through the root. Wouldn't it be easier just to share the folder to begin with? Why did you setup the FDS just to share a folder?
 
For latency issues. With the folder shared among the servers located all across the USA, the local user accesses the file from their local file server.

The only root folder is on the server that is handling the DFS, it then shares out that folder to the other servers downstream (when setup in a master/copy only relationship), that way nobody at a remote site can change a file on their folder and have that changed replicated across all the servers. Important when you need a master set of files.

Regardless, if your servers can't see each other directly and have a trust setup, it won't work for you.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top