---
title: "Overview"
description: ""
url: "https://docs.itrsgroup.com/docs/opsview/current/upgrade-notes/overview/index.html"
---
This document describes the steps required to upgrade an existing Opsview Monitor system running on either a single server instance or a distributed Opsview environment to the latest version of Opsview Monitor.

Prior to the installation or upgrade of Opsview Monitor to a newer version, please check the following documentation:

- [Opsview 6.x Release Notes](https://docs.itrsgroup.com/docs/all/opsview/opsview-release-notes/index.html)
- [What's New in ITRS Opsview](https://docs.itrsgroup.com/docs/all/whats-new/opsview-whats-new/index.html)
- [Known Issues](https://docs.itrsgroup.com/docs/all/opsview/opsview-known-issues-6x/index.html)

For information about performing an in-place upgrade to Opsview versions 6.3.x and 6.7.x, refer to the [Opsview Knowledge Center](https://knowledge.opsview.com/docs/upgrading).

Depending on the size and complexity of your current Opsview Monitor system, the upgrade process may take between a few hours to a full day. This includes the following:

- Back up your Opsview data
- Upgrade Opsview Deploy
- Run deployment process
- Verify the started processes
- Upgrade Opspacks
- [Apply Changes](https://docs.itrsgroup.com/docs/opsview/current/configuration/apply-changes/index.html) in Opsview Monitor


**Note**


After an upgrade, we recommended that you clear your browser cache. This ensures the new features and functionality are being used from the latest code instead of the cached ones from before the upgrade.



## Important notes

Before proceeding with your upgrade, please review the following upgrade considerations to help avoid issues during the process.

### Upgrade path requirements

You must have upgraded to Opsview 6.5.x or above and performed all post-upgrade tasks before upgrading to Opsview version 6.8.x or above. This includes completing the [Database Migration for SQL Strict Mode](https://knowledge.opsview.com/docs/migrate_db_strict_sql). If the database migration has not been completed, the upgrade will be cancelled with a `fatal` warning.

### Upgrade preparation

Before performing any upgrade, we strongly recommend that you backup your system including configuration files and databases. This ensures you can restore your environment if a rollback is required.

You must also upgrade all your hosts to the latest operating system packages, excluding Opsview packages. Do not manually upgrade any package beginning with `opsview-`, or the `infrastructure-agent` package. These will be automatically handled during the upgrade process.

#### Operating system and database compatibility

Starting with Opsview 6.11.1, new installations on the following operating systems use MariaDB 10.11 as the default database:

- RHEL 8.10
- RHEL 9.4 or newer
- OL 8
- OL 9

If you are upgrading from an older version, your existing database is retained to prevent unintended data loss from an automatic upgrade to MariaDB 10.11. For the manual instructions, refer to [Upgrade to MariaDB 10.11](https://docs.itrsgroup.com/docs/opsview/current/prerequisites/compatibility-matrix/upgrade-mariadb-10-11/index.html).

Starting with Opsview 6.11.7, new installations on the following operating systems use MySQL 8.4 as:

- Default database:
  - Ubuntu 22
- Non-default database option:
  - RHEL 8
  - RHEL 9
  - OL 8
  - OL 9
  - Debian 12

If you are upgrading from an earlier version of Opsview, your existing database will be retained to prevent unintended data loss from an automatic upgrade to MySQL 8.4. However, this configuration is no longer supported going forward.

For detailed manual upgrade instructions and guidance on resolving any issues, refer to [Upgrade to MySQL 8.4](https://docs.itrsgroup.com/docs/opsview/current/prerequisites/compatibility-matrix/upgrade-mysql-8-4/index.html).

Additionally, Opsview 6.11.x and above no longer supports Debian 10. If you are using Debian 10 on older Opsview versions, you must migrate to Debian 12 before upgrading. For the full instructions, refer to [Upgrade from Debian 10 to Debian 12](https://docs.itrsgroup.com/docs/opsview/current/prerequisites/compatibility-matrix/upgrade-debian-12/index.html).

To view the full list of supported platforms, see the documentation on [Supported databases](https://docs.itrsgroup.com/docs/opsview/current/prerequisites/compatibility-matrix/supported-databases/index.html#supported-databases) and [Supported operating systems](https://docs.itrsgroup.com/docs/opsview/current/prerequisites/compatibility-matrix/supported-os/index.html#supported-platform).

### Component version requirements

For Opsview to run correctly, all Opsview components on all servers must be installed from the same release repository. Mixing Opsview component versions from different releases, such as using `opsview-datastore` from 6.8.x and `opsview-messagequeue` from 6.7.x, is not supported.

Opsview collectors must also be installed from the same release repository as the core servers, whether they are deploy-based or are remotely managed collectors. The only exception to this is the [Infrastructure Agent](https://docs.itrsgroup.com/docs/infrastructure-agent/current/) installed on monitored devices. The agent version does not need to match the exact Opsview version you’re using. However, it is always recommended to install the latest version of the agent whenever possible.

### Monitoring collectors

During the upgrade, the system may temporarily report non-OK or non-UP states due to ongoing monitoring script configuration. To avoid false alarms and disruption during the upgrade process, you can temporarily disable Host Check, Service Check, and Event Handler execution on all Monitoring Clusters including the Master Monitoring Server.

For Opsview versions 6.8.5 and below, access the **Features Enabled** modal in **Configuration > Monitoring Collectors > Clusters** under the **Clusters** tab.

For Opsview versions 6.8.6 and newer, you can disable execution in the [Collector Management](https://docs.itrsgroup.com/docs/opsview/current/administration/distributed-monitoring/managing-clusters-and-collectors/index.html#controlling-check-executions) page.

### Messageque

If there is a significant upgrade of `opsview-messagequeue`, existing queues will be rebuilt and all unprocessed messages will be removed. For more information on `opsview-messagequeue` errors, refer to [Opsview 6.x Known Issues](https://docs.itrsgroup.com/docs/all/opsview/opsview-known-issues-6x/index.html#upgrade-and-installation).

## Activation key

Ensure you have your activation key for your system. For more information, refer to the following software key documentation:

- [Managing your Subscription](https://docs.itrsgroup.com/docs/opsview/current/support/managing-your-subscription/index.html)
- [Troubleshooting activation issues](https://docs.itrsgroup.com/docs/opsview/current/troubleshooting/activation-issues/index.html)

## Back up your Opsview data and system

For further guidance, refer to the [Common Tasks](https://docs.itrsgroup.com/docs/opsview/current/administration/common-tasks/index.html) documentation.

Run the following command as root which will back up all databases on the server (if upgrading from Opsview 6.7.x or older):

```shell
mysqldump -u root -p --add-drop-database --extended-insert --opt --all-databases | gzip -c > /tmp/databases.sql.gz
```

Run the following command instead if upgrading from Opsview 6.8.x or newer:

```shell
mysqldump -u root -p --default-character-set=utf8mb4 --add-drop-database --extended-insert --opt --all-databases | sed 's/character_set_client = utf8 /character_set_client = utf8mb4 /' | gzip -c > /tmp/databases.sql.gz
```

The MySQL root user password can be found in `/opt/opsview/deploy/etc/user_secrets.yml`. Ensure you copy your database dump (`/tmp/databases.sql.gz` in the preceding command) to a secure location.

