VSS and Networker services

Hi bingo

I have just receieved this error from networker logs

82720:save: Disaster Recovery backup is enabling hard link and 8.3 shortname set
tings.
77777:save: Added writer Registry Writer to disaster recover backup.
77777:save: Added writer Task Scheduler Writer to disaster recover backup.
77777:save: Added writer VSS Metadata Store Writer to disaster recover backup.
77777:save: Added writer Performance Counters Writer to disaster recover backup.

77777:save: Added writer System Writer to disaster recover backup.
77777:save: Added writer ASR Writer to disaster recover backup.
77777:save: Added writer IIS Config Writer to disaster recover backup.
77777:save: Added writer WMI Writer to disaster recover backup.
77777:save: Added writer BITS Writer to disaster recover backup.
77777:save: Added writer COM+ REGDB Writer to disaster recover backup.
5386:save: VSS failed to take the snapshot.
VSS Provider or hardware error. The provider logged the error in the event log.
80517:save: Snapshot attempt number 2 of 3 will occur in 10 minutes.
77775:save: Processing completed for disaster recover backup.
80520:save: ASR Backup..Critical error creating snapshot of ASR critical volumes
and cannot continue.
83449:save: Error occured while saving critical volumes.

You need to repair your VSS system.

For WIndows 2003 use this routine:

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       This command may fail if the library is not installed

net stop cryptsvc

net start cryptsvc

net stop nsrexecd

net start nsrexecd

For Windows 2008 and up use this procedure:

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

Depending on the NW version, do not forget to also start the PowerSnap daemon:    net start nsrpsd

Our Networker server and client are on below version

NetWorker 7.6.3.2.Build.860 Power Edition/104

We have already checked this .....

Writer name: 'IIS Config Writer'

   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

   Writer Instance Id: {fcbabae7-c75b-45d9-86a3-c677ded10158}

   State: [7] Failed

   Last error: Timed out

Writer name: 'WMI Writer'

   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Writer Instance Id: {21a8b158-5f24-4cea-9c58-1a03ae4112c9}

   State: [7] Failed

   Last error: Timed out

Writer name: 'System Writer'

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

   Writer Instance Id: {03f96159-0767-483d-abbd-094cbd051c76}

   State: [7] Failed

   Last error: Timed out

We have already do stop and start of this services . After doing this stop and start the services are stable .

But when we start the backup this services goes into failed status

Thanks & Regards

Karan Ghadge

Check your  VSS writers again. a reboot usually resolves these kind of errors. What version is your client and NetWorker server ?

Ramdas wrote: We need to have some specific reason for rebooting it is production server

SYSTEM write failure and lack of backup is quite specific   Try also to do backup with parallelism set to 1 for the client.  You didn't say which OS was that (which Windows version).

It is Windows NT Server on Intel

This means there is some issue on the OS that is causing the VSS writers to fail. Try rebooting the affected server and retry backup.

Not, it's not.. what you are doing is reading what is says in OS version field of client... what you should do is connect to host and check OS version.  Be aware that, for example, Windows 2000 should 7.5SP3 at max... and since you have 7.6.3 I suspect you have something higher.

We need to have some specific reason for rebooting it is production server