To configure high availability successfully, each step must be performed in order as they appear in this section. A use-case example to demonstrate the configuration process is provided following each step. The following table defines the terms used during the failover configuration process.
| Example Server Name | Server Type | Description |
|---|---|---|
| DM1 | Original-master | The system primarily used as the master system before failover occurred. Typically, the server where the primary Data Mover daemon runs, along with one Data Mover agent. |
| DM2 | Designated-slave | The slave system assigned to take responsibility as the master system if the original-master stops working. If the DM1 server fails, this is the server that becomes the next master. In the meantime, one Data Mover agent runs here. |
| DM3 | Additional agent | Server where one Data Mover agent runs. Not a slave server. |
| VP1 | Orignal-master 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 | Designated-slave 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 and initiates failover to DM1 if necessary. |