Search Engine Sizing

Last post 03-19-2017, 5:46 PM by arunprasada. 3 replies.
Sort Posts: Previous Next
  • Search Engine Sizing
    Posted: 03-15-2017, 6:33 AM

    We are looking at setting up a new Search solution at the moment and I have a question regarding the End-User Search requirements. When using the CommVault SDT, do we enter the total number of objects for ALL backup jobs that have ever run within the storage policy, or do we enter the number of objects based on the last full backup cycle?

    The total number of objects is over 1 billion based on over 5 years worth of backup jobs that have ran, which results in almost 50 End User Search Nodes required!

    Can anyone confirm if the number of objects should be based on ALL jobs that have ever ran within the single storage policy?...thanks

  • Re: Search Engine Sizing
    Posted: 03-15-2017, 8:32 AM

    Hi, If it is only for End User, it should be only the latest cycle that you should calculate. What does your retention look like for the end user data?

  • Re: Search Engine Sizing
    Posted: 03-15-2017, 8:37 AM

    The customer is retaining ALL full backup jobs within the storage policy via extended retention rules stretching back over 5 years since the SP was first created.

  • Re: Search Engine Sizing
    Posted: 03-19-2017, 5:46 PM

    Ideally we need to enter only the number of documents/emails in the last full cycle im the SDT but, in your query you mentioned that we have many fulls and that is a problem. The engine will treat the objects in all full as new documents and that is not desired. We should switch to running forever incremental backup here. Run a syntehtic full every 3 months. This will allow the engine to automatically track the new items and index only them.

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