Event ID 49 — Backup Operations

Event ID 49 — Backup Operations

Updated: January 27, 2011

Applies To: Windows Server 2008

You can use the Windows Server Backup snap-in or the wbadmin command to create and manage backups to protect your operating system, volumes, files, and application data. Backups can be saved to single or multiple disks, DVDs, removable media, or remote shared folders. They can also be scheduled to run automatically or manually.

However, system state backup is only available for the command line and is not available in the Windows Server Backup snap-in user interface. Also, you cannot configure a scheduled backup to create system state backups—but you can script the wbadmin start systemstatebackup command to run backups on a schedule.

In addition, you can use the Local Group Policy Editor snap-in (Gpedit.msc) to allow or disallow certain types of backups or backup locations. Policy settings for Windows Server Backup are located at: Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Backup\Server.

Event Details

Product: Windows Operating System
ID: 49
Source: Microsoft-Windows-Backup
Version: 6.0
Symbolic Name: NO_BACKUP_TARGET_AVAILABLE_EVENT
Message: Backup failed as no target could be found.

Resolve
Confirm that backup storage location is online

Make sure that the backup storage locations are available and then re-run the backup. If between the time the backup starts and ends, Event ID 49 is not logged, then the backup was successful.

To do this, follow these general steps:

  1. If the backup that failed was a scheduled backup, use wbadmin enable backup to determine what disk was used.
  2. Use Disk Management to determine that the disk to be used for storing the backup is online.
  3. Re-run the backup. If the backup that failed was a scheduled backup, see “Create and run a scheduled backup.” If the backup that failed was a one-time backup, see “Create a one-time backup.”
  4. Look for Event ID 49 in Event Viewer. For more information, see “Confirm that a backup completed with no errors.”

To create a scheduled backup, you must have membership in Administrators, or you must have been delegated the appropriate authority. To perform a one-time backup or work with events, you must have membership in Backup Operators or Administrators, or you must have been delegated the appropriate authority.

Create and run a scheduled backup

Note:  This procedures describes how to reconfigure and run a scheduled backup. Alternatively, you can use wbadmin start backup with no parameters. This will run a backup using the settings for the scheduled backup.

Make sure that at least one of the backup storage disks is online.

To configure a scheduled backup:

  1. Open an elevated Command Prompt window. Click Start, right-click Command Prompt, and then click Run as administrator.
  2. At the prompt, type: wbadmin enable 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:

    • Schedule backups of hard disk drives e:, d:\mountpoint, and \\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\
    • Save the files to the disk DiskID
    • Run the backups daily at 9:00 A.M. and 6:00 P.M.

    Type: wbadmin enable backup -addtarget:<DiskID> -schedule:09:00,18:00 -include:e:,d:\mountpoint,\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\.

Note: Reconfiguring a scheduled backup will reformat the backup storage disk and any old backups will be lost.

Create a one-time backup

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 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 49.
  4. If this event does not appear by the time the backup operation completes, then the backup was successful.

Verify

To verify that backup operations are running, or will run, successfully, you should do one or more of the following, as needed:

  • For any backup operations that you have run, look for Event ID 4, which indicates that the operation completed successfully with no errors.
  • Verify that no other backup or recovery operations are running so that you can start an operation.
  • Verify that you have enabled a scheduled backup, and is configured correctly.
  • Verify that the location where you plan to store your backups is available and online.

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

Verify the 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 value in the Source column is Backup.

Verify another operation is not running

To verify that another backup or recovery operation is not running:

  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 status.
  3. If the command output indicates that no operation is running, then you can start a backup.

Verify scheduled backup is enabled

To verify that a scheduled backup is enabled:

  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 enable backup.
  3. If the command output shows a schedule, then a scheduled backup is enabled.
  4. Confirm that the schedule contains the correct parameters.

Verify storage location is online

To verify that a disk used to store backups is online:

  1. For the computer that contains the storage disk, open Disk Management. Click Start, click Run, and then type: diskmgmt.msc.
  2. Click View, click Top, and then click Disk List.
  3. For the disk that contains the volume that you will use to store backups, confirm that the value in the Status column is Online.

