Federated Restore for Virtual Machine Clusters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large-scale cluster environments, restoring virtual machines from backup often results in resource imbalances, leading to performance degradation due to the lack of visibility into which node will host the virtual machines, causing resource over-utilization and increased response times.

Innovation Solution

Implementing a federated restore method that uses a backup management server to intelligently distribute virtual machine restorations across multiple nodes based on resource availability, using a node mapping list and load balancing algorithms to optimize resource allocation and prevent resource crunches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If virtual machines are restored to a single node, then restoration speed is improved, but resource over-utilization occurs leading to performance degradation

Engineering Contradiction:
Improverestoration speedVSAvoidperformance stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The restoration operation is segmented and distributed across multiple nodes in the cluster. Instead of restoring all virtual machines to a single node, the system divides the restoration workload among multiple nodes, with each node responsible for restoring a subset of virtual machines. This segmentation prevents resource over-utilization on any single node while maintaining efficient restoration throughput.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically determines the number of nodes to use for restoration and the distribution of virtual machines across those nodes. By changing the parameter of restoration distribution from centralized to distributed, the system achieves both speed and reliability - the restoration operates efficiently across multiple nodes while preventing any single node from becoming a bottleneck.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If restoration is distributed across multiple nodes, then resource utilization is balanced, but restoration complexity increases

Engineering Contradiction:
Improveresource allocation flexibilityVSAvoidrestoration process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A backup management server acts as an intermediary to coordinate the distributed restoration process. This server receives the list of virtual machines to restore, determines the optimal node distribution, assigns specific virtual machines to specific nodes, and monitors the restoration progress. This intermediary layer abstracts the complexity from the user while enabling flexible resource allocation across multiple nodes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where nodes report their restoration status to the backup management server, and the server monitors resource availability in real-time. This feedback loop allows the system to dynamically adjust the restoration distribution, ensuring optimal resource utilization while managing complexity through automated coordination.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If visibility into node hosting assignments is provided, then resource allocation can be optimized, but system complexity increases

Engineering Contradiction:
Improvenode assignment visibilityVSAvoidsystem configuration complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system provides automatic node selection and assignment without requiring manual configuration. The backup management server autonomously determines which nodes should host which virtual machines based on resource availability and restoration requirements. This self-service approach provides full visibility into node assignments while avoiding the complexity of manual system configuration.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10289441B1Intelligent scale-out federated restore
Publication Date: 2019.05.14 EMC IP HLDG CO LLC
  • US10289441B1 patent drawing
  • US10289441B1 patent drawing
  • US10289441B1 patent drawing

AI summary

A request is received to restore a set of virtual machines (VMs) to a cluster of nodes. The nodes are profiled to collect, for each node, a current load and health status. A participating node list is generated by excluding from the list any node having a current load that exceeds a threshold or having a health status of unavailable. For each participating node, a determination is made of a recommended number of VMs to assign to a node based on a current load of the node. A participating node and VM to restore is selected. The selected VM is assigned to the selected participating node. The selection and assignment is repeated until each participating node has been assigned its respective number of VMs to restore or all VMs to restore have been assigned. The participating nodes are instructed to begin restoring their assigned VMs.