Re: fix Journal wrap error
- From: deal1 <deal1@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 1 Oct 2006 09:17:01 -0700
"Jill Zoeller [MSFT]" wrote:
Here are some resources for you:.
More info about USN journal and how to increase its size (to prevent journal
wraps): http://support.microsoft.com/kb/292438/en-us
There is a KB article on performing non-authoritative restores, but it looks
like the procedure has been removed. I'm pasting the procedure from the
Ultrasound help below. I highly recommend that you use Ultrasound for your
FRS monitoring. You can install it from www.microsoft.com/frs.
Performing a Nonauthoritative Restore
The nonauthoritative restore (D2) is used to bring the local FRS replica set
back up to date with its partners. Nonauthoritative restores are often
necessary to resolve the following issues:
a.. Assertions in the FRS service
b.. Corruption of the local FRS jet database
c.. Journal wrap errors
d.. FRS replication failures
The nonauthoritative restore process brings a replica member up to date by
comparing all the local files in a replica set with the ones of the upstream
partners. After you set the Burflag to D2 and restart the service, FRS will
move all the data into a "pre-existing" directory and then start to compare
the file IDs and the files' MD5 checksums from the upstream partner with the
local ones. If the file ID and the MD5 checksum match, FRS copies this file
from the pre-existing directory into its original location. If they don't
match, then FRS copies the new file from the partner. Before Windows 2000
SP3, this work is performed with each of upstream partner at once; with
Windows 2000 SP3 and later and Windows Server 2003, this process is
performed sequentially - one partner at a time.
To perform a nonauthoritative restore, use the following procedure:
To perform a nonauthoritative restore
1.. At the command prompt, type net stop ntfrs.
2.. Click Start, click Run, type regedit, and then click OK.
3.. Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\
Backup/Restore\Process at Startup
4.. In the right pane, double-click BurFlags.
5.. In the Edit DWORD Value dialog box, type D2 and then click OK.
6.. Close Registry Editor.
7.. At the command prompt, type net start ntfrs.
When the FRS service restarts, the following actions occur:
a.. The value for BurFlags registry key returns to 0.
b.. Files in the reinitialized FRS folders are moved to a folder named
NtFrs_PreExisting_See_EventLog.
c.. The FRS database is rebuilt.
d.. The member performs an initial join of the replica set from an
upstream partner or from the computer that is specified in the Replica Set
Parent registry key if a parent has been specified for SYSVOL replica sets.
e.. The reinitialized computer performs a full replication of the affected
replica sets when the relevant replication schedule begins.
The placement of files in the NtFrs_PreExisting_See_EventLog folder on
reinitialized members is a safeguard in FRS designed to prevent accidental
data loss. Any files destined for the replica that exist only in the local
PreExisting folder and did not replicate in after the initial replication
can then be copied to the appropriate folder. When outbound replication has
occurred, delete files in the PreExisting folder to free up additional disk
space.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
"Owen@7" <Owen7@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8ACB1148-1DA8-41F0-A976-9E34D00B75AF@xxxxxxxxxxxxxxxx
I am receiving Event ID 13568
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"
any suggestionson how to fix this.
- Follow-Ups:
- Re: fix Journal wrap error
- From: deal1
- Re: fix Journal wrap error
- Prev by Date: Extreme fragmentation when writing large bkf files to compressed drive
- Next by Date: Re: fix Journal wrap error
- Previous by thread: Extreme fragmentation when writing large bkf files to compressed drive
- Next by thread: Re: fix Journal wrap error
- Index(es):
Relevant Pages
|
