Node Swap
- Last Updated: September 18, 2026
- 1 minute read
- MOVEit Automation
- Version 2026
- Documentation
You might want to switch the roles of a primary and secondary node after a failover event. For example, if NODE1 is normally configured as the primary node and a failover promotes NODE2 to primary, you may want to return NODE1 to its original primary role after the issue has been resolved.
In a failover configuration, the secondary node periodically checks whether the primary node is available. If the primary node does not respond for an extended period, MOVEit Automation automatically promotes the secondary node to primary.
Prerequisites
Before switching node roles:
- Verify that the current primary node contains the latest task configuration.
- Run both nodes temporarily in their current roles to allow configuration and state information to synchronize between nodes. Both nodes must be running for MOVEit Automation to synchronize the state file.
- Follow the appropriate database resynchronization procedure for your environment:
Do not start the MOVEit Automation services after completing the database resynchronization procedure. Always invoke the copy function from the current secondary node.
Switch primary and secondary node roles
- Stop the MOVEit Automation service on both nodes.
- On the current primary node, open the MOVEit Automation Config utility.
- On the Failover tab, change the Startup Role setting to Secondary.
- On the current secondary node, open the MOVEit Automation Config utility.
- On the Failover tab, change the Startup Role setting to Primary.
- Start the MOVEit Automation service on the new primary node.
- Start the MOVEit Automation service on the new secondary node.
- Wait approximately five minutes and verify that the nodes have assumed their intended roles.