Question About Offline Upgrade Process in FortiSIEM 7.3.2

[acronymm]

Hello FortiSIEM Community,
I am planning to upgrade FortiSIEM to the 7.3.2 in an environment without internet access and considering the offline upgrade process. However, I noticed that one of the first steps requires downloading the FortiSIEM OS Repository and copying the script fsm-sync-os-repo.sh from a FortiSIEM 7.3.2 host.
My concern is: Does this mean that an existing FortiSIEM 7.3.2 machine is mandatory to proceed with an offline upgrade? If we do not already have a 7.3.2 instance running, are there alternative ways to obtain the necessary files for an offline installation?
If anyone has experience with this scenario or knows potential workarounds (such as setting up an offline repository server), I would appreciate any insights or guidance.
Thanks in advance!

Ref: Offline Installation and Upgrade | FortiSIEM 7.3.2 | Fortinet Document Library

[Secusaurus · Accepted solution]

Hi @acronymm,

To make it simple for most users, all possible components (supervisor, worker, collector, ClickHouse keeper, and repository) can be deployed using the same initial image.

This is the reason why they are referencing to this path.

So, for the repository server, you deploy a FortiSIEM-VM-image, but don't run the configFSM.sh script. Instead, you follow the steps from the guide.

Note, that collectors don't support offline upgrades in the 7.2 versions. As far as I remember, this is only implemented if the collector already is on 7.3.x

Best,

Christian