Virtualization, Servers and Storage : UTORrecover - NetWorker Windows Client Backup – pseudo_saveset / Could not load file OSSR_Info.xml

Created by Misha Sekey on Dec 01, 2025

(blue star) Problem

  1. Typical symptoms include:

    • A backup job on the Windows client fails when attempting to process the pseudo_saveset. 

    • Example log entries: 

      181407:save: Step (1 of 5) for PID-22704: Save has been started on the client 'sepsrv1.utorcsi.utoronto.ca'.
174412:save: Step (2 of 5) for PID-22704: Running the backup on the client 'sepsrv1.utorcsi.utoronto.ca' for the save set 'pseudo_saveset'.
...
107204:save: 'Backup renamed directories' disabled, renamed directories will not be backed up
174908:save:Saving the backup data in the pool 'pool503'.
175019:save:Received the media management binding information on the host 'tabu3.bkup.utoronto.ca'.
174910:save:Connected to the nsrmmd process on the host 'tabu3.bkup.utoronto.ca'.
parse_ossr_info_file: Could not load file "C:\Program Files\EMC NetWorker\nsr\tmp\3344933b-39be-4713-ace7-6691c07984db\OSSR_Info.xml":[1] function not supported
80880:save: Failed to process OSSR_Info.xml
80885:save: Failed to create OSSR_opaque_props
90019:save: save of 'DISASTER_RECOVERY:\' to server 'tabu.bkup.utoronto.ca' failed.

  2. DISASTER RECOVERY saveset failing with: Could not load file C:\Program Files\EMC NetWorker\nsr\tmp\OSSR_Info.xml

(blue star) Cause

According to DELL that specific error is Client / Windows issue.

DELL’s Knowledge Base Article:

(blue star) Solution

Initially try the solution described in KB article 000462622 (Set the client parallelism to 1.)
If the issue remains, reboot the client and re-run backup, it should now work OK

References