Shared-All Persistence Usage

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. Ensure that the API call tibasSpace_SetPersister() in the C API or Space.setPersister() in Java are not used with spaces that are routed. Remember space routing cannot be used with cross-site replication.
  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.