DR replication and removing a few servers from the Dash to DR and dedupe

Last post 09-09-2014, 4:26 PM by Ali. 1 replies.
Sort Posts: Previous Next
  • DR replication and removing a few servers from the Dash to DR and dedupe
    Posted: 09-09-2014, 4:12 PM

     

    We currenty having a problem trying to get our data replicated out to our DR site in another state.  The problem is we have a pipe being utilized by our netapp, commvault and other mission critical systems. (we are currently looking at circuit options to upgrade the pipe between the two)

    So as an option to get mission critical systems replicated out to our DR - we decided taking a few of our SAS data out of the replication process and adding them onto a new storage policy that still continues to backup the sas data just removes it from the replication to DR process.

    So which leads me to my question - if we create a new SP and add our SAS data to the new policy and remove it from the old policy - what happens to the deduped data from the old SP will it have to dedupe the data using up more disk space?

    What I don't want to do is lose the deduped data and have to re-backup the data in the new storage policy and have to retain all the jobs and data on the old SP keeping it separate. 

     

    Or is there a way to exclude certain types of data from the aux copy replication to DR with creating a new SP?

     

  • Re: DR replication and removing a few servers from the Dash to DR and dedupe
    Posted: 09-09-2014, 4:26 PM
    • Ali is not online. Last active: 07-03-2019, 12:32 PM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Hello Tatsit,

    1. If you create a new copy or new policy and move any new jobs with dedupe enabled, you will lay down a new baseline as you're introducing new blocks into the engine

    2.  You could prevent the replication (guessing this is a DASH copy?) of select clients by removing them from the associations tab.

    3.  If you were to use option #1, the data would eventually age off the other copy once retention is met, or you manually prune those jobs to "catchup"

    4.  On the existing replication (guessing this is a DASH copy) you could also View Jobs and diable the jobs which are in a Partial or To Be Copied state as well to catchup

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