NetBackup 8.x Windows upgrade fails with "Configuration script configureCerts failed" in the NetBackup installation log.

Problem

The NetBackup 8.0 Windows master server upgrade is sensitive to the CLIENT_NAME and top SERVER entry in the registry mismatching. In the case where the CLIENT_NAME is referencing the server shortname and the top server entry is referencing the Fully Qualified Domain Name (FQDN) the upgrade will fail to find the Tomcat credential during the execution of the script, configureCerts.bat.

• Example: E:\Program Files\Veritas\NetBackup\wmc\bin\install\configureCerts.bat

Error Message

The following error may be seen in the NetBackup install log, C:\ProgramData\Symantec\NetBackup\InstallLogs\NetBackup Install.<date>.<time>.htm:

02-08-2017,22:57:58 : Running command: "E:\Program Files\Veritas\NetBackup\wmc\bin\install\configureCerts.bat" -logFileName "C:\ProgramData\Symantec\NetBackup\InstallLogs\WMC_configureCerts_20170208_225758554.txt".
02-08-2017,22:57:58 : Waiting for command: configureCerts.bat
02-08-2017,22:57:59 : Command returned status 1.
02-08-2017,22:57:59 : Configuration script configureCerts failed
02-08-2017,22:57:59 : CustomAction Deferred_WebAdminConsoleOps returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
02-08-2017,22:57:59 : Action ended 22:57:59: InstallFinalize. Return value 3.
 

In the log file, WMC_configureCerts_20170208_225758554.txt, for the script which failed, the error is:

"FINDING CREDENTIALS FOR MACHINE nbumaster.nbutest.local"
C:\Program Files\Veritas\NetBackup\var\global\vxss\tomcatcreds\nbwebsvc\certstore\*-nbumaster.nbutest.local*
The system cannot find the file specified.
        0 file(s) copied.
 

Note: If experienced at NetBackup 8.1 or higher, installation logs and WMC configure certificate logs can be examined in the following path...
%ALLUSERSPROFILE%\Veritas\NetBackup\InstallLogs\

Cause

• Using the CLIENT_NAME and SERVER name as defined in the following registry configuration
  
   
• The CLIENT_NAME determines hostname used to create Tomcat credential, in this case nbumaster. Example:
  Directory of C:\Program Files\Veritas\NetBackup\var\global\vxss\tomcatcreds\nbwebsvc\certstore
02/08/2017  10:57 PM                 0 CertStore.lock
02/08/2017  10:57 PM             2,006 e8217dca-nbumaster!1556!nbatd!1556.0
02/08/2017  10:57 PM    <DIR>          keystore
02/08/2017  10:57 PM    <DIR>          trusted
 

• The top SERVER entry determines the hostname to search the credential location for the configureCerts.bat script.
  "FINDING CREDENTIALS FOR MACHINE nbumaster.nbutest.local"
C:\Program Files\Veritas\NetBackup\var\global\vxss\tomcatcreds\nbwebsvc\certstore\*-nbumaster.nbutest.local*
The system cannot find the file specified.
0 file(s) copied.

Solution

1. Make sure the CLIENT_NAME and top SERVER entry match in the output of the command bpgetconfig, or in the registry before the upgrade.
   • Windows: install_path\Veritas\NetBackup\bin\admincmd\bpgetconfig
   • Linux/Unix: /usr/openv/netbackup/bin/admincmd/bpgetconfig
 
2. The roll back will not remove the Tomcat credential created for the CLIENT_NAME hostname, hence it need to be renamed to match the top SERVER entry.
   • Example:
     Directory of C:\Program Files\Veritas\NetBackup\var\global\vxss\tomcatcreds\nbwebsvc\certstore
02/08/2017  10:57 PM                 0 CertStore.lock
02/08/2017  11:14 PM             2,006 e8217dca-nbumaster!1556!nbatd!1556.0       <= Credential created on subsequent installation retry.
     02/08/2017  10:57 PM             2,006 e8217dca-nbumaster.nbutest.local!1556!nbatd!1556.0       <= Manually Renamed credential
      
3. Then, rerun the installation.

Note : In case of clustered master server the CLIENT_NAME entry should be node name and SERVER entry should be cluster name.