Backup Failure - File Replication Service and other errors

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi.

Our backup failed last night and the server restarted. I've posted the
info below, if someone could clarify what went wrong i'd greatly
appreciate it:


(RELEVANT INFO FROM BACKUP LOG. SERVER PERFORMANCE REPORT FURTHER
DOWN:)

Backup Type: Normal

Backup started on 05/04/2007 at 01:54.
The 'Microsoft Information Store' returned 'Error returned from an ESE
function call (d).

' from a call to 'HrESEBackupRead()' additional data '-'
The operation was ended.
Backup completed on 05/04/2007 at 02:06.
Directories: 0
Files: 2
Bytes: 1,738,340,572
Time: 12 minutes and 6 seconds

----------------------

The operation did not successfully complete.

----------------------

=======================<END NTBACKUP LOG FILE>=====================
cWMI.OpenNamespace failed. (0x8007045b)
The success or failure of this backup could not be confirmed. Ensure
the Windows Management Instrumentation service is started and try to
backup again.
GetResultFromEvents failed. (0x8007045b)
NTBackup finished the backup with errors.

For more information about failed backups, see the article on
troubleshooting your backup at the following Web page:
http://go.microsoft.com/fwlink/?LinkId=18414

EventLogger.Initialize failed. (0x80004005)
LogBackupEventViewer failed. (0x80004005)
Backup ended at 05 April 2007 02:09
Backup Runner finished.





SERVER PERFORMANCE REPORT:

NtFrs 13568 05/04/2007 02:18 1

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:
\windows\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 reasons. [1] Volume "\\.\C:" has been formatted. [2]
The NTFS USN journal on volume "\\.\C:" has been deleted. [3] The NTFS
USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate
the journal if it finds corrupt entries at the end of the journal. [4]
File Replication Service was not running on this computer for a long
time. [5] File Replication Service could not keep up with the rate of
Disk IO activity on "\\.\C:". Setting the "Enable Journal Wrap
Automatic Restore" registry parameter to 1 will cause the following
recovery steps to be taken to automatically recover from this error
state. [1] At the first poll, which will occur in 5 minutes, this
computer will be deleted from the replica set. If you do not want to
wait 5 minutes, then run "net stop ntfrs" followed by "net start
ntfrs" to restart the File Replication Service. [2] At the poll
following the deletion this computer will be re-added to the replica
set. The re-addition will trigger a full tree sync for the replica
set. WARNING: During the recovery process data in the replica tree may
be unavailable. You should reset the registry parameter described
above to 0 to prevent automatic recovery from making the data
unexpectedly unavailable if this error condition occurs again. To
change this registry parameter, run regedit. Click on Start, Run and
type regedit. Expand HKEY_LOCAL_MACHINE. Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters" Double click on
the value name "Enable Journal Wrap Automatic Restore" and update the
value. If the value name is not present you may add it with the New-
DWORD Value function under the Edit Menu item. Type the value name
exactly as shown above.

.



Relevant Pages

  • RE: Backup Failure
    ... The backup is configured to run to a HCL compliant usb2 Ext HDD that is ... The File Replication Service has detected that the replica set "DOMAIN ... A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to ... Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Backup Failure - File Replication Service and other errors
    ... Our backup failed last night and the server restarted. ... The File Replication Service has detected that the replica set "DOMAIN ... recovery steps to be taken to automatically recover from this error ...
    (microsoft.public.windows.server.sbs)
  • Re: ntfrs 13506 / 13555 - 13508
    ... but the dcdiag logs didn't look complete. ... 13555 - The File Replication Service is in an error state. ... unfortunately - you may have guessed- there is no backup from the ...
    (microsoft.public.windows.server.active_directory)
  • Re: ntfrs 13506 / 13555 - 13508
    ... the 2k is logging ntfrs errors: ... 13555 - The File Replication Service is in an error state. ... the "system state" of this DC from backup (using ntbackup or other ...
    (microsoft.public.windows.server.active_directory)
  • Re: ntfrs 13506 / 13555 - 13508
    ... i mailed you the logs... ... "Meinolf Weber" wrote: ... 13555 - The File Replication Service is in an error state. ... the "system state" of this DC from backup (using ntbackup or other ...
    (microsoft.public.windows.server.active_directory)