Networker 9.1 Windows Roles and Features failing

[pantelimon_alex]

Hello!

We recently installed a new Networker 9.1 Backup server and we got the next problem:

Windows Roles and features fail. After the automatically rerun backup is performed and successfully completed.

Client Specs:

Virtual Machine

Windows Server 2012 R2 "Not Cluster"

Agent 9.1.0.3

Logs

129292:save: Successfully established Client direct save session for save-set ID '1795000069' (CLIENT:WINDOWS ROLES AND FEATURES:\) with Data Domain volume 'DD'.

save: WMI Writer - ERROR: Failed to save xml file =  C:\Program Files\EMC NetWorker\nsr\tmp\WMI Writer.xml

90110:save: save of 'WINDOWS ROLES AND FEATURES:\' to server 'Backup Server' failed: The system cannot find the file specified. (Win32 error 0x2)

99123:save: Handling an abort while processing Windows backup.

ASR Backup: aborting VSS walker save because Quit flag is set.

90123:save: VSS save walkers: the backup of save set 'WINDOWS ROLES AND FEATURES:\' failed.

90123:save: VSS save walkers: the backup of save set 'WINDOWS ROLES AND FEATURES:\' failed.

86024:save: Error occured while saving disaster recovery save sets.

100129:save: Unable to update job with id '0' with name value 'pseudo_saveset': Invalid or NULL session channel

Does anyone had this problem?

[ble1]

Is this error on backup server itself or do you get it on clients?  If clients, are they also running 9.1.x?  I tested it with 9.1.0.4 and there it worked fine for me.

[pantelimon_alex]

I got this error when i try to backup one client.

In this moment we have two windows clients with 9.1.0.3. One is working ok and the other one have this error

[ble1]

Out of curiousity, if you use parallelism=1 for that client, do you still see the error?

[AdiYogi]

same problem here :-), working with support, will keep this forum posted

are rerun sometimes fixes the issue

I am not sure of significance of the pseudo saveset

[bingo.1]

This seems to be pretty close related to an issue we had when we installed NW 9.1 a while ago:

  - NW is backing up the client

  - The backup takes longer than 1 hr

  - NW will issue a timeout and retry

  - However the second attempt will also be aborted after 1 hr

After exactly 2 hrs the backup will fail.

As a consequence this pseudo save set will never have the change to be backed up.

There are 3 potential solutions:

  - Ensure that no save set will run longer than 1 hr 😉

  - Set the client's inactivity timeout to a reasonable high value or set it to 0

  - Update your client SW to NW 9.x

[Castromotorbox]

Hello all,

Thanks to bingo,i was able to solve this issue by removing the timeout on the action.

Cheers