would a global exclude list for all jobs make sense in further releases?
In my case I backup my VMs using the datastores as the include objects (most exciting pro, all new VMs are included automatically) for my jobs (meanwhile after increasing the datastores from 500 GB to 2 or 3 TB not the best choise anymore, i know, backups run around the clock, redesign is planned
). If one VM or parts of it are excluded in one job, then after Storage vMotion (which can be automated by Storage DRS) the VM will be backuped up in another job (not too funny for incrementals of i.e. Sharepoint Fastsearch Servers) . Would be the same when including the ESXi host as the include object, when a vMotion happened.Editing one global exclude list for this cases would be much easier, than editing each jobs exclude, that possibly could backup those "bad" VMs
Regards
Frank