Standard "direct to object storage" buckets work fine with the new switch but when I add a bucket that was used in a SOBR to a sidecar VBR using new -EnableReadOnlyMode, it shows No backups found when you run a rescan. This was the same issue in 12.x when using read only or read write keys. The fix was to run Import Backups which would then find the backups, but in 13.1 with the new switch, the Import Backups returns error:
"Failed : Infrastructure item save failed Error: "Failed : Repository does not support repository level encryption Agent failed to process method {Cloud.FindRepositoryKey}."
You may be hitting this limitation. However, please wait for the conclusion to the Support Case as per the forum rules. Only once your support case is complete and you have questions on the conclusion, then post.
David Domask | Product Management: Principal Analyst
I confirmed that we don't have encryption enabled on the SOBR. Encryption is only enabled on the copy job to the SOBR.
One more important piece of info - this SOBR is a Cloud Connect SOBR and that link you provided says "The read-only mode is not available for Veeam Cloud Connect repositories." so that seems to be the issue.
The regression is that read only keys worked fine in v12 and 13.0.x with Cloud Connect SOBR repositories and stopped working in v13.1.
Got it, then it's not really a regression, it's a current limitation of the built-in Read-Only object storage repository feature that was introduced with 13.1. Can you confirm, are you using the built-in feature for read-ony repositories or you're trying to add the object storage repository with read-only IAM policy?
David Domask | Product Management: Principal Analyst
I tried adding it without the switch, just using a read only IAM policy and it had an error. It works in older versions of Veeam but not the latest version, and I didn't see it mentioned in the documentation, which is why I used the word regression. But maybe I just missed it. Thank you!