Link to home
Start Free TrialLog in
Avatar of bikerhong
bikerhong

asked on

DFSR Replication issues

Hi

I have just added a second server on another site connected via IPSEC VPN to our DFS.

The other site is for backup only and all users access the primary server for files.

Initial replication of one share was fine and went without a hitch, it was about 30MB so completed pretty quickly.

The second replication group folder is just over a 1GB which again is not huge, but it's stalled with errors:

The DFS Replication service stopped replication on replicated folder XXXX at local path D:\shares\XXXX due to Error ID: 9098 (A tombstoned content set deletion has been scheduled). Event ID: 4004

and

A USN journal wrap occurred 1 times in the past 7 days on D:. DFS Replication monitors the USN journal to detect changes made to the replicated folder. A USN journal wrap occurs when large numbers of files change so quickly that the USN journal must discard the oldest changes (before DFS Replication has had a chance to detect the changes) to stay within the specified size limit of the USN journal. Although DFS Replication automatically recovers from this problem, replication stops temporarily for replicated folders stored on this volume. Repeated journal wraps usually indicate that the USN journal is too small. Event ID: 2202

Google isnt providing many clues - any ideas?
ASKER CERTIFIED SOLUTION
Avatar of Haresh Nikumbh
Haresh Nikumbh
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
Avatar of bikerhong
bikerhong

ASKER

I've read both of those but my replication is not starting at all....how do I run the dfrsadmin command to determine if there is a primary?
Where do you run the DFsradmin command?
On the primary server.
Ok - It shows me that the Primary server information is correct.

What now?

I tried removing the RG and starting from scratch, but same error straight away.
run check disk on the primary server and see if its shows any error ?

Also verify if you found error event for Volsnap
The first link did it. I was wary to run it because I didnt want to lose infortmation, but as soon as I ran it replication started popularting the second server.

Thanks :)
Good 2 know it solved