Comprehensive data protection for all workloads
Post Reply
nineoff
Service Provider
Posts: 4
Liked: never
Joined: Oct 04, 2013 2:46 pm
Full Name: DD
Contact:

Feature request - SCSI controller bus-sharing report

Post by nineoff »

Dear Veeam support,
I would like to make a feature request about the VMs that have a SCSI controller engaged in bus-sharing is present. If you expect that VM with such SCSI controller will be backed up, that will not happen, as mentioned here.
https://helpcenter.veeam.com/docs/backu ... tml?ver=95
... Virtual machines with disks engaged in SCSI bus sharing are not supported, because VMware does not support snapshotting such VMs. ...
I would like to get a warning about skipped VM in Veeam daily backup report to be able to react properly and either take action and remove SCSI controller with bus sharing or know that your VM or VMs are not beeing backed up.
Thank you.
foggy
Veeam Software
Posts: 21171
Liked: 2157 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Feature request - SCSI controller bus-sharing report

Post by foggy »

The warning about unsupported disks should be displayed once during the first ever VM backup, are you saying this is not the case?
Vitaliy S.
VP, Product Management
Posts: 27625
Liked: 2880 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Feature request - SCSI controller bus-sharing report

Post by Vitaliy S. »

BTW, we have a predefined Veeam ONE report for this use case > VM Configuration Assessment
JustinIzzard
Influencer
Posts: 16
Liked: 3 times
Joined: Sep 30, 2022 12:10 pm
Full Name: Justin Izzard
Contact:

Re: Feature request - SCSI controller bus-sharing report

Post by JustinIzzard »

Resurrecting an old thread to add a +1 vote for this feature request.

In our case, we had assigned a tag in vCenter to a VM that has a SCSI controller with bus sharing enabled. Veeam skipped this VM because VMware cannot take the snapshot, but there was no warning notification nor any indication in the VBR console that the VM was skipped. It took digging through the logs to find the warning and identify why Veeam skipped the job.

We have opened support case #07698992 to troubleshoot why the warning was provided in logs, but not via email notification.
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 13 guests