Should it be this slow?

[mega_IT]

Veeam completely destroys the server have it installed on. Even if one job is running, the server slows to a crawl and can hardly be used until the job finishes. This makes it really hard to look at job logs, or fix issues while it is running (which is almost 18 hours).

Details:
Veeam 4.1.1 (64 bit)
Two dual-core AMD opteron Processors (2210 - 1.8ghz)
8GB Ram
Windows Server 2003 64-bit server

Nothing else is running on it and the antivirus autoprotect is disabled.

[Vitaliy S.]

Hello Tyler,

It seems like your machine with Veeam Backup server installed is starving on CPU resources. Please try to use less compression ratio for your job, that should give you less stress your CPU resources and improve the job performance.

Thank you!

[mega_IT]

Right now it is set to 'optimal' for all jobs by default. We will try to set them for 'low' and see how it works out.

[Gostev]

Dual-proc dual-core sounds like pretty powerful configuration, so something is definitely wrong here, and I am not sure if Veeam compression is causing the issue here. I would check out Task Manager to see what is loading the machine so much when the job is running.

[Exrace]

Do you have a virus program running on this setup?
You can use sysinternals process explorer to see what is using all the cpu.

[mega_IT]

It is running a bit better, but still dogging down. Physical memory usage is currently at 98%.

Screencap from ProcExp:

[Vitaliy S.]

Tyler,

As far as I correctly see it from the screenshot provided, your Veeam agent consumes only 30% of total CPU. So could you please try disabling all antivirus processes as a part of further troubleshooting step to be sure it doesn't affect Veeam agents while the job is running.

[mega_IT]

This was happening before antivirus was installed. Veeam now just stopped the one job that was running and the physical memory usage is back down to 16% used. In addition, real-time scanning is disabled on the server.

[Vitaliy S.]

I guess this is it, running many concurrent backup jobs may put a heavy stess on the VM's CPU resources, to avoid that I would recommend either installing another Veeam backup server (in a VM) or running the jobs consequentially.