When VCS is upgraded on a NetBackup Master Server, if the following issue presents when attempting to start VCS:

hastart
attempting to connect...
VCS ERROR V-16-1-10600 Cannot connect to VCS engine
attempting to connect....not Available; will retry
attemping to connect....retryingattempting to connect....connected
system message
---------------------------- ------------------------------
(Nodename1) ADMIN WAIT
problem with configuration file?
(Nodename2) ADMIN WAIT
problem with configuration file?

This can be generated due to a NetBackup issue.

A simple test is as follows:

sum /opt/VRTSvcs/bin/ScriptAgent

Compare this output against

sum /usr/openv/netbackup/bin/cluster/vcs/NetbackupAgent

If the checksum between these two differs, then copy the ScriptAgent over NetbackupAgent as follows:

mv /usr/openv/netbackup/bin/cluster/vcs/NetbackupAgent /usr/openv/netbackup/bin/cluster/vcs/NetbackupAgent.bak
cp /opt/VRTSvcs/bin/ScriptAgent /usr/openv/netbackup/bin/cluster/vcs/NetbackupAgent

Attempt to start VCS after this.

 

VCS Upgrade in NBU clustered Master causes VCS instability