Question on stubbing process

Last post 05-12-2014, 10:09 AM by hwang. 1 replies.
Sort Posts: Previous Next
  • Question on stubbing process
    Posted: 05-05-2014, 11:32 AM


    Just want to confirm, during an archiving job (whether is standalone archiving agent or FS agent with one pass enabled), all file qualified for archiving are first copied to the storage policy repository first, then only get deleted on produciton storage and replaced by stub during the "stubbing" phase, correct?  meaning CV does not stub files one by one as it is being archived.

    also, if during the stubbing process, the job failed or goes into pending state due to unforeseen issue (black out, MA failure, CS failure etc), what is the impact to the production files?

    My guess is that those file that is not being stubbed remained as unarchived file on the production storage and will be archived during the next archive job.  But in the mean time, CV already has a copy of the un-stubbed file in the storage policy repository.


    please correct me if I am wrong.




  • Re: Question on stubbing process
    Posted: 05-12-2014, 10:09 AM



    There are four phases for archiving job (filescan, backup, archiveindex, stubbing). During an archiving job, files qualified for archiving are backed up in backup phase and files will be replaced by stub in stubbing phase.


    During stubbing phase, if job failed or goes to pending due to unforseen issue, archiving job will complete with errors. Files that are not stubbed will remain as unarchived file on source disk and will be archived during next archive job.  and Yes, for those not stubbed files, CV already backed up and there is one copy in the storage policy repository.



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