DFS replication member server question

We are currently running DFS between several of our remote sites. We are basically using DFS to replicate the remote sites data back to our main office to be backed up. Right now all of our DFS replications are connected in a 1 to 1 topology. The replication group only consits of two servers, the remote file server and our file server in the main office.

We are preparing to deploy a new file server to another remote site which is in close proximity to one of our other remote sites. It is forseeable that users could on any given day be working at either office.

Right now the new file server that is going to be built is in the same office as an existing server that we are going to replicate data to. What we would like to do is set a replication group between these two servers and let them utilize the gigabit lan speed to perform their initial replication.

Once initial replication is complete we would move one of the servers to the new site which is connected via T1. There should only be minimal traffic since the initial replication was done already. Once the two servers are in the different site we would like to add a third member server into the replication group in our main office to be able to backup the data.

Hopefully my terrible drawing helps you visualize what Im trying to do

So now my questions

1. We are planning on adding the replication members in two steps to take advantage of the ability to use FULL bandwidth when in the same LAN. Once the servers are seperated we will use a throttled schedule. Do you see any problems with this?

2. Can you start a DFS replication group and then add a third member after its initial replication?

3. Any other information I should be aware of?
LVL 35
Joseph DalyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joseph DalyAuthor Commented:
I forgot to mention in my original post we are planning on publishing a namespace for the replicated data in the three servers.
In my experience this is the best way to do it. Set your servers together on the same LAN for initial replication, then separate them and throttle bandwidth so you dont saturate the internet pipe.

Yes, you should still be able to add replication members after the initial replication. (though you'll probably want to do the same with the new partner - have it replication LAN-side initially then move it offsite)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Joseph DalyAuthor Commented:
The option to have the thrid member replicate LAN side is not possible as the sites are several thousand miles apart. This is the reason for the staged adding of members.

We can have the two servers in the same LAN replicate at full bandwith without an issue but we can not have the third server replicate over the WAN with full bandidth without causing major issues.
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

Right, you will saturate your WAN pipe which is not good. How much data? Something to cover a full-T1's worth of bandwidth over a weekend maybe?
Joseph DalyAuthor Commented:
The third server really isnt as much of a concern. We can poplate that using throttled bandwidth over a period of weeks if necessary. Right now we have been running on a schedule of Full bandwidth from 6pm to - 6am mon thru fri and full all weekend.

My main concern is adding the third replicated server after the fact. Just to clarify here when setting up the DFS replication we want to set it up as a multipurpose configuration rather than a backup configuration. Correct?
Multipurpose = two or more servers
Data collection/backup = two servers

As your diagram dictated, I am assuming you want all company data replicated between each server, and available locally at each site. In this case you would use multipurpose.
Joseph DalyAuthor Commented:
These are the two choices when setting up the DFS I believe choosing the first option is where we want to be.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.