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 

Suggest to add this known issue in the section of : https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/release_notes/release-notes#known-issues-backup-restore

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.

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

       In the process of backup and restore, if the customer backup and restore the hub to a same cluster, for example:  the customer backup a ACM hub, uninstall the ACM hub, and then install ACM hub on the same cluster again, and finally restore on this hub.

      The the cluster-proxy-addon will not function, the pod log will show error msg:

      ```

       E0430 19:11:20.810624 1 clientset.go:188] "cannot connect once" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate signed by unknown authority\""

      ```

      The workaround is to disable cluster-proxy-addon , wait for addons disabled, and enable it again via mce. The disable and enable commands list as follow:

```

oc patch mce multiclusterengine --type=merge -p '{"spec":{"overrides":{"components":[

]}}}'

oc patch mce multiclusterengine --type=merge -p '{"spec":{"overrides":{"components":[

]}}}'

```

     The issue is related to the bug: https://issues.redhat.com/browse/ACM-11411 

     The issue is fixed on 2.11 and later.

            
       - [ ] 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. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation: