Advice on media agent specs/multiple agents

Last post 06-05-2019, 6:13 PM by Wwong. 4 replies.
Sort Posts: Previous Next
  • Advice on media agent specs/multiple agents
    Posted: 05-24-2019, 12:50 PM

    We currently have a single media agent handling our main storage policy with three copies, primary, secondary, and tape.

    We are looking to refresh our environment this upcoming fiscal year, and in addition to replacing our current media agent, are also considering the purchase of an additional server to act as a second media agent to divide the load. Our front end data ranges from 18.5 to 21 TB, depending on the week. Our current media agent is connected to both our backup targets over 10 Gbit connections, which are dell servers running Ubuntu.  

    I’m looking for assistance/validation in our planning:

    Does anyone have suggestions for specs for the media agents? We are following the recommended guidelines, but were wondering how important the different components are relative to one another. Is it more important to many cpu cores with a slower clock speed, or better to have fewer cores with a very high clock speed? How important is ram vs cpu performance?

    Does anyone have advice/recommendations on best practices for integrating multiple media agents into the backup environment? Alternatively, do we even need a second media agent? What are the load numbers beyond which more media agents would be recommended?

  • Re: Advice on media agent specs/multiple agents
    Posted: 05-24-2019, 10:46 PM

    Hi Kuritzo

    The following documentation should help in your sizing plan (

    It provides detail on the required MediaAgent specification base on Front-end Data Size, IDA and workload. 

    On top of the recommended specification, if you are to use Commvault Deduplication, please consider getting local SSD, in RAID 1 or RAID 10 configuration (not HDD or SAN presented Volume) to improve overall Backup performance and minimize any potential latency



  • Re: Advice on media agent specs/multiple agents
    Posted: 05-28-2019, 12:39 PM

    Thanks Winston for your help!

    We are trying to follow the documentation you referenced, but couldn't find any information on the importance of CPU clock speed, e.g., would it be better to have 12 cores with 2Ghz clock speed, or 8 cores with 3.5 Ghz. We have a few options in purchasing new servers, and are trying to make the most informed decision possible.

    Also, do you think it would be useful for us to get a second media agent, given that our current workload falls squarely between the medium/large media agent sizing, and we are speccing for the large? Right now our single media agent handles our primary copy, our aux copy, and our tape backup. Is there any performance degradation from having a single media agent handle multiple copy policies at the same time?



  • Re: Advice on media agent specs/multiple agents
    Posted: 06-03-2019, 10:08 AM
    • Aplynx is not online. Last active: 09-13-2019, 12:47 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,705

    You may want to discuss these config questions with your account rep. 

  • Re: Advice on media agent specs/multiple agents
    Posted: 06-05-2019, 6:13 PM

    Hi Kuritzo

    Commvault being hardware agnostic will only provide a holistic architecture overview, it won't go down to Clock Speed. However it would be recommended to go with more core, as different Commvault operation could utilize more resources. 

    It would also be advisable to have a second MediaAgent if you have requirement of a secondary site, where the Primary Copy of Backup Data needs to be replicated. 

    Depending on the retention period the sizing would be relative in size. 

    As we move towards actual architecture design/implementation, I do agree with Liam it would be best to engage the Account Rep to discuss the finer details. 



The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy