Fortinet white logo
Fortinet white logo

Migrating from FortiWLM 32-bit to FortiWLM 64-bit

Migrating from FortiWLM 32-bit to FortiWLM 64-bit

To use new features and retain data, when upgrading from pre-8.4, perform this procedure to migrate a FortiWLM 32-bit to a 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.

Virtual FortiWLM

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.

  1. Backup the data in 32-bit FortiWLM and copy it using the copy scp/ftp command.
  2. Install the 64-bit FortiWLM image; use the forti-wlm-x.x-xbuild-y-x86_64.ova file.
  3. Shutdown the 32-bit FortiWLM instance.
  4. 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>
FortiWLM Hardware (FortiWLM-100D/1000D)

It is recommended to upgrade pre-8.6.3 FortiWLM 32-bit to 8.6.3 FortiWLM 32-bit and then migrate to the current release.

  1. Backup the data in 32-bit FortiWLM and copy it using the copy scp/ftp command.
  2. Contact the Fortinet Customer Support team to migrate from FortiWLM 32-bit to 64-bit.
  3. 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 FortiWLM 64-bit requires a new license file to be installed on FortiWLM 64-bit.
  • Migration from FortiWLM 32-bit to FortiWLM 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 required for FortiWLM 64-bit.

For licensing options contact the Sales Account team.

Migrating from FortiWLM 32-bit to FortiWLM 64-bit

Migrating from FortiWLM 32-bit to FortiWLM 64-bit

To use new features and retain data, when upgrading from pre-8.4, perform this procedure to migrate a FortiWLM 32-bit to a 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.

Virtual FortiWLM

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.

  1. Backup the data in 32-bit FortiWLM and copy it using the copy scp/ftp command.
  2. Install the 64-bit FortiWLM image; use the forti-wlm-x.x-xbuild-y-x86_64.ova file.
  3. Shutdown the 32-bit FortiWLM instance.
  4. 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>
FortiWLM Hardware (FortiWLM-100D/1000D)

It is recommended to upgrade pre-8.6.3 FortiWLM 32-bit to 8.6.3 FortiWLM 32-bit and then migrate to the current release.

  1. Backup the data in 32-bit FortiWLM and copy it using the copy scp/ftp command.
  2. Contact the Fortinet Customer Support team to migrate from FortiWLM 32-bit to 64-bit.
  3. 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 FortiWLM 64-bit requires a new license file to be installed on FortiWLM 64-bit.
  • Migration from FortiWLM 32-bit to FortiWLM 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 required for FortiWLM 64-bit.

For licensing options contact the Sales Account team.