In general, it is obvious how nsrpush works during an update: It will ...
  - copy the new software and some scripts to the client
  - deinstall the current software leaving the configuration behind
  - install the new version
  - update whatever is necessary (resource files)
  - finally start the client daemon and 
  - feedback the result

It looks that there was a problem in the final phase.

As far as i remember there is a nsrpush.raw file that you can check for 
details. Also, do not forget that running nsrpush from the command line can 
provide more info with added verbosity. 

Finally, let me suggest that you run the NetWorker Health Check Tool in 
preparation of the job - it recently helped me to solve SW inventory issues. 
Unfortunately, i have not updated the clients yet.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER