Loading...
Loading...
An Unstructured Data Backup of data from Google Cloud Storage added to Veeam Backup & Replication as an S3-Compatible Object Storage data source fails with the following error: Failed to perform object backup Error: Agent: Failed to process method {NasMaster.ExecuteBackupProcessor}: Failed to complete backup items
This issue is caused by a Google Cloud Storage feature called Decompressive Transcoding, which automatically decompresses gzip-encoded objects during download. This behavior is not part of the S3 specification and is not supported when Google Cloud Storage is added as an S3-Compatible Object Storage to the inventory of the backup server. When decompressive transcoding is triggered, the backup session fails with a Bad Request error. The issue can occur in two scenarios: A file in the bucket is a valid gzip file, and Google Cloud Storage decompresses it transparently during the backup read, producing an unexpected response. A file was uploaded with Content-Encoding: gzip in its metadata even though the file itself is not gzip-compressed, causing Google Cloud Storage to attempt decompressive transcoding on a file that does not require it.
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: In the Veeam Backup & Replication console, navigate to Inventory and locate the Google Cloud Storage source under Unstructured Data. Open the properties of the Google Cloud Storage and check the cache repository selected for object storage processing. Navigate to Backup Infrastructure > Repositories and identify the host assigned to the cache repository. Connect to the host used as a cache repository. Open the Master Agent log file. The default location is: C:\ProgramData\Veeam\Backup\<jobname>\Agent.<jobname>.Master.log 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
Google Documentation: Decompressive Transcoding Google Documentation: Installing the Google Cloud CLI
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.