Link to home
Start Free TrialLog in
Avatar of Nitin Pandey
Nitin PandeyFlag for Australia

asked on

DFSR : Re-replication configuration

Hi Team,

A DFSR scenario suggestion needed.

There was a Replication Group that mapped  \\server1\sydney and \\server2\sydney. Someone deleted this Replication Group sometime back and now server2 has old data. I performed following steps to fix it:

1. Renamed DFSPrivate in server2 to DFSPrivate.old
2. I ran below ROBOCOPY in server1 to copy incremental difference from server1 to server2:

robocopy "D:\Data\sydney" "\\server2\sydney" /XO /V /TS /FP /TEE /E /ZB /L /R:1 /W:1 /MT:64 /xd DfsrPrivate /COPYALL /tee /LOG+:C:\logs\sydney.log

3. Recreated replication group.

Now, when I run below command to compare backlog, it keeps returning huge numbers, unexpected to my understanding.

dfsrdiag backlog /RMem:server1 /SMem:server2 /RGName:"Sydney" /RFName:Sydney

Am I doing it wrong? What's the right way to deal with this situation?

Thanks, much appreciated.
ASKER CERTIFIED SOLUTION
Avatar of Mahesh
Mahesh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi,

Using robocopy causes the same load on the network as DFSR sonthis step was notnreally needed.
You should have reconfigured the distribution group and point to server 1 as the primairy. This decides which server is the leading one looking datawise and will update/perge data on server 2.

Cheers
Avatar of Nitin Pandey

ASKER

Thanks Mahesh. Seems it's Staging Quota.

One last question. Can I change the default location of Staging from it's existing drive to another drive on the fly? What factors do I need to consider? Any repercussions?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial