Jill, thanks for the reply! Its good to know that I can put normal shares on
the drives. And I'll have to look into upgrading those root shares to EE (to
add another unpublished namespace).
This post originated mainly from the conflicting information I've been
reading on the Microsoft website and in Microsoft docs- maybe you can help me
clear all this up?
Originally, I wanted to set up DFSR to create a namespace for all the users
in both of my sites. (Single AD domain, two sites, 2 DCs at each site) I
was going to make a GPO for Folder Redirection so everyone's folders would've
gone to \\mycompany.internal\users. It would've been easy to manage and very
redundant. Every user "local" to their site would've used the local target.
If one datacenter went down (say, cooling issues), then the users would've
gone over the WAN to the other site. I also wanted to set up offline files
in case we had a switch failure and a floor couldn't reach either datacenter-
their "My Documents" and etc would still be there for them while our network
guys fixed the problem.
However, a few Microsoft pages seemed to say this setup wasn't recommended
for redirected folders. It came down to the files being constantly
open/edited which would lead to synchronization conflicts. And I read your
team's blog entry at
http://blogs.technet.com/filecab/archive/2006/01/19/417761.aspx about offline
files and DFS. (But now that you mentioned an additional namespace, maybe I
could make a namespace "just" for users' redirected folders?)
But then I'll find pages like this:
(Question 68, under "Managing DFS: Can I use DFS with Offline Files and
redirected My Documents folder) and the demo at
http://www.microsoft.com/winme/0512/25905/Branch_Server_demo_mbr.asx ... both
of which make it seem like yes, what I want /is/ possible.
So based on the conflicting information (sorry this is so long), I figured
that I had to keep users' redirected folders, roaming profiles, and
collaborative-file-share-areas as normal, non-DFSR shares. With that
assumption, I thought that I could still leverage a bit of DFS by integrating
profiles and collaboration areas into one namespace /without/ DFSR replica
sets. The idea was if we lost a site (due to flood/fire/etc), I could
restore the lost data from offsite tape onto the surviving-site's servers.
Then I'd go to the surviving DFS root server, delete the "failed" link
targets, and replace them with the new "restored data" targets.
Can you point me in the right direction here? Could it be that I've just
been reading a mix of Win2k/2k3 FRS and Win2k3 DFSR documentation/best
Thanks for your time!
Post by Jill Zoeller [MSFT]
For a given namespace, it's fine if the folder targets for a given folder
are replicated (say \\domain\root\users where users has multiple targets)
and other folders, perhaps those with a single target, are not replicated.
And it's fine to put shares on your root server. Do whatever makes sense for
your organization. For example, if you don't mind the fact that your
profiles share will appear in the namespace, then it's fine to add it there.
However, if you don't want to expose this folder to your users via normal
browsing of the namespace, then create a new namespace that users don't know
For the best disaster recovery, you need to eliminate single points of
failure for your namespace and target data. This means two DCs (these hand
out referrals to the domain-based namespace itself), two namespace servers
(to hand out referrals to your folders with targets), and two folder targets
for each folder--or store the single folder target on a server cluster.
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by Thomas H
Hello everyone! At my medium-sized business, we've got two AD sites in a
single domain. Each site has a Win2k3 SE R2 root server with a
domain-integrated namespace. The namespace has multiple root targets, and
does use DFSR for some shares (examples= GPO software deployment and
company financial data).
Physically, these DFS servers have a large amount of free disk space, so
I'd like to put some "regular" shares onto their drives. However, these
shares shouldn't be replicated (such as roaming profiles for mobile
Should I just create the shares on the server as \\siteAdfs\profiles?
Or should I link them into the namespace too, even though they won't be
replicated with DFSR?
And which way (normal shares, or non-replicated in DFS) is best for a true
loss-of-site disaster-recovery scenario?
Thanks in advance!