seperate backupset for stubbing results in default backupset not recognizing stubs

Last post 04-25-2014, 1:56 AM by cvtech. 1 replies.
Sort Posts: Previous Next
  • seperate backupset for stubbing results in default backupset not recognizing stubs
    Posted: 04-23-2014, 8:51 AM

    In my search for the most optimum way to automatically move stubbed files only to the tape aux copies, many have recommended the seperate backupset model, default backupset does the regular backups to disk, then have essentially the same subclients defined in another backupset which only does archiving.


    Plan seems logical but when testing this v10 SP6 on a RHEL5.8 system with VXFS, the default bu set backs up fine. If I turn on disk cleanup it stubs and works good until you want to do the aux copies of the synth fulls, and you wind up copying the entire FS instead of just the stubs. So, turned off disk cleanup on the main subclient, created another backupset and identical subclient but only backing up archived files (in order to be able to move stubbed files around seperately via aux copies), ran the disk cleanup, all is fine. Stubs work fine but when you subsequently backup the original subclient under the default backupset, those files which were stubbed from the "new" backupset job appear as "files" not stubs in the content list. Plus, if you restore what should be a "stub" it restores the whole file (matching what is displayed in the backup file list when browsed). Now, to me this does not seem like it has connected the dots quite right. I understand this may sound confusing and it is until you actually see it in action. The default backup set does not honor the stubs of the secondary backupset disk cleanup.


    Anybody tried this or know whether this needs an incident open?



  • Re: seperate backupset for stubbing results in default backupset not recognizing stubs
    Posted: 04-25-2014, 1:56 AM

    The behavior you are observing could be correct , please route your query to the SME alias , to get a confirmation .

    Best Regards

    Biswanath Das

    Thanks & Regards

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