Technical Tip: FortiNAC-F 7.2.x migration from VMware to Nutanix

[Hawada1]

Description

This article will guide in the FortiNAC-F migration phase from VMware to Nutanix.

Scope

FortiNAC-F 7.2.X.

Solution

Import FortiNAC Database from Vmware to KVM FortiNAC-OS 7.2.x

1. On the new NACOS VM complete the Config Wizard for an initial configuration. Once completed click on Summary tab then Apply, give FortiNAC sometime it will ask for reboot.

Note: Make sure there are no red errors.

2. After FortiNAC boots up, enter the shell:

fortinac01 # execute enter-shell

3. Copy the database from remote scp server to new KVM NACOS:

scp root@<remote_server_IP>:/tmp/FortiNAC_DataBase_BackUp_2025_07_29_14_04_43_labnac01.gz /bsc/backups/database/

fortinac01:~$ scp root@192.168.xxx.xxx:/tmp/FortiNAC_DataBase_BackUp_2025_07_29_14_04_43_labnac01.gz /bsc/backups/database/

The authenticity of host '192.168.xxx.xxx(192.168.xxx.xxx)' can't be established.
ED25519 key fingerprint is SHA256:Wxxxxxxxxxxxxxxxxxxx.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.xxx.xxx' (ED25519) to the list of known hosts .
root@192.168.xxx.xxx's password:

FortiNAC_DataBase_BackUp_2025_07_29_14_04_43_ 100% 19MB 124.8MB/s 00:00

4. Go to /bsc/backups/database to verify that the database was successfully copied:

fortinac01:~$ cd /bsc/backups/database

fortinac01:/bsc/backups/database$ ll
total 21096
1152 -rw-r--r-- 1 root root 1176115 Jul 30 11:02 FortiNAC_DataBase_BackUp_2025_07_30_11_02_04_fortinac01.gz 25_07_30_11_02_04_fortinac01.gz
19944 -rw-r--r-- 1 admin admin 20420962 Jul 30 11:10 FortiNAC_DataBase_BackUp_2025_07_29_14_04_43_labnac01.gz

5. Shut down FortiNAC services:

fortinac01:/bsc/backups/database$ shutdownNAC

Wait for 30 seconds.

6. Exit the shell mode:

fortinac01:/bsc/backups/database$ exit

7. Restore the database:

fortinac01 # execute restore database local FortiNAC_DataBase_BackUp_2025_07_29_14_04_43_labnac01.gz
Restoring FortiNAC_DataBase_BackUp_2025_07_29_14_04_43_labnac01.gz...
Restore complete

8. Allow it few minutes, then service will start automatically:

fortinac01 # execute enter-shell
fortinac01:~$ jps
9858 com.bsc.server.Yams -m xx:xx:xx:xx:xx:xx
9735 com.bsc.server.Yams -m xx:xx:xx:xx:xx:xx
7113 com.fortinet.nacos.cli.FortiNACCLI
9195 com.bsc.server.CampusManager /bsc/campusMgr/bin/.networkConfig /bsc/campusMgr/master_loader/.cmas
12107 JpsAlternativeTool

9. Login with the GUI root/admin credentials used to access the old NACOS.

10. Note: Everything will be restored except the following:

• Config Wizard should be completed in the first stage.
• Certificates should be imported manually.
• Portal configuration.

11. Regarding the Portal configuration, export the portal configuration from the Primary VMware FortiNAC and import them to Primary Nutanix FortiNAC.

After selecting Export, all of the XML configuration will be compressed in a PortalContents.zip archive file and will be archived automatically by FortiNAC. If multiple portals were created, each individual portal and its contents will be stored as a separate XML file inside the PortalContents.zip archive.

Note: The portal configuration replicates every 10 minutes (FortiNAC 9.4.0 administration guide) when FortiNAC is configured in High Availability.

12. For New Secondary Node just configure the following, DO NOT import the Database:

• Config Wizard should be completed in the first stage.
• Certificates should be imported manually.

Note: After importing the Database on PRIMARY the GUI High Availability configuration will be imported. However, the Serial numbers (FortiNAC-F documentation) still needs to be added and configuration on primary and secondary.

13. Once this is done, select 'Save' on the Primary High Availability settings.
    
    
14. The Portal Configuration will replicate after forming the HA.