Please keep in mind that backups over a network that do not meet or exceed minimum requirements is not support. If there is no other solution and you must back up machines remotely, we can only suggest the following setting adjustments that may help. If they do resolve your issue, there is nothing else that we can suggest from a product point of view.
We suggest making changes to Agent settings first, as they apply to the specific Agent only. Make changes to Core settings as a last resort, as these changes affect all protected machines and can affect all jobs on the Core, not just transfers for a specific Agent.
Edit any setting by clicking on the value, increasing the timeout, and clicking the check mark to apply the change.
NOTE: Changing transfer settings on any Agent will affect that specific Agent. If editing more than one agent, all changes must be made individually per Agent.
- Open the Web UI, select the Agent you want to change, click Settings, and click Transfer.
- The following settings may be edited as needed:
- Maximum Concurrent Streams: Determines how many TCP streams of are processed in parallel.
NOTE: Maximum Concurrent Streams, Maximum Concurrent Writes, and Outstanding Reads per Stream work together to control the queuing of agents.
- Maximum Concurrent Writes: Sets the maximum number of simultaneous disk write actions per agent connection.
NOTE: This should match the Maximum Concurrent Streams.
- Maximum Segment Size: Specifies the largest amount of data, in bytes, that a computer can receive in a single TCP segment.
- Maximum Transfer Queue: Specifies the amount of commands that can be sent concurrently. You can adjust this to a higher number if your system has a high number of concurrent input/output operations.
- Outstanding Reads per Stream: Specifies how many read operations will be queued for each stream.
- Transfer Time Out: Specifies in minutes and seconds, the amount of time to allow a packet to be static without transfer.
- Snapshot Time Out: Specifies in minutes and seconds, the maximum time to wait to take a snapshot.
- Network Read Timeout: Specifies in minutes and seconds, the maximum time to wait for a read connection. If the network read cannot be performed in that time, the operation is retried.
- Network Write Timeout: Specifies the maximum time in seconds, to wait for a write connection. If the network write cannot be performed in that time, the operation is retried.
- Open the Web UI and go to Settings by clicking the "gear" icon.
- Select Client Time Out.
- Connection timeout: Timeout value for Agent-Core connection for protected agents and for Core-Core during Replication.
The maximum value is 20 minutes.
- Select Replay Engine.
- Read and Write timeout: Timeout value for reading and writing data from the Agent to the Core during transfer as well as for Replication from the Source to the Target Core.
There is no maximum value. We do recommend a setting higher than 15 minutes as this affects all transfers and all replication.
- Optional: Enable No delay by clicking on the check box and clicking the check mark to apply the change.
No delay affects the way packets are sent across the network. Under normal circumstances, network packets are held until they reach the maximum MTU size. Checking this box will prevent this from occurring, sending packets as soon as they are ready. This will not only send more packets across but will shorten the delay in receiving them. This option should be used as a last resort, as it will affect all jobs on the core.