Partager via

Event ID 2 — Backup Service Availability

  • Article

Applies To: Windows Server 2008

For Windows Server Backup to be able to perform backups and recoveries, the Block Level Backup Engine service (wbengine) must be able to start and the global or local catalogs must not be corrupted. Wbengine enables Windows Server Backup to perform block-level backup and recovery operations. The global catalog is a file that Windows Server Backup uses to store the details about all of your backups (what volumes are backed up and where the backups are located). The local catalog is a file that Windows Server Backup creates to store details about the backups that are stored on a specific backup destination.

Event Details

Product: Windows Operating System
ID: 2
Source: Microsoft-Windows-Backup
Version: 6.0
Symbolic Name: GLOBAL_CATALOG_FAILURE_EVENT
Message: Windows Backup catalog is corrupt. Please recover the catalog from a backup using 'WBADMIN RESTORE CATALOG' or using Windows Backup MMC Snapin.

Resolve

Restore the global catalog from a recent backup

You must have a global catalog file that is not corrupted to create backups (the global catalog contains information about all your backups and backup destinations). If the global catalog file becomes corrupted, you will receive an alert and an event will be added to the event log (Event ID 2 or 514). To continue with future backups, you will need to either restore the global catalog using the catalog from a recent backup—or delete the corrupted global catalog if no backups are available. If you delete the catalog, the information about previous backups will be lost, and you will not be able to access previous backups using the Windows Server Backup snap-in.

To recover or delete a catalog, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Restore the global catalog

To restore the global catalog from a backup destination:

  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 restore catalog -backuptarget:<drive letter>.

Delete the global catalog

To delete the global catalog:

  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 (no parameters): wbadmin delete catalog.

Verify

To verify that Windows Server Backup is able to perform backup and recovery operations, you should verify that the Block Level Backup Engine service (wbengine) is able to start and that the global catalog and the local catalog have not been corrupted. The global catalog is the file that contains information about all your backups, and the local catalog is the file that contains information about backups saved to a specific destination.

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

Verify that wbengine can start

To verify that wbengine can start:

  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: net start wbengine.
  3. View the text message to verify that the service starts or is already started.

Verify the local catalog

To verify that the local catalog stored on a backup destination exists and is not corrupted:

  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:<backup destination drive letter>.
  3. Verify that command runs without errors.

Verify the global catalog

To verify that the global catalog on the boot volume exists and is not corrupted:

  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 (with no parameters): wbadmin get versions.

    Without parameters this command shows all the backups you have taken that are stored in all locations—that is, information stored in the global catalog.

  3. Verify that the command runs without errors.

Backup Service Availability

File Services