Comprehensive data protection for all workloads
Post Reply
dmontgomeryth
Lurker
Posts: 2
Liked: never
Joined: May 04, 2010 10:18 am
Full Name: David
Contact:

Veeam Backup v3.1 - Very Slow ?

Post by dmontgomeryth » May 04, 2010 10:35 am

Quick question guys.

Our Veeam backup is running very very slow... between 50mb per sec to as low as 9 bp per sec.. our setup is below.

ESX 3.5 cluster
2x Fibre switches
IBM SAN ( Fibre )

1 x Windows 2003 SP2 phisical Veeam Server ( inc VCB ) with QLogic 2gb Fibre cards
1 x Ethernet NAS ( backup destination storage )

Veeam has access to both the NAS and the SAN ( where the VMs sit )
Veeam is configured to use SAN backup with VSS authentication

The backup is successfull with these setting, however the speed is very low, as low as 9mbs ( keeping in mind this is fibre ) - the server being backed-up is quite small ( 50GB in size )

Any suggestions to speed it up ?

Many thanks

Dmont

dmontgomeryth
Lurker
Posts: 2
Liked: never
Joined: May 04, 2010 10:18 am
Full Name: David
Contact:

Re: Veeam Backup v3.1 - Very Slow ?

Post by dmontgomeryth » May 04, 2010 11:10 am

Sorry, just noticed I've posted in the wrong place...

Can someone please move this to the Veeam Backup & Replication section.

Many thanks

Gostev
SVP, Product Management
Posts: 25768
Liked: 3964 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Veeam Backup v3.1 - Very Slow ?

Post by Gostev » May 04, 2010 11:21 am

Hello David,

First, I highly recommend upgrading to the latest version, because 3.1 is over 1 year old release. :D

Steps to find the performance bottleneck are usually as follows
1. Check CPU load on Veeam Backup server during backup, to make sure it is not at 100% due to weak CPU.
2. Try to backup locally to Veeam server (to see if issue is with your NAS speed, or with network connection to NAS).
3. Create new job with turned off VM, and run the job 2 times. Second pass speed will basically show how fast your source SAN storage is (Veeam Backup will have to read the whole VM to determine changed blocks, but there will be none due to the fact that VM is shut down - so processing rate would indicate how fast the data can be retrieved from the source storage). If you had ESX4, you would need to disable the use of changed block tracking in the job's settings as well for this test, but ESX 3.5 does not have СBT anyway.

Hope this helps!

Post Reply

Who is online

Users browsing this forum: tomi3 and 27 guests