nbu备份操作系统报error core 69

Question

大侠们！帮忙看看！
bmros backup 日志：
OS Backup error
2011-4-26 1:04:27 - requesting resource bk-xian-nas-voly-os
2011-4-26 1:04:27 - requesting resource bk-xian.NBU_CLIENT.MAXJOBS.xa_trend_db_nbu
2011-4-26 1:04:27 - requesting resource bk-xian.NBU_POLICY.MAXJOBS.xa-trend-os
2011-4-26 1:04:27 - granted resource  bk-xian.NBU_CLIENT.MAXJOBS.xa_trend_db_nbu
2011-4-26 1:04:27 - granted resource  bk-xian.NBU_POLICY.MAXJOBS.xa-trend-os
2011-4-26 1:04:27 - granted resource  MediaID=@aaaagath=/voly/os;MediaServer=bk-xian
2011-4-26 1:04:27 - granted resource  bk-xian-nas-voly-os
2011-4-26 1:04:27 - estimated 0 kbytes needed
2011-4-26 1:04:27 - started process bpbrm (pid=27821)
2011-4-26 1:04:28 - connecting
2011-4-26 1:04:29 - connected; connect time: 0:00:00
2011-4-26 1:04:38 - begin writing
2011-4-26 1:39:38 - Warning bpbrm (pid=27821) from client xa_trend_db_nbu: WRN - can't open file: C:\WINDOWS\system32\config\AppEvent.Evt (WIN32 3: ???????????????? )
2011-4-26 1:40:08 - Warning bpbrm (pid=27821) from client xa_trend_db_nbu: WRN - can't open file: C:\WINDOWS\system32\config\SecEvent.Evt (WIN32 3: ???????????????? )
2011-4-26 1:40:38 - Warning bpbrm (pid=27821) from client xa_trend_db_nbu: WRN - can't open file: C:\WINDOWS\system32\config\SysEvent.Evt (WIN32 3: ???????????????? )
2011-4-26 1:48:32 - Error bpbrm (pid=27821) from client xa_trend_db_nbu: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification
2011-4-26 1:48:39 - Error bptm (pid=27835) system call failed - Connection reset by peer (at child.c.1296)
2011-4-26 1:48:39 - Error bptm (pid=27835) unable to perform read from client socket, connection may have been broken
2011-4-26 1:48:39 - Critical bpbrm (pid=27821) unexpected termination of client xa_trend_db_nbu
2011-4-26 1:48:40 - Error bpbrm (pid=27821) could not send server status message
2011-4-26 1:48:41 - end writing; write time: 0:44:03
network read failed  (42)

Answer 1

问题解决了，唉，是操作系统本身问题，在windows 2003打了个sp2补丁就没问题了！