Related Management Information

Backup Operations

File Services

Related:

NLB Cluster %2 %1: Cluster mode control resumed. %3 %4

Details
Product: Windows Operating System
Event ID: 49
Source: WLBS
Version: 5.2
Symbolic Name: MSG_INFO_RESUMED
Message: NLB Cluster %2 %1: Cluster mode control resumed. %3 %4
   
Explanation

This event is logged to inform you that, in response to a user-initiated action, cluster operations have resumed.

   
User Action

No user action is required. For more information about the resume command, see Network Load Balancing in Help and Support.

Related:

This sender/recipient does not have a CCMAIL e-mail address: {name}

Details
Product: Exchange
Event ID: 49
Source: MSExchangeCCMC
Version: 6.0
Component: Connector for Lotus cc:Mail
Symbolic Name: MSG_TOCC_BAD_PROXY
Message: This sender/recipient does not have a CCMAIL e-mail address: {name}
   
Explanation
A sender or recipient requires an e-mail address when sending an Exchange message to a Lotus cc:Mail destination. Although the connector can usually generate a Lotus cc:Mail address, a Lotus cc:Mail address or an SMTP address is required.
   
User Action
Using the E-mail Addresses property page, provide the sender or recipient with a CCMAIL address. If this problem applies to many recipients, review the recipient policies in place.

Related:

Not used An AARP packet was not completely available in the lookahead data from NDIS on adapter “%2”.

Details
Product: Windows Operating System
Event ID: 49
Source: AppleTalk
Version: 5.0
Component: Services for Macintosh
Symbolic Name: EVENT_ATALK_AARPPACKET
Message: Not used An AARP packet was not completely available in the lookahead data from NDIS on adapter “%2”.
   
Explanation

The adapter is not working properly. The AppleTalk Address Resolution Protocol might not be able to communicate with some computers.

   
User Action

Check the Event Log in Event Viewer for messages related to this one. Try a different adapter if the specified adapter cannot communicate with a computer on the network and you see this message frequently.

Related:

The WebReady Document Viewing worker process cannot be found. To correct this problem, reinstall Outlook Web Access.

Details
Product: Exchange
Event ID: 49
Source: MSExchange OWA
Version: 8.0
Symbolic Name: TranscodingWorkerApplicationNotFound
Message: The WebReady Document Viewing worker process cannot be found. To correct this problem, reinstall Outlook Web Access.
   
Explanation

This Error indicates that the WebReady Document Viewing service did not open an attachment as a Web page. WebReady Document Viewing lets users access file attachments in Microsoft® Office Outlook® Web Access. Users can access common file types such as Microsoft Word documents even if the application is not installed. The event may occur if one or more of the following conditions are true:

  • The value of HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{F7CC98B4-F6F5-489D-98EB-000689C721DE}\LocalServer32\(Default) is empty. Alternatively, the file referenced by this registry key is incorrect.

  • The TranscodingService.exe file is missing from the computer that is running the Client Access server role.

   
User Action

To resolve this error, follow one or more of these steps:

  • Verify that the correct value exists for the registry specified in the Explanation.

    • In Registry editor, under the registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{F7CC98B4-F6F5-489D-98EB-000689C721DE}\LocalServer32, double-click the registry key (Default).

    • In Value data, verify that the value specified is a path of the TranscodingService.exe file. The default location of the file and the registry key value is C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\bin\DocumentViewing\TranscodingService.exe.

  • Verify that the TranscodingService.exe file exists in the location that is specified in the registry. If it does not exist, copy that file from the \Setup\ServerRoles\ClientAccess\owa\bin\DocumentViewing folder on the Microsoft Exchange Server 2007 DVD, and then paste it to the Client Access server. The default location to replace the file on the client Access server is C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\bin\DocumentViewing.

  • Remove and then re-install the Client Access server role. For more information about how to modify server roles, see Removing and Modifying Exchange 2007.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: