Introduction
This guide covers upgrading a FortiSOAR™ enterprise instance, High Availability (HA) cluster, or a distributed multi-tenant configuration.
|
FortiSOAR release 7.3.0 supports Rocky Linux release 8.6 or RHEL 8.6 systems and support for the CentOS operating system has been discontinued. |
As there is a change in the supported OS, there is a need to migrate the content from a pre-7.3.0 version to the 7.3.0 version. To migrate the content there are two methods:
- Using the FortiSOAR content export and restore method
- Using the in-place upgrade method
FortiSOAR Upgrade - Choosing between the content export and restore method and the in-place upgrade method
This topic lists some data points that should help you decide which upgrade method is better suited for your environment:
| Prerequisite | FortiSOAR Content Export and Restore | In-place Upgrade |
| VM | Require to provision a new VM with FortiSOAR7.3.0. | New VM not required. Your existing FortiSOAR VM is upgraded. |
|
Disk |
Require to add a new disk if the database size is more than free space available on FortiSOAR appliance. |
New disks are not required as this method does not take a backup of the database. |
|
Time |
Both methods take roughly the same amount of time. |
Both methods take roughly the same amount of time. |
The following tables present some additional data points to help you make your choice:
| FortiSOAR system with 127 GB database size - Number of files/attachments is more | ||
| Process | FortiSOAR Content Export and Restore -Time or Storage Requirement | In-place Upgrade-Time or Storage Requirement |
|
Backup DB |
30 minutes |
2 minutes (DB backup process is skipped) |
|
Requirement of extra disk space |
320 GB - New disk was added to the VM |
N/A |
|
Compressed DB backup file size |
91 GB |
N/A |
|
Configure the VM to add disk and update LVM |
7 minutes |
N/A |
|
Provision new VM |
10 minutes |
N/A |
|
Copy backup file to new VM |
14 minutes |
N/A |
|
OS Upgrade |
N/A |
20 minutes |
|
Install and configure FortiSOAR 7.3.0 |
N/A |
20 minutes |
|
Restore DB |
51 minutes |
10 minutes |
|
Total Process Duration |
Approximately 90 minutes |
Approximately 58 minutes |
| FortiSOAR system with 18 GB database size - Number of files/attachments is less | ||
| Process | FortiSOAR Content Export and Restore - Time or Storage Requirement | In-place Upgrade- Time or Storage Requirement |
|
Backup DB |
5 minutes |
1 minutes (DB backup process is skipped) |
|
Requirement of extra disk space |
40 GB - New disk was added to the VM |
N/A |
|
Compressed DB backup file size |
13 GB |
N/A |
|
Configure the VM to add disk and update LVM |
7 minutes |
N/A |
|
Provision new VM |
10 minutes |
N/A |
|
Copy backup file to new VM |
5 minutes |
N/A |
|
OS Upgrade |
N/A |
20 minutes |
|
Install and configure FortiSOAR 7.3.0 |
N/A |
20 minutes |
|
Restore DB |
15 minutes |
6 minutes |
|
Total Process Duration |
Approximately 42 minutes |
Approximately 47 minutes |
FortiSOAR Upgrade Notes
This document describes how to upgrade FortiSOAR to 7.3.0 using both the methods. This guide is intended to supplement the FortiSOAR Release Notes, and it includes the following chapters:
- Preparing to Upgrade FortiSOAR
- Upgrading FortiSOAR both the methods of upgrade, i.e., using the FortiSOAR content export and restore method and using the in-place upgrade script are described in this chapter.
- Upgrading a FortiSOAR High Availability Cluster
- Upgrading a FortiSOAR Distributed Multi-Tenancy Configuration
- Post-Upgrade Tasks
|
You can upgrade your FortiSOAR enterprise instance, High Availability (HA) cluster, or a distributed multi-tenant instance to version 7.3.0 from version 7.2.1 and 7.2.2 only. Also, once you have upgraded your instance, you must log out from the FortiSOAR UI and log back into FortiSOAR. |
Also, note that the upgrade procedure temporarily takes the FortiSOAR application offline while the upgrade operations are taking place. We recommend that you send a prior notification to all users of a scheduled upgrade as users are unable to log in to the FortiSOAR Platform during the upgrade.
|
From version 7.0.0 onwards, the FortiSOAR UI displays a notification when a new release (always the latest) is available. The notification also contains a link to that version's release notes so that you can get details about the latest available release. This keeps FortiSOAR users informed about the latest releases and then users can make informed decisions about upgrading to the latest available FortiSOAR version. |
Before you upgrade your FortiSOAR instance, it is highly recommended that you review the Special Notices chapter in the "Release Notes", so that you are aware of operational and breaking changes made in version 7.3.0.
To solve common issues that occur during the upgrade process, see the Troubleshooting FortiSOAR chapter in the “Deployment Guide.”