Hi Springs,


This may be a simple as Windows 2003 SP2 not being supported with NetWorker 7.1. You should have upgraded from this version some time ago and would suggest that you plan to upgrade to 7.4SP2 as soon as possible.


HtH

IKP

Thanks. I did updated the networker version.
Now the error is different.

SYSTEM STATE:\ Registry - Cannot save Registry key SYSTEM: 0x000005aa
SYSTEM STATE:\ Registry - Error saving
SYSTEM STATE:\ save: RPC error: RPC cannot encode arguments

Hi,


What version of NetWorker are the server and the Windows client running ?


IKP

Server Version 7.1.1
Windows Client version 7.4

Hi,


This may be your latest problem, I have always worked on the principal that the client version must never be newer than the server version.

Plan to upgrade the server version to 7.4SP2 and then the client to 7.4SP2.

Be warned about other clients and specifically storage nodes that you may have. There is a note in the 7.4SP2 documentation about backward compatibility or more specifically the lack of backward compatibility between Server version 7.4SP2 and older versions of Storage Nodes.

HtH

IKP

Thank you very much for you prompt response.
Any other Temporary fix for this issue bcz i do not want upgrade networker server now.

Nope, you need to upgrade the NetWorker server edition to a later / latest edition to enable the use of the later client.


IKP

Hi,

I had a problem or similar error in Windows 2003 Server.

Often the operating system applies patches or updates that can affect the condition(state) of the registry of the system.

I would prove the following steps:

1) If it is possible to reboot NetWorker Client with the issue "SYSTEM STATE backup failing".

2) Try Client-initiated-backup of only SYSTEM STATE.

[To use way debug to obtain more information of the error that producing]
save -D9 ...

3) Try Server-initiated-backup of NetWorker Client (only SYSTEM STATE).

[To use way debug to obtain more information of the error that producing]
savegrp -D9 ...

Perhaps this procedure has been done for you.

Tell us if that helped you

[EER]

I Ran command and got the following output.

:SYSTEM STATE:\ savegrp: suppressed 57 lines of output - check daemon.log for details.
:SYSTEM STATE:\ Registry - Cannot save Registry key SYSTEM: 0x00000000
:SYSTEM STATE:\ 08/22/08 06:45:17 nsrexec: errorfd rpc_read returns 139 bytes
:SYSTEM STATE:\ Registry - Error saving
:SYSTEM STATE:\ save: RPC error: RPC cannot encode arguments
:SYSTEM STATE:\ save: save of SYSTEM STATE:\ to lkus35.lagnr.chevrontexaco.net failed
:SYSTEM STATE:\ 08/22/08 06:45:24 nsrexec: errorfd rpc_read returns 1 bytes
:SYSTEM STATE:\ 08/22/08 06:45:24 nsrexec: errorfd NUL handshake
:SYSTEM STATE:\ 08/22/08 06:45:24 nsrexec: nleft 0 errorfd -1: (EOF)
:SYSTEM STATE:\ 08/22/08 06:45:24 nsrexec: out with nleft 0 errorfd -1, rem -1, rval 0

Can you please look at this and see what is causing.
Just checking in the power link and found some information about this
Run NSRIM -x and nsrck -L6 client name to cross check index resolve this issue Does it mean that media database inconsisten?

Thanks.

First of all, you need to make sure the ntbackup is able to successfully backup the SYSTEM STATE. If the OS is unable to backup SYSTEM STATE, then NetWorker is going to fail.

If the ntbackup of SYSTEM STATE succeeds, we probably have either a permissions issue or a NetWorker issue, and if Networker is the problem then upgrading will be the best solution as NetWorker 7.1.1 is already out of support. If you don¿t want to move to NetWorker 7.4.2 you might consider upgrading to the latest version of the NetWorker 7.1.x branch which is NetWorker 7.1.4 (it will have almost every fix made for this NetWorker branch.

You can also try a backup of the SYSTEM STATE from the NetWorker user GUI after logged in as the Domain Administrator account. If this works then the problem will be probably an authentication issue (by default NetWorker uses SYSTEM account to run scheduled backups unless specified otherwise in the ¿remote user¿ field or if the user that starts the NetWorker Remote Exec service on the client was modified.

If the manual backup (client initiated backup) fails, there is no need to try the server initiated backup as it will fail as well.