HotAdd Transfer Method
I currently backup VM's using SAN Transport, all of LUNs are presented to my backup host(s) / storage server(s) which backups up to MSDP.
I am noticing the snapshot times are excessive, and as previous discussions looking at HotAdd transfer to reduce this.
I've been looking for a white paper which I can try and understand the differences or the gains available from HotAdd, but have been unable to find this.
With the physical backup host, I know a snapshot of the VM is created, then the vmdk is sent in full to the backup host, then the data id deduplicated and written to MSDP.
Where Im not 100% clear how this functions using HotAdd, from my understanding is that the HotAdd VM would have access to the datastores via SAN, and also read the vmdk in full and then deduplicate and send the dedup data to the backup host (with CSD on). Where would my time saving be if the vmdk is still being sent to the HotAdd VM in full, or is the HotAdd VM able to do this on SAN level?
Can anyone clarify in detail the HotAdd procedure?
Using Windows 2008 / NBU 188.8.131.52