Upgrade Data Repository

Upgrading › How to Upgrade CA Performance Management Data Aggregator - Command Line › Upgrade Data Repository

Upgrade Data Repository

Upgrade Data Repository. The following scripts must be executed in sequence as part of the upgrade process:

dr_validate.sh - Helps ensure that Data Repository prerequisites have been satisfied.
dr_install.sh - Installs the Vertica database.

Note: For information about supported upgrade paths and when to upgrade Data Repository, see the Data Aggregator Release Notes.

Follow these steps:

Log in to the database server you use for Data Repository as the Vertica Linux database administrator user and determine what hosts Vertica is running on:
1. Type the following command:
```
/opt/vertica/bin/adminTools
```
  The Administration Tools dialog opens.
2. Select option 6 (Configuration Menu).
3. Select option 3 (View Database).
4. Select the database.
5. Make a note of the hostnames. You will need these hostnames later in this procedure.
6. Exit the adminTools utility.
Open a console and log in to the computer where you plan to install Data Repository as the root user. If you require sudo installation instructions, contact CA Support.
Important! In a cluster installation, you can initiate the Data Repository installation from any of the three hosts that is participating in the cluster. The required software components are pushed to the additional two nodes during the installation.
Copy the installDR.bin file locally.
Change permissions for the installation file by typing the following command:
```
chmod u+x installDR.bin
```
To extract the installation file, type the following command:
```
./installDR.bin
```
Important! The installDR.bin file does not install Data Repository. This file extracts the Data Repository rpm and license file. You install Data Repository later in this procedure.

The directory that was chosen during the installDR.bin installation must be accessible by all users. chmod can be used to enable read/write for directories within the user home directories (for example, chmod -R 755 ˜).

The License Agreement opens.

If you extract the Data Repository installation file from a secure shell or console and you are not running an X Window System on the computer where you want to install Data Repository, the License Agreement opens in console mode (command line). Otherwise, the agreement opens within a user interface.
Read the license agreement, accept the agreement, and click Next if you are in the user interface. Press Enter if you are in console mode.
When prompted, enter an installation directory to extract the Data Repository installation package and Vertica license file to, or accept the default installation directory of /opt/CA/IMDataRepository_vertica7/. Click Install and click Done if you are in the user interface. Press Enter, twice, if you are in console mode.
The Data Repository installation package and license file are extracted to the chosen directory. Three installation scripts that are required to complete the installation are extracted also.
To perform a manual backup of your Data Repository, type the following command:
```
/opt/vertica/bin/vbr.py --task backup --config-file configuration_filename
```
configuration_filename

Indicates the directory path and filename of the configuration file you created when you initially set up automatic backups. This file is located where you ran the backup utility (/opt/vertica/bin/vbr.py).

For example:
```
/opt/vertica/bin/vbr.py --task backup --config-file /home/vertica/vert-db-production.ini
```
If you are prompted about the authenticity of the host, answer yes.

Note: In a cluster installation, you only have to perform this step on one of the hosts that are participating in the cluster.

Important! If you back up Data Repository and have not been regularly backing up Data Repository previously, it can take several hours or more to back up Data Repository.
If available, copy your existing drinstall.properties from /opt/CA/IMDataRepository_vertica6 to /opt/CA/IMDataRepository_vertica7.
Note: The paths above reflect default values. Your exact locations may differ.
Verify that all of the parameters in the drinstall.properties file are correct. Review the following parameters:
- DbAdminLinuxUser=The Linux user created to serve as the Vertica database administrator
  Default: dradmin
- DbAdminLinuxUserHome=The Vertica Linux database administrator user home directory
  Default: /export/dradmin
- DbDataDir=The location of the data directory
  Default: /data
  
  Note: If you are unsure what your data directory is, do the following steps: Open the /opt/vertica/config/admintools.conf file. Scroll down until you see the [Nodes] section. Locate one of the lines that begins with v_dbname_nodeXXXX. This line contains the IP address of the node, the location of the catalog directory, and the location of the data directory, in that order, separated by commas. Make note of the data directory.
- DbCatalogDir=The location of the catalog directory
  Default: /catalog
  
  Note: If you are unsure what your catalog directory is, do the following steps: Open the /opt/vertica/config/admintools.conf file. Scroll down until you see the [Nodes] section. Locate one of the lines that begins with v_dbname_nodeXXXX. This line contains the IP address of the node, the location of the catalog directory, and the location of the data directory, in that order, separated by commas. Make note of the catalog directory.
- DbHostNames=The comma-delimited list of hostnames for Data Repository
  Default: yourhostname1,yourhostname2,yourhostname3
- DbName=The database name
  Default: drdata
  
  Note: If you are unsure what your database name is, run Admintools as the Vertica Linux database administrator. From the Main Menu, select “6 Configuration Menu” and then select “3 View Database”. The name of your database is in the “Select database to view” dialog. This value should correspond with the value specified for DbName. Note the database name and select “Cancel”.
- DbPwd=The database password
  Default: dbpass
Note: If you have an “InstallDestination” parameter in your drinstall.properties file, this parameter will no longer be used and can be safely removed.
Be sure that Data Repository is up and running and then type the following command to run the pre-installation script:
```
./dr_validate.sh -p properties_file
```
For example:
```
./dr_validate.sh -p drinstall.properties
```
The pre-installation script establishes passwordless SSH between all hosts in a cluster. If passwordless SSH does not exist, you are prompted for a password.

Note: The pre-installation script may prompt you to reboot.
Review any on-screen output for errors or warnings. You can run this script multiple times to verify that all system configuration prerequisites are set properly.
To run the installation script, type the following command:
```
./dr_install.sh -p properties_file
```
For example:
```
./dr_install.sh -p drinstall.properties
```
The installation script upgrades the data repository and disables unnecessary vertica processes. You may be prompted for the vertica Linux database administrator user password.

Note: Enter the password and press Enter twice to proceed.
Look for and resolve any failures.
Verify that you upgraded Data Repository correctly by doing the following steps:
1. Type the following command:
```
/opt/vertica/bin/adminTools
```
  The Administration Tools dialog opens.
2. Verify that the top of the banner indicates that the database version is 7.0.1-2.
Restart Data Repository as the Vertica Linux database administrator user by selecting option 3 (Start Database) from the main menu of the Administration Tools dialog.
Data Repository is upgraded.