Avamar: ADMe -How to Use and Create Multiple MCS Staging Threads

Establishing Multiple MCS Threads

To improve aggregate staging throughput, ADMe relies on the establishment of multiple MCS sessions. The process for establishing additional MCS threads to a staging server is scripted and follows a predefined naming convention.

See the attached pdf for instructions on how to use the two scripts. PDF can be found under the related tab (Files) 

Naming Convention

The naming convention for MCS thread names is as follows:

• base-client-name
  •  As seen in Avamar once the Staging Server (SS) is activated to the /ADME domain /ADME/base-client-name
• base-client-name_a
  •  As seen in Avamar after the process has run to establish the next sequential thread name /ADME/base-client-name_a
• base-client-name_b, so forth
  • Subsequent executions of the script process automatically establish the next sequential thread name using the appropriate suffix incrementing as _b _c _d so forth

Script Locations

The scripts for establishing multiple MCS threads can be found in the following locations:

• Windows:
  •  A common set of Avamar binaries is used but a separate /var folder is established incrementing its folder name suffix to /var2, /var3, /var4, so forth along with the creation of a dedicated service for each.

    C:\Program Files\avs\etc\scripts\wthreads2.bat

• Linux:
  • Separate copies of the Avamar binaries are used to folder /usr/local/avamar/base-client-name_a and a dedicated avagent is started for it, subsequent threads use _b, _c _d and so forth. 

    /usr/bin/Lthreads.sh