slow FC direct SAn access to eva4400

[lansol]

We recently upgraded our ESX hosts and i reused one of the hosts as a dedicated Veeam server for our Vm backups:

Veeam v6 (6.0.0.164)
Windows 2003 R2 64bit
HP proliant DL 380 G5
32Gb RAM
Dual Quad Core 2.66Ghz CPU's
Lpe 12000e 4GB Fibre HBA (connecting directly to Hp EVA4400 SAN)
local storage MSA with 6TB

I can confirm that Veeam can see the SAN directly, as i can see the vmfs datastores in the computer management, and have also disabled the "failback to LAN" option in the backup job.

My backsup are last couple of days have been running at a max of 38MB/s. I am getting the same speed for my backups as when i was using a hp proliant dl 360 g5 that had a single core CPU and 2GB of RAM.

I run my backups at night, yet if i select a single VM from the SAN during the day i can get a backup speed of 80-100MB/s

Im not sure why the inconsistancy of the job speeds, i would expect that with FC direct SAN access i would get at a minimum of 60MB considering i am running on fast hardware.

what can i do to increase and maintain high job rate speeds??? if i am going to get the same speeds i would use my older crappier proliant and not waste a beefier machine

[foggy]

Hello!
What does your job bottleneck statistics (available in the Realtime Statistics window on the job's shortcut menu) show? Did it show proxy as a bottleneck before the upgrade? If not, than upgrading Veeam server hardware would not likely affect the job performance.

Also, keep in mind that various processing speed for different VMs is expected. This could explain better rates for single VMs you're getting.

Thanks.

[Vitaliy S.]

I run my backups at night, yet if i select a single VM from the SAN during the day i can get a backup speed of 80-100MB/s

So you're saying that your backups are way faster during the day? Do you have any scheduled maintenance activities during the night (just wondering)?

[lansol]

if i try to do a backup of a single machine during the day i get way faster performance.

when i check the real time stats the bottleneck says SOURCE.

I ahve backup exec running on the same server however, if i pause or hold the job or let the job run (which does a B2D for 1 server) Veeam still runs like a dog!

we only run backups at night nothing else.

average process rate i get now is between 15mb-30mb at BEST...even taking into account the:

http://www.veeam.com/forums/viewtopic.p ... eed#p24708

i expect i would get better performance than what i am getting now. Backup exec over ethernet to be honest performs 10x better over ethernet doping atraditional backup method

[Gostev]

Actually, that topic is about per VM processing rate counter, that is no longer present in v6 because it was causing too many confusion.

[foggy]

Bottleneck 'Source' shows that the engine cannot retrieve the data from source as fast as it can process it, so the processing engine spends most time waiting for the data to be read.