[AWS S3] Backup copy issue

[AbdelO]

Hello,

We have set up VBR with a scale out on an AWS S3 bucket. We have set up backup copy to our S3 storage and we have errors can't figure out:

Code: Select all

5/23/2022 2:59:22 PM :: Processing <SERVER> Error: resolve: No such host is known
--tr:Unable to connect to target endpoint.
--tr:The client failed to process the command. Command: [connectByIPs].
--tr:event:1 :
--tr:event:3:

5/23/2022 6:36:48 AM :: Querying extents in scale-out backup repository.  

23/5/2022 6:37:38 AM :: Error: No scale-out repository extension has enough disk space to store the backup file. 

5/23/2022 6:41:49 AM :: Resource not ready: Backup Repository  

While on the AWS S3 side everything is ok.

Thanks in advance for your help.

Regards

[jorgedlcruz]

Hello,
I would totally recommend you open a support ticket, so one of our Support Engineers helps you to understand, and debug the issue. Also, which version of Veeam are you?

That error I have seen before, and following the next KB helped that Customer, but as said, please review, read, and understand the KB, and maybe double-check with Support.

Please let us know your Case Number so we can follow it as well.

[veremin]

Might be a stupid question - but do you performance extents have enough space to host backup copy job restore points? Backups need to land on Performance Tier first, before they get offloaded to Capacity Tier. Thanks!

[AbdelO]

So I just checked, indeed my extents in "Performance tier" (95GB) does not have enough space for the job I want to copy (720GB). That would mean that I must have as much space on my extents as my copy backup before it sends them to my "Capacity Tier"?

I thought that in the "Performance tier" it was only metadata that was stored and that the data goes directly into my S3 bucket? (Like on VBO365)

Thanks in advance.

[veremin]

Nope, the backup data lands first on Performance Tier and then gets moved or copied to Capacity Tier, based on the policy type.

You might want to check the corresponding section of our User Guide and get familiar with how the feature works.

Thanks!