Event ID 519 — Backup Set Integrity

  • Article

Applies To: Windows Server 2008

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: 519
Source: Microsoft-Windows-Backup
Version: 6.0
Symbolic Name: ADMIN_PARTIAL_BACKUP_FAILED_EVENT
Message: Backup started at '%1' failed to backup volume(s) '%2' with following error code %3 (%4). Please rerun backup once issue is resolved.

Resolve

Review event details for solutions for a failed backup

If a backup fails, review the details for the applicable events to find out why the backup operation failed. Then re-run the backup.

To do this, follow these general steps:

  1. Find the applicable events in Event Viewer, and then review the details for those events to find out why the backup operation failed. For more information, see "Review event details in Event Viewer."
  2. Review the error message for the failure in the Windows Server Backup snap-in start page. For more information, see "Review error messages in the Windows Server Backup snap-in."
  3. Confirm that the location to perform the backup to is online.
  4. After resolving any errors that you found in performing the steps above, re-run another backup. For more information, see "Create a one-time backup using the command line."

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 a backup in Event Viewer:

  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 right pane, click the Details tab, click an event in the list, and review the information.
  4. If the event was related to a particular volume, then error codes for the volume will be present in the details.
  5. Review error messages for the error codes, as described in "Review error messages in the Windows Server Backup snap-in."

Review error messages in the Windows Server Backup snap-in

To view error messages using Windows Server Backup:

  1. Open the Windows Server Backup snap-in. Click Start, click Administrative Tools, and then click Windows Server Backup.
  2. On the start page, under Messages, double-click the event for the failed backup, click the Errors tab, and view the text under Message.

Create a one-time backup using the command line

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}\.

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