I have a customer that has a tagging policy for all resources being stood up. Because of this, the worker VM fails to deploy and therefore the backup fails. Other than changing a global policy (which the customer will never do), are there any workarounds to this issue?
Thanks in advanced!
-
- Novice
- Posts: 9
- Liked: never
- Joined: Dec 05, 2017 2:05 pm
- Full Name: Joel Jimenez
- Contact:
-
- Veeam Software
- Posts: 171
- Liked: 54 times
- Joined: Oct 04, 2021 4:08 pm
- Full Name: Lyudmila Ezerskaya
- Contact:
Re: Worker VM Fails due Tagging Policy
Hi! You can assign custom tags to all deployed worker instances using the REST API. We are working on adding this feature to the UI in the next release.
-
- Novice
- Posts: 9
- Liked: never
- Joined: Dec 05, 2017 2:05 pm
- Full Name: Joel Jimenez
- Contact:
Re: Worker VM Fails due Tagging Policy
Thanks for that reply.
Your suggestion is great but this assumes you already have a worker that is fully deployed? I think my scenario is that the worker doesn't get fully deployed due to policy set (i.e. "EnforcementofTags). Perhaps a workaround is to disable the tagging policy in Azure, create backup jobs, perform backup so that workers get deployed, apply tagging to worker, and then re-enabling the Tag policy in Azure?
Your suggestion is great but this assumes you already have a worker that is fully deployed? I think my scenario is that the worker doesn't get fully deployed due to policy set (i.e. "EnforcementofTags). Perhaps a workaround is to disable the tagging policy in Azure, create backup jobs, perform backup so that workers get deployed, apply tagging to worker, and then re-enabling the Tag policy in Azure?
-
- VP, Product Management
- Posts: 27463
- Liked: 2825 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Worker VM Fails due Tagging Policy
No, this proposed solution exactly matches your scenario. You can define a tag that will be assigned to a worker each time a new worker instance is deployed. Thanks!odurasler wrote:Your suggestion is great but this assumes you already have a worker that is fully deployed?
Who is online
Users browsing this forum: No registered users and 5 guests