CommCell Migration and DASH with remote Office

Last post 11-27-2013, 3:48 PM by Ali. 7 replies.
Sort Posts: Previous Next
  • CommCell Migration and DASH with remote Office
    Posted: 10-25-2013, 8:53 AM

    Hi All,

    We have 2 commcell running V9 SP11a.

    In the first infrastructure, we have 12 media agent with local deduplicated copy. (One Storage Policy per site)

    Those local magnetic Library are synchronized every night with a central media agent in our datacenter using DASH. (a synchronous copy in SP pointing to a global dedup)

    We would like to :

    • Migrate those media agent in our second infrastructure, with ensure that we don't have to reseed the global ddbstore (reuse of block of backup perform by the 1rst CommCell)
    • Change the media agent hosting the Global DDB in datacenter.

    The media agent actually hosting the global database must stay in the first infrastructure.

    According the reading to the BOL CommCell Migration :

    http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/features/cc_migration/cc_migration.htm

    I understand that on all office media agent migrated from 1rst infra to the 2nd infra, DDB Store will be sealed so future job will seed a new store. So we must ensure we have sufficient space on office MagLib. The central DDB will be also sealed in the new infra and cannot be used to reference block, we must re-seed the central DDB.

    I also understand that I must manually copy the maglib and the sidb store to a new media agent according to the  IMPORT METADATA ON THE DESTINATION COMMCELL section in the migration process.

    So according to our previous question, my answers should be :

    Yes, we must re-seed the global DDB.  Cry

    Yes, we can change the media agent hosting the ddb when migrating from one commserve to another. Cool

     

    Does anyone have already perform this operation and can confirm/infirm ?

    Many thanks.

  • Re: CommCell Migration and DASH with remote Office
    Posted: 10-28-2013, 8:56 PM
    • Ali is not online. Last active: 07-03-2019, 12:32 PM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Hi Mathieu, yes stores will seal post merge.

    Another option, if space is not an issue, allow the data to age off 1st infra and disable the clients for backup, use them for restores only.  Move clients over to 2nd infra and start fresh backups there, once retention is met on 1st infra, remove those clients/data which is not required.

     

  • Re: CommCell Migration and DASH with remote Office
    Posted: 11-03-2013, 12:22 PM
    Hi Ali,

    Thanks for your reply.

    Well, space is not a issue, either locally or in datacenter... But network are ^^
    So we would like to ensure we will not have to re-seed the store in datacenter using our WAN...
     
    Can you confirm that referenced block in a sealed ddb can only be used for restore ?
    And then, all block are treated as new reference and transfered in datacenter in our case ?
     
    Many thanks.
  • Re: CommCell Migration and DASH with remote Office
    Posted: 11-04-2013, 2:29 PM
    • Ali is not online. Last active: 07-03-2019, 12:32 PM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Hi Mathieu, thats correct.

    The moment a store is sealed, any incoming block to the DDB would be treated as unique, and will not reference the sealed store going forward, a new baseline of blocks will be wirtten to disk, guesing that's what you're meaning to ask.

  • Re: CommCell Migration and DASH with remote Office
    Posted: 11-06-2013, 3:55 AM

    Hi Ali, 

    Thanks for your reply.

    Yes, this is exactly the information I like to confirm.

    As disk space is not a problem, we consider an alternative :

    We think to restore all the available jobs in datacenter on a new disk (re-hydrated data) and plan a backup of those data from the new media agent. This operation should seed the DDB with block of data known remotely ?

    Then we can migrate the remote media agent to 2nd infra, backup and synchronise them with datacenter.

    In our comprehension, this should reduce the time needed for the first dash copy.

    Can you confirm this option ?

    Many thanks

  • Re: CommCell Migration and DASH with remote Office
    Posted: 11-11-2013, 4:19 PM
    • Ali is not online. Last active: 07-03-2019, 12:32 PM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Thanks, intresting thought, that may work, would suggest to just test a few clients just in case.   Also if doable reach your local account team to run this by your local SE/PS teams to see if there may be a better way, given the overall business impact/recovery SLAs.

     

  • Re: CommCell Migration and DASH with remote Office
    Posted: 11-21-2013, 7:22 AM

    Hi Ali,

    We just have made the test last day and .... It's working fine :

    First Backup of rehydrated and migrated data :

    Second Backup :

    Only signature and log are transfered :-)

     

    Many thanks.

  • Re: CommCell Migration and DASH with remote Office
    Posted: 11-27-2013, 3:48 PM
    • Ali is not online. Last active: 07-03-2019, 12:32 PM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Thanks for the confirmation and marking this solved Smile

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