In most scenarios, an access key with read-only permissions to your object storage is required.
In certain situations where Veeam does not support a read-only key, you can open a support ticket to have your account configured to allow for read-write keys. Examples are:
- Repositories with Automatic Bucket creation enabled
- Veeam Data Vault Repositories
- Object Storage backups with Agent Based Backups through a Cloud Connect provider
Each time you run a recovery with a read-write key, the Cloud IBR VBR will “take over management” of the repository, causing your backups to temporarily fail.
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 Repository. For simplicity, you can schedule the script to run daily, either every morning or just before your daily backup window starts.
Create a powershell script on your VBR, i.e. “repomanagement.ps1”, with one of the following powershell commands, depending on if you’re using Veeam Vault or any S3 compatible object storage:
For Vault repositories:
- Set-VBRDataCloudVaultRepository -Repository “Your Repository Name”
For S3 compatible repositories:
- Set-VBRAmazonS3CompatibleRepository -Repository “Your Repository Name”
Replace “Your Repository Name” with the actual name of your repository as shown in your VBR.
Create a daily scheduled task:
- Program/script: powershell.exe
- Add arguments: “C:\location_of_script\repomanagement.ps1”
- Select SYSTEM account for “When running the task, use the following user account:”
- Select the radio option “Run whether user is logged on or not”
Run the scheduled task to make sure it runs successfully.