Create an informative issue (See each section, incomplete templates/issues won't be triaged)

Using the current documentation as a model, please complete the issue template. 

Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

Prerequisite: Start with what we have

Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

 - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

 - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

Describe the changes in the doc and link to your dev story

Provide info for the following steps:

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

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

      - [ ] New topic in an existing section or new section
      - [ ] Update to an existing topic

3. - [ ] Mandatory for GA content:
            
       - [ ] Add steps and/or other important conceptual information here: 
       
            
       - [ ] Add Required access level for the user to complete the task here:
       

       - [ ] 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:

4. - [X] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:

This should be added to the hub backup known issues

 Title : Only the OADP version installed by the ACM backup component can run on the hub

Description of the issue: 

MultiClusterHub overwrites velero and OADP CRD with the ones that are shipped and supported by the ACM cluster backup component, even if the cluster-backup flag is set to false. As a result, if you try to install the OADP operator manually, unless the version you are trying to install uses the same CRDs as the version that would be installed by the ACM cluster backup component, your installation will fail since the CRDs will be overwritten by the MultiClusterHub reconcile operation.

 
Workaround:

You could pause the MCH reconciliation using this command so that the MCH doesn't update the CRD's installed by your OADP operator version, although this is not recommended for a production environment.

oc annotate mch multiclusterhub -n open-cluster-management mch-pause=true