Running file archiving and stubbing to a different server maintaining file structure

Last post 06-15-2016, 11:03 AM by Walter Grande. 1 replies.
Sort Posts: Previous Next
  • Running file archiving and stubbing to a different server maintaining file structure
    Posted: 04-04-2016, 3:50 AM


    We are running file archiving and have done so many years. We are working on consolidating our file servers and archiving rules going forward on our new file servers.

    Archive stubs:
    I would like to know whether it is possible to run archiving on a file server , lets call it Server A, and any files that meet the archiving rules, stub them on a different server, lets call it Server B. Whilst the data is stubbed we would like to maintain the original file structure so if file 1 is archived and stubbed , the stub file is actually stubbed on Server B, and if it is nested 2-3 paths down from the root then this should be maintained.

    If the above is possible we would like to know if recalls are triggered on Server B, whether these will be moved back to the original server A or would they be re-hydrated on server B. Is there a way to do it to either way.


    Thanks and hope that makes sense


  • Re: Running file archiving and stubbing to a different server maintaining file structure
    Posted: 06-15-2016, 11:03 AM


    Archive stubs:

    Within your scenario: I will assume that Server A and Server B presently have completely different data (Not Replicated), and that you want to decommission Server A.

    It sounds like you want to archive Server A's data, and copy/restore the Server A's stub files onto Server B.

    Is this a one-time archive and copy/restore operation or were you planning on continuously performing this operation (From Server A to Server B)?



    If the stub file recall (originally from Server A) is triggered on Server B, the data will be restore to Server B. It will be recalled to the present stub file location, and not the stub files original file location.

    The production data will forever be associated with the Commvault Client for Server A, even if the stub files are restored to Server B.

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