Configuring replication between collectives

[Version 2.0.0.3 and later] By establishing collective links between the catalog servers in your collectives, you can asynchronously replicate data between data grids in two different collectives.

Before you begin

  • You must have at least two collectives configured. For data to replicate between the collectives, you must create identical data grid configurations in each collective.
  • Decide which type of multiple collective topology you want to define. For more information about multimaster topologies, see Topologies for multiple collectives.

About this task

A single collective does not span an unreliable network because false positive failure detections might occur. However, you might still want to replicate data grid data across appliances that have unreliable network connectivity. Some common scenarios where you might want to use this type of topology follow:
  • Disaster recovery between data centers where one collective is active and the other is used for backup.
  • Geographically distributed data centers where all collectives are active for geographically close clients.
After you connect two collectives, any data grids that have the same names are asynchronously replicated between the collectives. These data grids must have the same number of replicas in each collective, and must have the same dynamic map configurations.

Procedure

  1. Establish a link between the collectives.
    • Establishing collective links with the xscmd utility:
      1. Get the catalog server IP address and port for the catalog servers in each collective. In the user interface, click Collective > Members > collective_member_name. A list of catalog servers and port numbers is displayed. Repeat this step for each collective that you want to connect.
      2. Connect the xscmd utility to one of the collectives. For more information about starting the xscmd utility, see Administering with the xscmd utility.
        xscmd.sh -ts xsatruststore.jks -tst jks -ssl -tsp xc10pass 
        -user xcadmin -tsp xcadmin -cep myxc10.mycompany.com:2809 
        [additional_xscmd_parameters]
      3. From the collective to which you are currently connected, run the following command:
        xscmd –c establishLink -cep myxc10.mycompany.com:2809 -fd dname 
        -fe myxc102.mycompany.com:2809,myxc103.mycompany.com:2809
        In the previous example, the -fd dname parameter gives a name to the remote collective. the -fe myxc102.mycompany.com:2809,myxc103.mycompany.com:2809 parameter lists the catalog servers within the foreign collective to which you want to connect.

    When the link is established, the catalog servers in the collectives begin to replicate with each other. You do not need to establish the link in both directions.

  2. You can also dismiss links between collectives.
    • Dismissing collective links with the user interface: In the user interface, click the remove icon (delete) to remove a selected link.
    • Dismissing collective links with the xscmd utility: With the xscmd utility, run the following command:
      xscmd –c dismissLink -cep myxc10.mycompany.com:2809 -fd dname
Parent topic: Administering collectives and zones
Previous topic: Creating and modifying zones
Related concepts:
Topologies for multiple collectives
Appliance topology: collectives, zones, and data grids