Low disk space on the SIDB index [copy - [Primary] doesn't have enough space to Backup SIDB files in to /cvstorage/cv_lv_01/SP_DDP_HQ_VM/CV_SIDB/2/94/BACKUP/94].

Last post 03-27-2012, 5:07 PM by PhilippeMorin. 1 replies.
Sort Posts: Previous Next
  • Low disk space on the SIDB index [copy - [Primary] doesn't have enough space to Backup SIDB files in to /cvstorage/cv_lv_01/SP_DDP_HQ_VM/CV_SIDB/2/94/BACKUP/94].
    Posted: 03-27-2012, 4:10 PM

    I think my deduplication store isnt pruning the old jobs properly.  Is there an easy way that I can determine what the problem is and or fix this problem so that my storage is not filled up over time?


    Thanks ahead of time for the input!


  • Re: Low disk space on the SIDB index [copy - [Primary] doesn't have enough space to Backup SIDB files in to /cvstorage/cv_lv_01/SP_DDP_HQ_VM/CV_SIDB/2/94/BACKUP/94].
    Posted: 03-27-2012, 5:07 PM

    There was a bug many service packs ago where the DDB backups wouldn't get pruned automatically. Usually, it should only keep the last backup but from time to time, it would stop deleting old jobs and your DDB mount path would fill up.

    The SIDB's current backup will only be in the most recent folder (you can check by comparing the size of your SIDB and the size of your backup) so it is safe to delete older folders in your /cvstorage/cv_lv_01/SP_DDP_HQ_VM/CV_SIDB/2/94/BACKUP/94 folder. This should free up a lot of space.

    If you're using SP4 or later, I'd suggest moving away from those backups and using the new way which is through the filesystem agent. You can check the following link in the BOL for more info:


    If you are pre SP4 and can't upgrade, there's a registry key to move the DDB backup to another mount path so that at least if it fills up, it won't impact your live DDB. I'll have to search to find what the key was... let me know if you need it or if you're just going to move to the new DDB backup strategy.


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