updated ARS documentation for configuration of replication between 2 cell managers and b2d deduplication stores.

Hello all,

Can anyone share a new updated step by step documentation for configuring and implementing ARS between two Cells and their associated B2D deduplication stores?

  • Suggested Answer

    0  

    Hi Nick,

    you can find the details you are asking in DP administrer section manual in chapter "replicate Object" and then "Automated replication synchronization"

    Kind regards,

    Dionisio Sciascia

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.

  • Suggested Answer

    0  

    And here's the direct link into the 24.4 documentation: Automated replication synchronization

  • 0 in reply to   

    Thank you Dionisio.

    The administer section of the manual, under prerequisites states:


    Create new target Deduplication devices on both source and foreign Cell Managers. Ensure that the store name of the target deduplication
    device you select for replication is identically the same on the source Cell Manager as well as the foreign Cell Manager.

    This part I understand, but I was wondering if you could elaborate on the number of devices that are required on the source Cell Manager in order to perform ARS.  For example, the object copy specification will not allow the source and destination device to be the same. Which makes sense, am I correct to assume that two B2D devices are required on the source CM that point to the same dedupe store?  One store, which the backup spec writes to and then a "dummy" device which points to the same store which is selected as the destination device in the object copy spec?

  • Suggested Answer

    0   in reply to   

    Dionisio seems to be offline right now. Let me try to clarify this.

    You'll need 2 devices on your source cell indeed. But they aren't pointing to the same store. The first one is pointing to your store on the primary site. This is the one your backups are written to. The other one is pointing to the store on the secondary or replication site and will be the destination of your replication. On the secondary or replication cell, you will have a device pointing to the replication store, so that is again the destination of your replication. After the ARS completes, the media will only be seen once on the primary site (in the original backup store) and once on the secondary site (in the replication store). The replication destination on the primary site will be empty. So even though there are devices pointing to the same replication store on both sites, from a DP perspective the replication destination seen from the primary site will be empty after the session has finished. You have to look at that device as temporary and only to be used by the replication session. Or better: its content is temporary from a DP perspective.

  • 0 in reply to   

    Thank you Koen for the clarification, it is very helpful.

    One follow up question I had was about the second store that is required on the source CM.  This store as seen from the source cell manager can belong to any device and associated deduplication server as long as the store name is the same as the FCM ? 

  • Verified Answer

    0   in reply to   

    I'm sorry for my later reply. I have had login issues on this forum.

    Well it is essentially the same store on both sides, so the store name is obviously the same. This store is configured twice, one time in each cell. The store itself only exists once on 1 hardware device. Not sure what exactly you mean by "can belong to any device and associated deduplication server". But that doesn't sound right. As it is one and only one store, it will be on one specific deduplication server.