How many simultaneous client sessions can be made to the Avamar server

Goal: The purpose of this document is to discuss factors which determine the number of concurrent backup and restore connections which can be made to the Avamar server.

Fact:

Avamar v5.x Avamar v6.0 Avamar v6.1

Symptoms: A typical symptom where the number of concurrent sessions has been exhausted is where backups fail to start running within their allotted backup schedule. At the end of the backup schedule they are recorded on the activity monitor as "Timed out - start".

Resolution: The total number of client connections which can be made to the Avamar server will vary according to which operations are currently running, how the connection is made and the number of data nodes which are online.

Various parameters in the /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml file govern this behavior.

Generated by Jive on 2013-03-13-07:00 1

How many simultaneous client sessions can be made to the Avamar server

Example from v5.x or v6.0 system:

<entry key="max_jobs_per_node" value="20" /> <entry key="percent_of_max_concurrent_jobs" value="90" /> <entry key="percent_of_max_concurrent_jobs_hfscheck" value="10" /> <entry key="max_concurrent_jobs" value="250" />

Example from a v6.1 system: <entry key="max_jobs_per_node" value="30" /> <entry key="percent_of_max_concurrent_jobs_hfscheck" value="10" /> <entry key="percent_of_max_concurrent_jobs" value="90" /> <entry key="max_concurrent_jobs" value="480" />

When HFScheck is not running, the MCS will queue up max_jobs_per_node * percent_of_max_concurrent_jobs / 100.

The number of concurrent jobs for the whole grid will not exceed max_current_jobs.

During hfscheck, the MCS will queue up a maximum of max_jobs_per_node * percent_of_max_concurrent_jobs_hfscheck / 100.

The MCS always reserve one connection per grid (not per data node) for the restore activity.

Generated by Jive on 2013-03-13-07:00 2

How many simultaneous client sessions can be made to the Avamar server

The following examples are based upon the mcserver.xml parameters shown above which cover v5.x through v6.1.

During garbage collection and during checkpoint jobs:

No backup sessions allowed Restore jobs are possible, potentially 18 per node (v5.x, 6.0) or 27 per node (v6.1) although testing should be carried out to confirm this

During hfscheck:

v5.x, 6.0: Two jobs per data node (less one for the overall grid for restore)
v6.1: Three jobs per data node (less one for the overall grid for restore)

One restore for the entire grid

At all other times:

(v5.x, 6.0) 18 jobs per data node (less one for the overall grid for restore) and a maximum of 250 for the grid
(v6.1) 27 jobs per data node (less one for the overall grid for restore) and a maximum of 480 for the grid

One restore for the entire grid

Please refer to Knowledge Base article esg117139 for detailed explanation.

Generated by Jive on 2013-03-13-07:00 3