Hi guys,
I found the source of the problem.
Comparing backups started in two different environments (CommCells), I saw that the VM discovery in one environment, discovered san attached datastores for a VSA, while the other environment did not.
Having in mind, that in the past, the default behavior changed for a couple of features with newer SPs, I added the additional setting bEnableSanDatastoreDispatch = true (which should be the default, according to the documentation), enforcing the presence of this parameter on all VSA.
Surprise !
Last night’s backups used san mode for the vast majority of VMs !
BOL lists the dispatching rules in the following order:
- Virtual machines are backed up by proxies running as physical machines that have SAN connectivity to the datastore.
- Virtual machines are backed up by proxies that are running as virtual machines on the same host.
- Virtual machines that are part of a vSAN stretched cluster are backed up by proxies that are in the same fault domain.
- Virtual machines are backed up by proxies that are running as virtual machines on hosts that have access to the datastore.
- Virtual machines are backed up by proxies that are on the same subnet as the virtual machine's host.
- The remaining virtual machines are distributed evenly across the proxies.
but this was not true for one of my environments
we use nbdssl and not nbd to meet the requirement of end-to-end encryption of data. This also includes the encryption of data in-transit.
rgds
Klaus