Technical Tip: Upgrading a FortiPortal KVM Deployment

[yamidt_FTNT]

Description	This article describes and focuses on identifying the correct image for upgrading the FortiPortal deployment.
Scope	This document clarifies the specific image names associated with the use of images for upgrading or deploying FortiPortal.
Solution	Since version 7.0, FortiPortal offers three types of images within Fortinet support accounts. From the firmware page: FPC_VM64-AWS-AZURE-V7.X.X-buildXXXX-release-Portal.ova FPC_VM64-V7.X.X-buildXXX-release-kvm-Portal.out.qcow2 FPC_VM64-V7.X.X-buildXXX-release-Portal.ova In FortiPortal hypervisor deployments, the following image formats are utilized: VMDK (VMware): Used for virtual machine disk images in VMware environments. QCOW2 (QEMU): Employed for flexible and efficient virtual disk images in QEMU-based systems. These formats facilitate efficient management and deployment in their respective hypervisor environments. The following is the purpose of the FortiPortal images: QCOW2: Specifically designed for initial deployments on KVM. OVA: Used for VMware and Azure deployments and applicable for upgrades on both VMware and KVM environments. It is important to highlight that the QCOW2 file format is specifically intended for KVM deployments. Furthermore, for all FortiPortal upgrades - regardless of whether they are for VMware or KVM - the OVA file format should be used exclusively for upgrade purposes.