EMC Networker 客户端VSS SYSTEM FILESET 备份失败

最近在公司的备份服务器上发现有个服务器的备份老是失败(VSS SYSTEM FILESET 备份失败,其他的数据备份都正常), 服务器的操作系统是windows server 20…

最近在公司的备份服务器上发现有个服务器的备份老是失败(VSS SYSTEM FILESET 备份失败,其他的数据备份都正常), 服务器的操作系统是windows server 2003 R2 (客户端和服务器都是 2003 R2), 备份软件是EMC Networker 7.6.2 。重启了多次客户端服务器,问题依然依旧,一直搞不清楚是什么原因。。。起初以为是备份软件的问题,找了EMC的售后,做了各种各样的诊断,告诉我们不是软件的问题,应该是系统原因。。。

image

     在网上搜了半天,没有什么好的建议,只好自己来找原因了,首先,从错误看应该是VSS (Valume shadow copy ) 的问题,看看系统日志里有没有错误,查了半天好像没有什么错误。。。 晕了,怎么办?  有了,我们检查一下VSS工作是否正常:

进入到命令行 运行 : vssadmin list writer  查看一下所有的writer 是否正常,

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: ‘Task Scheduler Writer’
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: ‘VSS Metadata Store Writer’
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: ‘Performance Counters Writer’
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: ‘MSSearch Service Writer’
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {a76ca37c-9398-4373-b4bc-3e7798d0acfc}
   State: [1] Stable
   Last error: No error

Writer name: ‘IIS Metabase Writer’
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {42f3b756-2471-4760-b48b-a100fbfb980b}
   State: [1] Stable
   Last error: No error

Writer name: ‘ASR Writer’
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {2892b464-b63e-496b-929b-a5ddea3191f1}
   State: [1] Stable
   Last error: No error

Writer name: ‘BITS Writer’
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {49dbcb52-28a2-4b82-95e1-b4e12367bdc6}
   State: [1] Stable
   Last error: No error

Writer name: ‘WMI Writer’
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {0678adbc-3f98-44b3-b310-3ecf578da64c}
   State: [1] Stable
   Last error: No error

Writer name: ‘Registry Writer’
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {edff679c-d7ee-4f3c-a548-9cff491c9a99}
   State: [1] Stable
   Last error: No error

Writer name: ‘Shadow Copy Optimization Writer’
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {797c3062-49c9-4f47-908e-6bb7372ce1f7}
   State: [1] Stable
   Last error: No error

Writer name: ‘COM+ REGDB Writer’
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {a783582f-cef8-424d-815c-b83682e60498}
   State: [1] Stable
   Last error: No error

问题真的来了, 好像并没有发现‘system writer’ 这个实例,看了问题应该是出在这里了, 为了验证一下是不是这个原因,特地找了一台工作正常的机器查看一下:

C:\windows\system32>vssadmin list writers

vssadmin 1.1 – Volume Shadow Copy Service administrative command-line

(C) Copyright 2001-2005 Microsoft Corp.

Writer name: ‘Task Scheduler Writer’

   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

   State: [1] Stable

   Last error: No error

Writer name: ‘VSS Metadata Store Writer’

   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

   State: [1] Stable

   Last error: No error

Writer name: ‘Performance Counters Writer’

   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

   State: [1] Stable

   Last error: No error

Writer name: ‘System Writer’

   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

   Writer Instance Id: {c7dc00e8-4e88-4777-b336-c8a6f83faa93}

   State: [5] Waiting for completion

   Last error: No error

果真,其他的机器都有这个实例。看来只有修复好这个问题才能解决备份的问题,如何修复呢。呵呵, 有方法如下:

打开命令行依次运行如下命令:

Takeown /f %windir%\winsxs\temp\PendingRenames /a
icacls %windir%\winsxs\temp\PendingRenames /grant “NT AUTHORITY\SYSTEM:(RX)”
icacls %windir%\winsxs\temp\PendingRenames /grant “YourDomain\Domain Admins”:(RX)
icacls %windir%\winsxs\temp\PendingRenames /grant “YourDomain\Domain Users”:(RX)
icacls %windir%\winsxs\temp\PendingRenames /grant “NT Service\trustedinstaller:(F)”
icacls %windir%\winsxs\temp\PendingRenames /grant BUILTIN\Users:(RX)
Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant “NT AUTHORITY\SYSTEM:(RX)”
icacls %windir%\winsxs\filemaps\*.* /grant “NT Service\trustedinstaller:(F)”
icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)
net stop cryptsvc && net start cryptsvc
net stop vss && net start vss
net stop Winmgmt && net start Winmgmt

注意 上面命令行中的 YourDomain 是公司域名请注意更改。

运行完以上命令后重启机器

再次运行 vssadmin list writers  看看

‘system writer’ 出现了,呵呵。

运行一下备份, 成功了。错误消失了,呵呵

©著作权归作者所有:来自51CTO博客作者jet_xia的原创作品,如需转载,请注明出处,否则将追究法律责任https://blog.51cto.com/jetxia/1133914

作者: admin

为您推荐

发表评论

电子邮件地址不会被公开。

返回顶部