Hello world have a nice day.
Recently I'm facing an issue, I created a backup job to backup a VMware machine, I have created one backup repository on a compatible S3 bucket (not as SOBR), and in this job I have selected the -Retention Policy "8" restore points-.
The problem is this one:
Some backup chain does not have the Full Backup any more, I mean does not exist.
But on other backup chain the Full backup exist.
On both cases when I try to recover one incremental backup the process ends and send the follow error:
Some one of you do you know
1) How this policy works mainly on a S3 compatible bucket as backup repository?
2) Is there any special configuration that we should do to prevent that the backup chain be deleted?
3) Why this could happening?
4) any idea about the root cause.
Thanks in advance to all of you.
Recently I'm facing an issue, I created a backup job to backup a VMware machine, I have created one backup repository on a compatible S3 bucket (not as SOBR), and in this job I have selected the -Retention Policy "8" restore points-.
The problem is this one:
Some backup chain does not have the Full Backup any more, I mean does not exist.
But on other backup chain the Full backup exist.
On both cases when I try to recover one incremental backup the process ends and send the follow error:
Code:
<VCPCommandResult result="false" exception='S3 error: The specified key does not exist.
Code: NoSuchKey
--tr:Request ID: xxxx Other: HostId: '9m2RW/K/vXXAlQbdvaNp+J4fX12C0PGZimFCMW0Q3ZO4Ezsf6YLgPDBuiThKW7RX', Key: 'Veeam/xx/xx/Clients/{xxx-27b9-4836-ba85-60e4db4f7ba3}/xxx-9bdc-458b-9ec3-d4934ee72067/CloudStg/Meta/Crypto/{xxxx-219e-42de-8916-6fba1b509a4c}.{xxxx-15ba-4e53-99ed-2b2be1ead27a}'
--tr:CS3CloudClient::DownloadFileAsyncImpl async task has failed, path [/Veeam/Backup/xxxx/Clients/{xxx-27b9-4836-ba85-60e4db4f7ba3}/xxxx-9bdc-458b-9ec3-d4934ee72067/CloudStg/Meta/Crypto/{86ca0e1e-219e-42de-8916-6fba1b509a4c}.{4e3f57d4-15ba-4e53-99ed-2b2be1ead27a}], offset [0], length [0]
Storage chain is corrupted. Some objects are missing.
Failed to load object. Object path: [/Meta/Crypto/{xxxx-219e-42de-8916-6fba1b509a4c}.{xxxxx-15ba-4e53-99ed-2b2be1ead27a}], version: [].
--tr:Failed to access to existing storage ID: [{xxxx-219e-42de-8916-6fba1b509a4c}], Path: [FsPath: <Path ConnId="4241ee6d-e304-4fdc-8bf4-36c777087e38"BackupId="dd82bcab-9bdc-458b-9ec3-d4934ee72067" StgId="{xxxxx-219e-42de-8916-6fba1b509a4c}" LocalPath="" Tag="DSH_sicotrac2.vm-6823D2025-08-04T020758_99B6.vbk"/> Platform: cloud].
--tr:Failed to access to existing storage ID: [{xxxxx-219e-42de-8916-6fba1b509a4c}], Path: [FsPath: <Path ConnId="4241ee6d-e304-4fdc-8bf4-36c777087e38" BackupId="xxxxx-9bdc-458b-9ec3-d4934ee72067" StgId="{xxxxx-219e-42de-8916-6fba1b509a4c}" LocalPath="" Tag="DSH_sicotrac2.vm-6823D2025-08-04T020758_99B6.vbk"/> Platform: cloud].
--tr:Cannot apply patches stored in folder [cloud://<Path ConnId="4241ee6d-e304-4fdc-8bf4-36c777087e38"BackupId="dd82bcab-9bdc-458b-9ec3-d4934ee72067" StgId="{xxxx-219e-42de-8916-6fba1b509a4c}" LocalPath="" Tag="DSH_sicotrac2.vm-6823D2025-08-04T020758_99B6.vbk"/>[9a74314f-7898-4efc-8d42-395a5bd623c5 (vm-6823)]].
--tr:Failed to build restore point.
Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{22dbb04c-4bc3-40f0-88c0-e442f9056a30}]. CHMOD mask: [0].
Agent failed to process method {DataTransfer.RestoreText}.' />1) How this policy works mainly on a S3 compatible bucket as backup repository?
2) Is there any special configuration that we should do to prevent that the backup chain be deleted?
3) Why this could happening?
4) any idea about the root cause.
Thanks in advance to all of you.
Statistics: Posted by fga_fer — Aug 19, 2025 9:55 pm