Skip to content

Commit

Permalink
Merge pull request #7148 from stolostron/jcberger-13207-typ-2.10
Browse files Browse the repository at this point in the history
made changes for 2.10
  • Loading branch information
jc-berger authored Oct 22, 2024
2 parents fde81e6 + cd10ffe commit 3e3eaa3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion business_continuity/backup_restore/backup_schedule.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -155,7 +155,7 @@ For descriptions of the various `BackupSchedule` statuses, see the following tab
[#avoid-backup-collision]
=== Avoiding backup collisions

Backup collisions might occur if the hub cluster changes from being a passive hub cluster to becoming a primary hub cluster, or the other way around, and different managed clusters back up data at the same storage location.
Backup collisions might occur if the hub cluster changes status from passive to primary hub cluster, or from primary to passive, and different hub clusters back up data at the same storage location.

As a result, the latest backups are generated by a hub cluster that is no longer set as the primary hub cluster. This hub cluster still produces backups because the `BackupSchedule.cluster.open-cluster-management.io` resource is still enabled.

Expand Down

0 comments on commit 3e3eaa3

Please sign in to comment.