HA Restrictions/Requirements

  • The ftmssvr.exe service must run under a user account that has full access to the haRoot shared network folder.

  • All the ftmssvr.exe apps in a HA cluster must be in the same Windows domain.

  • All the ftmssvr.exe apps in a HA cluster can connect with each other. There is no firewall restrictions on the rpc port 6678 between the HA machines.

  • All the ftmssvr.exe apps in a HA cluster should be configured similarly and have the same protocols. It is a good practice to keep the Dispatcher Cycle on all machines in a HA cluster to be the same. If you plan on using SSL or TLS transfers to a HA cluster, it is recommended to keep all keys in the same folder. For example, HaRoot/config or HaRoot/config/Tls.

  • All ftmsmgr.exe and cfinq.exe apps have read access to the haRoot/servers folder.

  • All cfinq.exe apps have a read access to the haRoot/log folder.

  • All cfinq.exe act command run under an admin account.

  • All cfinq.exe act command have a read/write access to the haRoot/active folder.

  • cfsend/ftmscmd can perform submit operation to primary HA server in the HA mode. However, transfers submitted to the secondary server will be routed to the primary server to be executed.

  • Command Center transfer requests to a non-primay server will be redirected to the primary server.

  • You might need to reset your MFT Command Center Collector after you migrated to HA mode and started using new log files and new transnum file.

  • If one primary ftmssvr.exe app is parsing DNI folders and stops running, and another ftmssvr.exe becomes the primary, it should have read/write access to those folders as well.