Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-1412

Comprehensive Backup and Restore Solution for OCP Virt HCP Clusters

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-1408Comprehensive Automation of HCP Backup and Restore Processes for Enhanced Scalability and Reliability
    • 100% To Do, 0% In Progress, 0% Done
    • 9
    • 0
    • 0

      Feature Overview (aka. Goal Summary)

      The objective is to create a comprehensive backup and restore mechanism for HCP OpenShift Virtualization Provider. This feature ensures both the HCP state and the worker node state are backed up and can be restored efficiently, addressing the unique requirements of KubeVirt environments.

      Goals (aka. Expected User Outcomes)

      • Users will be able to backup and restore the KubeVirt HCP cluster, including both HCP state and worker node state.
      • Ensures continuity and reliability of operations after a restore, minimizing downtime and data loss.
      • Supports seamless re-connection of HCP to worker nodes post-restore.

      Requirements (aka. Acceptance Criteria)

      • Backup of KubeVirt CSI infra PVCs
      • Backup of KubeVirt VMs + VM state + (possibly even network attachment definitions)
      • Backup of Cloud Provider KubeVirt Infra Load Balancer services (having IP addresses change here on the service could be problematic)
      • Backup of Any custom network policies associated with VM pods
      • Backup of VMs and state placed on External Infra

      Use Cases (Optional)

      1. Disaster Recovery: In case of a disaster, the system can restore the HCP and worker nodes to the previous state, ensuring minimal disruption.
      2. Cluster Migration: Allows migration of hosted clusters across different management clusters/
      3. System Upgrades: Facilitates safe upgrades by providing a reliable restore point.

      Out of Scope

      • Real-time synchronization of backup data.
      • Non-disruptive Backup and restore (ideal but not required)

      Documentation Considerations

      Interoperability Considerations

      • Impact on other projects like ACM/MCE vol-sync.
      • Test scenarios to validate interoperability with existing backup solutions.

            azaalouk Adel Zaalouk
            azaalouk Adel Zaalouk
            Antoni Segura Puimedon, David Vossel, Fabian Deutsch, Joshua Packer, Peter Lauterbach, Roke Jung
            David Vossel David Vossel
            Catherine Tomasko Catherine Tomasko
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: