To upgrade a Release 22.9 or later NFM-P auxiliary database cluster

Description

The following procedure is performed as part of a standalone or redundant system upgrade from Release 22.9 or later.

In a redundant NFM-P system upgrade, the standby components are upgraded while the primary components remain operational. The upgraded standby components then assume the primary role while the former primary components are upgraded.

If a redundant system includes a redundant auxiliary database, the network outage during a redundant system upgrade is limited to the initialization time of the upgraded former standby components.

If a redundant system includes a standalone auxiliary database, the network outage during a redundant system upgrade includes the auxiliary database upgrade duration.

Note: CPU frequency scaling must be set to “performance” in the BIOS of each auxiliary database station, or the auxiliary database upgrade fails. See the RHEL power management documentation for information about enabling the “performance” CPU frequency scaling governor on a station.

Setting CPU frequency scaling to “performance” effectively disables the function, so may result in greater energy consumption by a station.

Note: Enabling TLS on an auxiliary database is not supported during an upgrade.

Note: You require the following user privileges on each auxiliary database station:

Note: Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses.

Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands

Steps
Obtain software
 
1 

Download the following installation files to an empty local directory on a station that is reachable by each auxiliary database station in the cluster:

  • nspos-auxdb-R.r.p-rel.v.rpm

  • VerticaSw_PreInstall.sh

  • nspos-jre-R.r.p-rel.v.rpm

  • vertica-R.r.p-rel.tar

where

R.r.p is the NSP release identifier, in the form MAJOR.minor.patch

v is a version number

Back up database
 
2 
CAUTION 

CAUTION

Data Loss

If you specify a backup location on the database data partition, data loss or corruption may occur.

The auxiliary database backup location must be an absolute path on a partition other than the database data partition.

If you are upgrading a standalone auxiliary database, or the standby cluster in a redundant auxiliary database, back up the auxiliary database.

Note: The backup location requires 20% more space than the database data consumes.

Note: If the backup location is remote, a 1 Gb/s link to the location is required; if achievable, a higher-capacity link is recommended.

For auxiliary database backup information, see the NSP System Administrator Guide for the installed release.

Stop cluster
 
3 

Log in as the root user on an auxiliary database station in the cluster that is being upgraded.

4 

Open a console window.

5 

Enter the following:

# cd /opt/nsp/nfmp/auxdb/install/bin ↵

6 

Enter the following to stop the auxiliary database:

# ./auxdbAdmin.sh stop ↵

7 

Enter the following to display the auxiliary database status:

# ./auxdbAdmin.sh status ↵

Information like the following is displayed:

Database status

 Node       | Host          | State | Version | DB

------------+---------------+-------+---------+-------

 node_1 | internal_IP_1 | STATE | version | db_name

 node_2 | internal_IP_2 | STATE | version | db_name

.

.

.

 node_n | internal_IP_n | STATE | version | db_name

      Output captured in log_file

The cluster is stopped when each STATE entry reads DOWN.

8 

Repeat Step 7 periodically until the cluster is stopped.

Note: You must not proceed to the next step until the cluster is stopped.

Prepare all stations for upgrade
 
9 

Perform Step 11 to Step 28 on each auxiliary database station in the cluster that is being upgraded.

10 

Go to Step 29.

Prepare individual station for upgrade
 
11 

If the auxiliary database station is deployed in a VM created using an NSP RHEL OS disk image, perform To apply a RHEL update to an NSP image-based OS.

12 

Log into the auxiliary database station as the root user.

13 

Open a console window.

14 

Enter the following sequence of commands to stop the auxiliary database services:

# systemctl stop nfmp-auxdb.service ↵

# systemctl stop vertica_agent.service ↵

# systemctl stop verticad.service ↵

15 

Enter the following sequence of commands to disable the database services:

# systemctl disable nfmp-auxdb.service ↵

# systemctl disable nfmp-auxdbproxy.service ↵

# systemctl disable vertica_agent.service ↵

# systemctl disable verticad.service ↵

16 

Transfer the downloaded installation files to an empty directory on the station.

Note: In subsequent steps, the directory is called the software directory.

17 

Navigate to the software directory.

Note: Ensure that the directory contains only the installation files.

18 

Enter the following:

# chmod +x * ↵

19 

Enter the following:

# ./VerticaSw_PreInstall.sh ↵

Information like the following is displayed:

Logging Vertica pre install checks to log_file

INFO: About to remove proxy parameters set by a previous run of this script from /etc/profile.d/proxy.sh

INFO: Completed removing proxy parameters set by a previous run of this script from /etc/profile.d/proxy.sh

INFO: About to set proxy parameters in /etc/profile.d/proxy.sh...

INFO: Completed setting proxy parameters in /etc/profile.d/proxy.sh...

INFO: About to remove kernel parameters set by a previous run of this script from /etc/sysctl.conf

INFO: Completed removing kernel parameters set by a previous run of this script from /etc/sysctl.conf

INFO: About to set kernel parameters in /etc/sysctl.conf...

INFO: Completed setting kernel parameters in /etc/sysctl.conf...

INFO: About to change the current values of the kernel parameters

INFO: Completed changing the current values of the kernel parameters

INFO: About to remove ulimit parameters set by a previous run of this script from /etc/security/limits.conf

INFO: Completed removing ulimit parameters set by a previous run of this script from /etc/security/limits.conf

INFO: About to set ulimit parameters in /etc/security/limits.conf...

INFO: Completed setting ulimit parameters in /etc/security/limits.conf...

Checking Vertica DBA group samauxdb...

WARNING: Vertica DBA group with the specified name already exists locally.

Checking Vertica user samauxdb...

WARNING: Vertica user with the specified name already exists locally.

Changing ownership of the directory /opt/nsp/nfmp/auxdb/install to samauxdb:samauxdb.

Adding samauxdb to sudoers file.

Changing ownership of /opt/nsp/nfmp/auxdb files.

INFO: About to remove commands set by a previous run of this script from /etc/rc.d/rc.local

INFO: Completed removing commands set by a previous run of this script from /etc/rc.d/rc.local

INFO: About to add setting to /etc/rc.d/rc.local...

INFO: Completed adding setting to /etc/rc.d/rc.local...

20 

Enter the following to reboot the station:

# systemctl reboot ↵

The station reboots.

21 

When the reboot is complete, log in to the station as the root user.

22 

Open a console window.

23 

Enter the following:

# cd /opt/nsp/nfmp/auxdb/install/bin ↵

24 

Enter the following to display the auxiliary database status:

# ./auxdbAdmin.sh status ↵

Information like the following is displayed:

Database status

 Node       | Host          | State | Version | DB

------------+---------------+-------+---------+-------

 node_1 | internal_IP_1 | STATE | version | db_name

 node_2 | internal_IP_2 | STATE | version | db_name

.

.

.

 node_n | internal_IP_n | STATE | version | db_name

      Output captured in log_file

25 

if any STATE entry is not DOWN, perform the following steps.

  1. Enter the following to stop the auxiliary database:

    # ./auxdbAdmin.sh stop ↵

  2. Repeat Step 24 periodically until each STATE entry reads DOWN.

    Note: You must not proceed to the next step until each STATE entry reads DOWN.

26 

Navigate to the software directory.

27 

Enter the following:

# dnf install nspos-*.rpm ↵

The dnf utility resolves any package dependencies, and displays the following prompt for each package:

Total size: nn G

Installed size: nn G 

Is this ok [y/d/N]: 

28 

Enter y. The following and the installation status are displayed as each package is installed:

Downloading Packages:

Running transaction check

Transaction check succeeded.

Running transaction test

Transaction test succeeded.

Running transaction check

The package installation is complete when the following is displayed:

Complete!

Upgrade database
 
29 

Log in as the root user on an auxiliary database station in the cluster that is being upgraded.

30 

Open a console window.

31 

Enter the following:

# cd /opt/nsp/nfmp/auxdb/install/bin ↵

32 

Enter the following:

# ./auxdbAdmin.sh upgrade tar_file ↵

where tar_file is the absolute path and filename of the vertica-R.r.p-rel.tar file in the software directory

The following prompt is displayed:

Updating Vertica - Please perform a backup before proceeding with this option

Do you want to proceed (YES/NO)?

33 

Enter YES ↵.

The following prompt is displayed:

Please enter auxiliary database dba password [if you are doing initial setup for auxiliary database, press enter]:

