﻿---
title: Bi-directional recovery: Failback when clusterA comes back
description: You can simulate this by turning cluster A back on.Data ingested to cluster B during cluster A 's downtime will be automatically replicated.If you have...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5385/deploy-manage/tools/cross-cluster-replication/_failback_when_clustera_comes_back_2
products:
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Bi-directional recovery: Failback when clusterA comes back
1. You can simulate this by turning `cluster A` back on.
2. Data ingested to `cluster B` during `cluster A` 's downtime will be automatically replicated.
   - data streams on cluster A
  - 150 documents in `logs-generic-default-replicated_from_clusterb`
- 50 documents in `logs-generic-default`
- data streams on cluster B
  - 50 documents in `logs-generic-default-replicated_from_clustera`
- 150 documents in `logs-generic-default`
3. If you have Logstash running at this time, you will also observe traffic is sent to both clusters.