#1 in Disaster Recovery for Backups
Try It For Free
Book A Demo

No servers restored from repository with Automatic Bucket Creation enabled

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.

THE VBR BUILT BY CLOUD IBR AT TIME OF RECOVERY WILL “TAKE OVER MANAGEMENT” OF YOUR REPOSITORY DUE TO USING A READ-WRITE KEY, CAUSING YOUR PRODUTION BACKUPS TO TEMPORARILY FAIL UNLESS YOU FOLLOW THE STEPS BELOW. CREATING THE SCHEDULED TASK BELOW ON YOUR PRODUCTION VBR WILL PREVENT THE BACKUP FAILURES.

TO ENSURE YOUR BACKUPS RUN PROPERLY AFTER EACH RECOVERY TEST:

Schedule the below script to run on your production VBR to take over management of your VDV and ensure backups run successfully.

  • Create a powershell script on your VBR, i.e. “vaultmanagement.ps1”, with the following powershell command:
  • Set-VBRAmazonS3CompatibleRepository -Repository “Your Repository Name“
  • Replace “Your Repository Name” with the actual name of your Veeam Data Vault as shown in your VBR.
  • Create a scheduled task to run this command hourly every day of the week:
    powershell.exe “C:\location_of_script\vaultmanagement.ps1”
  • Select the option “Run whether user is logged on or not”

The above steps will ensure that your production backups continue to run.

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.