Slow, slow, slow backup (Proxy 99%)

[ArchParks]

OK....I read the FAQ before I posted it but some of the terminology escapes me.

Here is my setup:
Machine 1 - Veeam Backup software version 6 running in 64 bit Windows Server on Vsphere 5 box #1
Machine 2 - 64 bit Windows Server on Vsphere 5 box #2
Machine 3 - Openfile running NFS on Vsphere 5 box #3

Veeam Backup backs up Machine #2 to Machine #3. I ran my first test a while ago. When it ran, the VM running Veeam is almost inaccessible (I assume due to the load). It transfers the data at 15 MB/s.
12/18/2011 1:23:13 PM :: Job started at 12/18/2011 1:23:09 PM
12/18/2011 1:23:13 PM :: Building VM list
12/18/2011 1:23:49 PM :: VM size: 236.9 GB
12/18/2011 1:23:49 PM :: Changed block tracking is enabled
12/18/2011 1:23:58 PM :: Preparing next VM for processing
12/18/2011 1:23:58 PM :: Processing 'computer1.ourdomain.com'
12/18/2011 3:56:12 PM :: All VMs have been processed
12/18/2011 3:56:17 PM :: Load: Source 6% > Proxy 99% > Network 0% > Target 2%
12/18/2011 3:56:17 PM :: Primary bottleneck: Proxy
12/18/2011 3:56:17 PM :: Job finished at 12/18/2011 3:56:17 PM
Time 2 hrs :33 mins
Processed 134.1
Read 121.3
Transferred 79gb

The backup proxy is set liek this:

Transport mode: Automatic selection
Connection Datastores: Automatic detection (recommended)
Maximum tasks: 2


In comparison, when the Windows Machine that does the backup, does its own native backup across the network, it takes 32 minutes (two hours less than the Veeam backup))

Is this normal? Any suggestions?

Arch

[Gostev]

12/18/2011 3:56:17 PM :: Load: Source 6% > Proxy 99% > Network 0% > Target 2%
12/18/2011 3:56:17 PM :: Primary bottleneck: Proxy

Hi Arch, not sure what is not clear here - just as the log explains, your backup proxy struggles on CPU resources and this is causing a bottleneck that affects performance of the whole job. As you can see, all other components are doing nothing most of the time, waiting for the proxy to process the data.

Since your backup server is a VM, give it at least 4 vCPUs to start with (per our system requirements, 2 vCPU is a minimum - however, this may not be enough if the VM is running on a weak host).

Alternative, you can disable compression in the job settings, this would take some load off proxy server CPU as well at the cost of much larger backup files.

Thanks!