That's great, thanks for the link. I did do a search but obviously wasn't using the right terms!
I think that post confirms my assumption, in that clones will be coordinated by the hosts concerned (i.e. Source/Destination hosts will transfer data between themselves via the Service Console - assuming there is no VAAI involved), but it's not specific in excluding vCenter:
"A cloning between ESXs use also the network (the service console, or the management interface) and, of course, the storage."
Is vCenter only used for VMware Tools & Customisation? How does it keep track of the clone process if it doesn't proxy data?
I have a customer in mind that this could be of interest to - a Head Office site (which houses most infrastructure), with a 20MB MPLS link to two remote sites - both of which host ESX hosts managed by the vCenter at HQ. The two remote sites have a 100MB leased line between them, and would benefit from being able to clone between hosts on either side of the link. If vCenter plays a more active role however, there could be significant consequences from a performance perspective.
I think i'd like to understand the clone process in a little more detail if anyone can help?!
Thanks,
Kelvin
