Hi there
I have several vCenters included in my backups and have now (finally) switched to VM tags to make my life easier. Of course, they should all be structured in a similar way, and I have numbered them nicely so that my colleagues assign the VM tags correctly. For example, “1.1 File server with indexing.” However, there have now been two changes in one vCenter. First, I added a 10th tag, and since it looked silly, I adjusted the numbering to “1.01” in the above example. In addition, indexing was no longer necessary for one tag. So I removed this from the Veeam job and also changed the description of the tag.
Again, using the example above, “1.1 File server with indexing” has now become “1.01 File server without indexing.”
Basically, only I can see what happens in the jobs, but it's still unfortunate that the tag names aren't updated in the jobs as well. I've already tried to update the vCenter by rescan. When I change the job, I see exactly these changes from above when adding a new tag. But if I simply select the new 1.01 again, it is not applied (the ID for the tag has remained the same as for 1.1) – but the display of the existing VM tag in the job is not updated either.
Is there a workaround here—other than removing the old tag from the job and generally reinserting it? I am currently still on the latest build of version 12—will this be different with version 13?
-
dspringer
- Enthusiast
- Posts: 63
- Liked: 5 times
- Joined: Feb 01, 2022 10:57 am
- Full Name: David Springer
- Contact:
-
Mildur
- Product Manager
- Posts: 11546
- Liked: 3239 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Backup Job with changed VM Tag
Hi David,
I apologize for the late reply to this topic. I tested it in v13.0.1 P1 and can confirm, after renaming a tag in vCenter, that the tag name gets updated in our new Web UI introduced in v13.
Unfortunately, the tag keeps its old name in the Windows‑based Backup Console.
I’ll report this internally, but I don’t expect any changes in the Backup Console, as our focus is on bringing all features and workloads to the Web UI as quickly as possible. Once that’s done, you probably won’t need to open the Windows‑based Backup Console anymore.
Primary and Copy Jobs for VMware and Hyper‑V are already fully supported, as well as Restore Options (Instant Recovery, Entire VM, Guest Files). With more features and workloads to be added within the next minor releases.
Maybe you can give it a try and share your feedback if you have updated to version 13.

Best,
Fabian
I apologize for the late reply to this topic. I tested it in v13.0.1 P1 and can confirm, after renaming a tag in vCenter, that the tag name gets updated in our new Web UI introduced in v13.
Unfortunately, the tag keeps its old name in the Windows‑based Backup Console.
I’ll report this internally, but I don’t expect any changes in the Backup Console, as our focus is on bringing all features and workloads to the Web UI as quickly as possible. Once that’s done, you probably won’t need to open the Windows‑based Backup Console anymore.
Primary and Copy Jobs for VMware and Hyper‑V are already fully supported, as well as Restore Options (Instant Recovery, Entire VM, Guest Files). With more features and workloads to be added within the next minor releases.
Maybe you can give it a try and share your feedback if you have updated to version 13.

Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: 6equj5, AdsBot [Google], Bing [Bot], Chris Kay, johannesk, NikoWana and 12 guests