Timeouts properties
To access this setting, in the web UI select . Select the server or client. If necessary click , then click , , or . Click .
The Timeouts properties apply to the selected primary server, media server, or client.
Table: Timeouts host properties
Property | Description |
|---|---|
Client connect timeout | This property applies to the currently selected server. Specifies the number of seconds the server waits before it times out when it connects to a client. The default is 300 seconds. |
Backup start notify timeout | This property applies to the currently selected server . Specifies the number of seconds the server waits for the bpstart_notify script on a client to complete. The default is 300 seconds. 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 time out while the bpstart_notify script is running. |
Media server connect timeout | This property applies to the currently selected server . Specifies the number of seconds that the primary server waits before it times out when it connects to a remote media server. The default is 30 seconds. |
Client read timeout | This property applies to the currently selected server or client. Specifies the number of seconds that NetBackup waits for a response from a client before the operation attempt fails. This timeout can apply to a NetBackup primary, remote media server, or database-extension client (such as NetBackup for Oracle). The default is 300 seconds. If the server does not get a response from a client within the Client read timeout period, the backup or the restore operation can fail. See Recommendations for the . The sequence on a database-extension client is as follows:
|
Backup end notify timeout | This property applies to the currently selected server. Specifies the number of seconds that the server waits for the bpend_notify script on a client to complete. The default is 300 seconds. Note: If this timeout is changed, verify that Client read timeout is set to the same or higher value. |
Use OS dependent timeouts | This property applies to the currently selected server or client. Specifies that the client waits for the timeout period as determined by the operating system when it lists files, as follows:
File browse timeout Specifies how long the client can wait for a response from the NetBackup primary server while it lists files. If the limit is exceeded, the user receives a socket read failed error. The timeout can be exceeded even while the server processes the request. Note: If it exists, the value in a UNIX client's $HOME/bp.conf file takes precedence to the property here. |
Media mount timeout | This property applies to the currently selected primary server. Specifies how long NetBackup waits for the requested media to be mounted, positioned, and ready on backups, restores, and duplications. Use this timeout to eliminate excessive waiting time during manual media mounts. (For example, when robotic media is out of the robot or is off-site.) |
It is recommended to increase the timeout value in the following situations:
The client-read timeout on a database-extension client is a special case. Clients can initially require more time to get ready than other clients. More time is required because database backup utilities frequently start several backup jobs at the same time, slowing the central processing unit. A setting of 15 minutes is adequate for many installations.
Backing up directly to an MSDP cloud storage server. If the value is not increased for both the primary server and the media server, you may see jobs failing with the following message in the job details:
Error bpbrm (pid=119850) socket read failed: errno = 62 - Timer expired
Note that increasing the timeout is not needed it you use a storage lifecycle policy to first back up to an MSDP storage server and then duplicate the data to an MSDP cloud storage server using an optimized duplication operation. (This operation is the recommended method of operation.)
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.