Client parallelism defines the number of save streams that a client can send simultaneously during backup.while the physical client parallelism (which i think has been added starting from 7.5.4) is to enable virtual machine clients to use the physical client parallelism instead of their own in order to limit client parallelism on the host, not inside VM.
For example, if you have an ESX running 40 VMs and each VM has client parallelism of 4 (for guest backup), that’s a total of 160 save sessions on a single physical box. Which is not a good idea.By configuring physical client parallelism, you can limit total number of sessions on that physical system. Also, it does require that the “physical host” be correctly assigned as it cannot know which physical host to count parallelism towards automatically.
Bebo2k
544 Posts
0
October 31st, 2012 13:00
Hi GoEagles,
Client parallelism defines the number of save streams that a client can send simultaneously during backup.while the physical client parallelism (which i think has been added starting from 7.5.4) is to enable virtual machine clients to use the physical client parallelism instead of their own in order to limit client parallelism on the host, not inside VM.
For example, if you have an ESX running 40 VMs and each VM has client parallelism of 4 (for guest backup), that’s a total of 160 save sessions on a single physical box. Which is not a good idea.By configuring physical client parallelism, you can limit total number of sessions on that physical system. Also, it does require that the “physical host” be correctly assigned as it cannot know which physical host to count parallelism towards automatically.
Hope this helps,
Ahmed Bahaa