icinga2/doc/16-upgrading-icinga-2.md

#  Upgrading Icinga 2 <a id="upgrading-icinga-2"></a>

Upgrading Icinga 2 is usually quite straightforward. Ordinarily the only manual steps involved
are scheme updates for the IDO database.

## Upgrading the MySQL database <a id="upgrading-mysql-db"></a>

If you're upgrading an existing Icinga 2 instance, you should check the
`/usr/share/icinga2-ido-mysql/schema/upgrade` directory for an incremental schema upgrade file.

> **Note**
>
> If there isn't an upgrade file for your current version available, there's nothing to do.

Apply all database schema upgrade files incrementally.

    # mysql -u root -p icinga < /usr/share/icinga2-ido-mysql/schema/upgrade/<version>.sql

The Icinga 2 DB IDO module will check for the required database schema version on startup
and generate an error message if not satisfied.


**Example:** You are upgrading Icinga 2 from version `2.0.2` to `2.3.0`. Look into
the *upgrade* directory:

    $ ls /usr/share/icinga2-ido-mysql/schema/upgrade/
    2.0.2.sql  2.1.0.sql 2.2.0.sql 2.3.0.sql

There are two new upgrade files called `2.1.0.sql`, `2.2.0.sql` and `2.3.0.sql`
which must be applied incrementally to your IDO database.

## Upgrading the PostgreSQL database <a id="upgrading-postgresql-db"></a>

If you're updating an existing Icinga 2 instance, you should check the
`/usr/share/icinga2-ido-pgsql/schema/upgrade` directory for an incremental schema upgrade file.

> **Note**
>
> If there isn't an upgrade file for your current version available, there's nothing to do.

Apply all database schema upgrade files incrementally.

    # export PGPASSWORD=icinga
    # psql -U icinga -d icinga < /usr/share/icinga2-ido-pgsql/schema/upgrade/<version>.sql

The Icinga 2 DB IDO module will check for the required database schema version on startup
and generate an error message if not satisfied.

**Example:** You are upgrading Icinga 2 from version `2.0.2` to `2.3.0`. Look into
the *upgrade* directory:

    $ ls /usr/share/icinga2-ido-pgsql/schema/upgrade/
    2.0.2.sql  2.1.0.sql 2.2.0.sql 2.3.0.sql

There are two new upgrade files called `2.1.0.sql`, `2.2.0.sql` and `2.3.0.sql`
which must be applied incrementally to your IDO database.
Update docs for better compatibility with mkdocs * Rename files to allow easy ordering * Update links inside markdown according to new file names * Move HTML links (<a>...</a>) to the end of the header lines * This is necessary to allow mkdocs to parse headers correctly and display them in the TOC * Following sed command was used: sed -i .bu 's/\(<a.a>\) \(.\)/\2 \1/g' $filename 2017-07-12 20:46:12 +02:00			`# Upgrading Icinga 2 <a id="upgrading-icinga-2"></a>`
Update documentation 2015-01-23 14:15:57 +01:00
			`Upgrading Icinga 2 is usually quite straightforward. Ordinarily the only manual steps involved`
			`are scheme updates for the IDO database.`

Update docs for better compatibility with mkdocs * Rename files to allow easy ordering * Update links inside markdown according to new file names * Move HTML links (<a>...</a>) to the end of the header lines * This is necessary to allow mkdocs to parse headers correctly and display them in the TOC * Following sed command was used: sed -i .bu 's/\(<a.a>\) \(.\)/\2 \1/g' $filename 2017-07-12 20:46:12 +02:00			`## Upgrading the MySQL database <a id="upgrading-mysql-db"></a>`
Update documentation 2015-01-23 14:15:57 +01:00
Fixes typos, dashes and some punctuation mark refs #11599 2016-05-23 14:14:59 +02:00			`If you're upgrading an existing Icinga 2 instance, you should check the`
Update documentation 2015-01-23 14:15:57 +01:00			`/usr/share/icinga2-ido-mysql/schema/upgrade` directory for an incremental schema upgrade file.

			`> Note`
			`>`
