Feature Overview

As an ACM customer I expect a backup and restore to include all components that are part of the hub experience.

Goals

We need component sign-off from:
- Observability,
- HyperShift,
- Global Hub,
- OpenShift GitOps
- Ansible automation (ALC, GRC, CLC)
- ~~Application lifecycle~~
- Cluster lifecycle
- Infrastructure operator
- Server foundation
- Policy
- Search
- Multicluster networking
- Gatekeeper
- ODF Advanced - AppDR
We need to ensure all available hub backup job 'hooks' are being used for Application LC, Cluster LC, Policy/GRC LC areas

Requirement	Notes	isMvp?
CI - MUST be running successfully with test automation	This is a requirement for ALL features.	YES
Release Technical Enablement	Provide necessary release enablement details and documents.	YES
All hub components need to indicate their implementation details and ensure that it is documented	ACM backup/restore DOC should be the single location for all b/r materials	YES

This Section:

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Questions to be addressed:

What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)?
Does this feature have a doc impact?
New Content, Updates to existing content, Release Note, or No Doc Impact
If unsure and no Technical Writer is available, please contact Content
Strategy.
What concepts do customers need to understand to be successful in
[action]?
How do we expect customers will use the feature? For what purpose(s)?
What reference material might a customer want/need to complete [action]?
Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available.
What is the doc impact (New Content, Updates to existing content, or
Release Note)?

#acm-9643-backup-all-components