No Warning or Error for SCSI Bus sharing when VMs are added by tag

[mv@cloudio.dk]

Adding my vote for a visible warning on every run where a VM is skipped because it cannot be backed up.

## What happened

In VBR 13.1.0.411, two VMs included through VMware tags were skipped because of SCSI bus sharing. The job log recorded the reason, but the console showed `Success` and `Warnings: 0`. Neither VM appeared in the VM list or action log, and neither had ever had a restore point.

This also happened on the first run with those VMs included. Support is investigating that separately under case #08220566, including whether tag-based selection affects the notification. That is not yet a confirmed cause.

## What I am asking for

I understand the VMware snapshot limitation and accept that these VMs need agent-based protection. I also understand from Support that the current warning is intended to appear only once.

For Product Management:

1. Please make every affected run show a visible warning in the console and job report, identifying each skipped VM and the reason.
2. Please confirm whether this existing feature request is tracked and share its current status, if available.

A successful backup of the remaining VMs leaves a protection gap that should stay visible until it is addressed. Neither request blocks the separate Support investigation into the missing first-run warning.

[mv@cloudio.dk]

Follow-up to my post from 8 September (case #08220566, VBR 13.1.0.411).

I ran two test jobs with the same two VMs on the same backup server:

- VMs added directly to the job: `Errors: 2`, and both VMs are listed as failed with name and reason. That works.
- VMs added through a VMware tag: `0 of 0 VMs`, no VM names anywhere, only "Nothing to process: all objects were excluded from the task list".

In a tag job where other VMs are processed, like our production job, the result is `Success` with `Warnings: 0`. The skipped VMs are not mentioned in the console at all. Only the job log has them.

Support confirmed on 17 September that this is "a missing feature" and "currently expected" for tag-based jobs. So the 2017 answer in this thread, that the warning is shown during the first backup, does not hold for tag-based jobs.

This request turned 9 years this June.

Question for the PMs: is this feature request registered internally, and is it planned for a specific version?

[david.domask]

Hi Martin,

I discussed the case with Support as I tested and saw the same behavior, I'm not sure why we have this discrepancy.

Support's most recent answer was regrettably based on incorrect internal documentation; I've discussed with Support and there is agreement to continue validation on this specific behavior, as I'm not aware that there should be a difference for this error depending on how the VM is added. (The incorrect internal documentation will also be adjusted to avoid further confusion until the behavior is validated)

Thanks for reporting it, and please await a further update from Support to validate this behavior.