Fixes typos, dashes and some punctuation mark refs #11599 2016-05-23 14:14:59 +02:00			`> If there isn't an upgrade file for your current version available, there's nothing to do.`
Update documentation 2015-01-23 14:15:57 +01:00
Fix typos in the documentation fixes #10692 Signed-off-by: Gunnar Beutner <gunnar@beutner.name> 2015-11-20 15:57:16 +01:00			`Apply all database schema upgrade files incrementally.`
Update documentation 2015-01-23 14:15:57 +01:00
			`# mysql -u root -p icinga < /usr/share/icinga2-ido-mysql/schema/upgrade/<version>.sql`

			`The Icinga 2 DB IDO module will check for the required database schema version on startup`
			`and generate an error message if not satisfied.`


DB IDO: Fix duplicate entries in {host,service}depencencies table fixes #7765 2015-02-12 13:16:30 +01:00			Example: You are upgrading Icinga 2 from version `2.0.2` to `2.3.0`. Look into
Update documentation 2015-01-23 14:15:57 +01:00			`the upgrade directory:`

			`$ ls /usr/share/icinga2-ido-mysql/schema/upgrade/`
DB IDO: Fix duplicate entries in {host,service}depencencies table fixes #7765 2015-02-12 13:16:30 +01:00			`2.0.2.sql 2.1.0.sql 2.2.0.sql 2.3.0.sql`
Update documentation 2015-01-23 14:15:57 +01:00
DB IDO: Fix duplicate entries in {host,service}depencencies table fixes #7765 2015-02-12 13:16:30 +01:00			There are two new upgrade files called `2.1.0.sql`, `2.2.0.sql` and `2.3.0.sql`
Fix typos in the documentation fixes #10692 Signed-off-by: Gunnar Beutner <gunnar@beutner.name> 2015-11-20 15:57:16 +01:00			`which must be applied incrementally to your IDO database.`
Update documentation 2015-01-23 14:15:57 +01:00
Update docs for better compatibility with mkdocs * Rename files to allow easy ordering * Update links inside markdown according to new file names * Move HTML links (<a>...</a>) to the end of the header lines * This is necessary to allow mkdocs to parse headers correctly and display them in the TOC * Following sed command was used: sed -i .bu 's/\(<a.a>\) \(.\)/\2 \1/g' $filename 2017-07-12 20:46:12 +02:00			`## Upgrading the PostgreSQL database <a id="upgrading-postgresql-db"></a>`
Update documentation 2015-01-23 14:15:57 +01:00
Fixes typos, dashes and some punctuation mark refs #11599 2016-05-23 14:14:59 +02:00			`If you're updating an existing Icinga 2 instance, you should check the`
Update documentation 2015-01-23 14:15:57 +01:00			`/usr/share/icinga2-ido-pgsql/schema/upgrade` directory for an incremental schema upgrade file.

			`> Note`
			`>`
Fixes typos, dashes and some punctuation mark refs #11599 2016-05-23 14:14:59 +02:00			`> If there isn't an upgrade file for your current version available, there's nothing to do.`
Update documentation 2015-01-23 14:15:57 +01:00
Fix typos in the documentation fixes #10692 Signed-off-by: Gunnar Beutner <gunnar@beutner.name> 2015-11-20 15:57:16 +01:00			`Apply all database schema upgrade files incrementally.`
Update documentation 2015-01-23 14:15:57 +01:00
			`# export PGPASSWORD=icinga`
			`# psql -U icinga -d icinga < /usr/share/icinga2-ido-pgsql/schema/upgrade/<version>.sql`

			`The Icinga 2 DB IDO module will check for the required database schema version on startup`
			`and generate an error message if not satisfied.`

DB IDO: Fix duplicate entries in {host,service}depencencies table fixes #7765 2015-02-12 13:16:30 +01:00			Example: You are upgrading Icinga 2 from version `2.0.2` to `2.3.0`. Look into
Update documentation 2015-01-23 14:15:57 +01:00			`the upgrade directory:`

			`$ ls /usr/share/icinga2-ido-pgsql/schema/upgrade/`
DB IDO: Fix duplicate entries in {host,service}depencencies table fixes #7765 2015-02-12 13:16:30 +01:00			`2.0.2.sql 2.1.0.sql 2.2.0.sql 2.3.0.sql`
Update documentation 2015-01-23 14:15:57 +01:00
DB IDO: Fix duplicate entries in {host,service}depencencies table fixes #7765 2015-02-12 13:16:30 +01:00			There are two new upgrade files called `2.1.0.sql`, `2.2.0.sql` and `2.3.0.sql`
Fix typos in the documentation fixes #10692 Signed-off-by: Gunnar Beutner <gunnar@beutner.name> 2015-11-20 15:57:16 +01:00			`which must be applied incrementally to your IDO database.`