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.

This link

https://github.com/stolostron/rhacm-docs/blob/2.12_stage/business_continuity/backup_restore/backup_install.adoc

Change #1

Under https://github.com/stolostron/rhacm-docs/blob/2.12_stage/business_continuity/backup_restore/backup_install.adoc#enabling-the-backup-operator

Step 3 and 4 should be subitems of item 2:

Replace :

2.Manually install the cluster backup and restore operator.

3. Enable the cluster backup and restore operator (cluster-backup).

4. Edit the MultiClusterHub resource by setting the cluster-backup parameter to true. If this hub cluster does not have the AWS Security Token Service (STS) option enabled, the OADP operator is also installed in the same namespace with the backup component. For hub clusters where the STS option is enabled, you must manually install the OADP operator.

To:

2. Manually install the cluster backup and restore operator.  To install the cluster backup and restore operator, edit the MultiClusterHub resource and set the cluster-backup parameter to true.

Note: If this hub cluster does not have the AWS Security Token Service (STS) option enabled, the OADP operator is also installed in the same namespace with the backup component. For hub clusters where the STS option is enabled, you must manually install the OADP operator.

Change #2

Replace steps 5-7 :

1. Ensure that the restore hub cluster uses the same {acm-short} version that the backup hub cluster uses. You cannot restore a backup on a hub cluster with a version earlier than the one used by the backup hub cluster.

1. Optional: If you want to run the restore operation on a hub cluster that has a version newer than the hub cluster where the backup was created, complete the following:
2. On the restore hub cluster, install the operator at the same version as the hub cluster where the backup was created.

1. Restore the date on the restore hub cluster.

1. On the restore hub cluster, use the upgrade operation to upgrade to the version you want to use.

1. Manually configure the hub cluster.

1. Install all operators on the active hub cluster and in the same namespace as the active hub cluster.

1. Verify that other operators, such as {aap-short}, {ocp-short} GitOps, or certificate manager, are installed.

1. Verify that the new hub cluster is configured the same way as the initial hub cluster.

1. Use the same namespace name as the initial hub cluster when you install the backup and restore operator and any operators that are configured on the earlier hub cluster.

With :

5. Ensure that the restore hub cluster uses the same {acm-short} version that the backup hub cluster uses. You cannot restore a backup on a hub cluster with a version earlier than the one used by the backup hub cluster.

           *           *Optional: If you want to run the restore operation on a hub cluster that has a version newer than the hub cluster where the backup was created, complete the following:

• • On the restore hub cluster, install the {acm-short}  operator at the same version as the hub cluster where the backup was created.
  • Restore the backup data on the restore hub cluster.
  • On the restore hub cluster, use the upgrade operation to upgrade to the {acm-short} version you want to use.
     

6.  On the restore hub, install all operators that are installed on the active hub cluster and in the same namespace as the active hub cluster.

7. Create the DataProtectionApplication resource on both active and passive hub cluster.