Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  3. NetBackup™ for Cloud Object Store Administrator's Guide
  5. Troubleshooting
  7. Restore fails: "Error bpbrm (PID=3899) client restore EXIT STATUS 40: network connection broken"
NetBackup™ for Cloud Object Store Administrator's Guide

Restore fails: "Error bpbrm (PID=3899) client restore EXIT STATUS 40: network connection broken"

Explanation

Delay in accessing the backup image and uploading the blobs for the restore. In this process, the bptm is getting timed out.

Workaround

If restore fails with a network error message in the Activity monitor, change the system configuration time-out to 900/1200 or the appropriate high value, in seconds. Start a new restore job.

Steps to set a time-out are as follows: On the left, click Hosts > Host properties > Select Primary/ Media server > select the Time-out option > set the time-out value -> click Save. Refer to the Web UI Administrator Guide for details.

Feedback

Was this page helpful?
Previous

Recovery Job does not start

Next

Access tier property not restored after overwriting the existing object in the original location

Feedback

Was this page helpful?