Unstructured Data Backup from Google Cloud Storage fails with a Bad Request error

Identify the affected file

The error includes an ObjectPath: value that identifies the specific file triggering the issue. This value is recorded in the Master Agent log on the cache repository assigned to the source. To locate the log:

1. In the Veeam Backup & Replication console, navigate to Inventory and locate the Google Cloud Storage source under Unstructured Data.
2. Open the properties of the Google Cloud Storage and check the cache repository selected for object storage processing.
3. Navigate to Backup Infrastructure > Repositories and identify the host assigned to the cache repository.
4. Connect to the host used as a cache repository.
5. Open the Master Agent log file. The default location is:

   C:\ProgramData\Veeam\Backup\<jobname>\Agent.<jobname>.Master.log
   

6. In the log, find the error entry with the ObjectPath: value. This value contains information on the specific file in the bucket causing the issue.
   
   Example:

   nasbackup| WARN|Failed to complete backup items
   nasbackup| >>  |Bad Request
   nasbackup| >>  |--tr:Failed to download file part. [StorageName: [S3], Bucket: [], Delimiter: /], ObjectPath: [], VersionId: [], Offset: [0], Count: [1114610]
   nasbackup| >>  |--tr:Failed to read S3 object. Object: [[CS3DataReadStream]. ObjectPath: [Path: [], Delimiter: /, Type: [EObject (1)]], ObjectSize: [1114610], Validator: [Path: [Path [|], Nodes: [[]], Nodes count: 1, RootId [0000000000000000]], Size: [1114610], Modification time: [2019-08-31 20:19:23.000 (132117563630000000)]], VersionId: [undefined], KeepVersionId: [true]], Offset: [0], Data size: [8388608], Stream validator:: [Path: [Path [|], Nodes: [[]], Nodes count: 1, RootId [0000000000000000]], Size: [1114610], Modification time: [2019-08-31 20:19:23.000 (132117563630000000)]]
   nasbackup| >>  |--tr:Failed to read from block stream. Requested offset: [0], Requested size: [131072], BlockIo read stream: [BlockIoFs read stream. Current offset: [0], Preloaded data size: [0], Was EOF: [false]]
   nasbackup| >>  |--tr:Failed to initialize primary stream ([EFileContent:0])
   nasbackup| >>  |--tr:Rethrowing remote exception
   nasbackup| ERR |Register critical error. Stop further processing. Error info: [Error [0]:
   nasbackup| >>  |Failed to complete backup items
   

Determine whether a workaround is applicable

• If the file is a valid gzip file, this behavior is expected. Support for this scenario is planned for a future release of Veeam Backup & Replication. No workaround is available at this time.
• If the file has a non-gzip extension, it was likely uploaded with an incorrect Content-Encoding: gzip metadata tag. The method described in the next section can be used to download and re-upload the file.

4. Re-run the Unstructured Data Backup job.