Chapter 12. Managing Geo-replication
- 12.1. About Geo-replication
- 12.2. Replicated Volumes vs Geo-replication
- 12.3. Preparing to Deploy Geo-replication
- 12.4. Starting Geo-replication
- 12.5. Starting Geo-replication on a Newly Added Brick
- 12.6. Disaster Recovery
- 12.7. Example - Setting up Cascading Geo-replication
- 12.8. Recommended Practices
- 12.9. Troubleshooting Geo-replication
This section introduces geo-replication, illustrates the various deployment scenarios, and explains how to configure geo-replication and mirroring.
12.1. About Geo-replication
Geo-replication provides a distributed, continuous, asynchronous, and incremental replication service from one site to another over Local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
Geo-replication uses a master–slave model, where replication and mirroring occurs between the following partners:
- Master – a Red Hat Storage volume.
- Slave – a Red Hat Storage volume. A slave volume can be either a local volume, such as
localhost::volname, or a volume on a remote host, such asremote-host::volname.