This was a great thread! ANd great information, I do however have a couple questions.
1) Has DirectNFS, and DirectSAN been merged now into Direct Storage Access Transport mode?
"Depending on the connection the proxy can be deployed as follows:
On a physical server with FibreChannel, FCoE, iSCSI or NFS
On a VM with iSCSI and NFS"
2) CBT is not used when Virtual Appliance Mode is used.
"Note: Changed block tracking (CBT) will be disabled for these hot-add proxies. Consider that it may impact the backup window in case the said virtual machines should be included in backup or replication jobs."
In my Case I use an All-in-One Veeam on a VM within my cluster. As of right now most of my VMs are in a NFS datastore shared by my hosts.
My Veeam VM has a leg in the NFS network via a added VMPG on my hosts networking stack, for this one VM allowing direct NFS to work (And works great). I recent started making changes to move over to
iSCSI so I could utilize MPIO and get faster single session activities done (svMotion in particular). I moved one of my VM's to the new iSCSI datastore. However checking the results of the Job I got this:
"Using Backup Proxy VMware backup proxy for Hard Disk 1 [hotadd]
Hard Disk 1 (300 GB) 8GB read @ 60 MB/s [CBT]"
I already have iSCSI IPs for my Veeam VM for it's local repo to another SAN (using the same 2 seperated iSCSI subnets) so at this point as long as I add the target IP of the production VMware to the Veeams windows iSCSI initiator settings, make sure I can see the disc in disk manager (don't initialize it, of course) and then I'm assuming it would change form hotadd to DirectSAN. But my questio is if CBT isn't supposedly used in Virtual Appliance mode, why does my Veeam backup job say CBT after saying it's using [hotadd] mode?