Best Practices for efficient Storage Usage in Commvault

Last post 10-12-2017, 9:41 AM by vpru. 3 replies.
Sort Posts: Previous Next
  • Best Practices for efficient Storage Usage in Commvault
    Posted: 08-22-2017, 4:54 AM

    Hello guys,


    we are planning to open two new DCs with planned 3000-4000 clients. Currently we have ~1PB storage in each space and want to prepare for such load by having an efficient storage usage.

    We have various data - VMs, Windows, Linux, zLinux, SQL, DB2.

    Could you please share your thoughts what is best way to create disk libraries? Should we create disk libraries by data types (i.e. one for VMs, one for Windows/Linux, one for databases) to have better deduplication ratio or better mix data and distrubute the data load by Media Agents (4 MA planned).

    Please share share experience what to check and take more atention before go-live.


    Thank you!

  • Re: Best Practices for efficient Storage Usage in Commvault
    Posted: 08-22-2017, 9:26 AM
    Hi rolbraz, You can achieve better utilization of storage by using deduplication similar kind of data at storage policy level. Eg - Create a deduplication enabled policy for filesystem/VM backups Create a another deuplication policy for SQL backups and another deduplication policy for oracle database backups. For better dedup ratio you should always deduplicate similar kind of data.We should not deduplicate dissimilar kind of data. We can hold upto 2 DDB's on a mediaagent. So you can create appropriate storage policies as you have 4 mediaagents and then back them up. Secret is always use a single global deduplication policy for similar kind of data. Hope it is helpful
  • Re: Best Practices for efficient Storage Usage in Commvault
    Posted: 08-23-2017, 3:29 AM

    Thanks, vpru, for your message.

    To reach the best deduplication ration and efficiency, do you know which data we can separate.. as an example, we want to create 3 or 4 deduplication engines and disk libraries.. one disk library will be dedicated for databases (SQL, DB2), another could be dedicated for NAS data, next one for VMs/Windwos/Linux.. how do you think, is it worth to separate NAS data or keep it with Windows for example, or better separate Linux or VM data to separate pool?

  • Re: Best Practices for efficient Storage Usage in Commvault
    Posted: 10-12-2017, 9:41 AM

    Sorry for the delay.You cna seperate structured data from unstructured data.Again this is for creation deduplication policies dedicated for structured data.And seperate deduplication policy for unstructured data.


    You can always share your disk libraries which are going to save the backed up data

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