A server whose backup needs to be taken fails at the saveset - SYSTEM STATE:\ only (all other savesets are backing up successfully.)
Below is a sample error log that we are encountering :-
xxxxxx.net SYSTEM STATE:\ incr 1309223044 371 1 retry attempted Registry - Cannot save Registry key SOFTWARE: 0x000003f8 Registry - Error saving 39078:save: RPC error: Can't encode arguments 7162:save: save of SYSTEM STATE:\ to "Backup server name" failed. xxxxxx.net ---> is the server whose backup need to be taken "Backup server name"---> Backup server name
As suggested from EMC powerlink the hotfixes suggesed on it was applied and also rebooted server after it was applied. Still the backup fals.
Is there any other solutions to have a successful backupn of SYSTEM STATE:\ saveset ?
This is a Microsoft issue, which is frusterating at time.
There are two articles that EMC has for this issue. There is not clear answer, except a work around to reboot the affect machine (client) to clear the issue.
Something that may give you a clearer answer is to render the daemon.raw file on the client and see what error messages are being listed.
To render the file, do the following:
All on the client:
Browse to the nsr\logs directory
Copy and paste the daemon.raw file
Rename the file from copy of daemon.raw to another name - best practice: daemon.raw_date.raw
open command line
cd to the location of the daemon_date.raw file
run the nsr_render_log command:
nsr_render_log daemon_date.raw daemon_date.log
This will create a readable version of the contents of the daemon.raw file. You can open it with wordpad or notepad and look for errors to help you narrow down the cause of the issues.
Once you fins the issues, if you have any more questions, post here again with the error messages you found and we will see what we can do the help resolve this for you.
I think this is an OS issue rather than NetWorker, where some temporary registry entries don't get deleted, so my suggestions would be:
1.- Reboot the affected client (to force the deletion of those registry entries) and run a new backup.
If that doesn't solve the issue then check this Microsoft article: