Upgrade to MariaDB 10.11

Prerequisites Copied

Before performing the upgrade, ensure the following prerequisites are met:

Back up Opsview databases and configuration Copied

Warning

This step is crucial to prevent data loss in your Opsview system.

To backup your Opsview data and system, refer to Back up your Opsview data and system for instructions on backing up all databases on the server. If you are using a remote database server, perform the backup on your database host. Otherwise, perform the backup on the orchestrator.

If you are using a RHEL or OL system and your MariaDB packages come from the MariaDB repository instead of the OS repository, you must perform additional steps before upgrading to MariaDB 10.11. This is due to the upgrade process switching the package source to the OS repository. For detailed instructions, see Disable the MariaDB repository and remove its packages.

Upgrade to MariaDB 10.11 Copied

On your orchestrator, do the following steps:

  1. Add the following configuration to the user_vars.yml file.
opsview_database_package_vendor: 'mariadb'
opsview_database_package_version: '10.11'
  1. Run the check-deploy and setup-everything playbooks to upgrade the databases to MariaDB 10.11.
cd /opt/opsview/deploy
./bin/opsview-deploy lib/playbooks/check-deploy.yml
./bin/opsview-deploy lib/playbooks/setup-everything.yml

Note

On RHEL or OL systems, if MariaDB packages are installed from the MariaDB repository instead of the OS repository, running check-deploy.yml will fail. The error message will state that MariaDB packages from the MariaDB repository must be removed.

For detailed instructions, see Disable the MariaDB repository and remove its packages.

Restore the database backup Copied

Run the following commands on your database host or your orchestrator, depending on where the database is located.

  1. To restore the backup of all Opsview databases, start by decompressing the backup file.
gunzip -c /path/to/databases.sql.gz > /path/to/databases.sql
  1. Restore the databases. The MySQL root user password can be found in the /opt/opsview/deploy/etc/user_secrets.yml file.
mysql -u root -p < /path/to/databases.sql

Note

If you encounter ERROR: Access to system schema 'mysql' is rejected, refer to the Error when restoring the MySQL database.

Run setup-monitoring Copied

Note

Before executing this step, ensure that all your databases have been fully restored.

On your orchestrator, run the setup-monitoring playbook.

cd /opt/opsview/deploy
./bin/opsview-deploy lib/playbooks/setup-monitoring.yml

After completing the step, Apply Changes to submit your database modifications.

Troubleshooting Copied

To help resolve any issues you may encounter during the upgrade, refer to the Database issues troubleshooting documentation.

["Opsview On-Premises"] ["User Guide", "Technical Reference", "Compatibility Matrix"]

Was this topic helpful?