34 

Enter the dba password.

The following prompt is displayed:

Please verify auxiliary database dba password:

35 

Enter the dba password again.

The upgrade begins, and operational messages are displayed.

The upgrade is complete when the following is displayed:

Database database_name started successfully

  Output captured in log_file

36 

Enter the following to display the auxiliary database status:

# ./auxdbAdmin.sh status ↵

Information like the following is displayed:

Database status

 Node       | Host          | State | Version | DB

------------+---------------+-------+---------+-------

 node_1 | internal_IP_1 | STATE | version | db_name

 node_2 | internal_IP_2 | STATE | version | db_name

.

.

.

 node_n | internal_IP_n | STATE | version | db_name

      Output captured in log_file

The cluster is running when each STATE entry reads UP.

37 

Repeat Step 36 periodically until the cluster is running.

Note: You must not proceed to the next step until the cluster is running.

Update database schema
 
38 

Update the NFM-P database schema.

Note: The schema update may take considerable time.

  1. Log in as the nsp user on the NFM-P main server.

  2. Open a console window.

  3. Enter the following:

    bash$ cd /opt/nsp/nfmp/server/nms/bin ↵

  4. Enter the following:

    bash$ ./nmsserver.bash upgradeAuxDbSchema ↵

    The following prompt is displayed:

    Auxiliary database clusters:

    1: IP_a,IP_b,IP_c

    2: IP_x,IP_y,IP_z

    Select auxiliary database to upgrade:

  5. Enter the number that corresponds to the cluster you are upgrading.

    The following messages and prompt are displayed:

    WARNING: About to upgrade samdb schema on the auxiliary database cluster [IP_a,IP_b,IP_c].

    It is recommended that a database backup is performed before proceeding.

    Type "YES" to continue

  6. Enter YES.

    The following prompt is displayed:

    Please enter the auxiliary database port [5433]:

  7. Enter the auxiliary database port number; press Enter to accept the default of 5433.

    The following prompt is displayed:

    Please enter the auxiliary database user password:

  8. Enter the required password.

    The following messages are displayed as the upgrade begins:

    INFO: Database upgrade can take a very long time on large databases.

    INFO: logs are stored under /opt/nsp/nfmp/server/nms/log/auxdb. Check the logs for progress.

    INFO: Node Name[v_samdb_node0001]->IP[IP_address]->Status[UP]

    INFO: About to perform upgrade

Synchronize auxiliary database password
 
39 

If the NFM-P is in a shared-mode NSP system, perform the following steps.

  1. Log on as the root user on the NSP cluster host.

  2. Open a console window.

  3. Enter the following:

    # cd /opt ↵

  4. Enter the following:

    # sftp root@deployer_IP ↵

    where deployer_IP is the NSP deployer host IP address

    The prompt changes to sftp>.

  5. Enter the following:

    sftp> cd /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/tools/database ↵

  6. Enter the following:

    sftp> get sync-auxdb-password.bash ↵

  7. Enter the following:

    sftp> quit ↵

  8. Enter the following:

    # chmod 777 sync-auxdb-password.bash ↵

  9. Enter the following:

    # ./sync-auxdb-password.bash ↵

  10. If the command in substep 9 succeeds, output like the following is displayed:

    timestamp: Synchronizing password for Auxiliary DB Output...

    timestamp: deployment.apps/tlm-vertica-output scaled

    timestamp: secret/tlm-vertica-output patched

    timestamp: deployment.apps/tlm-vertica-output scaled

    timestamp: Synchronization completed.

  11. If the command output is not as expected, the NFM-P initialization may not be complete; wait 30 minutes, and then return to substep 9. Several attempts may be required.

40 

Perform the following steps on each station in the auxiliary database cluster.

  1. Log in as the root user.

  2. Open a console window.

  3. Enter the following sequence of commands to enable the database services:

    systemctl enable nspos-auxdb.service

    systemctl enable nspos-auxdbproxy.service

    systemctl enable vertica_agent.service

    systemctl enable verticad.service

41 

If you are upgrading the standby cluster in a redundant deployment, go to Step 43.

42 

Enter the following on each station in the cluster to start the database proxy:

# systemctl start nspos-auxdbproxy.service ↵

43 

Close the open console windows.

End of steps