我的环境有A和B两台机器，操作系统是2008r2企业版，做oracle+failsave的集群。B机上安装有BackupEXEC（以下简称BE）服务器端，A机只有BE agent。
问题是：集群上挂载2个应用，一个是APP应用，另外一个是DB应用。如果DB应用，挂载在哪一台机器上，那么通过BE备份那台机器的系统状态就会失败，失败的原因为大部分的writers超时。使用windows server backup备份是没有问题的，不会引起writers超时问题。但是由于需要写入到磁带机，WSB不支持磁带机，所以想解决这个问题。
根据BE工程师近1个月的协助，将问题锁定在了系统上，但由于缺少解决的思路，所以特来请教各位专家，提供一些线索。
根据BE工程师反馈的信息，BE系统备份时的日志显示：
=================================================
[3372] 2013-10-29T17:17:29.945 [fsys\shadow] - Informational: deleted temporary ESE snapshot utility path 'C:\Backup Exec AOFO Store\ESEUtils'
[3372] 2013-10-29T17:17:29.945 [fsys\shadow] - Informational: deleted temporary ESE snapshot utility path 'D:\Backup Exec AOFO Store\ESEUtils'
[3372] 2013-10-29T17:17:29.945 [fsys\shadow] - Informational: deleted temporary ESE snapshot utility path '\\?\VOLUME{4D22134B-1141-11E3-B139-806E6F6E6963}\Backup Exec AOFO Store\ESEUtils'
[3372] 2013-10-29T17:17:30.194 [fsys\shadow] - Status VSS_E_WRITERERROR_TIMEOUT (0x800423F2) State 9 getting Writer System Writer ID {E8132975-6F93-4464-A53E-1050253AE220} Instance ID {5D96DA78-6F82-42B3-B43C-1A86737C9002}
status in SHADOW::GetWriterStatus
[3372] 2013-10-29T17:17:30.194 [fsys\shadow] - Status VSS_E_WRITERERROR_TIMEOUT (0x800423F2) State 9 getting Writer ASR Writer ID {BE000CBE-11FE-4426-9C58-531AA6355FC4} Instance ID {E4E2BD37-BEFF-4DBB-B5D6-9C9AB8454005}
status in SHADOW::GetWriterStatus
[3372] 2013-10-29T17:17:30.194 [fsys\shadow] - Informational: Status VSS_E_WRITERERROR_TIMEOUT (0x800423F2) State 9 getting Writer Shadow Copy Optimization Writer ID {4DC3BDD4-AB48-4D07-ADB0-3BEE2926FD7F}
Instance ID {466F7DD9-2124-4733-BCD3-E5D5125A27FC} status in SHADOW::GetWriterStatus
[3372] 2013-10-29T17:17:30.194 [fsys\shadow] - Status VSS_E_WRITERERROR_TIMEOUT (0x800423F2) State 9 getting Writer Registry Writer ID {AFBAB4A2-367D-4D15-A586-71DBB18F8485} Instance ID {8C4B62B5-35ED-4736-A764-5C6F8443FC76}
status in SHADOW::GetWriterStatus
[3372] 2013-10-29T17:17:30.194 [fsys\shadow] - Status VSS_E_WRITERERROR_TIMEOUT (0x800423F2) State 9 getting Writer COM+ REGDB Writer ID {542DA469-D3E1-473C-9F4F-7847F01FC64F} Instance ID {21132AE6-E361-4B8A-AD51-FAD8E69ED0E5}
status in SHADOW::GetWriterStatus
[3372] 2013-10-29T17:17:30.194 [fsys\shadow] - Status VSS_E_WRITERERROR_TIMEOUT (0x800423F2) State 9 getting Writer IIS Config Writer ID {2A40FD15-DFCA-4AA8-A654-1F8C654603F6} Instance ID {181C2C15-AC9D-4ABB-928B-B1BF57C3EE16}
status in SHADOW::GetWriterStatus
[3372] 2013-10-29T17:17:30.194 [fsys\shadow] - Status VSS_E_WRITERERROR_TIMEOUT (0x800423F2) State 9 getting Writer Cluster Database ID {41E12264-35D8-479B-8E5C-9B23D1DAD37E} Instance ID {AA66D7FE-1EF4-4BCB-A5EA-3CC114B8680B}
status in SHADOW::GetWriterStatus
[3372] 2013-10-29T17:17:30.194 [fsys\shadow] - Status VSS_E_WRITERERROR_TIMEOUT (0x800423F2) State 9 getting Writer WMI Writer ID {A6AD56C2-B509-4E6C-BB19-49D8F43532F0} Instance ID {FA48DB37-2D0B-469E-9DC8-29CE5E1665B7}
status in SHADOW::GetWriterStatus
[3372] 2013-10-29T17:17:30.194 [fsys\shadow] - Status FS_WRITER_STATUS_FAILURE (0xE000FED1) returned getting Writer status during SNAPSHOT_NOTIFICATION::PostSnapshot
[3372] 2013-10-29T17:17:30.194 [besc] - SnapshotBackupEngine - SNAPSHOT_NOTIFICATION::PostSnapshot failed with fstatus: 0xe000fed1
[3372] 2013-10-29T17:17:30.194 [besc] - Error SnapshotBackupEngine::snap_file_systems failed.
====================================================
当08系统准备好要备份的文件副本后，几个writers就直接TIMEOUT了，但没有办法看出系统出了什么问题导致了TIMEOUT。所以能不能有什么办法或工具，可以找出在这个时间点，系统的这几个WRITERS为什么会TIMEOUT
出现问题后，系统日志里面没有错误。只有一条1544的警告。而这条警告，在用WSB备份的时候，也会出现，但是WSB备份系统状态并没有失败。所以我们认为1544的警告不是引发错误的原因。同时，根据BE工程师介绍，BE工具并不能直接抓取备份副本，是需要通过Microsoft Software Shadow Copy provider 来抓取的，所以理论上是WSB一样的方法，只是界面不同。
另外附带1544的警告内容：
来源：FailoverClustering
ID：1544
内容：群集配置数据的备份操作已取消。群集卷影复制服务(VSS)写入程序接收到中止请求。
