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 FortiAnalyzer 6.4, 7.0, o 7.2 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.4.3 or later |
7.4.5 |
No |
|
7.4.0 to 7.4.2 |
7.4.3, and then to 7.4.5 |
No |
|
7.2.0 or later |
Latest 7.2 version, then to 7.4.3, and then to 7.4.5 |
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. |
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.0.0 or later before you upgrade FortiOS to 7.0.0 or later.
PostgreSQL database upgrade
FortiAnalyzer 7.4.1 includes an upgrade of the PostgreSQL database. Upon upgrading to FortiAnalyzer 7.4.1, by default analytical features, such as Log View, FortiView, Reports, and Event Management are unavailable until the PostgreSQL database finishes upgrading. During this time, FortiAnalyzer will continue to receive new logs, but they will not be inserted into the PostgreSQL database. PostgreSQL database upgrade times depend on the number of ADOM configured and the analytical log volume. Some sample upgrade times are shown below.
| Model | Number of ADOMs | Analytical Data Size | DB Upgrade Time |
|---|---|---|---|
| FAZ-3700F | 1200 | 5TB | one hour |
| FAZ-3500G | 100 | 1TB | 15 minutes |
| FAZ-3000F | 1 | 12TB | 10 minutes |
For customers who prefer to not wait for accessing the analytical features, such as Log View, FortiView, Reports, and Event Management, for new logs, they can execute a SQL. This command can take a long time to complete depending on the amount of data.
FAZVM64 # exec sql-local rebuild-db
Rebuild the entire log SQL database has been requested.
This operation will remove the log SQL database and rebuild from log data.
This operation will reboot the device.
Do you want to continue? (y/n)