- Elastic Docs/
- Deploy and manage/
- Backup, high availability, and resilience tools/
- Cross-cluster replication/
- Uni-directional disaster recovery
Prerequisites for uni-directional disaster recovery
Before completing this tutorial,set up cross-cluster replication to connect two clusters and configure a follower index.
In this tutorial,kibana_sample_data_ecommerce is replicated fromclusterA toclusterB.
## On clusterB ###PUT _cluster/settings{ "persistent": { "cluster": { "remote": { "clusterA": { "mode": "proxy", "skip_unavailable": "true", "server_name": "clustera.es.region-a.gcp.elastic-cloud.com", "proxy_socket_connections": "18", "proxy_address": "clustera.es.region-a.gcp.elastic-cloud.com:9400" } } } }}
## On clusterB ###PUT /kibana_sample_data_ecommerce2/_ccr/follow?wait_for_active_shards=1{ "remote_cluster": "clusterA", "leader_index": "kibana_sample_data_ecommerce"}
Important
Writes (such as ingestion or updates) should occur only on the leader index. Follower indices are read-only and will reject any writes.