Link to home
Create AccountLog in
Avatar of Marty Block
Marty BlockFlag for United States of America

asked on

Can you stop and restart DFS replication and restart it without losing the initial synch in Server 2008 R2

I maintain a 'warm' disaster recovery site and we are upgrading storage equipment at the this remote site. I am staging the replacement equipment locally and performing synchronizations locally for testing and because initial data synch is in excess of 1Tb. Our plan is to relocate the new equipment to the disaster recovery site. The link from home office to d/r site is 10 meg Ethernet.

Servers are two 2008 R2 Enterprise  servers replicating server1 and server2

Initial replication staging was done from server1 to 2. health reports show all ok for a few weeks.

Topology at the home or main location is two servers: one Active Directory 2003 R2 with one primary and the 2nd a 2008 R2 unit serving as a bridge head to the remote site. At the remote (target) site we have 1 full 2008 R2 AD server.

Can I simply stop dfsr replication services on both 2008 R2 servers than restart dfsr services once server 2 at remote site shows up in all AD servers with new ip subnet address.

At present we use other technology for this synch job and so the site-to-site connection is solid and reliable and working well. Site to site AD  and AD DNS syncing is currently working and updates are propagating

The question focus is: if we stop the local replication for a day or two in order to ship and install the new equipment at the disaster recovery site, will DFS 'pick up' where it left off, or will it want to resynch the TB of data (a process we want to avoid. What do we need to do in order to prevent DFS from thinking it needs to resend all the data once the link is again available and the target server in place in their new location?
Avatar of kevinhsieh
Flag of United States of America image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of Marty Block


We presently use Secure Copy from Script Logic (now Quest Software). It works well, but is expensive, and, is licensed to the server name. This means if you retire a server, you trash the license, and, they won't let you move it to something else. You have to buy a new license. We were adding a new SAN to our disaster recovery location, and for a variety of reasons we needed to add a new server while leaving the existing server in place (it is the a/d controller at the remote site..) We asked to transfer the license, they said no. So we switched to DFS. But the product has worked well for years, it's not the fastest, but has been very reliable.