Hi everyone,
We’re currently working on standardizing our VM Tagging structure across multiple vCenters, and I wanted to share an observation and ask for some guidance regarding how Veeam handles renamed Tag Categories.
Scenario:
We use VM Tags to dynamically populate Veeam jobs.
These Tags are organized under a specific Tag Category.
To standardize naming conventions, we renamed the Tag Category in one of our vCenters (we did not create a new category or reassign tags—just renamed the existing one).
What We Observed:
After renaming the Tag Category, all jobs continued to function correctly:
VMs are still being processed as expected.
Disk exclusions are still applied correctly.
(Pending verification: Application-aware processing objects still seem to work without needing to re-add them.)
So far, so good.
The Question:
Using PowerShell:
When we run:
Find-VBRViEntity
we can see the updated Tag Category name in the path.
However, when we inspect job objects using:
$job | Get-VBRJobObject | Select-Object *
the "Location" property still shows the old Tag Category name.
We’re wondering:
Is there a way to refresh or update this value so that the Location property reflects the new Tag Category name?
We’re looking for a way to do this programmatically, ideally without having to remove and re-add the objects to the job.
Why This Matters:
We rely on the Location property for reporting and auditing.
Having outdated values could lead to confusion or misinterpretation of job configurations.
Any insights, PowerShell tips, or internal behavior explanations from the Veeam team or community would be greatly appreciated!
Thanks in advance!
We’re currently working on standardizing our VM Tagging structure across multiple vCenters, and I wanted to share an observation and ask for some guidance regarding how Veeam handles renamed Tag Categories.
Scenario:
We use VM Tags to dynamically populate Veeam jobs.
These Tags are organized under a specific Tag Category.
To standardize naming conventions, we renamed the Tag Category in one of our vCenters (we did not create a new category or reassign tags—just renamed the existing one).
What We Observed:
After renaming the Tag Category, all jobs continued to function correctly:
VMs are still being processed as expected.
Disk exclusions are still applied correctly.
(Pending verification: Application-aware processing objects still seem to work without needing to re-add them.)
So far, so good.
The Question:
Using PowerShell:
When we run:
Find-VBRViEntity
we can see the updated Tag Category name in the path.
However, when we inspect job objects using:
$job | Get-VBRJobObject | Select-Object *
the "Location" property still shows the old Tag Category name.
We’re wondering:
Is there a way to refresh or update this value so that the Location property reflects the new Tag Category name?
We’re looking for a way to do this programmatically, ideally without having to remove and re-add the objects to the job.
Why This Matters:
We rely on the Location property for reporting and auditing.
Having outdated values could lead to confusion or misinterpretation of job configurations.
Any insights, PowerShell tips, or internal behavior explanations from the Veeam team or community would be greatly appreciated!
Thanks in advance!
Statistics: Posted by Kosk — Jul 10, 2025 9:09 am
