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.

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

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

See Changing cloud storage server properties.

See NetBackup cloud storage server connection properties.