Unexpected Status after Recreation of DFSR-Replication Groups in 2003 R2

hi folks,

i have recreated dfsr-replication group hours ago migrating envoirement 2 2003 r2 servers unsupported one-sided replication two-way replication descibed in http://blogs.technet.com/askds/archive/2009/06/23/recovering-from-unsupported-one-way-replication-in-dfsr-windows-server-2003-r2-and-windows-server-2008.aspx .

this 2 local fileservers in 1 site 1 gbe between , 1,8 tb of data (divided in 3 folders). main reason action was, 2 of 3 folders not replicating long time.

i have recreated first replication group via following steps:

• deleting replication group (share in dfs allways deactivated, one-way config)
• delete data on folder in downstream-server (incl. dfsr_private)
• restoring last full-backup via backupexec & folder redirection
• move data correct folder (backup exec allways restores additional dfsr-replicated fodlers subdir , pute data that)
• recrate replication group setting data on upstream server primary

good: upstream reports, repl. group has been created ; downstream reports, waiting initial sync .. staging fills .. perfmon shows data movement, seems fine far ..

however, there things wonder me (and keep me sleepless next nights) , want make sure expected:

if check initial sync-status on both servers, upstream reports status 4 (completed) , downstream status 2 (not completed). expected 2 on both sides, until completion reported.

the "isprimary" - flag set on none of servers !? (this makes me bit afraid, expected upstream primary until initial sync done)

the backlog up->down , vise versa identical (i expected down->up empty) , reduced syncronous.

the backlog includes files (~90000 folder) mean, files have replicated or backlog include files, checked differences between 2 servers ?

 

thanks in advance.

Windows Server  >  File Services and Storage