Fortinet white logo
Fortinet white logo

Firmware Upgrade Paths

Firmware Upgrade Paths

The following table identifies the supported FortiAnalyzer upgrade paths and whether the upgrade requires a rebuild of the log database. If you need information about upgrading to a specific version, see the corresponding FortiAnalyzer Upgrade Guide.

As a best practice, it typically is recommended to upgrade to the latest patch version before upgrading to the next major version. For recommended upgrade paths from a specific version and model, see the Upgrade Path Tool Table on the Fortinet Document Library.

Before upgrading your device, see details in the applicable FortiAnalyzer Release Notes.

Initial Version

Upgrade to

Log Database Rebuild

7.6.0

7.6.1

No

7.4.3 or later

Latest 7.4 version, then to 7.6.1

No; however, migration is required when upgrading to 7.6.0. See Migrating the log database.

7.4.0 to 7.4.2

7.4.3, then to latest 7.4 version, and then to 7.6.1

Caution

Log insertion might be interrupted if FortiAnalyzer is upgraded directly from version 7.4.0/7.4.1 to 7.6.0/7.6.1.

See the FortiAnalyzer Release Notes for more information.

No; however, migration is required when upgrading to 7.6.0. See Migrating the log database.

7.2.0 or later

7.4.3, then to latest 7.4 version

No

7.0.0 or later

Latest 7.2 version

No

6.4.0 or later

Latest 7.0 version

No

6.2.0 or later

Latest 6.4 version

Yes if upgrading from a previous maintenance release

FortiGate units with logdisk buffer log data while FortiAnalyzer units are rebooting. In most cases, the buffer is enough to cover the time needed for FortiAnalyzer to reboot. However, Fortinet still recommends configuring multiple log destinations to ensure no logs are lost.

Migrating the log database

Beginning in 7.6.0, FortiAnalyzer stores logs in a ClickHouse SQL database rather than a Postgres SQL database. If upgrading from an earlier version, the log database will automatically begin migration after upgrading to FortiAnalyzer 7.6.0 or later. During the migration process, all historical logs will insert from the Postgres database to the ClickHouse database.

After the upgrade, the progress of the migration can be viewed from the GUI banner or from the CLI using the following command:

diagnose sql status migrate-db

FortiView, Log View, Fabric View, Incident & Events, and Reports are available during the migration, but the data will not be accurate. These features can be used with accurate data after the migration is complete.

Fortinet Security Fabric

If you are upgrading the firmware for a FortiAnalyzer unit that is part of a FortiOS Security Fabric, be aware of how the FortiOS Security Fabric upgrade affects the FortiAnalyzer upgrade. You must upgrade the products in the Security Fabric in a specific order. For example, you must upgrade FortiAnalyzer to 7.2.0 or later before you upgrade FortiOS to 7.2.0 or later.

Firmware Upgrade Paths

Firmware Upgrade Paths

The following table identifies the supported FortiAnalyzer upgrade paths and whether the upgrade requires a rebuild of the log database. If you need information about upgrading to a specific version, see the corresponding FortiAnalyzer Upgrade Guide.

As a best practice, it typically is recommended to upgrade to the latest patch version before upgrading to the next major version. For recommended upgrade paths from a specific version and model, see the Upgrade Path Tool Table on the Fortinet Document Library.

Before upgrading your device, see details in the applicable FortiAnalyzer Release Notes.

Initial Version

Upgrade to

Log Database Rebuild

7.6.0

7.6.1

No

7.4.3 or later

Latest 7.4 version, then to 7.6.1

No; however, migration is required when upgrading to 7.6.0. See Migrating the log database.

7.4.0 to 7.4.2

7.4.3, then to latest 7.4 version, and then to 7.6.1

Caution

Log insertion might be interrupted if FortiAnalyzer is upgraded directly from version 7.4.0/7.4.1 to 7.6.0/7.6.1.

See the FortiAnalyzer Release Notes for more information.

No; however, migration is required when upgrading to 7.6.0. See Migrating the log database.

7.2.0 or later

7.4.3, then to latest 7.4 version

No

7.0.0 or later

Latest 7.2 version

No

6.4.0 or later

Latest 7.0 version

No

6.2.0 or later

Latest 6.4 version

Yes if upgrading from a previous maintenance release

FortiGate units with logdisk buffer log data while FortiAnalyzer units are rebooting. In most cases, the buffer is enough to cover the time needed for FortiAnalyzer to reboot. However, Fortinet still recommends configuring multiple log destinations to ensure no logs are lost.

Migrating the log database

Beginning in 7.6.0, FortiAnalyzer stores logs in a ClickHouse SQL database rather than a Postgres SQL database. If upgrading from an earlier version, the log database will automatically begin migration after upgrading to FortiAnalyzer 7.6.0 or later. During the migration process, all historical logs will insert from the Postgres database to the ClickHouse database.

After the upgrade, the progress of the migration can be viewed from the GUI banner or from the CLI using the following command:

diagnose sql status migrate-db

FortiView, Log View, Fabric View, Incident & Events, and Reports are available during the migration, but the data will not be accurate. These features can be used with accurate data after the migration is complete.

Fortinet Security Fabric

If you are upgrading the firmware for a FortiAnalyzer unit that is part of a FortiOS Security Fabric, be aware of how the FortiOS Security Fabric upgrade affects the FortiAnalyzer upgrade. You must upgrade the products in the Security Fabric in a specific order. For example, you must upgrade FortiAnalyzer to 7.2.0 or later before you upgrade FortiOS to 7.2.0 or later.