I prefer DFS over Robocopy as DFS stores it information in a central location.. Active Directory ;-)) I would go for DFS replicated with DFS-R, which is available on R2 servers. DFS-R is so much cooler when compared with NTFRS. For example DFS-R ONLY replicates changes whereas NTFRS replicates everything, even when only ONE bit has changed. Independent of which replication mechanism used, DFS is a site aware service. It tries to locate the nearest Root Target and Link Target. However, be aware that when auto site link bridging is disable you need additional configuration with REPADMIN.
Remember however, domain based DFS is just like it says...domain-based and not forest based. A domain DFS namespace can only have root targets from the domain where the DFS namespace exists and not from other domains. So, DCs from the domain that hosts the domain based DFS root must be available and preferably nearby as those are contacted to refer the client to the DFS root, even if a client is in another domain in the forest. The DFS link targets can be in any domain however. So if a client wants to connect to \\SOMEDOMAIN.COM\DFSROOT$\DFSLINK 1 it contacts a DC in the SOMEDOMAIN.COM 2 the DCs checks the nearest DFS root for DFSROOT$ and refers the client to it 2 the client contacts the DFS root and refers the client to the nearest DFS link target for "DFSLINK" I could tell you a complete story about DFS and DFS-R but you can also read it yourself. You might wanna have a look at: "Designing Distributed File Systems" http://technet2.microsoft.com/WindowsServer/en/library/1aa249c0-40f3-4974-b67f-e650b602415e1033.mspx?mfr=true Met vriendelijke groeten / Kind regards, __________________________________________________________________________________ MVP Profile → https://mvp.support.microsoft.com/profile=f8c04f4a-bff2-453e-9aed-7dfedab0be10 MVP Home Site → https://mvp.support.microsoft.com/ MVP Overview → https://mvp.support.microsoft.com/mvpexecsum BLOG → http://blogs.dirteam.com/blogs/jorge/default.aspx __________________________________________________________________________________ >>>-----Original Message----- >>>From: [EMAIL PROTECTED] [mailto:ActiveDir- >>>[EMAIL PROTECTED] On Behalf Of Condra, Jerry W Mr HP >>>Sent: Wednesday, December 06, 2006 17:34 >>>To: [email protected] >>>Subject: [ActiveDir] DFS vs Robocopy question >>> >>>Hi all >>>I'm looking for feedback on a couple of scenarios for our environment. We >>>have three W2K3 SP1 domains and WAN separated regions in a couple of them. >>>When deploying software, hotfixes and such I want to go to the 'distribution >>>point' for that domain/region so as not to traverse the WAN for downloads. >>>Each distribution point needs to mirror the others. Each region has an app >>>server where we maintain these distribution points for downloads, patches >>>and such and currently is managed manually as far as keeping each server >>>identical to the other. I'm not familiar with DFS other than what is and >>>does and have not configured or used it. Robocopy seems okay but also has a >>>lot of configuration to deal with. DFS seems to be the best but wanted to >>>see what the experts thought. My concern is if I create the DFS hierarchy >>>I'd still be pointed to one server for the files. In reading the >>>documentation I see multiple roots can be established which I'm hoping would >>>provide access to each regional distribution point and still replicate the >>>latest uploads from one point to all others. >>> >>>Appreciate any feedback. >>> >>>Thanks >>> >>>Jerry This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/[email protected]/
