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.
-
mamosorre84
- Veeam Vanguard
- Posts: 372
- Liked: 39 times
- Joined: Oct 24, 2016 3:56 pm
- Full Name: Marco Sorrentino
- Location: Ancona - Italy
- Contact:
-
sfirmes
- Veeam Software
- Posts: 375
- Liked: 171 times
- Joined: Jul 24, 2018 8:38 pm
- Full Name: Stephen Firmes
- Contact:
Re: S3 Read Only Permissions
Marco,
This is the expected behavior.
Steve
This is the expected behavior.
Steve
Steve Firmes | Staff Solutions Architect - Object Storage, Product Management - Alliances @ Veeam Software
-
mamosorre84
- Veeam Vanguard
- Posts: 372
- Liked: 39 times
- Joined: Oct 24, 2016 3:56 pm
- Full Name: Marco Sorrentino
- Location: Ancona - Italy
- Contact:
Re: S3 Read Only Permissions
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.
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.
Who is online
Users browsing this forum: No registered users and 21 guests