It will be in the version after the version after that if you get a jump start on complaining now.
-ASB: http://XeeSM.com/AndrewBaker On Wed, Jul 28, 2010 at 4:56 PM, Tom Miller <[email protected]> wrote: > Too bad there is no "folder exclusion" option, then I wouldn't have to do > the work-around. That must be in the next version... > > >>> "Joe Tinney" <[email protected]> 7/28/2010 4:47 PM >>> > > I happened to be in the DFS FAQ earlier today and ran across this: > > > > From > http://technet.microsoft.com/en-us/library/cc773238(WS.10).aspx#BKMK_006: > > *Can more than one folder be replicated on a single server?* > > Yes. DFS Replication can replicate numerous folders between servers. Ensure > that each of the replicated folders has a unique root path and that they do > not overlap.* For example, D:\Sales and D:\Accounting can be the root > paths for two replicated folders, but D:\Sales and D:\Sales\Reports cannot > be the root paths for two replicated folders.* > > That would seem to indicate that you shouldn’t, but not necessarily that > you can’t and doesn’t spell out the apparent doom that would occur from > doing so. I would imagine you could end up in some kind of replication loop > based on the asynchronous and serial method of replication that this > document also indicates is possible. That is just a guess, though. > > > > Good luck, > > Joe > > > > *From:* Sean Martin [mailto:[email protected]] > *Sent:* Wednesday, July 28, 2010 3:41 PM > *To:* NT System Admin Issues > *Subject:* Re: DFS Quandary > > > > Can you create a new folder target beneath your namespace and then create a > new replication group for that folder target? > > > > Example: > > > > Current Config: > > > > Namespace = \\domain\share > > Existing folder target = DirectoryA > > DirectoryA contains = Directory1, Directory2, Directory3 > > Existing Replication group = \\domain\share\DirectoryA > > > > New Config: > > > > Namespace = \\domain\share > > Existing folder target = DirectoryA > > New folder target = Directory2 > > Existing replication group = \\domain\share\DirectoryA > > New replication group = \\domain\share\DirectoryA\Directory1 > > > > > > It's been awhile since I messed with DFS and that was on 2003, but it seems > that should work. I don't have the ability to test however.... > > > > - Sean > > On Wed, Jul 28, 2010 at 9:43 AM, Tom Miller <[email protected]> wrote: > > Doesn't work. The folder I want to use is a subfolder of an entire share I > already have configuration in a replication group. You'd think there'd be > an easy way to exclude a subfolder. I think what I'll have to do is move > the folder to be in a namespace to a separate share. > > > > Tom > > > > >>> "Charlie Kaiser" <[email protected]> 7/28/2010 1:11 PM >>> > See if this helps... > http://blogs.dirteam.com/blogs/r2/archive/2005/12/08/250.aspx > > *********************** > Charlie Kaiser > [email protected] > Kingman, AZ > *********************** > > > -----Original Message----- > > From: Tom Miller [mailto:[email protected]] > > Sent: Wednesday, July 28, 2010 9:37 AM > > To: NT System Admin Issues > > Subject: DFS Quandary > > > > Folks, > > > > I need some advice on a DFS setup. All of my WAN servers > > have several shares replicated for backup purposes to our > > main campus storage server. I also replicate the main data > > shares on our file and print servers here at campus to the > > same storage server via DFS. > > > > Now I have a need to replicate via DFS name space a > > particular folder. One of our programs is sending a portion > > of its staff to one of our vacant buildings, so the program > > will be split into two locations. I want to use DFS name > > space to replicate changes both ways, but since I already use > > DFS for backup, the DFS console gives me an error that it's > > already replicated. > > > > Suggestions or work-arounds? > > > > > > > > > > Tom Miller > > Engineer, Information Technology > > Hampton-Newport News Community Services Board > > 757-788-0528 > > > > > > Confidentiality Notice: This e-mail message, including > > attachments, is for the sole use of the intended recipient(s) > > and may contain confidential and privileged information. Any > > unauthorized review, use, disclosure, or distribution is > > prohibited. If you are not the intended recipient, please > > contact the sender by reply e-mail and destroy all copies of > > the original message. > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > Confidentiality Notice: This e-mail message, including attachments, is for > the sole use of the intended recipient(s) and may contain confidential and > privileged information. Any unauthorized review, use, disclosure, or > distribution is prohibited. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. > > > > > > > > > > > > > > > > > Confidentiality Notice: This e-mail message, including attachments, is > for the sole use of the intended recipient(s) and may contain confidential > and privileged information. Any unauthorized review, use, disclosure, or > distribution is prohibited. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
