Database Replication ​

Asynchronous database replication is the process of maintaining a replica of a Yellowbrick database on a remote Yellowbrick instance. Replication supports the following use cases:

• Disaster recovery (DR) and high availability (HA): A replica is virtually a live backup, preserving an exact copy of a database on a separate system, ready for use in the event of a failure or loss of data on the source system. The primary and secondary (source and target) systems can reverse roles as needed, providing failover and failback support.
• Automated backup and restore: Replication may be used simply as a way to automate backup and restore operations without the need for intermediate storage.
• One-time data migration: replication is a convenient way to move data, such as when you are migrating a database from a small Yellowbrick system to a larger system.
• Adding reporting horsepower: for example, replication supports two instances synchronized with the same data, both of which can provide reporting capability.

Replication occurs at the database level, based on transactions that have been committed to a source database. A database replica is maintained by "backup snapshots" of the source database in the source system. These backups are taken frequently and automatically by a service that runs in the background. The changes are automatically streamed to the database replica in the target system at regular intervals.

The following sections explain how to set up replication, create database replicas, and start the replication of specific databases.