Cluster Resource Manager Backup Sequencing via Policy Engine

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of sequencing resource freeze and thaw operations in server clusters, especially with distributed resources and dependencies, complicates the process of creating consistent backups or snapshots, and managing failures during these operations.

Innovation Solution

A method involving a cluster resource manager and a policy engine that maintains resource dependencies, providing an instruction sequence for proper sequencing of backup operations, including handling failures through recovery sections to ensure orderly shutdown and restart of resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If resources are frozen and thawed in sequence during backup operations, then data consistency is achieved, but system complexity and operational difficulty increase

Engineering Contradiction:
Improvedata consistencyVSAvoidsequencing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a cluster resource manager as an intermediary component that coordinates the freezing and thawing of resources across multiple nodes. This manager receives backup requests, determines the proper sequence based on resource dependencies, and executes the freeze-thaw operations systematically, thereby achieving data consistency without requiring complex manual sequencing procedures

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by first freezing dependent resources before freezing the target resource, and subsequently thawing in the reverse order. This preliminary sequencing of operations ensures that when the backup is taken, all resources are in a consistent state without requiring the operator to manage the complexity of sequencing during the backup process itself

Inventive Principle:
Principle #10Preliminary action

2Reliability

If resources are frozen to ensure consistent backup, then data integrity is maintained, but service availability is reduced

Engineering Contradiction:
Improvedata integrityVSAvoidservice availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the freezing and thawing operations into discrete, manageable steps that are executed sequentially. By dividing the backup process into distinct phases (freezing dependent resources, freezing target resource, performing backup, thawing target resource, thawing dependent resources), the system minimizes the overall time resources remain frozen while ensuring data integrity, thus reducing the impact on service availability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically adjusts the backup process by automatically determining the freeze-thaw sequence based on resource dependencies. This dynamic approach allows the system to optimize the duration of the frozen state by only freezing necessary resources for the minimum required time, thereby maintaining data integrity while minimizing service disruption

Inventive Principle:
Principle #15Dynamics

3Reliability

If distributed file system instances are coordinated for simultaneous backup, then consistency across nodes is achieved, but coordination complexity increases

Engineering Contradiction:
Improvedistributed system consistencyVSAvoidcoordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The cluster resource manager serves as a universal coordination mechanism that handles backup requests for distributed file system instances across multiple nodes. This single manager can coordinate the freezing and thawing of file system instances on different nodes simultaneously or in the proper sequence, achieving distributed system consistency without requiring separate coordination mechanisms for each node or instance

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Reliability

If proper sequencing of freeze and thaw operations is implemented, then backup consistency is ensured, but operation time increases

Engineering Contradiction:
Improvebackup consistencyVSAvoidoperation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary determination of the freeze-thaw sequence based on resource dependencies before executing the backup operation. By pre-calculating and storing the proper sequence, the system avoids time-consuming decisions during the actual backup process, ensuring backup consistency while minimizing the total operation time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system efficiently executes the predetermined freeze-thaw sequence by rapidly transitioning through each state change without unnecessary delays. By skipping intermediate verification steps that are not critical to consistency and directly executing the pre-determined sequence, the system maintains backup consistency while reducing the overall operation time

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentUS8209568B2System and method for implementing an intelligent backup technique for cluster resources
Publication Date: 2012.06.26 SUSE LLC
  • US8209568B2 patent drawing
  • US8209568B2 patent drawing
  • US8209568B2 patent drawing

AI summary

Method and system for implementing a backup in a cluster comprising a plurality of interconnected nodes, at least one of the nodes comprising a cluster resource manager (CRM), and at least one of the nodes comprising a policy engine (PE), the PE maintaining at least one dependency associated with at least a first resource executing on at least one of the nodes. For example, the method comprises, receiving by the CRM a backup request for the first resource from an administrator; responsive to the request, updating by the CRM the cluster configuration; communicating by the CRM to the PE a cluster status and the updated configuration; providing by the PE to the CRM an instruction sequence for carrying out the backup, the instruction sequence based on the dependency associated with the first resource; and responsive to the instruction sequence, carrying out by the CRM the backup of the first resource.