This is a fine way to define a structure for automatic selection of VMs to Jobs. Great extension of this functionality.

Is there a mechanism in VMWare to be sure that the tags have to be set at the creation of a VM? Otherwise the admins will forget it for most of the maschines…

This is great, and thanks for breaking down the logic of the tag combination as you did, it was great to see that example of selecting both DCs!

@JMeixner: I don’t know any. But as a workaround you could create a catch-all job, which backups only VMs without tags. Or create a scheduled PowerCLI script which reports VMs without tags or assigns a default tag to those.

Seeing the example with the two DCs I fear that this can easily happen and result in missing backups. Double checking or reporting will be a must if using tag combinations.

Yes it is quite easy to query for not-tagged VMs. Simple like this:

$NotTaggedVMs = @()
Get-VM | ForEach-Object {if((Get-TagAssignment $_) -eq $null) {$NotTaggedVMs += $_}}

I normally start such a script scheduled. It could tag VMs or report per mail. 

@JMeixner Actually there is solution for this: VMware Event Broker Appliance. It is currently a fling (no support) that is still in development. Just a few days ago, version 0.5 was released. It uses a new approach: Event driven automation. In this example, a tag is assigned to a new VM, when the event of VM-creation appears.

I personally believe, this will be part of vSphere one day.

Thank you for the code snippet, @vNote42 

And the hint to the Event Broker Appliance is great, too. I will suggest ths to our VMWare Admins.

The VMware Event Broker Appliance sounds great! Will need to test this out soon.

Please share your experiences here. 

+1 on this, every day’s a school day!

And almost every day is too short ...

$NotTaggedVMs = @()
Get-VM | ForEach-Object {if((Get-TagAssignment $_) -eq $null) {$NotTaggedVMs += $_}}

This will help me for sure

Thanks a lot for the wonderful write-up. I always encourage people to use TAGs as it's a brilliant way to manage your VMs and your backups. I also tend to TAG the VMs that require Copy/Replication as normally we don't replicate/Copy everything to DR. 

One problem I see with tags is that they don't allow you to set an execution order within the tag itself. Is that so?

One problem I see with tags is that they don't allow you to set an execution order within the tag itself. Is that so?

You are speaking of the order the VMs are processed within a job?

One problem I see with tags is that they don't allow you to set an execution order within the tag itself. Is that so?

This is not completely true! You can order the tags within the selection. If you need to backup your most important VMs first, you can add them explicitly by selecting them beneath your tags.

A tag on your datastore can cover this as well.
Newly created vm’s on that datastore are automatically in back-up with the job.

Another great chapter @vNote42 , I admit not using tags enough...

Are you using this tool even in production or only for testing prouposes?

For production purpose I am waiting for the final version of the broker .. it is still a fling

Nice!