The process of moving your FlowTraq install from one platform to another, particularly between operating systems, is straighforward but requires attention to several details. Follow these steps for each host in the cluster to be migrated, starting with the workers and ending with the portal.
Determine the new locations of the FlowTraq databases (SESSIONDB and ARCHIVEDB), particularly if they are going to reside on separate disks from the FlowTraq install. Ensure that all disks have sufficient capacity to store FlowTraq's data when full. (Note that without the SESSIONDB directory, the main FlowTraq install directory may still require up to 70GB of space.)
Plan for the process of moving the backed-up data either directly from the old FlowTraq host or from backup, and for IP migration if necessary.
Install FlowTraq on the new host (no license key is needed) so that the installer for that operating system can create any necessary directories, scripts, and keys. Mount all drives and create database directories as needed.
Make a full or partial backup of the original FlowTraq install according to the backup instuctions in the previous section, shutting down the FlowTraq daemon in the process. The choice of full or partial backup depends upon whether the full-fidelity session data is to be preserved. Either copy the backed-up files to storage, or move them directly to their final locations on the new host. Do not restart FlowTraq on the original host after the process is complete.
![[Important]](../common/images/admon/important.png)
Important Do not overwrite the FlowTraq binary on the new host if at all possible. If the binary is accidentally overwritten, complete the remaining steps, and then run the FlowTraq installer script again. It will ensure that the correct binary is in place.
Start the FlowTraq process on the new host and monitor the flowtraq.log file for error messages.
Once you have verified the success of the migration, the original host may be decommissioned if desired, or the uninstall routine may be run so that the old hardware can be repurposed without the old copy of FlowTraq using resources.
Make any necessary IP changes on the new host.
When all hosts have been migrated, check the Cluster page in the FlowTraq UI to ensure connectivity among all nodes. Missing nodes may still be starting up, may not have the expected IP addresses, may be unreachable from the portal, or may have out-of-date licenses.
