Compartilhar via

Event ID 565 — Backup Set Integrity

  • Artigo

Applies To: Windows Server 2008 R2

When you run a backup operation, Windows Server Backup runs checks for consistency and hardware and software corruption to determine the integrity of the backup set.

Event Details

Product: Windows Operating System
ID: 565
Source: Microsoft-Windows-Backup
Version: 6.1
Symbolic Name: ADMIN_APP_CONSISTENCY_CHECK_FAILED
Message: Consistency check for component '%1'\'%2' failed. Application '%3' will not be avaliable in the backup done at time '%4'

Resolve

Review event details for information about consistency check issues

When you run a backup operation, Windows Server Backup checks the application data being backed up to confirm that it is in a consistent state so it can be trusted to perform a recovery. If inconsistencies are found, the operation will complete, but with errors. To resolve this issue, follow these general steps:

  1. Find the applicable event in Event Viewer, and then review the details for that event. For more information, see "Review event details in Event Viewer."
  2. Review the events associated with the application that includes the failed component. 
  3. After resolving any errors that you found when performing the steps above, re-run another backup. For more information, see "Create a one-time backup using the command line."
  4. Check for Event ID 4, indicating that the backup completed with no errors. For more information, see "Confirm a backup completed with no errors."

To perform these procedures, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Review event details in Event Viewer

To review event details for backup consistency, check failures in Event Viewer:

  1. Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
  2. In the left pane, double-click Windows Logs, and then click Application.
  3. In the right pane, for the event, review the error code to determine why the consistency check failed. Also, review the application or component name, logical path, and Writer ID details to determine which component failed.
  4. Then, look for events logged by the application that includes the failed component, and then resolve any relevant failures.

Create a one-time backup using the command line

If you use wbadmin start backup with no parameters, the settings for your scheduled backup are used.

Make sure that the backup storage location specified by -backupTarget is online.

To perform a one-time backup:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  2. At the prompt, type: wbadmin start backup. Use parameters, as needed. (To view the parameters and help for this command, at a command line, type: wbadmin start backup /?).

    For example, to create a backup that will be stored on drive f, of volumes e:, d:\mountpoint, and \\?\Volume{cc566d14-4410-11d9-9d93-806e6f6e6963}, type: wbadmin start backup -backupTarget:f: -include:e:,d:\mountpoint,\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\.

Confirm a backup completed with no errors

To confirm that a backup operation completed with no errors:

  1. Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
  2. In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
  3. In the Event ID column, look for event 4.
  4. For this event, confirm that the the value in the Source column is Backup.

Verify

To verify that a backup set is complete and will be able to be used for recovery, you should do the following:

  • Verify that the backup operation to create the backup set completed with no errors.
  • Verify that the global catalog has information about the backup set.
  • Verify that the local catalog has information about the backup set.
  • Verify that the backup set itself is not corrupted by performing a recovery with the backup set.

To perform these procedures, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Verify that a backup completed with no errors

To verify that a backup operation completed with no errors:

  1. Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
  2. In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
  3. In the Event ID column, look for event 4.
  4. For this event, confirm that the the value in the Source column is Backup.

Verify the global catalog

To verify that the global catalog has information about the backup set:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin get versions.
  3. If the command output shows information about backups, then the global catalog is intact.

Verify the local catalog

To verify that the local catalog has information about the backup set:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin get versions -backuptarget:<VolumeName>.
  3. If backup versions are listed, then the local backup catalog is not corrupted and is intact. 

Verify that a backup works for recovery

To verify that a backup will work for recovery, you should try recovering something from the backup.

Note: Make sure that you do not mistakenly overwrite newer data. To avoid this, you can perform a recovery to a different volume than was backed up as part of the backup set. You will receive a message that any data on the destination volume will be lost when you perform the recovery. Make sure that the destination volume is empty or does not contain information that you will need later.

To perform a recovery:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  2. At the prompt, type: wbadmin start recovery. Use parameters, as needed. (To view the parameters and help for this command, at a command line, type: wbadmin start recovery /?).

    For example, to run a recovery of the backup from March 1, 2005, taken at 9:00 A.M. of the d:\folder and its sub-folders, type: wbadmin start recovery -version:03/1/2005-09:00 -itemType:File -items:d:\folder -recursive.

  3. Review the items that you recovered to make sure that they were recovered as you expected.

Backup Set Integrity

File Services