Veeam version 12.3.1 and later enable Automatic Bucket Creation by default when you add an S3 compatible bucket as a repository.
We suggest using repositories that do NOT have this feature enabled until full compatibility has been established with Cloud IBR. If you wish to test with this new feature, following is an experimental workaround that can be used for testing but should not be used to recover your production backups.
- Open a ticket within the Cloud IBR portal asking for your account to have the read-write key override enabled.
- Once you receive confirmation we have enabled the override, delete your bucket from the Cloud IBR portal and add it back with your root read-write key to ensure Cloud IBR has access to the bucket you created as well as all the buckets that Veeam automatically creates.
- Follow steps below to ensure your test backups continue running.
TO ENSURE YOUR BACKUPS RUN PROPERLY AFTER EACH RECOVERY TEST:
View this kb article for instructions: https://cloudibr.com/kb/using-read-write-access-keys-for-object-storage/
We also encourage you to open a ticket with Veeam requesting that they allow the use of read-only keys on the auto created buckets.
Note: One customer told us that Automatic Bucket Creation is enabled when you add Wasabi Object Storage and there is no way to disable it. The resolution is to add the Wasabi repository using the “S3 Compatible” option on your Veeam server, instead of choosing Wasabi, which will display the option to disable Automatic Bucket Creation.