For sync source failovers, configure replication between the PingDirectory servers to ensure data consistency between the servers. A PingDirectoryProxy server can also front the backend PingDirectory server set to redirect traffic, if connection to the primary server fails. A PingDirectoryProxy server must be used for synchronizing changes in an entry-balancing environment. Once the primary PingDirectory server is online, it assumes control with no information loss as its state information is kept across the backend PingDirectory servers.
For sync destination failovers, connection retry logic must be implemented in the server extension, which will use the Sync Pipe’s advanced property settings to retry failed operations. There is a difference between a connection retry and an operation retry. An extension should not retry operations because PingDataSync does this automatically. However, the server extension is responsible for re-establishing connections to a destination that has gone down, or failing over to an alternate server. The server extension can also be designed to trigger its own error- handling code during a failed operation.
For PingDataSync failovers, the secondary PingDataSyncs will be at or slightly behind the state where the primary server initiated a failover. Both primary and secondary PingDataSyncs track the last failed acknowledgement, so once the primary server fails over to a secondary server, the secondary server will not miss a change.
If failover is a concern between PingDataSyncs, change the
sync-failover-polling-interval property from 7500 ms
to a smaller value. This will result in a quicker failover, but will
marginally increase traffic between the two PingDataSyncs. The
sync-failover-response-timeout properties may also be
updated to use different failover timeout durations. Use
dsconfig to access the property on the Global Sync