Value Statement

We had a lot of requests from customers asking to run the  restore operation in a controlled, test environment, without having to stop the backup hub. Some customers cannot stop the hub or it would be too difficult to restart

Need a documented set of options for being able to run a restore hub operation without stopping the backup hub - we document now that you need to stop the backup hub because the managed clusters would otherwise bounce between the hubs.

The solution need to take into consideration any type of managed cluster:

• imported
• hive
• discovered .. 
• ztp / assisted installer 

Definition of Done for Engineering Story Owner (Checklist)

• A documented set of steps on how to run a hub restore without having to stop the backup hub.
• It could be simply stopping some pods; or providing for the user a policy configuration to block backup hub connection with the managed clusters .. or something in between

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.