Note: Doc team updates the current version of the documentation and the
two previous versions (n-2), but we address *only high-priority, or
customer-reported issues* for -2 releases in support.
Describe the changes in the doc and link to your dev story:

1. - [x] Mandatory: Add the required version to the Fix version/s field.

2. - [ ] Mandatory: Choose the type of documentation change or review.

• [x] We need to update to an existing topic

• [ ] We need to add a new document to an existing section

• [ ] We need a whole new section; this is a function not
  documented before and doesn't belong in any current section

• [ ] We need an Operator Advisory review and approval

• [ ] We need a z-Stream (Errata) Advisory and Release note
  for MCE and/or ACM

3. - [ ] *Mandatory: *Use the following link to open the doc and find where the
documentation update should go. Note: As the feature and doc is
understood and developed, this placement decision may change:

• Published doc: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10
• Source: https://github.com/stolostron/rhacm-docs

4. - [ ] Mandatory for GA content:

• [ ] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:

• [ ] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:

• [ ] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)

• [ ] Add link to dev story here:

5. - [ ] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.

Update this link

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/business_continuity/business-cont-overview#resources-that-are-backed-up

Update : 

• Back up all resources from: argoproj.io, app.k8s.io, core.observatorium.io, hive.openshift.io. These resources are backed up within the acm-resources-schedule backup, with the exception of the resources from the agent-install.openshift.io API group. These resources are backed up within the acm-managed-clusters-schedule backup.

With ( add extra info )

• Back up all resources from: argoproj.io, app.k8s.io, core.observatorium.io, hive.openshift.io. These resources are backed up within the acm-resources-schedule backup, with the exception of the resources from the agent-install.openshift.io API group. These resources are backed up within the acm-managed-clusters-schedule backup. The following hive.openshift.io and hiveinternal.openshift.io
  resources are also backed up by the }}{{acm-managed-clusters-schedule backup: 

• • clusterdeployment.hive.openshift.io

  • machinepool.hive.openshift.io
    clusterpool.hive.openshift.io
    clusterclaim.hive.openshift.io
    clusterimageset.hive.openshift.io
    clustersync.hiveinternal.openshift.io