Veritas NetBackup™ Flex Scale Installation and Configuration Guide

To verify if the license is valid:

1. Log in to one of the nodes using SSH and enter the support elevate command to access the root shell.
2. Identify the cluster node on which the NetBackup master server is online:

   hagrp -state | grep NBUMasterWorker | grep ONLINE

   For example:

   nbfs-01:~ # hagrp -state | grep NBUMasterWorker | grep ONLINE
   NBUMasterWorker             State          nbfs-04 |ONLINE|
   nbfs-01:~ #

3. Use SSH to log in to the node where the NetBackup master server is online and enter the support elevate command to access the root shell.
4. On the node where the NetBackup master server is online, run the following command to view the NetBackup license key information:

   /usr/bin/docker exec -i nb_master bash -c "/usr/openv/netbackup/bin/admincmd/bpminlicense -nb_ufid 20"

   For example:

   nbfs-04:~ # /usr/bin/docker exec -i nb_master bash -c "/usr/openv/netbackup/bin/admincmd/bpminlicense -nb_ufid 20"
   0x05000000;PRID=6 (NetBackup Enterprise Server);FID=20 (Base NetBackup);SERIAL=0;VALUE=2000;DEXPIRE=2022/11/05 01:00:00 0 (Not expired);
   UXDEXPIRE=1667635200 0 (Not expired);UKEY=KLNN-VEIK-SWJT-7MLX-P6P6-BDOS-L4LS-A7SS-AXPP-P36C;
   UKEY=KLNP-JR8T-YX76-4KFF-ZCRP-RNWO-4F4K-4V7G-GVEC-PO4T
   nbfs-04:~ # 

5. Check for the UXDEXPIRE keyword in the output. If the license is valid, the keyword is set to Not expired. If the license has expired, the keyword is set to Expired along with the expiration value. For example, the following snippet shows the keyword in the above sample output:

   UXDEXPIRE=1667635200 0 (Not expired)  

   To find the exact expiration timestamp, use the following command:

   /bin/date --d='@expiration-value'

   For example, in the above output the expiration-value is 1667635200

   nbfs-04:~ # /bin/date --d='@1667635200'
   Sat Nov  5 01:00:00 PDT 2022
   nbfs-04:~ #

   If the license has expired, contact Veritas Support to get the new license key.

To add a license:

1. Check the status of the dedupe_ctrl_ip resource using the hares -display dedup_ctrl_ip -attribute State command. The resource should be online on one of the cluster nodes. If the resource is not online, check the status of the dedupe_ctrl_ip1 resource using the same command.

   For example:

   nbfs-04:~ # hares -display dedup_ctrl_ip -attribute State
   #Resource      Attribute  System   Value
   dedup_ctrl_ip  State      nbfs-01  OFFLINE
   dedup_ctrl_ip  State      nbfs-02  OFFLINE
   dedup_ctrl_ip  State      nbfs-03  OFFLINE
   dedup_ctrl_ip  State      nbfs-04  ONLINE
   nbfs-04:~ #

   For example:

   nbfs-04:~ # hares -display dedup_ctrl_ip1 -attribute State
   #Resource       Attribute  System   Value
   dedup_ctrl_ip1  State      nbfs-01  OFFLINE
   dedup_ctrl_ip1  State      nbfs-02  OFFLINE
   dedup_ctrl_ip1  State      nbfs-03  OFFLINE
   dedup_ctrl_ip1  State      nbfs-04  ONLINE
   nbfs-04:~ #

2. Use the following command to find the IP address assigned to the resource.

   For example, if the dedup_ctrl_ip resource is online:

   nbfs-04:~ # hares -value dedup_ctrl_ip Address
   172.16.0.65
   nbfs-04:~ # 

   For example, if the dedup_ctrl_ip1 resource is online:

   nbfs-04:~ # hares -value dedup_ctrl_ip1 Address
   172.16.1.65
   nbfs-04:~ # 

3. Run the following commands. The controller-ip is the IP address that is assigned to the resource that is online: