Discussions related to using object storage as a backup target.
Post Reply
fga_fer
Influencer
Posts: 10
Liked: never
Joined: Apr 29, 2024 5:55 pm
Full Name: Fer Garcia
Contact:

Retention policy as recover point - issue

Post by fga_fer »

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:

Code: Select all

<VCPCommandResult result="false" exception='S3 error: The specified key does not exist.&#x0A;Code: NoSuchKey&#x0A;--tr:Request ID: xxxx Other: 
HostId: &apos;9m2RW/K/vXXAlQbdvaNp+J4fX12C0PGZimFCMW0Q3ZO4Ezsf6YLgPDBuiThKW7RX&apos;, Key: &apos;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}&apos;&#x0A;--
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]&#x0A;Storage chain is corrupted. 
Some objects are missing.&#x0A;Failed to load object. Object path: [/Meta/Crypto/{xxxx-219e-42de-8916-6fba1b509a4c}.{xxxxx-15ba-4e53-99ed-2b2be1ead27a}], 
version: [].&#x0A;--tr:Failed to access to existing storage ID: [{xxxx-219e-42de-8916-6fba1b509a4c}], Path: [FsPath: &lt;Path ConnId=&quot;4241ee6d-e304-4fdc-8bf4-36c777087e38&quot;
BackupId=&quot;dd82bcab-9bdc-458b-9ec3-d4934ee72067&quot; StgId=&quot;{xxxxx-219e-42de-8916-6fba1b509a4c}&quot; LocalPath=&quot;&quot; Tag=&quot;
DSH_sicotrac2.vm-6823D2025-08-04T020758_99B6.vbk&quot;/&gt; Platform: cloud].&#x0A;--tr:Failed to access to existing storage ID: [{xxxxx-219e-42de-8916-6fba1b509a4c}], 
Path: [FsPath: &lt;Path ConnId=&quot;4241ee6d-e304-4fdc-8bf4-36c777087e38&quot; BackupId=&quot;xxxxx-9bdc-458b-9ec3-d4934ee72067&quot; 
StgId=&quot;{xxxxx-219e-42de-8916-6fba1b509a4c}&quot; LocalPath=&quot;&quot; Tag=&quot;DSH_sicotrac2.vm-6823D2025-08-04T020758_99B6.vbk&quot;/&gt; 
Platform: cloud].&#x0A;--tr:Cannot apply patches stored in folder [cloud://&lt;Path ConnId=&quot;4241ee6d-e304-4fdc-8bf4-36c777087e38&quot;
BackupId=&quot;dd82bcab-9bdc-458b-9ec3-d4934ee72067&quot; StgId=&quot;{xxxx-219e-42de-8916-6fba1b509a4c}&quot; LocalPath=&quot;&quot; 
Tag=&quot;DSH_sicotrac2.vm-6823D2025-08-04T020758_99B6.vbk&quot;/&gt;[9a74314f-7898-4efc-8d42-395a5bd623c5 (vm-6823)]].&#x0A;--tr:Failed to build restore point.&#x0A;
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].&#x0A;Agent failed to process method {DataTransfer.RestoreText}.' />
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.
karsten123
Service Provider
Posts: 634
Liked: 157 times
Joined: Apr 03, 2019 6:53 am
Full Name: Karsten Meja
Contact:

Re: Retention policy as recover point - issue

Post by karsten123 »

open a Veeam support case. and please do not post logs.

what exactly is this S3 compatible system and how did you configure it?
Mildur
Product Manager
Posts: 10761
Liked: 2930 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Retention policy as recover point - issue

Post by Mildur »

Hi FGA

Please do not upload logs to our forum. Additionally, Every forum topic about a technical issue must provide a support case number or the topic may be deleted.

Missing/corrupted objects could been caused by lifecycle policies on the object storage side. These policies are not supported and will lead to backup and restore issues.

Therefore please open a case, and provide us with your case number.

Best,
Fabian
Product Management Analyst @ Veeam Software
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests