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
  2. Veritas NetBackup™ Cloud Administrator's Guide
  3. Troubleshooting
  4. Troubleshooting cloud storage configuration issues
  5. Data restore from the Google Nearline storage class may fail
Veritas NetBackup™ Cloud Administrator's Guide

Data restore from the Google Nearline storage class may fail

Data restore from the Google Nearline storage class may fail, if your READ_BUFFER_SIZE in NetBackup is set to a value that is greater than the allotted read throughput. Google allots the read throughput based on the total size of the data that you have stored in the Google Nearline storage class.

Note:

The default READ_BUFFER_SIZE is 100 MB.

The NetBackup bptm logs show the following error after the data restore from Google Nearline fails:

HTTP status: 429, Retry type: RETRY_EXHAUSTED

Google provides 4 MB/s of read throughput per TB of data that you store in the Google Nearline storage class per location. You should change the READ_BUFFER_SIZE value in NetBackup to match it to the read throughput that Google allots.

For example, if the data that you have stored in the Google Nearline storage class is 5 TB, you should change the READ_BUFFER_SIZE value to match it to the allotted read throughput, which equals to 20 MB.

Refer to the Google guidelines, for more information:

https://cloud.google.com/storage/docs/nearline?hl=en

See Changing cloud storage server properties.

See NetBackup cloud storage server connection properties.

Feedback

Was this page helpful?
Previous

Amazon GovCloud cloud storage configuration fails in non-SSL mode

Next

Backups may fail for cloud storage configurations with Frankfurt region

Feedback

Was this page helpful?