|
|
I have DFS hosted on windows 2003 R2 32bit and replicating to an off-site
2003 R2 64bit.
I was randomly checking folders and files, and noticed that it is actually
not updating data. I ran a diag from the DFS mgmnt console and it reported
everything is healthy. Not sure how to troublshoot this. How can I force
replication to scan the src/trgt and compare the difference? I get my 1206
DFSR events that say it successfully contact the DC on the Target Server. On
the Src I see 1104 that DFS restarted replication after a backup operation.
Thanks,
|
|
Dear Customer,
Thank you for posting in newsgroup.
According to the description, it seems that some files and folders is not
updated on the DFS member. If I have any misunderstanding, please feel free
to let me know.
Analysis and Suggestions:
=====================
To narrow down the issue, we need to verify that DFS replication is normal
between the source and target DFS member server.
Please create a propagation report on both of the source and target DFS
member server.
Steps to create a propagation report for DFS Replication:
1. Click Start, point to Administrative Tools, and then click DFS Management.
2. In the console tree, under the Replication node, right-click the
replication group that you want to create a diagnostic report for, and then
click Create Diagnostic Report.
3. when the Diagnostic Report Wizard popup, select Propagation report
4. Select the Replicated folder and Propagation server in the drop down list.
5. Click OK to generate the report.
You may check the report to see if the DFS replication is normal and if
there is any error message within the DFS replication.
Then, you may force replication over a given replication group with either
of the 2 methods.
Method1. User DFS management console to force replication in GUI mode.
1. Click Start, point to Administrative Tools, and then click DFS Management.
2. In the console tree, under the Replication node, select the replication
group that you want to force replication
3. in the middle pane, select Connections tab, right-click one of the
Sending member and select Replicate now…
4. Click OK to replicate.
Method2. Use dfsrdiag utility to force replication in command line.
Dfsrdiag syncnow </partner:name> </RGName:name> </Member:name> </v>
E.X. if we want to force replication of the replication group with
Win2003-DFS2 on current DFS member server, you may run the following command.
Dfsrdiag syncnow /partner:win2003-DFS2 /RGname:replication /time:1
Afterwards, you may open the target folders in the Windows Explorer on the
DFS management console to check if the files and folders were replicated.
Hope it helps.
David Shen
Microsoft Online Technical Support
"SJMP" wrote:
[Quoted Text] > I have DFS hosted on windows 2003 R2 32bit and replicating to an off-site
> 2003 R2 64bit.
>
> I was randomly checking folders and files, and noticed that it is actually
> not updating data. I ran a diag from the DFS mgmnt console and it reported
> everything is healthy. Not sure how to troublshoot this. How can I force
> replication to scan the src/trgt and compare the difference? I get my 1206
> DFSR events that say it successfully contact the DC on the Target Server. On
> the Src I see 1104 that DFS restarted replication after a backup operation.
>
> Thanks,
|
|
Dear Customer,
Thank you for posting in newsgroup.
According to the description, it seems that some files and folders is not
updated on the DFS member. If I have any misunderstanding, please feel free
to let me know.
Analysis and Suggestions:
=====================
To narrow down the issue, we need to verify that DFS replication is normal
between the source and target DFS member server.
Please create a propagation report on both of the source and target DFS
member server.
Steps to create a propagation report for DFS Replication:
1. Click Start, point to Administrative Tools, and then click DFS Management.
2. In the console tree, under the Replication node, right-click the
replication group that you want to create a diagnostic report for, and then
click Create Diagnostic Report.
3. when the Diagnostic Report Wizard popup, select Propagation report
4. Select the Replicated folder and Propagation server in the drop down list.
5. Click OK to generate the report.
You may check the report to see if the DFS replication is normal and if
there is any error message within the DFS replication.
Then, you may force replication over a given replication group with either
of the 2 methods.
Method1. User DFS management console to force replication in GUI mode.
1. Click Start, point to Administrative Tools, and then click DFS Management.
2. In the console tree, under the Replication node, select the replication
group that you want to force replication
3. in the middle pane, select Connections tab, right-click one of the
Sending member and select Replicate now…
4. Click OK to replicate.
Method2. Use dfsrdiag utility to force replication in command line.
Dfsrdiag syncnow </partner:name> </RGName:name> </Member:name> </v>
E.X. if we want to force replication of the replication group with
Win2003-DFS2 on current DFS member server, you may run the following command.
Dfsrdiag syncnow /partner:win2003-DFS2 /RGname:replication /time:1
Afterwards, you may open the target folders in the Windows Explorer on the
DFS management console to check if the files and folders were replicated.
Hope it helps.
"SJMP" wrote:
[Quoted Text] > I have DFS hosted on windows 2003 R2 32bit and replicating to an off-site
> 2003 R2 64bit.
>
> I was randomly checking folders and files, and noticed that it is actually
> not updating data. I ran a diag from the DFS mgmnt console and it reported
> everything is healthy. Not sure how to troublshoot this. How can I force
> replication to scan the src/trgt and compare the difference? I get my 1206
> DFSR events that say it successfully contact the DC on the Target Server. On
> the Src I see 1104 that DFS restarted replication after a backup operation.
>
> Thanks,
|
|
I open the Diagnostic Report Wizard and I do not see "Propagation report"
"David Shen" wrote:
[Quoted Text] > Dear Customer,
>
> Thank you for posting in newsgroup.
>
> According to the description, it seems that some files and folders is not
> updated on the DFS member. If I have any misunderstanding, please feel free
> to let me know.
>
> Analysis and Suggestions:
> =====================
>
> To narrow down the issue, we need to verify that DFS replication is normal
> between the source and target DFS member server.
> Please create a propagation report on both of the source and target DFS
> member server.
>
> Steps to create a propagation report for DFS Replication:
>
> 1. Click Start, point to Administrative Tools, and then click DFS Management.
>
> 2. In the console tree, under the Replication node, right-click the
> replication group that you want to create a diagnostic report for, and then
> click Create Diagnostic Report.
>
> 3. when the Diagnostic Report Wizard popup, select Propagation report
>
> 4. Select the Replicated folder and Propagation server in the drop down list.
>
> 5. Click OK to generate the report.
>
> You may check the report to see if the DFS replication is normal and if
> there is any error message within the DFS replication.
>
> Then, you may force replication over a given replication group with either
> of the 2 methods.
>
> Method1. User DFS management console to force replication in GUI mode.
>
> 1. Click Start, point to Administrative Tools, and then click DFS Management.
>
> 2. In the console tree, under the Replication node, select the replication
> group that you want to force replication
>
> 3. in the middle pane, select Connections tab, right-click one of the
> Sending member and select Replicate now…
>
> 4. Click OK to replicate.
>
> Method2. Use dfsrdiag utility to force replication in command line.
>
> Dfsrdiag syncnow </partner:name> </RGName:name> </Member:name> </v>
>
> E.X. if we want to force replication of the replication group with
> Win2003-DFS2 on current DFS member server, you may run the following command.
>
> Dfsrdiag syncnow /partner:win2003-DFS2 /RGname:replication /time:1
>
> Afterwards, you may open the target folders in the Windows Explorer on the
> DFS management console to check if the files and folders were replicated.
>
> Hope it helps.
>
> "SJMP" wrote:
>
> > I have DFS hosted on windows 2003 R2 32bit and replicating to an off-site
> > 2003 R2 64bit.
> >
> > I was randomly checking folders and files, and noticed that it is actually
> > not updating data. I ran a diag from the DFS mgmnt console and it reported
> > everything is healthy. Not sure how to troublshoot this. How can I force
> > replication to scan the src/trgt and compare the difference? I get my 1206
> > DFSR events that say it successfully contact the DC on the Target Server. On
> > the Src I see 1104 that DFS restarted replication after a backup operation.
> >
> > Thanks,
|
|
Here it is failing - how would I address this:
[INFO] Check for test file at
\??\UNC\fs01.mydomain.com\G$\Users\__DFSR_DIAGNOSTICS_TEST_FOLDER__\dfstest.xml
[ERROR] Failed to read file at
<\??\UNC\fs01.mydomain.com\G$\Users\__DFSR_DIAGNOSTICS_TEST_FOLDER__\dfstest.xml> Err: 3 (0x3)
PROCESSING MEMBER GBDRFS [2 OUT OF 2]
[INFO] Found <1> subscriber objects under computer: DRFS
[INFO] GBDRFS.DnsHostName = drfs.mydomain.com
[INFO] Computer Name: drfs
[INFO] Computer DNS: drfs.mydomain.com
[INFO] Domain Name: mydomain
[INFO] Domain DNS: mydomain.com
[INFO] Site Name: DisasterRecovery
[INFO] DRFS.RootPath = C:\SHARED\Users
[INFO] Check for test file at
\??\UNC\drfs.mydomain.com\C$\SHARED\Users\__DFSR_DIAGNOSTICS_TEST_FOLDER__\dfstest.xml
[ERROR] Failed to read file at
<\??\UNC\drfs.mydomain.com\C$\SHARED\Users\__DFSR_DIAGNOSTICS_TEST_FOLDER__\dfstest.xml> Err: 2 (0x2)
[ERROR] Failed to write file at <:c:\dfsreportdec4.xml> Err: -2147024773
(0x8007007b)
Save file to current working directory at: \\.\C:\Documents and
Settings\Administrator\dfsreportdec4.xml
|
|
David,
I did see the option under dfsrdiag. I ran propagationtest and backlog and
both came back clean. So something else here has gone awry.
[Quoted Text] >dfsrdiag PropReport /RGName:repl /RFName:"Users\uid" /TestFileName:"
fstest.xml" /ReportFile:":C:\dfsreportdec4.xml" /Domain:mydomain.com /v
[INFO] Found replication group <repl> under system naming context
[INFO] Found <2> msDFSR-Member objects under the replication group
[INFO] Found <2> msDFSR-ContentSet objects under the replication group
[INFO] Execution Time: 0 seconds
Operation Failed
|
|
Hi sjmp,
Thanks for the reply.
To narrow down the issue, would you please delete the old replication group
and re-create a new replication group which also hold 2 replicated folders
on both of the DFS member, and then run the following command line to test
if the replication is normal?
Dfsrdiag propagationtest /RGName:<replication group name>
/RFName:<replicated folder name> /TestFileName:test.xml /V >
C:\replicationtest.txt
Meanwhile, please also create a diagnostic report on the new replication
group to check if the if there is any error or warning message in it.
If possible, please run the following commands on the problematic server to
dump the AD configuration settings and service-wide configuration of DFS
replication.
Dfsrdiag dumpADcfg > C:\ADCFG.txt
Dfsrdiag dumpMachinecfg > C:\MachineCFG.txt
For further research, you may send all the test result files and the
diagnostic report to tfwst[ at ]microsoft.com for the further research
David Shen
Microsoft Online Technical Support
|
|
So I should delete the repl grp and recreate the same one to see if it
initializes replication? Once I recreate the new replication group should i
delete the data on the reciever side which has some of the replicated data?
"David Shen [MSFT]" wrote:
[Quoted Text] > Hi sjmp,
>
> Thanks for the reply.
>
> To narrow down the issue, would you please delete the old replication group
> and re-create a new replication group which also hold 2 replicated folders
> on both of the DFS member, and then run the following command line to test
> if the replication is normal?
>
> Dfsrdiag propagationtest /RGName:<replication group name>
> /RFName:<replicated folder name> /TestFileName:test.xml /V >
> C:\replicationtest.txt
>
> Meanwhile, please also create a diagnostic report on the new replication
> group to check if the if there is any error or warning message in it.
>
> If possible, please run the following commands on the problematic server to
> dump the AD configuration settings and service-wide configuration of DFS
> replication.
>
> Dfsrdiag dumpADcfg > C:\ADCFG.txt
>
> Dfsrdiag dumpMachinecfg > C:\MachineCFG.txt
>
> For further research, you may send all the test result files and the
> diagnostic report to tfwst[ at ]microsoft.com for the further research
>
> David Shen
> Microsoft Online Technical Support
>
>
|
|
Hi sjmp,
Yes. You may delete the replication group and recreate the same one to see
if it initializes replication.
Once you recreate the new replication group, please do not delete the data
on the receiver side which has some of the replicated data. You may add a
new DFS member into the new replication group to check if the initial
replication is normal.
Thanks.
David Shen
|
|
Hi sjmp,
I am just writing to see how everything is going. If you have any updates
or need any further assistance on this issue, please feel free to let me
know. I am glad to be of assistance.
David Shen
Microsoft Online Technical Support
|
|
|