Migrating from non-object lock to object lock bucket

[shebang]

Dear community

We are looking to migrate from one bucket to another within the same private object storage platform (s3 compatible and is Veeam Ready) to allow us to configure object locking.

I have read the following article: https://helpcenter.veeam.com/docs/backu ... ml?ver=110 but just want to be clear as at the bottom, it seems to deal with moving from a bucket with versioning enabled and doesn't provide full steps.

Our object storage platform does support content versioning and object lock. We have the following plan:

1. Stop all backup operations to the bucket.
2. Create a new bucket with content versioning and object lock disabled.
2. Use AWS CLI with sync command to copy from source to destination: https://awscli.amazonaws.com/v2/documen ... /sync.html
3. Once complete, enable content versioning and object lock (but leave the default retention mode and object lock retention to none as Veeam will deal with this).
4. Replace the bucket in the SOBR policy with the new one and enable object locking.
5. Synchronise the capacity tier data: https://helpcenter.veeam.com/docs/backu ... _tier_data

Is this correct?

Thanks All!

[sfirmes]

@shebang does your object storage platform allow object lock to be enabled after a bucket is created?

[shebang]

Yes it does.

[veremin]

This scenario will be similar to the following one which we do not support:

"Versioning and Object Lock must not be enabled or disabled on buckets that have been added to Veeam Backup & Replication as it may lead to unpredictable system behavior and data loss

We've already reached the Technical Writers team to remove the misleading part (you refenced) from the documentation.

Thanks!