As per info from Veeam tech support, current VBAWS cannot set the worker config within the policy page unless you remove the subnets from the worker config under prod. accounts so it does not see them and use the ones you intend the worker to be deployed in only.
With that limitation, we'd like to know if there is future plan from product team to add new feature there on allowing to select/choose worker subnet in the backup policy?
Thanks.
-
felixasiapac
- Influencer
- Posts: 10
- Liked: never
- Joined: May 09, 2023 2:01 am
- Full Name: Felix
- Contact:
-
nielsengelen
- Product Manager
- Posts: 6191
- Liked: 1295 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Question for case #07919483
Hi,
There are no direct plans to add changes to our policies for this.
Can you clarify your use case to better understand the issue with workers and subnets?
There are no direct plans to add changes to our policies for this.
Can you clarify your use case to better understand the issue with workers and subnets?
GitHub: https://github.com/nielsengelen
-
felixasiapac
- Influencer
- Posts: 10
- Liked: never
- Joined: May 09, 2023 2:01 am
- Full Name: Felix
- Contact:
Re: Question for case #07919483
The use case is that our client has multiple same aws account with different subnets and our cloud team would like to avoid creating many private endpoints for each those subnets to save cost and to reduce complexities on managing those private endpoints in each different subnets and/or AWS accounts
So, instead of creating more private endpoints, they'd like to route those to the private endpoints to one central place on AWS account thru transit gateway.
With that, they would only need to maintain private endpoints at one AWS account.
If VBA cannot select/choose worker subnet in the backup policy, then they would need to create more private endpoints for each those subnets that are used by the workers, in which it will increase cost and complexities on managing those when the client is having many AWS accounts with many subnets there.
Thanks.
So, instead of creating more private endpoints, they'd like to route those to the private endpoints to one central place on AWS account thru transit gateway.
With that, they would only need to maintain private endpoints at one AWS account.
If VBA cannot select/choose worker subnet in the backup policy, then they would need to create more private endpoints for each those subnets that are used by the workers, in which it will increase cost and complexities on managing those when the client is having many AWS accounts with many subnets there.
Thanks.
Who is online
Users browsing this forum: No registered users and 1 guest