DeviceLock Enterprise Server : Consolidating Logs : Administering the Consolidation of Logs : Retry parameters
  
Retry parameters
When you click Advanced Settings in the dialog box for log consolidation settings, the console opens a dialog box to view, set, or change parameters of retries of data exchange in case of failure in the communication channel between the consolidation servers:
Number of retries - Specifies the maximum number of times to retry data exchange in a situation where the remote server cannot reach the central collection server or the central server fails to collect logs from the remote server. If this parameter is set to 0, no retries of data exchange are performed.
Retry timeout - Specifies the time interval between successive attempts to exchange data between the servers. In the event of a communication failure, the server waits the specified number of seconds before attempting to communicate again.
Different remote servers may have different retry parameters. The remote server employs its retry parameters when issuing a consolidation request to the central collection server. If the request is successful, the same parameters are then used by the central server when collecting logs from the respective remote server.
When configuring retry parameters, consider how data exchange retries are related to the regular log collection on a schedule:
The retry count is reset only upon successful data exchange. If the specified number of retries were made and all of them were not successful, then, until the logs are successfully submitted to the central collection server, attempts of their transmission occur only on a schedule, without retries in case of communication failure between the servers. Retries can be resumed only after the logs are successfully collected.
The regular log collection on a schedule takes precedence over retries. When a retry is scheduled on a later time than the start of a regular log collection session, the session will start according to the schedule, regardless of the scheduled retry. In this case, if the session fails, the retry will occur on the lapse of the retry timeout after session start.