![flashcode 2035 httpstatus 0 flashcode 2035 httpstatus 0](https://dp6mhagng1yw3.cloudfront.net/entries/4th-socialgood/1066ee2f-ad53-4048-a434-bc3b4aeb186a.jpg)
On Windows clients: The bpbkar client process is not hung. On UNIX, Linux, or Windows clients, check for the following problems with the bpbkar client process. The last file in the log is the file that causes problems. The names of the files are logged on the debug log file in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar processes them. The default for this timeout is 300 seconds.Īlso, set the File browse timeouton the Timeouts tab to a value greater than 4000. These settings are on the Universal Settings tab in the Master Server Properties dialog box. If you back up too many files, use Host Properties on the NetBackup server to change Client read timeout to a much higher value (e.g., 4000).
![flashcode 2035 httpstatus 0 flashcode 2035 httpstatus 0](https://pbs.twimg.com/media/DgDlKfiWkAArtOt.jpg)
Recommended Action: Do the following, as appropriate:
![flashcode 2035 httpstatus 0 flashcode 2035 httpstatus 0](http://aucimages.jdmvip.com/1989_NISSAN_SILVIA_KS_S13-4rDculWQanuj5T-2035/1989_NISSAN_SILVIA_KS_S13-4rDculWQanuj5T-2035-1-large.jpg)
This issue occurs only if a higher bandwidth is available between NetBackup and the cloud storage. In the media server, bpbrm logs the following: bpbrm Exit: client backup EXIT STATUS 41: network HTTP status: 503, XML response: SlowDown, RetryType: RETRY_EXHAUSTED In the media server, bptm logs the following: bptm:4940:: AmzResiliency:ĪmzResiliency::getRetryType cURL error: 0, multi cURL error: 0, The cloud vendor returns error 503 to slow down the requests and the backup job fails with the following errors: NetBackup uses the available bandwidth to it's maximum potential and pushes the requests accordingly however, the Amazon S3 compliant cloud cannot process the high number of requests. You have attempted to back up too many files using FSCP (File level fast single copy backup) with fast backup enabled. The server did not receive any information from the client for too long a period of time.