Skip to content

Commit 6ee0d04

Browse files
committed
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-26582
1 parent eed1cc0 commit 6ee0d04

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

release_notes/known_issues_continuity.adoc

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -93,6 +93,15 @@ oc delete appliedmanifestwork <the-left-appliedmanifestwork-name>
9393

9494
link:https://github.com/stolostron/backlog/issues/27129[ACM-27129]
9595

96+
[#baremetalhost-not-backed-up]
97+
=== The BareMetalHost resources are not backed up by default
98+
99+
BareMetalHosts used to add hosts to a host inventory when using Central Infrastructure Management are not included in backups by default.
100+
101+
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.
102+
103+
link:https://issues.redhat.com/browse/ACM-26582[ACM-26582]
104+
96105
[#known-issues-volsync]
97106
== Volsync known issues
98107

0 commit comments

Comments
 (0)