Resynchronization for MSSQL

You might need to resynchronize the two nodes under certain conditions. For example, after a failover, if the former secondary has become primary, you might want to force the original primary to be primary again. Follow these instructions to resynchronize the nodes on an MSSQL system:

1. Stop MOVEit Automation service on the current secondary node.
2. Stop MOVEit Automation service on the current primary node (using MOVEit Automation Admin's "Shut Down Service" command if tasks could be running).
3. If you are resynchronizing manually, copy the following items from the most up-to-date node to the other node, otherwise proceed to step 4.
   • miccfg.xml config file
   • state files folder
   • PGPpath folder
4. On the desired new primary node, run the MOVEit Automation configuration utility and:
   1. Set the startup role to primary.
   2. Choose the "Clear Admin Rep" button.
5. On the desired new secondary node, run the MOVEit Automation configuration utility and:
   1. Set the startup role to secondary.
   2. Choose the "Clear Admin Rep" button.
6. Start MOVEit Automation service on the new primary node.
7. To verify that the presumed primary node is the primary node, connect using the Admin Console. If a connection warning messages displays, retry after a few minutes.
8. Start MOVEit Automation service on the new secondary node.