Upgrading Management Console manually

If you installed MC manually, follow the procedure below to upgrade MC.

If you installed MC automatically on AWS resources, see Upgrading MC automatically on AWS.

Backing up MC before you upgrade

Log in as root or a user with sudo privileges on the server where MC is already installed.
Open a terminal window and shut down the MC process:
```
# /etc/init.d/vertica-consoled stop
```
For versions of Red Hat 7/CentOS 7 and above, use:
```
# systemctl stop vertica-consoled
```
Back up MC to preserve configuration metadata.

Important
A full backup is required in order to restore MC to its previous state. Restoring MC is essential if the upgrade fails, or you decide to revert to the previous version of Vertica. For details, see Backing up MC.
Stop the database if MC was installed on an Ubuntu or Debian platform.

Extended monitoring upgrade recommendations

If you use Extended monitoring to monitor a database with MC, Vertica recommends the following upgrade procedure to avoid data loss.

Log in to MC as an administrator.
To stop the monitored database, navigate to the Existing Infrastructure > Databases and Clusters page, select the monitored database and click Stop.
On MC Settings > MC Storage DB Setup, click Disable Streaming to stop the storage database's collection of monitoring data.
To stop the storage database, navigate to the Existing Infrastructure > Databases and Clusters page, select the monitored database and click Stop.
Upgrade MC and Vertica according to Upgrade MC and Upgrading Vertica instructions.
To start the storage database, navigate to the Existing Infrastructure > Databases and Clusters page, select the monitored database and click Start.
Start the monitored database.
On MC Settings > MC Storage DB Setup, click Enable Streaming to enable collection of monitoring data.

Important
To avoid data loss, enable streaming soon after starting your monitored database. While your storage database is down and streaming is disabled, the Kafka server can retain data from your running monitored database for a limited amount of time. Data loss occurs when the data exceeds the Kafka retention policy's log size or retention time limits.

Upgrading MC

Note

After you upgrade, you can authenticate users to the MC with a federated server or your corporate identity provider. In addition, you are prompted to provide the following information:

A new password.
If your user profile does not have an email address, you must enter one immediately after accepting the end-user license agreement (EULA).

Download the MC package from the Vertica website:
```
vertica-console-current-version.Linux-distro)
```
Save the package to a location on the target server, such as /tmp.
On the target server, log in as root or a user with sudo privileges.
Change to the directory where you saved the MC package.
Install MC using your local Linux distribution package management system—rpm, yum, zypper, apt, dpkg. For example:

Red Hat 8
```
# rpm -Uvh vertica-console-current-version.x86_64.rpm
```
Debian and Ubuntu
```
# dpkg -i vertica-console-current-version.deb
```
If you stopped the database before upgrading MC, restart the database.

As the root user, use the following command:
```
/etc/init.d/verticad start
```
For versions of Red Hat 8/CentOS 8 and above, run:
```
# systemctl start verticad
```
Open a browser and enter the URL of the MC installation, one of the following:
- IP address:
```
https://ip-address:mc-port/
```
- Server host name:
```
https://hostname:mc-port/
```
By default, mc-port is 5450.

If MC was not previously configured, the Configuration Wizard dialog box appears. Configuration steps are described in Configuring MC.

If MC was previously configured, Vertica prompts you to accept the end-user license agreement (EULA) when you first log in to MC after the upgrade.

Additionally, you can choose to provide Vertica with analytic information about your MC usage. For details, see Management Console settings.