Failed to save object storage repository: The request is rejected because of object replication policy

[TRE3]

Hi Veeam Forum,

we try to add an existing Azure Capacity Tier repository to a new Veeam installation (for recovery testing purposes). The Azure container that we want to add as object repository has been replicated (exact copy) by an Azure object replication policy from another Azure tenant / storage account / container. The error message we receive when adding this replicated container is this one:

Code: Select all

25.03.2024 10:46:10 Error    Failed to save object storage repository: The request is rejected because of object replication policy.
                             CAzureCloudClientImpl::CreateFolderAsync async task has failed, path [/Veeam] Details: HTTP code: 409, Content Length: 247, Code: OrsPolicyConflict, Error: The request is rejected because of object replication policy.
                             RequestId:b60553f9-e01e-0086-5499-7e886c000000
                             Time:2024-03-25T09:46:09.2897680Z
25.03.2024 10:46:10 Error    Infrastructure item save failed Error: The request is rejected because of object replication policy.
                             CAzureCloudClientImpl::CreateFolderAsync async task has failed, path [/Veeam] Details: HTTP code: 409, Content Length: 247, Code: OrsPolicyConflict, Error: The request is rejected because of object replication policy.
                             RequestId:b60553f9-e01e-0086-5499-7e886c000000
                             Time:2024-03-25T09:46:09.2897680Z

My question is: Do we have to remove the object replication policy in order to use this container in Veeam or is there a workaround or is it not possible to use a replicated container with Veeam?

Tom

[Mildur]

Hello TRE3

Lifecycle policies is not supported by our products. Which is stated in our user guide:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Also we don't test such scenarios where external tools are doing the replication outside of Veeam Backup & Replication.

Is the replicated Azure Container writable or is it a read only copy? We cannot work with read only Azure containers. It must be writable.

Best,
Fabian

[TRE3]

Hi Mildur,

it's an object replication policy (not lifecycle policy) but I see the problem. When replication of containers is active, the target container is read-only. But when disabling replication (just delete the policy), you can add the container as writable Azure object storage repository in Veeam. Thanks for the hint!

Tom