NetBackup configuration and certificate files do not persist after the container-based NetBackup appliance restarts
The NetBackup configuration files like hadoop.conf or hbase.conf or SSL certificate and CRL paths do not persist after the container-based NetBackup Appliance restarts for any reason. This issue is applicable where container-based NetBackup Appliance is used as a backup host to protect the Hadoop or HBase workload.
Reason:
In the NetBackup Appliance environments the files that are available in the docker host's persistent location are retained after restart operation. The hadoop.conf and hbase.conf files are custom configuration files and are not listed in the persistent location.
The configuration files are used for defining values like HA (high availability) nodes during a failover and number of threads for backup. If these files get deleted, backups use the default values for both HA and number of threads that are Primary Name Node and 4 respectively. Backup fails only if the primary node goes down in such a case as plug-in fails to find secondary server.
If the SSL certificates and CRL path files are stored at a location that is not persistent the appliance restart, the backups and restore operations fail.
Workaround:
If custom configuration files for Hadoop and HBase get deleted after a restart, you can manually create the files at the following location:
Hadoop:
/usr/openv/netbackup/hadoop.confHBase:
/usr/openv/netbackup/hbase.conf
You can store the CA certificate that has signed the Hadoop or HBase SSL certificate and CRL at the following location:
/usr/openv/var/global/