Page 1 of 1

Bottlenecks during jobs

Posted: Dec 18, 2017 8:04 pm
by baber
Dear all
Hi

in Bottlenecks documents said we have 6 Bottlenecks :

1- Source — source disk reader component responsible for retrieving data from the source storage.
is that your means from source disk Bottlenecks speed of read data is slow ?

2- Proxy — backup proxy component responsible for processing VM data.
is your means from backup proxy Bottlenecks the load on backup proxy is high ?

3- Network — network queue writer component responsible for getting processed VM data from the backup proxy and sending it over the network to the backup repository or another backup proxy
is your means from network Bottlenecks the network between backup proxy and backup repository maybe problem ?

4- Target — target disk writer component (backup storage or replica datastore).
is your means from Target Bottlenecks that speed write data on destination disk is low?

for example i run a job and bottlenecks show :source
is that means weakest component in my environment is source disk ?

BR

Re: Bottlenecks during jobs

Posted: Dec 19, 2017 10:34 am
by foggy
Yes to all questions.

Re: Bottlenecks during jobs

Posted: Dec 20, 2017 3:10 pm
by baber
thanks
but when show our Bottlenecks is source or target or backup proxy can one of that reason deficiency resource such as (CPU - Memory ) or the reason is just read or write low disk speed ?

BR

Re: Bottlenecks during jobs

Posted: Dec 20, 2017 3:49 pm
by foggy
For the source/target it is disk read/write speed, for the proxy it is CPU. Here's a good explanation.

Re: Bottlenecks during jobs

Posted: Dec 20, 2017 6:07 pm
by baber
so thanks
now if my veeam backup and replication has been installed on physical server and this server has been connected to san and my source vms on SAN now when show Bottlenecks = source is that means the disk speed on veeam backup and replication server is low or disk speed on SAN(my vms are on that) is low?

BR

Re: Bottlenecks during jobs

Posted: Dec 20, 2017 6:12 pm
by foggy
That means that your production storage cannot provide data any faster.