MOVEit Automation has the capability of running in failover mode, in which one server automatically stands in for another if the first one fails.
NOTE: This information describes the Legacy Failover system, which has been replaced by the Ipswitch Failover Manager. The Ipswitch Failover Manager is available. It requires a separate installation and managed externally. For more information, go to the Ipswitch support site, and under Secure Information and File Transfer, in the dropdown box, select Ipswitch Failover.
Ipswitch will continue to support Legacy Failover installations for MOVEit Automation. The Legacy Failover system is built into MOVEit Automation. The Legacy Failover system is included in the MOVEit Automation documentation. The new Ipswitch Failover system is documented separately; see the above link.
The Failover tab is used to configure the Failover capability of MOVEit Automation. This tab is grayed out unless you have entered a license key that enables failover. Sites which have not licensed failover can ignore this tab.
The settings on this tab are:
This node
Startup role. This is the role that this node will assume when MOVEit Automation starts. When installing failover for the first time, you should set one node to be Primary and the other node to be Secondary. Subsequently, MOVEit Automation itself will manage this value on the two nodes when a failover occurs.
Node number. This is 0, 1, or 2. 0 disables the failover feature even if you have a license for failover. To enable failover, assign the number 1 to one node, and 2 to the other node. The numbers 1 and 2 have no special significance; however, by convention, the value 1 is typically given to the node that is initially assigned the primary role, and the value 2 is given to the node initially assigned the secondary role.
Nodes to ping. This is an optional comma-separated list of nodes that MOVEit Automation should "ping" before assuming the primary role. If this list is empty, no ping test is done. If the list is not empty, at least one of the nodes must respond to a ping before MOVEit Automation will start running tasks. The purpose of this feature is to prevent two copies of MOVEit Automation from each thinking the other is down because the network between them is down. To take best advantage of this feature, you should enter the hostname of one or more computers that reside on the same network as the other node.
It is recommended that the value of a "nearby" and trusted router be configured in this field. If you do not have a dedicated network device which fits the bill, it is probably best to leave this value blank.
Other node
Hostname or IP. The hostname or IP address of the other node.
MOVEit Admin user. The Windows user on the other node which MOVEit Automation should use to login to the other node. You must create this user on the other node, and make it a member of the "MOVEit Admin" group. It does not need to be a member of the "Users" group. You might want to follow the convention of using the username "micfailover" on both nodes.
Password. The password of the above user. This password is stored in the registry, using 256-bit AES encryption.
The buttons on this tab are typically used only during a resynchronization operation after MOVEit Automation has been stopped:
Clear Admin Rep... This erases any MOVEit Automation Admin commands that are scheduled to be replicated from this node to the other node. It does this by deleting the MICMisc.blg file. (A new blank file will be created automatically when MOVEit Automation is next started.)
Clear SQL Rep... This erases any SQL statements that are scheduled to be replicated from this node to the other node. It does this by deleting the MICSQL.blg file. (A new blank file will be created automatically when MOVEit Automation is next started.)
Copy Database... This allows you to copy the MICStats database from the other node to this node. This process overwrites the current node's statistics database with the contents of the other node's database. This operation should ordinarily be performed only on the secondary node.
You need to do a Copy Database on the secondary node when you first install the secondary node. You may also perform this operation subsequently if the database on the current node has gotten out-of-sync with the one on the other node.
When you choose Copy Database, you will be prompted for the remote directory from which to copy the database files, and the local directory to which you should copy them. The program's initial defaults assume that you have installed MySQL on C: and that you are using the default database name. Check the suggested paths and, if necessary, correct them for your installation before choosing OK to start the copy. The configuration program will remember the changed values the next time you choose Copy Database.
The Copy Database command requires that there be a Windows user on the remote node with the same username and password as the session under which you are running the configuration program. This user must have read access to the files in the MySQL\Data\micstats directory.
Please note that if you change the IP address of the other MOVEit Automation node in this dialog, the Copy Database parameters will not automatically pick up on the change. If, however, you are using hostnames to define your other host, you may not need to make a change here.
