We are preparing to use Swing IT!! to migrate from SBS2000 to Server 2003 Standard. In going over the preparations before we begin I checked the System log on SBS2000 and found this (summarized):
The File Replication Service has detected that the replica set "Domain System Volume (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is: "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reason.
It then lists the reasons and gives instructions to modify a registry value. I've looked this up and have seen posts detailing how people fixed the condition on their servers. My question is, since this is SBS2000 the server isn't going to be replicating to anything right now anyway, will it?
Apparently it's been going on for a while and it doesn't seem to be affecting anything obvious. We stopped running Exchange over six months ago so it can't impact that (I read an article where someone claimed fixing this improved an Exchange problem they were having).
Do we need to fix this before we start our migration process? Or can we ignore it if the existing production server is about to be migrated over and decommissioned in a matter of two weeks? We begin the migration process on Thursday of this week. Thanks.