VM's got selected because of Datastore ISO in CD

[mkaaden]

I have build my back-up jobs based on datastore locality, because I use a VMware metro storage cluster.

Now I noticed for a couple of day's 2 extra VM's in one job for no reason at all, simply because they are not locate on the included datastore of the job.
Wondering for day's why they pop-up in the job it shot me: a week ago I connected an ISO to these VM's to update the software.
And of of course the ISO was situated on the included datastore of the job.
So by switching CD/DVD of the VM to Client Device the problem has been solved.

I know that VMware links the VM to that datastore, but Veeam should be smarter than that and just look at the VMDK's locality and ignore whatever ISO is linked to the CD/DVD drive.
Never seen this behavior before by the way.

[Mike Resseler]

Mkaaden,

Thanks for bringing this up. First: It is good that a simple workaround solves the problem but I will pass this information to the QC department so they can check this behavior.

Many thanks
Mike

[DeadEyedJacks]

FWIW, It's standard VMware behaviour to show a VM as utilising a datastore if it has an ISO mounted from it. Being that way for as long as I can remember.

Backup Jobs which target datastores always have the risk of a cascade effect if VMs have files on multiple datastore / datastore clusters.

[veremin]

There is a regkey to prevent this from happening; shared with you via PM. Thanks!

[Fatih]

Hi veremin , I am also interested in that regkey, could you PM me also ?
Will it work the same way also for those Netapp NFS volumes Veeam does the snapshot for ?


Thanks
Fatih

[veremin]

If you're still struggling with the reported issue, try this key; might help:

Code: Select all

StrictDatastoreScope (DWORD) = 1

Thanks!