运行Windows 2008 R2,有两个运行Windows 2008的虚拟机,虚拟文件放在D盘,使用WSB备份D盘文件到E盘时,出现如标题所示的错误,察看事件察看器出现如下错误:

日志名称:          Application
来源:            Microsoft-Windows-Backup
日期:            2011/7/19 14:53:47
事件 ID:         517
任务类别:          无
级别:            错误
关键字:           
用户:            SYSTEM
计算机:           HYPERV1
描述:
在“‎2011‎-‎07‎-‎19T06:23:42.451032700Z”上启动的备份操作失败,返回下列错误代码“2155348301”(更新已删除项目的备份时出错。)。请查看事件详细信息以获得解决方案,然后在解决问题后重新运行备份操作。

 

微软官方相关资料:

http://msdn.microsoft.com/zh-cn/cc734395(ws.10).aspx

 

Event ID 517 — Backup Operations

Updated: January 27, 2011

Applies To: Windows Server 2008

red

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

Resolve

Review event details for solutions for 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 details provided about 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 find in performing the steps above, re-run another backup. For more information, see "Perform a 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 clickOperational.
  3. In the right pane, click the Details tab, and then click XML View.
  4. Click an event in the list.
  5. Review <Data Name="VolumesInfo"> to see the error code (XML Node: HResult) and detailed error code (XML Node: DetailedHResult), along with other details about the volumes whose backup failed.
  6. 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 volume recovery, click the Errors tab, and view the text under Message.
Perform a 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 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 clickOperational.
  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.

 

 

最后解决的方法:

http://social.microsoft.com/Forums/fr-FR/windowsserversystemzhchs/thread/d0ca819f-8330-44a9-a3e7-6a2a45c8d21b

环境是Windows Server 2008 with SP2,使用一块USB的移动硬盘为C盘(OS与应用程序)和D盘(存放Hyper-V的磁盘文件)做备份,就用Windows自带的Windows Server Backup ,每天定时执行。

前日开始发现备份失败,日志信息是“卷影副本操作失败”,错误代码2155348129。

检查服务发现Volume Shadow Copy服务没有启动,于是设置为“自动”并启动了该服务。

再次运行WSB,仍然失败,这次是“Shared Protection Point ” 失败,错误代码2155348001。

现在启动WSB时,一直停留在“正在读取数据,请稍候。。。”

是哪里出了问题?

 

您好!

使用WSB备份,您是用命令行还是图形界面?保证该账户具有对备份目的地有相关权限。


是图形界面。

权限没问题,因为之前一直正常。

貌似是与Symantec Endpoint Protection有关,SEP同时对Symantec Backup Exec的Remote Agent也有干扰,卸载SEP后WSB正常。

今天又装上SEP,看看效果。。。。。。

这几天打过最新的补丁,会不会是某个新补丁干扰了WSB?

谢谢!