It appears to be a limitation @Dynamic , although the documentation doesn’t appear to explicitly say you can’t add them. See here.

The helpcenter redirects to the VM Tags page, but doesn’t talk about Copy Jobs not being supported; or, doesn’t say Tags are supported by Copy Jobs. I think they’re only supported in a specific Copy job mode maybe. Whatever mode you’re trying to use...select the other one instead & see if you can add Tags

And, according to this Forums Post, Tags are available in Periodic but not Immediate Mode. So if you’re using Immediate, that is probably the issue.

Hey, very interesting I also noticed that after the update and didnt find a solution so far. 

I have several customers who use tags in copy jobs and wonder what happens with this AFTER the update to V12 .

Is it for both Modes? It should be only for Immediate Mode you can’t use Tags. That is also the case in v11, which I still use at the moment. To use Tags with Immediate Mode, refer to that Forums post. It suggests making a backup of VMs wanting to use Tags with and back them up. Then use Immediate Mode and Copy from that Backup. Not pretty, but works.

@coolsport00 i tried both modes. Seems to be an issue within V12. 
The option is not available anymore. 

Gotcha. Hmm...report a bug in the Forums maybe. PMs monitor there pretty regularly. That may be by design...though I can’t imagine why as Tags are used by many, tho not by me (I do use container-based backup methods, but use Datastores as my source...not Tags). Would be interested in PM response.

Just had a quick look in the Lab, in both Immediate and Periodic modes the option for tags is missing. 

just found a post in the support forum regarding this:

From infrastructure function missing in new backup copy job - R&D Forums (veeam.com)

Thank you for the link, I was not aware of that. How do I realise the following scenario?
1) Backup job on datastore level with 50 VMs
2) Backup copy job of the most important 5 VMs

Neither with the repository nor with the whole job as source i can do this?

Maybe with exclusion Tags for 45 VMs but...

you are totally right..

but im afraid, like @HannesK mentioned “from infrastructure” will not come back. So i think, also the option to select or filter by Tags..

I have a lot of customers, who are relaying on that feature They cannot copy “everything” to another offsite location, they must select a portion of the whole systems.

You could tag the 5 most important VMs in your scenario and pit the into an own job. This job can be handled by a backup copy job.

You will have to build your jobs  and/or repos to reflect your scenarios.

@JMeixner this one is clear, but thats nöt a good solution. In many projects we use netapp storage and a part of the concept are storage snapshots and backups of the whole datatstore.

After this depending on the SLA we use tags to define what we need to copy offside.

Maybe @HannesK has an good idea? Removing the Feature without an alternative solution isnt so nice 

sorry, hit the solved button :( 
do i have the option to revert this?

@Madi.Cristil or @safiya  can revert this.

maybe it’s a workaroung to realize that by make an exclusion, and Tag every “non-business-critical” VM with an additional Tag…

see screenshot for an example

edited/deleted.

I agree with @MatzeB , I’m discussing this now with @Mildur in the other forum.. :)

Maybe a “Include/Exclude” filter (as per Agent’s backup jobs) could help?

I just found the thread and also described our use case again

Hey,

I see that I'm not the only one missing this functionality. We'll need to rethink the initial job configuration. It's a shame because it loses some flexibility, especially for direct S3 storage usage.
I ll take a look to the “Move backup”feature :)

any news or good workarounds on this? 

Facing this issue now on another customer site, with backup copies to a remote site with tape out - the customer only needs about 10% of the whole systems on that site/tape