If you haven’t yet upgraded to Veeam v13, we suggest you wait until Veeam has released the next revision and Cloud IBR has completed testing across various environments.
If you have upgraded to v13, please open a support ticket with Cloud IBR so we can enable v13 for your account as we are still using the latest v12 version as the default for all recoveries.
Once we confirm the change and you run a recovery test, if it shows There were no backups found in any repository, please follow these steps:
- Delete your existing Backup Repository(s) from Cloud IBR.
- Re-add the repository with the read-write key. (Read directions below for your vendor)
- Add the repository back to Cloud IBR and run a recovery.
At Wasabi and any other Object Storage that utilizes IAM policies:
- You can either edit your existing policy and change it to read-write by changing:
- Action”: [
- “s3:List“,
- “s3:Get“
- to:
- “Action”: [
- “s3:*”
- Or you can delete the existing policy and create a new one with the above change, applying it to the same programmatic user you created.
At BackBlaze:
- Create a brand new key.
- Follow the directions in the Cloud IBR portal to create a new key but choose “Read and Write” for “Type of Access” when creating the key in the BackBlaze portal.
All other Vendors:
- If you are unsure how to create a Read-Write key for your vendor, please check their website for directions.