Comprehensive data protection for all workloads
Post Reply
dspringer
Enthusiast
Posts: 63
Liked: 5 times
Joined: Feb 01, 2022 10:57 am
Full Name: David Springer
Contact:

Backup Job with changed VM Tag

Post by dspringer »

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?
Post Reply

Who is online

Users browsing this forum: Amazon [Bot], MILJW002 and 14 guests