Media Agent v10

Last post 02-25-2015, 5:55 AM by Ali. 3 replies.
Sort Posts: Previous Next
  • Media Agent v10
    Posted: 02-23-2015, 2:50 PM

    I am building a Media Agent for v10, small according to the sizing document. I am wondering if there are any special considerations, best proactises when configuring the OS (2012 R2). Also for the Index Cache drives and the Dedupe drives is there a specific block size needed or recommended.

    I've taken a look at BOL but didn't find much when looking at the v10 requirement docs.

     

    Thanks

  • Re: Media Agent v10
    Posted: 02-23-2015, 3:02 PM

    Good Day,

    Perhaps the following links may help.

    http://documentation.commvault.com/commvault/v10/article?p=features/os_upgrade/windows8_considerations.htm

    http://documentation.commvault.com/commvault/v10/article?p=features/index_cache/prerequisites.htm

    http://documentation.commvault.com/commvault/v10/article?p=features/deduplication/deduplication_building_block.htm#Hardware_Requirements

    Best Regards

    SG1

  • Re: Media Agent v10
    Posted: 02-24-2015, 3:24 PM

    We have a couple of "small" MA's in our environment. I still configure the DDB disk as a 4K block size and leave the Index Cache on the OS drive. I know this isn't recommended, but I have not come across any issues with sites under 1TB of front end data.

  • Re: Media Agent v10
    Posted: 02-25-2015, 5:55 AM
    • Ali is not online. Last active: 07-03-2019, 12:32 PM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Most of the time I've seen it come down to I/O, if you have the spec to handle that workload you typically wouldn't see issues, until the data sets themselves start balooning

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.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy