When a schedule Backup Exec System Recovery (BESR) starts a recovery point image the Event ID 55: The file system structure on the disk is corrupt and unusable

Problem

When a schedule Backup Exec System Recovery (BESR) starts a recovery point image the Event ID 55: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume is generated repeatedly filling up the system event logs.

Error Message

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume
1392, C:\Data\Systems Admin\Site Log\Privacy SBS\Event logs.

When a schedule Backup Exec System Recovery (BESR) starts a recovery point image the following Windows System event is generated repeatedly filling up the System event logs:

=====================================================

Event Type:      Error
Event Source:      Ntfs
Event Category:      Disk
Event ID:      55
Description: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume <SYSTEM_NAME>.

====================================================

Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 57481
Description:
1392, C:\Data\Systems Admin\Site Log\Privacy SBS\Event logs.

====================================================

Cause

It is suspected the issue is an overlap of backup schedules between Backup Exec Windows Server and Backup Exec System Recovery.
 

Solution


Observation:
 

  • Backup images that are created are capable of being successfully be used for files extraction and for full disk restores.



 

         It is suspected the issue is an overlap of backup schedules between Backup Exec Windows Server and Backup Exec System Recovery.

Resolution:

         If a CHKDSK utility has been ran, and all errors has been corrected, change the backup schedules between the two products to be sequential without overlap.

 

 

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)