Prioritized Virtual Machine Restoration Sequence

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for restoring virtual data centers after a disaster result in significant downtime for highly available virtual machines due to the sequential restoration of storage domains and entities, leading to extended periods before HA VMs can be run again.

Innovation Solution

The technology prioritizes the execution of highly available virtual machines by accessing metadata to identify and sort storage domains based on the number of associated HA VMs, allowing the storage domain with the highest number of HA VMs to be attached and initiated first, thereby minimizing downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If storage domains are restored sequentially in conventional order, then all storage domains can be restored systematically, but highly available virtual machines experience extended downtime

Engineering Contradiction:
Improvesystem restoration completenessVSAvoidHA VM downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary identification of highly available virtual machines and their associated storage domains before the restoration process begins. By pre-marking storage domains that contain HA VMs, the system prepares the restoration sequence in advance, ensuring that critical storage domains are restored first without requiring real-time decision-making during the restoration process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention changes the restoration priority parameter from conventional sequential order to a priority-based order determined by HA VM associations. Storage domains are re-ranked based on their importance to highly available virtual machines, transforming the restoration sequence from a fixed conventional order to a dynamic priority-driven order that minimizes HA VM downtime.

Inventive Principle:
Principle #35Parameter changes

2Ease of manufacture

If all storage domains are restored before running HA VMs, then systematic restoration is maintained, but the time to resume critical operations is extended

Engineering Contradiction:
Improverestoration process systematicityVSAvoidHA VM execution speed
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The restoration process is segmented into distinct phases: identification of HA VMs, prioritization of their storage domains, and selective restoration. Instead of restoring all storage domains uniformly, the system divides the restoration task into critical segments (storage domains containing HA VMs) and non-critical segments, restoring the critical segments first to enable faster HA VM execution.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary identification and prioritization of storage domains associated with highly available virtual machines before the restoration process begins. This advance preparation allows the system to immediately begin restoring critical storage domains without waiting for the entire restoration sequence to complete, thereby accelerating HA VM execution while maintaining systematic restoration of remaining domains.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11086649B2Minimizing downtime of highly available virtual machines
Publication Date: 2021.08.10 RED HAT INC
  • US11086649B2 patent drawing
  • US11086649B2 patent drawing
  • US11086649B2 patent drawing

AI summary

Implementations for prioritized execution of highly available virtual machines for minimizing downtime of the highly available virtual machines are described. An example method may include accessing metadata identifying a plurality of virtual machines indicated as highly available virtual machines, determining, in view of the metadata, a number of highly available virtual machines of the plurality of virtual machines that are associated with each storage domain of a plurality of storage domains, and initiating, starting with a storage domain associated with a highest number of highly available virtual machines, execution of one or more highly available virtual machines associated with each of the plurality of storage domains in a sequential manner.