CLIENT_READ_TIMEOUT option for NetBackup servers
The CLIENT_READ_TIMEOUT option specifies the number of seconds that NetBackup waits for a response from a client before the operation attempt fails. For example, if the master server does not get a response from a client within the CLIENT_READ_TIMEOUT period, the backup or restore operation fails.
Table: CLIENT_READ_TIMEOUT information
Usage | Description |
|---|---|
Where to use | On NetBackup master and media servers. |
How to use | Use the nbgetconfig and the nbsetconfig commands to view, add, or change the option. For information about these commands, see the NetBackup Commands Reference Guide. Use the following format: CLIENT_READ_TIMEOUT = seconds By default, CLIENT_READ_TIMEOUT is not present on the server or the database agent and the client-read timeout is 300 seconds (five minutes). This time is a reasonable default. Change only in the event of problems. CLIENT_READ_TIMEOUT on a database agent is a special case because these types of clients can initially require more time to get ready than other clients. Database backup utilities frequently start several backup jobs at the same time, which can slow the CPU. The sequence on a database agent is as follows:
Veritas recommends increasing the timeout value on the master and media server in the following situations:
Note: If using the bpstart_notify script: The Client read timeout (CLIENT_READ_TIMEOUT option) must be equal to or greater than the Backup start notify timeout (BPSTART_TIMEOUT option). If the Client read timeout is less than the Backup start notify timeout, the job can timeout while the bpstart_notify script is running. |
Example | The following example configures a client read timeout of 15 minutes. CLIENT_READ_TIMEOUT = 900 |
Equivalent Administration Console property |
Click or > Double-click on server . See Timeouts properties. |