In Replication Server 15.5, you can use in-memory and relaxed-durability databases as the replicate database. With Replication Server 15.6, you can use in-memory and relaxed-durability databases as the primary database, and use database resynchronization and bulk materialization to restore in-memory and relaxed-durability databases.
Since an in-memory database exists only in cache, the data and database objects are not saved if the supporting host is shut down or the database fails. To restore in-memory or relaxed-durability replicate databases, you can use:
- Database resynchronization – follow the procedures in "Resynchronize One
or More Replicate Databases Directly from a Primary Database." Ensure that you have enough disk space and time to perform a database dump and load, and that the period of time during which Replication Server skips transactions is acceptable. You can estimate the acceptable period of time by monitoring the segments in the outbound queue with admin who, sqm. See "admin who," in Chapter 3, "Replication Server Commands" in the Replication Server Reference Manual.
- Bulk materialization – follow the instructions in "Resynchronizing a Replicate In-Memory or Relaxed-Durability Database with Bulk Materialization."
See "Support for in-memory and relaxed-durability databases," in Chapter 5, "Managing RepAgent and Supporting Adaptive Server" in the Replication Server Administration Guide Volume 1 to set up replication for the first time or restore in-memory and relaxed-durability databases, using either a template database or a database dump.