Shared-All Persistence Usage

  1. Cross-site replication only replicates PUT and TAKE operations and transactions across sites. On the DR site, iIt does not automatically create metaspaces, members, spaces, and so on. This is up to you to handle appropriately.
  2. The space definition on the DR site need not exactly match the space definition on the primary site. Only the space name and data field related settings should match. For example, if you expect to failover to the DR site and perform the same queries as you would on the primary site, then the indexes should match. Other space definition settings, such as persistence and minimum seeder count, can be varied on the DR site according to the your needs.
  3. Cross-site replication occurs for all spaces within a metaspace. You cannot choose individual spaces to be replicated.
  4. Space routing cannot be used with cross-site replication.
It is not required that persistence must be run on both the primary and DR sites. If you are running shared-all persistence on both your primary and DR sites, keep the following in mind:.
  1. Each site should have an independent persister callback implementation and external persistent storage medium.
  2. Remember space routing cannot be used with cross-site replication. The setPersister() calls are not routed. Ensure that you call setPersister() on both the sites.
  3. Run the persister callback client on each site.

Alternatively, you can run shared-all persistence only on your primary site without also running it on your DR site. For this scenario, create a space definition on your DR site without setting the persistence type and persistence policy. With cross-site replication, space definitions between the primary site and DR site are not compared. Only the space name and data fields need to match. Other space definition settings, such as persistence, can differ between sites.