S3 Read Only Permissions

[mamosorre84]

Hi all,

I’m trying to connect a Wasabi bucket to a secondary Veeam server (VSA - v13) deployed at the DR site, using a user account with read-only permissions as documented here:
https://helpcenter.veeam.com/docs/vbr/u ... s3readonly

However, during configuration, a pop-up appears indicating that the repository is managed by another Veeam server. Is this normal behaviour even for read-only accounts?

I don’t want to have missed something and risk disrupting the production Veeam environment.

Regards

Marco S.

[sfirmes]

Marco,

This is the expected behavior.

Steve

[mamosorre84]

Hi Stephen,

do you mean it will take the ownership of the bucket like a full user?

Ii is not possible to have a production VBR working if I use a read only bucket on a second VBR?

Thank you

Marco S.

[sfirmes]

Marco,

You are correct. The current behavior is the secondary VBR server will become the owner of the repository. We’re working on delivering functionality in a future release of VBR that will allow the secondary VBR server to access the repository in read-only mode.

Hope this answers your question.

[mamosorre84]

Hi Stephen,

thank you for your info.

Just to be sure: is it safe actually to take ownership and then go back or do we have to take some precautions (like shutdown primary VBR/save some bucket configs)?

[sfirmes]

Marco,

It is perfectly safe to switch ownership back to the primary VBR server after the testing is done.

In a future release of VBR this process will be much improved.

Thanks

[mamosorre84]

Hi Stephen,

I've just tried: the secondary VBR was supposed to take ownership, but in reality it didn’t because it’s in read-only mode..is that possible?

In any case, the repository has been attached correctly, and it is possible to restore the backups.

Meanwhile, the primary VBR is continuing to function correctly, and I believe it still holds ownership… is that correct?