{page-title}
At times it may be necessary to increase the amount of time the Server Backup Manager waits for the agent to respond. The default timeout is 30 minutes.
Increasing the timeout can be helpful when backing up larger partitions with large block maps, or when backing up extremely busy servers.
{color:windowtext}Additionally{color}{color:windowtext}, replication tasks may fail with an error similar to :{color}{color:windowtext} {color}
{code}Could not complete backups on any devices deleting recovery point #XXX
Socket timed out after waiting for more than 1,800 seconds to read/write{code}
h2. Solution
----
h5. 1. {color:#000000}Edit the following file on the Backup Manager:{color}
{code}/usr/sbin/r1soft/conf/server.properties{code}
h5. 2. {color:windowtext}Change the following line to adjust the timeout:{color}{color:windowtext} {color}
{code}agent-network-connection-timeout=1800{code}
{info}The default timeout is 1800 seconds. When increasing the timeout to correct a failing backup, we recommend starting with double the default number of seconds. If more time is needed double the number of seconds again until the backup completes successfully.{info}
h5. 3. {color:#000000}Save and exit the file.{color}
h5. {color:#000000}4. {color}{color:#000000}Restart the Backup Manager:{color}
{color:#000000}Place the SBM in{color} {color:#000000}[maintenance mode|ServerBackupManager:Manager Options]{color} {color:#000000}and allow all tasks to complete. T{color}{color:#000000}hen execute the appropriate service restart command for your operating system.{color}
{code}# /etc/init.d/cdp-server restart
OR
# service cdp-server restart
OR
# systemctl restart sbm-server{code}
{kb-related-articles}
At times it may be necessary to increase the amount of time the Server Backup Manager waits for the agent to respond. The default timeout is 30 minutes.
Increasing the timeout can be helpful when backing up larger partitions with large block maps, or when backing up extremely busy servers.
{color:windowtext}Additionally{color}{color:windowtext}, replication tasks may fail with an error similar to :{color}{color:windowtext} {color}
{code}Could not complete backups on any devices deleting recovery point #XXX
Socket timed out after waiting for more than 1,800 seconds to read/write{code}
h2. Solution
----
h5. 1. {color:#000000}Edit the following file on the Backup Manager:{color}
{code}/usr/sbin/r1soft/conf/server.properties{code}
h5. 2. {color:windowtext}Change the following line to adjust the timeout:{color}{color:windowtext} {color}
{code}agent-network-connection-timeout=1800{code}
{info}The default timeout is 1800 seconds. When increasing the timeout to correct a failing backup, we recommend starting with double the default number of seconds. If more time is needed double the number of seconds again until the backup completes successfully.{info}
h5. 3. {color:#000000}Save and exit the file.{color}
h5. {color:#000000}4. {color}{color:#000000}Restart the Backup Manager:{color}
{color:#000000}Place the SBM in{color} {color:#000000}[maintenance mode|ServerBackupManager:Manager Options]{color} {color:#000000}and allow all tasks to complete. T{color}{color:#000000}hen execute the appropriate service restart command for your operating system.{color}
{code}# /etc/init.d/cdp-server restart
OR
# service cdp-server restart
OR
# systemctl restart sbm-server{code}
{kb-related-articles}