question on ddb verification - large difference in time/size within SP

Last post 10-10-2019, 8:11 PM by Watson. 1 replies.
Sort Posts: Previous Next
  • question on ddb verification - large difference in time/size within SP
    Posted: 10-10-2019, 4:10 PM

    I have a storage policy, with one primary, and a secondary copies.  When the daily DDB verification process runs, the verification in the primary takes an hour and forty-five minutes, the application size is reported to be 1.21 TB

    For the secondary copy, it takes 13 minutes, and the application size is 82 GB.

    Not understanding why there would be such a difference in the size within the same storage policy.  Should be the same data.

    If anyone could throw some light on my ignorance, it would be appreaciated.

  • Re: question on ddb verification - large difference in time/size within SP
    Posted: 10-10-2019, 8:11 PM
    Hi Deb,
    The DDB Verification Job that is scheduled to run daily, verifies all that were written since the last 
    DDB Verification.
    If the secondary copies are an exact replica of the source (same jobs were written) then we would 
    expect the Incremental DDB Verification on the Primary and Secondary to be similar size.
    If the jobs are not copied to the secondary copy when the Incremental DDB Verification runs, 
    it would be smaller.  On a storage policy copy if you view jobs on a storage policy copy you can
    view the Data Verification Status and Last Verified Time.
    If you would like to create a Commvault support ticket we can check further to determine 
    why there Incremental DDB Verification on the secondary copies is verifying less than the 
    primary copies.
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 © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy