Technical Tip: FortiMail and FortiSandBox-VM migration

[Sunil_Panchal]

Description	This article describes the Best practices for FortiMail and FortiSandBox-VM migration.
Scope	FortiMail and FortiSandBox.
Solution	A situation arises when the FortiMail and FortiSandBox-VM need to move to a different Virtualization Server like Vmware to Nutanix, KVM, Xen, or Vice Versa FortiMail and FortiSandBox as a whole VM can not be migrated from one hypervisor to another hypervisor due to the nature, working, and disk type. What can be done: Spin up the new VM in a different hypervisor with the same spec as the older VM: FortiMail VM Overview For FortiSandBox VM Deployment:-https://docs.fortinet.com/document/fortisandbox-private-cloud/4.4.0/vmware-esxi-vm-install-guide/369760/preparing-for-deployment Take the configuration backup from the old VM for FortiMail: System maintenance for FortiSandBox: System Recovery Shut down the old VM. Install the license file to the New VM and upload the configuration. License Validation can take some time to Accept from a new VM, but same time older VM should not be running. This can cause a new VM invalid license/Duplicate license error. With the configuration, FortiMail will have all settings but data like Logs file and generated report files can not be migrated. For logs, an external logging server is suggested like FortiAnalyzer. All other types of firmware for Hypervisor can be downloaded from: https://support.fortinet.com/support/#/downloads/firmware FML_VMKV-64-v705-build0208-FORTINET.out.kvm.zip FSA_KVM-v500-build0080-FORTINET.out.kvm.zip Like the above example, the extension of the virtualization type will be at the end of the firmware name.