From fda43d5834fd6a542bf040c5bd5bb849d0cb0cbd Mon Sep 17 00:00:00 2001 From: Nick Carboni Date: Thu, 20 Nov 2025 10:42:55 -0500 Subject: [PATCH] Note that BMHs are not backed up by default BMHs used to add hosts in CIM are not backed up by default. Add a note about this in the DR known issues and document a workaround. https://issues.redhat.com/browse/ACM-26586 --- release_notes/known_issues_continuity.adoc | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/release_notes/known_issues_continuity.adoc b/release_notes/known_issues_continuity.adoc index 1dc72e7fcf..6ffcb3cd35 100644 --- a/release_notes/known_issues_continuity.adoc +++ b/release_notes/known_issues_continuity.adoc @@ -93,6 +93,15 @@ oc delete appliedmanifestwork link:https://github.com/stolostron/backlog/issues/27129[ACM-27129] +[#baremetalhost-not-backed-up] +=== The BareMetalHost resources are not backed up by default + +BareMetalHosts used to add hosts to a host inventory when using Central Infrastructure Management are not included in backups by default. + +You can add the `cluster.open-cluster-management.io/backup: cluster-activation` label to the BareMetalHosts to include them in backups. For more information, see the link:../business_continuity/backup_restore/backup_arch.adoc#resources-restored-managed-cluster-activation[Resources restored at managed clusters activation time] topic. + +link:https://issues.redhat.com/browse/ACM-26582[ACM-26582] + [#known-issues-volsync] == Volsync known issues