# Cross-site Disaster Recovery with Percona Operator for MySQL | Percona Community

**URL:** <https://forums.percona.com/t/cross-site-disaster-recovery-with-percona-operator-for-mysql-percona-community/41034>\
**Category:** Community website\
**Created:** [July 6, 2026, 7:42am UTC](https://forums.percona.com/t/cross-site-disaster-recovery-with-percona-operator-for-mysql-percona-community/41034 "2026-07-06T07:42:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [July 6, 2026, 7:42am UTC](https://forums.percona.com/t/cross-site-disaster-recovery-with-percona-operator-for-mysql-percona-community/41034/1 "2026-07-06T07:42:01Z")

</div>

A MySQL InnoDB Cluster provides high availability for a single database cluster using Group Replication. This works well for node failures inside the cluster, but disaster recovery usually requires another cluster in a separate location: another Kubernetes cluster, region, data center, or cloud.

* * *
This is a companion discussion topic for the original entry at [https://percona.community/blog/2026/07/06/cross-site-disaster-recovery-with-percona-operator-for-mysql/](https://percona.community/blog/2026/07/06/cross-site-disaster-recovery-with-percona-operator-for-mysql/)