Hi,

Windows 2008 R2 operating system is supported by NetWorker starting from 7.6.2 version , so NetWorker 7.6.1 version is not supporting Windows 2K8 R2 , you have to upgrade your client version. I recommend updating to the latest version 7.6.4 and try again the backup after upgrading.

Waiting your updates,

Ahmed Bahaa

Additionally, After upgrading the NetWorker client version , please modify the client configuration by changing the save command field with :

save -a '"ignore-all-missing-system-files=yes"'

Thanks,

Ahmed Bahaa

We are going to try this fix and get back to you. Thank you for the help.

Just a quick question, so Windows 2008 R2 is not supported with networker 7.6.1 both as netwroker client and server? I am asking because my client has 7.6.1 on windows 2003 server and we are backing up 2008 R2 clients.

cbaughma, I will be waiting your updates.

Sridhar246, For NetWorker Server 7.6.1 on Windows 2003 it is supported, but for Windows 2008 R2 clients you have to have NetWorker 7.6.2 or later installed on the client machines to support this operating system. The backup server 7.6.1 on windows 2003 is compatible to backup 7.6.2 or later on Windows 2008 R2 clients , no problem in that.

Hope this helps,

Ahmed Bahaa

Try this out.

1.       Stop networker (make sure that nsrexecd is killed by double checking in the task manager)

2.       Stop VSS service if its running

3.       Restart WMI performance adapter service

4.       Restart com+ event system (and all other dependent services)

5.       Delete all the files under /nsr/tmp (not the folder, but the files inside it)

6.       Put vss to manual and start it

7.       start networker (make sure that nsrexecd is running by double checking in the task manager)

No need to reboot your machine.

Looks like Ahmed's save set fix worked. we will be updating our clients to 7.6.3.7 at some point in the future.

Thank you very much!

Hi Ahmed,

I have issue with VSS error too. I'm running windows 2008 R2 clients with NMM installed on it. I have no issue backing up File system using NMM group but getting error while backing up DISASTER RECOVERY:\ only in normal group. Below is the error message. I've tried both save and backup command

save -a '"ignore-all-missing-system-files=yes"' and NSR_IGNORE_MISSING_SYSTEM_FILES=yes

error message:

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
90110:save: save of 'VSS SYSTEM FILESET:\' to server 'xxxxxx' failed: No such file or directory
90123:save: VSS save walkers: the backup of save set 'VSS SYSTEM FILESET:\' failed.

90123:save: VSS save walkers: the backup of save set 'VSS SYSTEM FILESET:\' failed.

86024:save: Error occured while saving disaster recovery save sets.
:  Failed with error(s)

Any idea?

Hi Iman,

For DISASTER RECOVERY:\ saveset please remove the NSR_IGNORE_MISSING_SYSTEM_FILES=yes variable, use only save -a ´"ignore-all-missing-system-files=yes"´ backup command.

The error you are seeing I believe that is related to the system writer not being "present".

In most of the cases after a Windows update the system writer either needs to be re-registered or it lost the permissions, so please run the following command on the NMM client and check if the system writer is listed. If it is it has to be in status 1, stable.

vssadmin list writers.

Thank you.

Carlos.

Hi Carlos,

Yeap, I tried that as well. Using save -a ´"ignore-all-missing-system-files=yes"´ in backup command but still getting those errors. This is happening after we did the server patch last weekend and I have another 3 clients with the same issue as well. below is the result for vssadmin list writers. It looks good though.

C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-li
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

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: {d672b076-8a2e-430c-9568-9f4f8bd56ba3}
State: [1] Stable
Last error: No error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {4b8c6c1d-520a-4cc9-8321-d695a63d61f0}
State: [1] Stable
Last error: No error

Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {cc46379b-a882-4d28-8478-380787e4ad0d}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {4bbc2cb3-3de1-431d-a5f8-8ea4f4bf6d57}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {ffe7f93c-7b66-42fc-800e-ca29e9542178}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {c97b66e2-86fe-45c7-bcf6-8f69a1eabbdf}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {9b86c75d-2f62-4717-9e85-e4c5861c9bc4}
State: [1] Stable
Last error: No error

C:\>

Hi Iman,

I think that you have lost permissions to the System Writer, to correct that please run the following commands (reboot is required):

Open a command prompt using Run As Administrator and execute these the following commands individually:

Takeown /f %windir%\winsxs\temp\PendingRenames /a
icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(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)

After that please run the following command to restart the cryptographic services:

net stop cryptsvc

net start cryptsvc

Then re-run the backup again and observe the status of the backup. Waiting your updates.

Hope this helps,

Ahmed Bahaa

Still no luck Ahmed.. I've already executed all the steps above and reboot the server but still getting the same error..

Carlos,

I have a question here, if NMM is installed on this machine.

Will the following command you suggested work in this case.

use only save -a ´"ignore-all-missing-system-files=yes"´ backup command.

As NMM client uses nsrsnap_vss_save and not save program to run backups.

Please throw some light on this.

Hi Iman,

What are the events exists in the Application logs or System logs in the event viewer regarding the VSS ???

Ahmed Bahaa

Hi Ahmed,

The only VSS entry I can find in the Application logs is "The VSS service is shutting down due to idle timeout. "