To configure high availability successfully, each step must be performed in order as they appear in this section. After each step, a use-case example to demonstrate the configuration process is provided. The following figure and table describe the terms used during the failover configuration process. 
| Example Server Name | Server Type | Description |
|---|---|---|
| DM1 | Primary (Designated-active) | The system primarily used as the active system before failover occurred. Typically, the server where the primary Data Mover ActiveMQ daemon, agent, and REST reside. |
| DM2 | Secondary (Designated-standby) | The standby system assigned to take responsibility as the active system if the primary stops working. If the DM1 server fails, this is the server that becomes the next active. In the meantime, one Data Mover agent runs here. |
| DM3 | Additional agent | Server where one Data Mover agent runs. Not a standby server. |
| VP1 | Primary server monitor | Server where the primary Data Mover monitor runs. This monitor continuously checks that DM1 is running properly and initiates failover to DM2 if necessary. |
| VP2 | Secondary server monitor | Server where the secondary Data Mover monitor runs. This monitor only becomes active if failover occurs. If failover occurs, this monitor continuously checks that DM2 is running properly. There is no failover if failure occurs. If Data Mover is configured to log to server management, TVI failure alerts are generated. |