This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

"Failed To Activate Trigger" error on AIX

Good Morning All,

Our UNIX Admin recently updated our core Netvault server, as well as several client plugins including two AIX boxes; for brevity, let's call the clients Box1 and Box2 which are supposed to be relatively identical.

 

Ever since the Netvault Server was upgraded, Box1 has been returning an error every time it tries to call the Netvault Trigger; however, Box2 has no problems calling the trigger in the same fashion.  To give a light background, these boxes hold a DB2 database and we have a script on the box that runs a native backup on the server and once complete, it calls the Netvault trigger which is supposed to launch the appropriate Netvault job that backs up the Backup image that db2 made and afetrwards, removes the image off the server.

Can someone point me in the right direction on possible logs to check out or things to try, as web search hasn't yielded very much at all regarding the trigger failure.

 

Error: Failed to activate trigger

Trigger Call:  /usr/netvault/bin/nvtrigger -server <netvault server name> <Backup Job Name>

Parents
  • I guess we can try running the trigger that works on client B on the problematic client which should confirm the problem is with that client.

    After the upgrade of the 2 clients can you confirm in the manage clients screen that the problematic client is indeed online etc. Do a check access on it to confirm that there is nothing blocking communication...when the job started when you ran the trigger on the backup server did it complete ok?
Reply
  • I guess we can try running the trigger that works on client B on the problematic client which should confirm the problem is with that client.

    After the upgrade of the 2 clients can you confirm in the manage clients screen that the problematic client is indeed online etc. Do a check access on it to confirm that there is nothing blocking communication...when the job started when you ran the trigger on the backup server did it complete ok?
Children
No Data