VeeamZip should ignore global exclusions

[doktornotor]

I have a bunch of VMs in global exclusions. Tried to do a one-time VeeamZip backups of them. The job starts, does nothing and completes "successfully". This is a bit stupid, isn't it?

[david.domask]

Hi doktornotor,

Well, while I can understand the confusion and irony of "doing nothing, successfully" in the job, I think that Global Exclusions is doing exactly what it should be doing: preventing a backup of the production VM.

Since VeeamZIP requires a snapshot and the main goal of excluding a machine from processing is to ensure a machine is not negatively impacted by the backup process, I think it's appropriate that VeeamZIP also respects the processing exclusion since presumably the exclusion was set intentionally.

Though I would agree that we should give something more informative when a VM is excluded due to the global exclusions.

[doktornotor]

I guess we have completely different workflows then. These globally excluded machines are not production VMs. They are used for testing / temporary experiments etc. They are not even running most of the time. Yes, the exclusion were set intentionally - to not waste disk space and CPU resources with needless regular backups.

Perhaps hide it under Ctrl + right-click like some other things, still whole lot less obnoxious than having to remove and re-add those from / to global exclusions.

[doktornotor]

On another note - the job output actually says nothíng about doing nothing due to global exclusions. So, if you are unaware of the fact, that leaves you with quite some head scratching. Why is the job even created and started? VBR should be aware that the VM is globally excluded at the point when you try to select it... why not just spit some useful message.