Client failback
- Last UpdatedJan 11, 2023
- 1 minute read
Depending on how the client connection is configured, failback automatically switches the client back to either the primary server of the Data Archive collective or a server with a higher connection priority value.
Failover occurs when the primary Data Archive server for the client becomes unavailable. When this occurs, the client automatically connects to another server within the collective to minimize the disruption for the client.
Failback attempts to restore the client connection back to the original server before the disruption and failover occurred, depending on the configurations set for the connection. If the client connection is set to prefer the primary server, it checks for the primary server to become available and switches to that server. If the connection preference is set to any, the client connection checks for any server with a higher connection priority value available and switches to that server.