This post is more than 5 years old
30 Posts
0
3218
VSS SYSTEM FILESET Always failed
Hi,
I have some troubles when trying to backup Windows Server hosts (2K8 mostly). I always have errors like this. VSS on server side in default configuration. Do I need to configure VSS (disk size for example) to backup system fileset and what is the main reason for these errors
Thank you very much for your time
avegrp: suppressed 2 lines of verbose output
System Writer - ERROR: Failed to save FileGroup files, writer = System Writer
System Writer - Error saving writer System Writer
System Writer - ERROR: Aborting backup of saveset VSS SYSTEM FILESET: because of the error with writer System Writer.
System Writer - Error saving
7162:save: save of VSS SYSTEM FILESET:\ to host.dmn.name failed
: Failed with error(s)
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
July 22nd, 2014 06:00
its only a client correct ? Is the change management that strict that you have to wait for another 2 months for a client package upgrade ?
crazyrov
4 Operator
4 Operator
•
1.3K Posts
1
July 21st, 2014 09:00
Hi Godz,
Upgrade to NetWorker 8.1.X which ever is the latest. Such errors should go away.
bingo.1
2.4K Posts
0
July 21st, 2014 09:00
This is most likely due to a problem with the appropriate VSS writer. These fail sometimes.
Please check with "vssadmin list writers".
To repair it on a Windows 2008 server, logon with admin accounts and run the following commands (/script):
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 nsrexecd
net start nsrexecd
net start nsrpsd <--- NW 8.1.+
Please check again with "vssadmin list writers". the problem should have been solved.
Then retry the backup.
Godz2
30 Posts
0
July 21st, 2014 23:00
Yep, probably this is the best way in our case. Moreover we are scheduled update. But we need to keep our savesets alive this time
Godz2
30 Posts
0
July 21st, 2014 23:00
Thank you very much.Will try today
Godz2
30 Posts
0
July 22nd, 2014 01:00
Tried vssadmin list writers. I dont see any errors, all of writers in Stable condition. Other commands will be executed later today.
The same conditions on other servers.
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: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {ac3c0233-e42e-432d-b4cc-ab9656de40b8}
State: [1] Stable
Last error: No error
Writer name: 'FSRM Writer'
Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
Writer Instance Id: {f5a3737b-d6c4-4253-829d-ae45d6b1ec44}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {aedd274c-0ab5-4692-a06b-e67c9c1feb46}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {d585e5f9-9a7d-49b7-a1aa-a3261f17101d}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {95624acb-b14a-4b8b-afa6-8c9c52979256}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {db56a792-186a-4faf-bec2-c9ef8251c70d}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {12ec7627-d9f0-4d74-8425-c05ddfc0a38d}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {4be344f0-7446-45e1-a082-cfde308615bd}
State: [1] Stable
Last error: No error
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
July 22nd, 2014 02:00
Are you still getting an error after upgrade ? id yes, please share the error here.
Godz2
30 Posts
0
July 22nd, 2014 03:00
No, we just planning to upgrade NW. Current version is 7.6.5.It will be completed in 2 months. Is it possible to fix VSS SYSTEM FILESET issue before update?
ble1
2 Intern
2 Intern
•
14.3K Posts
0
July 22nd, 2014 04:00
Do you have VSS patches installed for win2k8? Did you check event logs for time when error was logged?
Godz2
30 Posts
0
July 22nd, 2014 05:00
Servers are on remote site. Im waiting for EventLogs now. Do you have a list of patches to check?
ble1
2 Intern
2 Intern
•
14.3K Posts
0
July 22nd, 2014 05:00
Some of those I know about...
Godz2
30 Posts
0
July 22nd, 2014 06:00
Ok, now it's clear. So do I need to update client to last version and it should be ok?
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
July 22nd, 2014 06:00
Yep. You are correct !
Godz2
30 Posts
1
July 24th, 2014 04:00
Crazyrov, thank you very much!. Everything is OK after client update!! Thank you all for your help