Migrating from Virtual FortiWLM 32-bit to Virtual FortiWLM 64-bit
To use new features and retain data, when upgrading from pre-8.4, perform this procedure to migrate a virtual FortiWLM 32-bit to a virtual FortiWLM 64-bit.
The migration can be performed to the current 64-bit version from two prior versions ONLY, for example, data from 8.3.3 and 8.3.2 can only be migrated to 8.4. Hence, it is recommended to migrate pre-8.4 virtual FortiWLM 32-bit to 8.4/8.4.1/8.4.2 virtual FortiWLM 64-bit and then to the current release.
- Backup the data in 32-bit FortiWLM and copy it using the copy scp/ftp command.
- Install the 64-bit FortiWLM image; use the forti-wlm-x.x-xbuild-y-x86_64.ova file.
- Shutdown the 32-bit FortiWLM instance.
- Run the following commands in the 64-bit FortiWLM to copy and restore the backed up 32-bit data.
-
copy scp://<user name>@<IP server>/<Backup file path> /data/backup/nms/.
OR
copy ftp://<user name>@<IP server>/<Backup file path> /data/backup/nms/. - restore <Backup file name>
The following are recommended to perform the migration operation:
- Do not change the name of the database backup file.
- During the backup/restore operation, do not close the CLI session; closing the session aborts the backup/restore operation. For more information, see the backup and restore command details in the FortiWLM User Guide.
NOTES:
- Migration from SA2000-VE to FWM-VM 64-bit requires a new license file to be installed on FWM-VM 64-bit.
- Migration from FWM-VM 32-bit to FWM-VM 64-bit does NOT require any license changes if the system ID is the same on both. However, if the system ID differs then a new license file is requiredfor FWM-VM 64-bit.
For licensing options contact the Sales Account team.