DFS-R Database Corrupt

Hi,
While DFS-R was performing an Online defragmentation of the DFS-R DB, a
restore job started using Backupexec 12. The DFS-R service was stopped,
restore completed, DFS-R Service started.
DFS-R Reported a Corrupt Database, Tried a Recovery which failed, then
started a new "Initial Replication".
Now as most of the data was already on the server every replication ended
with a conflict, the files were moved to ConflictandDeleted and eventually
deleted. This led to a huge data loss.
Does anyone know why does DFS-R starts a new Initial replication on its own?
This is NOT supposed to happen.

Sorry, I found a Dokument,
http://msdn.microsoft.com/en-us/libr...26(VS.85).aspx apparently it is
supposed to happen.

This however is a real problem, if the DFSR DB recovery is on the Primary
target, then most of the data on the other Partner(s) is bound to be out of
date, and nearly every file will already exist on the server and will result
in a Conflict which will eventually be overwritten.



"RodMan" wrote:

> Hi,
> While DFS-R was performing an Online defragmentation of the DFS-R DB, a
> restore job started using Backupexec 12. The DFS-R service was stopped,
> restore completed, DFS-R Service started.
> DFS-R Reported a Corrupt Database, Tried a Recovery which failed, then
> started a new "Initial Replication".
> Now as most of the data was already on the server every replication ended
> with a conflict, the files were moved to ConflictandDeleted and eventually
> deleted. This led to a huge data loss.
> Does anyone know why does DFS-R starts a new Initial replication on its own?
> This is NOT supposed to happen.
>
>
>
>

Does any one know if:
1. it is possible to stop DFSR from initiating an Initial Backup?
2. it is possible to recreate the database only by file comparission not
replication?


"RodMan" wrote:

> Sorry, I found a Dokument,
> http://msdn.microsoft.com/en-us/libr...26(VS.85).aspx apparently it is
> supposed to happen.
>
> This however is a real problem, if the DFSR DB recovery is on the Primary
> target, then most of the data on the other Partner(s) is bound to be out of
> date, and nearly every file will already exist on the server and will result
> in a Conflict which will eventually be overwritten.
>
>
>
> "RodMan" wrote:
>
> > Hi,
> > While DFS-R was performing an Online defragmentation of the DFS-R DB, a
> > restore job started using Backupexec 12. The DFS-R service was stopped,
> > restore completed, DFS-R Service started.
> > DFS-R Reported a Corrupt Database, Tried a Recovery which failed, then
> > started a new "Initial Replication".
> > Now as most of the data was already on the server every replication ended
> > with a conflict, the files were moved to ConflictandDeleted and eventually
> > deleted. This led to a huge data loss.
> > Does anyone know why does DFS-R starts a new Initial replication on its own?
> > This is NOT supposed to happen.
> >
> >
> >
> >