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. - [ ] Mandatory: Add the required version to the Fix version/s field.

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

• [ ] 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.

related to https://access.redhat.com/support/cases/#/case/03939562

Need to make this section more visible : Use the advanced options with velero.io.restore to filer out resources you want to restore.

Changes:

This link

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html/business_continuity/business-cont-overview#more-restore-samples

Add a sublink named : Advanced restore options

Content for this link:

Move the following content ( 2.12 and 2.13 ) under that link - make sure the indentation is as below ! the doc has some errors, fixed here

• Use the advanced options with velero.io.restore to filer out resources you want to restore. Use the following sample with velero.io.restore spec options to restore resources only from the vb-managed-cls-2 managed cluster namespace and to exclude global MultiCluster resources:
•  

• apiVersion: cluster.open-cluster-management.io/v1beta1
  kind: Restore
  metadata:
    name: restore-filter-sample 
    namespace: open-cluster-management-backup
  spec:
    cleanupBeforeRestore: None 
    veleroCredentialsBackupName: latest 
    veleroResourcesBackupName: latest 
    veleroManagedClustersBackupName: latest
    excludedResources:
      - ManagedCluster

• Set the following velero.io.restore spec options when you create the Red Hat Advanced Cluster Management restore resource:

spec: 
  includedResources
  includedNamespaces
  excludedResources
  excludedNamespaces
  LabelSelector
  OrLabelSelector

 
 
Note:

• When you set any of these Velero restore filters, set the cleanupBeforeRestore to None to avoid cleaning up hub cluster resources that are part of the restored backup but are not being restored because of the applied filter.

For 2.10, 2.11

Add a sublink under https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/business_continuity/business-cont-overview#more-restore-samples, named : Advanced restore options

Content for this link:

• Use the advanced options with velero.io.restore to filer out resources you want to restore. Use the following sample with velero.io.restore spec options to  exclude global MultiCluster resources from the restore operation: 

• apiVersion: cluster.open-cluster-management.io/v1beta1
  kind: Restore
  metadata:
    name: restore-filter-sample 
    namespace: open-cluster-management-backup
  spec:
    cleanupBeforeRestore: None 
    veleroCredentialsBackupName: latest 
    veleroResourcesBackupName: latest 
    veleroManagedClustersBackupName: latest
    excludedResources:
     - ManagedCluster

• Set the following velero.io.restore spec options when you create the Red Hat Advanced Cluster Management restore resource:

spec: 
  excludedResources
  excludedNamespaces

 
 
Note:

• When you set any of these Velero restore filters, set the cleanupBeforeRestore to None to avoid cleaning up hub cluster resources that are part of the restored backup but are not being restored because of the applied filter.