Processing rate Direct SAN Access

VMware specific discussions

Processing rate Direct SAN Access

Veeam Logoby SilentDeath » Tue Feb 02, 2016 9:48 am

Hello Veeam newbie here,

We just implemented Veeam in our environment using the Direct SAN Access method w/ max. 8 concurrent tasks.
The back-up server a BL460C G6 running WS2012 R2 and is also the only proxy.
I forced the Transport mode to Direct SAN to make sure it's backing up this way.

Now for the storage, we have 4 P4500 & 2 P4530 HP Lefthand nodes.
This SAN storage presents the volumes as VMware datastore to the vCenter which is a VM running WS2008 R2.
The blade and the storage is linked via a 10Gbit core-switch.

As back-up repository we use an EMC NAS which is linked to the same core-switch.
This repo has 2 NIC's which are trunked resulting in a 2 Gbit processing rate.

I have a seperate job which backs up the Fileserver (WS2008 R2) with a processing rate of 75 MB/s.
Another job which covers 8 VM's has a processing rate of 58 MB/s.

Are these "normal" values? I don't have any experience in this matter and don't know what to expect.
SilentDeath
Novice
 
Posts: 6
Liked: never
Joined: Sat Apr 25, 2015 12:52 pm
Full Name: JohnDoe

Re: Processing rate Direct SAN Access

Veeam Logoby foggy » Tue Feb 02, 2016 10:06 am

Pretty common numbers. What are the bottleneck stats these jobs report?
foggy
Veeam Software
 
Posts: 14765
Liked: 1083 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Processing rate Direct SAN Access

Veeam Logoby SilentDeath » Tue Feb 02, 2016 12:09 pm

foggy wrote:Pretty common numbers. What are the bottleneck stats these jobs report?


For the Fileserver, the bottleneck is the Source & for the other job it's the Network.
I would suspect the target is the bottleneck since this has the slowest link speed.
SilentDeath
Novice
 
Posts: 6
Liked: never
Joined: Sat Apr 25, 2015 12:52 pm
Full Name: JohnDoe

Re: Processing rate Direct SAN Access

Veeam Logoby foggy » Tue Feb 02, 2016 12:25 pm

In case where source is the bottleneck, you should look at your source storage configuration for possible improvements.

For the job with Network being identified as bottleneck, consider increasing compression level. Btw, how the target storage is added to the Veeam B&R console (what type of repository is used)?
foggy
Veeam Software
 
Posts: 14765
Liked: 1083 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson


Return to VMware vSphere



Who is online

Users browsing this forum: No registered users and 23 guests

cron