Replication Server supports as the replicate database:
In-memory databases
Relaxed-durability databases set with durability at no_recovery
The primary database must be a traditional full-durability, disk-resident database. For convenience, this document refers to relaxed-durability databases with durability set to non_recovery as “relaxed-durability databases.”
You can initialize an in-memory and relaxed-durability database as a new replicate database by obtaining data, object schema, and configuration information from one of:
A template database that retains basic information.
A database dump from another database. Load the dump to the target in-memory database or relaxed-durability database.
The dump source database can be another in-memory database, relaxed durability database, or a traditional disk-resident database.
In-memory and relaxed-durability databases lose their object definition, data, and RepAgent configuration once the host data server shuts down or restarts. You must reinitialize the in-memory or relaxed-durability database from the template or database dump from a source database.
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 configure an in-memory or a relaxed-durability database as a replicate database.