How do you copy a table from the backup object server to the primary object server using the TRANSFER command?
Tag: WBAdmin
Event ID 8228 — Volume Shadow Copy Service Operations
Event ID 8228 — Volume Shadow Copy Service Operations
Updated: January 27, 2011
Applies To: Windows Server 2008 R2
The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.
Event Details
| Product: | Windows Operating System |
| ID: | 8228 |
| Source: | VSS |
| Version: | 6.1 |
| Symbolic Name: | VSS_ERROR_IXMLDOMDOCUMENT_PARSEERROR |
| Message: | Fail to parse XML file. Reason %1 Line %2 Position %3 Errorcode %4 Problem text %5 %6 |
Resolve
Contact the backup software vendor
This event is usually caused by restoring from a backup that was created on a more recent Windows operating system version.
To resolve this issue, contact the backup software vendor for further support.
Verify
To verify that the Volume Shadow Copy Service (VSS) is operating correctly, retry the previous VSS operation.
Related Management Information
Volume Shadow Copy Service Operations
Related:
Event ID 8220 — Volume Shadow Copy Service Operations
Event ID 8220 — Volume Shadow Copy Service Operations
Updated: January 27, 2011
Applies To: Windows Server 2008 R2
The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.
Event Details
| Product: | Windows Operating System |
| ID: | 8220 |
| Source: | VSS |
| Version: | 6.1 |
| Symbolic Name: | VSS_INFO_DELETION_TIMEOUT |
| Message: | Ran out of time while deleting files. %1 |
Resolve
This is a normal condition. No further action is required.
Related Management Information
Volume Shadow Copy Service Operations
Related:
Event ID 8219 — Volume Shadow Copy Service Operations
Event ID 8219 — Volume Shadow Copy Service Operations
Updated: January 27, 2011
Applies To: Windows Server 2008 R2
The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.
Event Details
| Product: | Windows Operating System |
| ID: | 8219 |
| Source: | VSS |
| Version: | 6.1 |
| Symbolic Name: | VSS_INFO_SCAN_TIMEOUT_INSTANCE |
| Message: | Ran out of time while expanding file specification %1\%2. This was being done for the %3 subscriber. %4 |
Resolve
This is a normal condition. No further action is required.
Related Management Information
Volume Shadow Copy Service Operations
Related:
Event ID 6029 — Domain Rename
Event ID 6029 — Domain Rename
Updated: November 25, 2009
Applies To: Windows Server 2008
The Local Security Authority (LSA) stores the domain name and the domain security identifier (SID). During a domain rename operation, the LSA domain name is updated.
Event Details
| Product: | Windows Operating System |
| ID: | 6029 |
| Source: | LsaSrv |
| Version: | 6.0 |
| Symbolic Name: | LSA_DOMAIN_RENAME_ERROR1 |
| Message: | LSA could not update domain information in the registry to match the DS. Error=%1. |
Resolve
Restore the Active Directory database from backup
The domain controller is not able to read domain information from the data store. Restore the Active Directory database from backup. Perform the following procedure using the computer that is logging the event to be resolved.
To restore the Active Directory database from backup, you need the Directory Services Restore Mode password. If you do not know the Directory Services Restore Mode password, you can reset it using the Ntdsutil tool and the steps in article 322672 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=95915).
To perform these procedures, you must have membership in Domain Admins, or you must have been delegated the appropriate authority.
To restore a domain controller from backup:
- From a command prompt that you opened as administrator, type bcdedit /set safeboot dsrepair, and then press ENTER. This causes the domain controller to start in Directory Services Restore Mode.
- Restart the domain controller.
- At the Windows logon screen, click Switch User.
- Click Other User.
- Type .\administrator as the user name, type the Directory Services Restore Mode password for the server, and then press ENTER.
- Click Start, right-click Command Prompt, and then click Run as Administrator.
- At the command prompt, type wbadmin get versions -backuptarget:targetDrive:, and then press ENTER. Substitute the location of the backup that you want to restore for targetDrive.
- Identify the version of the backup that you want to restore. You must enter this version exactly in the next step.
- Type wbadmin start systemstaterecovery -version:dateTime -backuptarget:targetDrive:-quiet, and then press ENTER. Substitute the version of the backup that you want to restore for dateTime and the volume that contains the backup for targetDrive.
- Open a command prompt, type bcdedit /deletevalue safeboot, and then press ENTER. This causes the domain controller to restart in normal mode.
- After the recovery operation has completed, restart the domain controller.
Verify
To verify that a domain rename was successful:
- On a domain controller in the renamed domain, open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- At the command prompt, type dcdiag, and then press ENTER.
- At the command prompt, type dcdiag /dns, and then press ENTER.
If the diagnostic tests pass with the correct domain name, the domain name was successful.
Related Management Information
Related:
Event ID 4422 — Volume Shadow Copy Service Support
Event ID 4422 — Volume Shadow Copy Service Support
Updated: December 3, 2008
Applies To: Windows Server 2008 R2
The Microsoft Distributed Transaction Coordinator service (MSDTC) supports the Windows Volume Shadow Copy Service, a feature that is used by System Restore, Windows Complete PC Backup, and Windows Server Backup. Through this support, MSDTC guarantees transaction completeness without data corruption across backup and restore operations.
Event Details
| Product: | Windows Operating System |
| ID: | 4422 |
| Source: | Microsoft-Windows-MSDTC |
| Version: | 6.1 |
| Symbolic Name: | IDS_DTC_E_PROCESS_SYSTEM_RESTORE_SUCCESS |
| Message: | MS DTC has processed a system restore event. As a result the transaction log has been reset and the identity of the transaction manager has been changed.%0 |
Resolve
This is a normal condition. No further action is required.
Related Management Information
Volume Shadow Copy Service Support
Related:
Event ID 2089 — Backups
Event ID 2089 — Backups
Updated: November 25, 2009
Applies To: Windows Server 2008
You should back up the directory database on a domain controller routinely so that if hardware fails or data becomes corrupt, you can quickly recover the information in the database.
Event Details
| Product: | Windows Operating System |
| ID: | 2089 |
| Source: | Microsoft-Windows-ActiveDirectory_DomainService |
| Version: | 6.0 |
| Symbolic Name: | DIRLOG_BACKUP_LATENCY_WARNINGS |
| Message: | This directory partition has not been backed up since at least the following number of days.
Directory partition: “DN of the partition” ‘Backup latency interval’ (days): “Value in days of the backup latency interval” It is recommended that you take a backup as often as possible to recover from accidental loss of data. However if you haven’t taken a backup since at least the ‘backup latency interval’ number of days, this message will be logged every day until a backup is taken. You can take a backup of any replica that holds this partition. By default the ‘Backup latency interval’ is set to half the ‘Tombstone Lifetime Interval’. If you want to change the default ‘Backup latency interval’, you could do so by adding the following registry key. ‘Backup latency interval’ (days) registry key: |
Resolve
Ensure that backups are taken more frequently than the backup latency interval
You should ensure that the Active Directory database is backed up more frequently than the interval that is set for the tombstone lifetime of your forest. If you are using a non-Microsoft backup solution and you confirm that the backup interval is more frequent than the tombstone lifetime, you may want to contact the vendor of the backup solution so that they can register their backups in Active Directory Domani Services (AD DS), as recommended.
You can use Windows Server Backup or a non-Microsoft program to back up system state on a domain controller. If you plan to use a non-Microsoft program, check the software vendor’s instructions for completing and verifying the system state backup. For more information, see Steps for Backing Up and Recovering AD DS (http://go.microsoft.com/fwlink/?LinkId=151349).
The following procedures guide you through the process of installing Windows Server Backup and creating a manual backup from the command line. You may want to consider scheduling backups with the Task Scheduler application. For more information, see Task Scheduler How To (http://go.microsoft.com/fwlink/?LinkId=151352).
Membership in Builtin Administrators or Backup Operators, or equivalent, is the minimum required to complete these procedures. In addition, you must have write access to the target backup location. Review details about default group memberships at http://go.microsoft.com/fwlink/?LinkID=150761.
To install Windows Server Backup:
- Click Start, click Administrative Programs, and then click Server Manager. Right-click Features, and then click Add Features.
- Expand Windows Server Backup Features, and then click Windows Server Backup. As an option, you can click Command-line Tools. Click Next.
- Click Install. After the installation is complete, click Close.
For additional options for installing Windows Server Backup, see Active Directory Backup and Restore in Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkID=149696).
To perform a manual system state backup of a domain controller from a command prompt:
- Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, enter the appropriate credentials (if requested) and confirm that the action it displays is what you want, and then click Continue.
- At the command prompt, type the following command, and then press ENTER: wbadmin start systemstatebackup -backuptarget:<drive>: -quiet. Substitute the actual drive letter or volume to which you want to send the backup for <drive>. If you do not specify the -quiet parameter, you are prompted to press Y to proceed with the backup operation. The target volume for a system state backup can be a local drive, but it cannot be any of the volumes that are included in the backup by default.
Note: To store the system state backup on a volume that is included in the backup, you must add the AllowSSBToAnyVolume registry entry to the server that you are backing up. There are also some prerequisites for storing system state backup on a volume that is included in the backup. For more information, see Known Issues for AD DS Backup and Recovery (http://go.microsoft.com/fwlink/?LinkID=117940).
For more information, see Create Backups of the System State Using a Command Line (http://go.microsoft.com/fwlink/?LinkID=151353).
Verify
Ensure that the domain controller is configured to back up the directory database within a time interval that is more frequent than the tombstone lifetime for the forest. However, if the forest functional level is raised to Windows Server 2008 R2 and the Active Directory Recycle Bin feature is enabled, backups should occur more frequently than the lesser of the values that are set for the tombstoneLifetime and msDS-deletedObjectLifetime attributes).
Note: If no value is set for msDS-deletedObjectLifetime, the value that is set for the tombstoneLifetime is used.
Membership in Enterprise Admins, or equivalent, is the minimum required to complete this procedure. Review details about default group memberships at http://go.microsoft.com/fwlink/?LinkID=150761.
Check the value for the backup latency interval threshold
The default time period of the backup latency interval is half the tombstone lifetime value, when the Active Directory Recycle Bin feature is not enabled. The default tombstone lifetime is 60 or 180 days, depending on the domain controller operating system version that was used to create the forest. For more information, see Determine the Tombstone Lifetime for the Forest (http://go.microsoft.com/fwlink/?LinkID=137177). If the Active Directory Recycle Bin is enabled, the backup latency interval becomes half the lesser of the values of tombstoneLifetime and msDS-deletedObjectLifetime.
Note: After the Active Directory Recycle Bin feature is enabled, it cannot be disabled.
To check the value of the backup latency interval:
- Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- At the command prompt, type regedit, and then press ENTER.
- In the Registry Editor, navigate to the following registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\
- In the details pane, determine whether there is a Backup Latency Threshold (days) value. If there is a value, note the value that is configured here.
- To check the value of the tombstone lifetime, at a command prompt, type the following command, and then press ENTER: dsquery * “cn=Directory Service, cn=Windows NT,cn=Services,Cn=Configuration,dc=<forestDN>” –scope base –attr tombstonelifetime. Substitute the actual forest distinguished name for <forestDN>. For example, if your forest name is corp.cpandl.com, the forest distinguished name is dc=corp,dc=cpandl,dc=com. The word attribute tombstonelifetime is returned, along with the value for which it is set. Divide the value by two to determine the default backup latency interval, which is in effect if there is no backup latency threshold (days) value defined.
- If the Active Directory Recycle Bin optional feature is enabled, you can check the value of the msDS-deletedObjectLifetime attribute by running the following command: dsquery * “cn=Directory Service, cn=Windows NT,cn=Services,Cn=Configuration,dc=<forestDN>” –scope base –attr msDS-deletedObjectLifetime
- As in the previous step, substitute the actual forest distinguished name for <forestDN>. If no value is shown for msDS-deletedObjectLifetime, its value is equal to the value of tombstoneLifetime.
For more information about the Active Directory Recycle Bin and its relationship to the useful backup lifetime, see Scenario Overview for Restoring Deleted Active Directory Objects (http://go.microsoft.com/fwlink/?LinkID=148279).
Check when a backup was last taken
To check when the last backup was registered in AD DS:
- Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, enter the appropriate credentials (if requested) and confirm that the action it displays is what you want, and then click Continue.
- At the command prompt, type repadmin /showbackup, and then press ENTER. Review the Org.Time/Date column to see when the most recent backup of the Active Directory database was made. This is the value that you use to determine whether your last backup is too old (as defined in the backup latency interval).
If you use a non-Microsoft backup solution and you know that backups were taken more recently than the date that you just retrieved, you may want to contact the vendor of the backup solution so that they can register their backups in AD DS as recommended. If the date you retrieved is older than the tombstone lifetime, it is critical that you take a backup of your Active Directory environment.
Test your system state backups to ensure that they are good
To ensure that the backups you are creating are good, restore them to a test location. For complete information about restoring system state backups from the command line, see Recover the System State Using a Command Line (http://technet.microsoft.com/en-us/library/cc753789.aspx). The following procedure is a simple restore of the system state backup to an alternate location. You can restore the files to any alternate location, but we recommend that you use a volume that is physically secure and that can be formatted after the procedure.
Membership in Backup Operators, or equivalent, is the minimum required to complete this procedure. Review details about default group memberships at http://go.microsoft.com/fwlink/?LinkID=150761.
To restore a system state backup to an alternate test location:
- Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, enter the appropriate credentials (if requested) and confirm that the action it displays is what you want, and then click Continue.
- At the command prompt, type wbadmin get versions, and then press ENTER.
- Identify the name of the backup file that you want to verify.
- At the command prompt, type the following command, and then press ENTER: wbadmin start systemstaterecovery –verson:<verID> -recoveryTarget:<Tgt>
- Substitute the actual version identifier for <verID>, and replace <Tgt> with the drive or volume location to which you want to restore the system state backup so that you can check that the data is good. For example, to restore a backup with version identifier 03/19/2009-04:02 to the C:\BackupCheck folder, run the following command: wbadmin start systemstaterecovery -verson:03/19/2009-04:02 -recoveryTarget:B:\Backups -quiet
- The command output displays the success of the recovery operation as it happens. A success message should appear, as well as the location of the log file of the restore process. You can use Notepad or a similar text editor to review the log.
- You can also navigate the structure of the restored files to ensure that critical items have been restored. For example, you can verify that the NTDS.DIT file that is located in the \Windows\NTDS folder by default has been restored to the alternate location.
Related Management Information
Related:
Event ID 13 — Volume Shadow Copy Service Operations
Event ID 13 — Volume Shadow Copy Service Operations
Updated: January 27, 2011
Applies To: Windows Server 2008 R2
The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.
Event Details
| Product: | Windows Operating System |
| ID: | 13 |
| Source: | VSS |
| Version: | 6.1 |
| Symbolic Name: | VSS_ERROR_STARTING_COM_SERVER |
| Message: | Volume Shadow Copy Service information: The COM Server with CLSID %1 and name %2 cannot be started. [%3] %4 |
Resolve
Check that services are enabled and providers are operating properly
Note: This event can be caused by running backup software containing a 32-bit Volume Shadow Copy service (VSS) requester on a 64-bit version of Windows.
This event can indicate that the computer is low on resources or has incorrect COM registration information.
To resolve this issue, check that the COM+ Event System service is started and that the VSS service and Microsoft Software Shadow Copy Provider service are both enabled. You should also make sure that third-party installed VSS providers are operating properly. If a VSS provider is not operating properly, you should try reinstalling it. If that does not work, you should contact the provider vendor.
To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.
Check that the COM+ Event System service is started
To check that the COM+ Event System service is started:
- Click Start, click Administrative Tools, and then click Services.
- In the results pane, double-click COM+ Event System.
- In Service status, make sure that the status is Started. If the status is not Started, click Start.
- Ensure that Startup type is set to Automatic.
- Click OK.
Check that the VSS service is enabled
To check that the VSS service is enabled:
- Click Start, click Administrative Tools, and then click Services.
- In the results pane, double-click Volume Shadow Copy.
- Ensure that Startup type is set to Manual.
- Click OK.
Check that the Microsoft Software Shadow Copy Provider service is enabled
To check that the Microsoft Software Shadow Copy Provider service is enabled:
- Click Start, click Administrative Tools, and then click Services.
- In the results pane, double-click Microsoft Software Shadow Copy Provider.
- Ensure that Startup type is set to Manual.
- Click OK.
Make sure that third-party installed VSS providers are operating properly
To make sure that third-party installed VSS providers are operating properly:
- Open an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- Type diskshadow at the command prompt, and then press Enter.
- Type list providers, and then press Enter.
- If a provider is missing from the list of registered providers, try reinstalling it.
- For each provider in the list, use the DiskShadow tool’s add and create commands to create a shadow copy of the volume for which the provider is responsible. If a provider is unable to create a shadow copy, contact the provider vendor if it is not Microsoft. If a Microsoft provider is unable to create the shadow copy, contact Microsoft Customer Service and Support. For more information, see http://go.microsoft.com/fwlink/?LinkId=102491. You should provide the entire event log message as it appears in the Event Viewer.
For more information about the DiskShadow tool, including usage examples, see http://go.microsoft.com/fwlink/?LinkID=117722.
Verify
To verify that the Volume Shadow Copy Service (VSS) is operating correctly, retry the previous VSS operation.
Related Management Information
Volume Shadow Copy Service Operations
Related:
Event ID 774 — System State Recovery
Event ID 774 — System State Recovery
Updated: January 27, 2011
Applies To: Windows Server 2008
You can use the wbadmin start systemstaterecovery command to recover the system state for a computer.
Event Details
| Product: | Windows Operating System |
| ID: | 774 |
| Source: | Microsoft-Windows-Backup |
| Version: | 6.0 |
| Symbolic Name: | ADMIN_SYSTEM_STATE_RESTORE_GENERIC_FAILURE_EVENT |
| Message: | The System State Restore started at ‘%1’ failed with errors. Error reported ‘%2′(%3). Please rerun recovery once the issue is resolved. |
Resolve
Review event details for solutions for failed recovery
If the system state recovery fails, review the details for the applicable events to find out why the recovery operation failed. Then re-run the recovery.
To do this, follow these general steps:
- Find the applicable events in Event Viewer, and then review the details for those events to find out why the recovery operation failed. For more information, see “Review event details in Event Viewer.”
- Confirm that the location to perform the recovery to is online.
- After resolving any errors that you find in performing the steps above, re-run another application recovery. Fore more information, see “Recover the system state 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 an application recovery in Event Viewer:
- Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
- In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
- In the right pane, click the Details tab, and then click XML View.
- Click an event in the list.
- Review <Data Name=”WritersInfo”> to see the error code (XML Node: HResult) and detailed error code (XML Node: DetailedHResult), along with other details about the application component whose recovery failed. If HRest corresponds to a Volume Shadow Copy Service (VSS) error, then review the VSS event logs to find more information on the error and how to resolve it.
- Review <Data Name=”RestoreSuccessLogPath”>. If NoOfFilesFailed is greater than zero (>0), then review the failed file log list referred to in the event details to determine what files failed with what system errors.
- Review error messages for the error codes, as described in “Review error messages in the Windows Server Backup snap-in.”
Recover the system state using the command line
Note: If you are using BitLocker Drive Encryption to protect your server and you need to perform a system state recovery, make sure to reapply BitLocker Drive Encryption. This will not happen automatically—it must be enabled explicitly. For instructions, see the Windows BitLocker Drive Encryption Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=93107).
To recover the system state by using the command line:
- Open a command prompt with elevated privileges. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- At the prompt, type: wbadmin start systemstaterecovery. Use parameters, as needed. (To view the parameters and help for this command, at a command line, type: wbadmin start backup /?).
For example, to run a system state recovery of the backup from 04/30/2005 at 9:00 A.M. that is stored on the shared resource \\servername\share for server01, type: wbadmin start systemstaterecovery -version:04/30/2005-09:00 -backupTarget:\\servername\share -machine:server01.
Verify
To verify that a system state recovery was successful, after you perform the recovery, look for Event ID 242, which indicates that the recovery completed without errors.
To perform this procedure, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.
To verify that a system state recovery was successful:
- Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
- In the left pane, double-click Applications and Service Logs, double-click Microsoft, double-click Windows, double-click Backup, and then click Operational.
- In the Event ID column, look for event 242.
- For this event, confirm that the the value in the Source column is Backup.
Related Management Information
Related:
Event ID 755 — Backup Service Availability
Event ID 755 — Backup Service Availability
Updated: January 27, 2011
Applies To: Windows Server 2008 R2
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: | 755 |
| Source: | Microsoft-Windows-Backup |
| Version: | 6.1 |
| Symbolic Name: | BLB_SERVICE_COULDNOT_INSTALL_HANDLER_EVENT |
| Message: | Installing the handler for Block level backup engine service failed with error code ‘%1’. |
Resolve
Review Service Control Manager events in Event Viewer
Review Service Control Manager events for Windows Server Backup in Event Viewer in the Windows System event log.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To view the Windows Server Backup events in the Windows System event log:
- Open Event Viewer. Click Start, click Administrative Tools, and then click Event Viewer.
- In the left pane, expand Windows Logs, and then click System.
- To create a filtered view of just the Service Control Manager events, click Action, click Create Custom View, and in the Event sources drop-down list, select Service Control Manager Eventlog Provider, and then click OK.
- In Save Filter to Custom View, provide a name and description.
- In the left pane, expand Custom View, right-click the name of the custom view that you created, and then click Find.
- To find all the Service Control Manager Eventlog Provider events for Windows Server Backup, in Find what, type: Backup.
- Double-click the event, and then click Event Log Online Help for more information about how to fix the event.
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:
- Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- At the prompt, type: net start wbengine.
- 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:
- Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- At the prompt, type: wbadmin get versions -backuptarget:<backup destination drive letter>.
- 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:
- Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- 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.
- Verify that the command runs without errors.
Related Management Information