SDR Aging

Last post 09-27-2012, 8:21 AM by Stupek. 2 replies.
Sort Posts: Previous Next
  • SDR Aging
    Posted: 09-20-2012, 5:15 PM

    Working on a V8 to V9 migration and have a question. Currently using SDR, but want to repurpose the SDR target SAN disk in to the new V9 environment to use as the DASH Copy target. The question is – once we stop replication and then break the SDR process (i.e. we will still have the source primary copy , but no longer have the target available), will the data age out of the source primary copy okay, or will it error out since it cannot age the data out of the SDR target.

  • Re: SDR Aging
    Posted: 09-26-2012, 7:42 PM

     

    Primary copy job will have dependency on sync copies with respect to Data Aging. 

    If you intend to break SDR and start with DASH, you first need to make sure the auxcopy doesn't have any jobs on it or non set as 'to-be-copied'. Make sure to delete these jobs from Auxcopy(SDR target) prior to breaking SDR, this way DB is clear and primary copy dependency is gracefully unlinked. 

     

    If you just take the target out, the DB will still know that these jobs existing on the Target copy and will be in an Orphan state. You can still go and delete them manually but that is goinga round in reverse.

     

    If you intend to retain the jobs on target, the best way is to Migrate SDR to DASH. Thee way to achieve this is create another Deduplication auxcopy on the Storage Policy, and the the source copy for this auxcopy is the target auxcopy of the SDR replication. When you now run this new Auxcopym, it will seed all these jobs in to the Dedupe database on target MA and once done,you can change this new Auxcopy to copy from primary and then can get rid of SDR and old auxcopy.

     


    Raj A
  • Re: SDR Aging
    Posted: 09-27-2012, 8:21 AM

    Aging on the destination is done by Replication.  The Source is done by standard data aging.  The only way that data aging will have an issue is if the customer is running Aux copies from the Destination side and not the source, then the Aux copies would be dependent on the destination being up to date.  If the Aux copies are failing then data will not age correctly. 

    All you will need to do is ensure that the Aux copies (if running them) are being done against the source data, if that is the case then aging will work correctly and no further action will be required.  You will have to manually prune the data from the destination once its not needed.

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