This post is more than 5 years old
3 Posts
1
1949
October 27th, 2015 09:00
DISASTER_RECOVERY Backup failures
We have experiencing DISASTER_RECOVERY backup failures Kindly advise.
Error:
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.
No Events found!
MoinMansuri
2 Intern
•
147 Posts
2
October 28th, 2015 07:00
Hi,
If you using below or equal to 8.0 Networker version. You should upgrade Networker version up to 8.1.1.9.
DR save set issue will resolved......This solution worked in my environment.
bingo.1
2.4K Posts
0
October 27th, 2015 11:00
For Windows 2003, login on the client and execute:
cd /d %windir%\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll (may fail if the program is not installed)
then
net stop cryptsvc
net start cryptsvc
net stop nsrexecd
net start nsrexecd
#########################
For Windows 2008/2012, login on the client and execute:
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
WLYeung
25 Posts
0
October 27th, 2015 12:00
What's the version of NW and OS?
crazyrov
4 Operator
•
1.3K Posts
0
October 28th, 2015 01:00
Just restarting the Cryptographic service should resolve this.
net stop cryptsvc
net start cryptsvc
net stop nsrexecd
net start nsrexecd
Vakil
1 Rookie
•
35 Posts
0
October 28th, 2015 04:00
What NetWorker version and OS you are using.
DISASTER_RECOVERY:\ fails when child save sets run > 24 hours, which means if the child save set runs for more than 24 hours, it fails the DISASTER_RECOVERY:\ .
Could you kindly paste the error message here.
bingo.1
2.4K Posts
0
October 28th, 2015 04:00
Hi Vakil,
we recently ran into this issue ourselves (NW 8.2.1).
Right now there is only one solution:
- move the appropriate client into a separate group
- specify the savegrp parallelism =1"
MoinMansuri
2 Intern
•
147 Posts
0
October 28th, 2015 07:00
Hi,
Which Networker version you are using ?
Moin
PPandit1
3 Posts
0
October 28th, 2015 07:00
Hi,
We are using 8.0.
PPandit1
3 Posts
0
October 28th, 2015 12:00
Hi...Thank you very much ..its really works.
bingo.1
2.4K Posts
0
October 28th, 2015 13:00
Just to clarify that - It is a likely better solution to update the software to the latest version ... if possible.
However, VSS is a Microsoft method which NW uses. So a newer NW version does not necessarily help - nor will it ensure that a VSS error will not occur in the future.
Readers should very carefully read your statement and remember what you mentioned correctly "This solution worked in my environment."
MoinMansuri
2 Intern
•
147 Posts
1
October 30th, 2015 08:00
Bingo,
You are correct, it totally depends on Microsoft. May be in future this issue will occur again.
In here my case.....After Microsoft patched severs this issue were occurred on Networker version 8.0 and OS 2008 R2. Then we have upgraded some servers to 8.1.1.9 and it worked successfully.
So after this workaround we have upgraded 8.1.1.9 on all 200 impacted servers and we observed all upgraded servers’s VSS backups got completed successfully and also backup successful ratio increased.
Thank
Moin