Vmware restore speed - what do you get?

Hi Anders,

To get a better understanding here, I have a few questions: 

Can you confirm what Disk Provisioning type you have for the VM Disk? - From the above results I am assuming Thin Provisioned?
Was the NBD restore using the Physical MA/VSA or the Virtual VSA Proxy?

Also, do you have any features on the Datastore Volume in play here? I.e. Thin-Provision, Deduplication or Compression?

Best Regards,

Michael

Hi Anders, Apologies for the delay in getting back here.

Given you are using Thin Provisioning Disks, It makes sense that NBD and HOTADD are faster here. - Ref: https://documentation.commvault.com/11.24/expert/32040_san_transport_for_vmware.html

HOTADD can be faster than NBD/NBDSSL where there are network limitations between MA and ESX. - On the HyperScale node does the ESX Name resolve to a 1GB or 10GB/Faster interface here? 

I can’t give numbers on the “expected” speeds here, since there are factors such as Storage Performance, Network Performance, MA Performance etc.

If you wanted to check the performance from the logs, you can check the “stat-” counters in CVD.log (Media Agent) and vsrst.log on VSA Proxies used for restore.

Best Regards,

Michael

@ApK , can you clarify what you mean about the Hyperscale nodes?  You want to see which node is doing the restore?

hi @ApK 

Are you using VSA indexing v1 or v2 ?

As indexing v2 should perform multiple streams restore, if your VMs have multiple vmdks, this should increase performance.

I understood from your answers that your’re using Hyperscale appliances, which I don’t use on the environment under my scope. So maybe they’re all using v2..