Failover Cluster Service Group Overlap Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cluster environments, the traditional method of waiting for a service group to be completely offline before bringing it back online is inefficient and may fail to meet service level agreements, particularly for mission-critical applications that require minimal downtime.

Innovation Solution

A computer-implemented method for managing failover clusters that involves identifying a service group on a first cluster node and initiating failover to a second cluster node, where at least a portion of the service group is brought online on the second node before the first instance is completely offline, allowing for overlapping online and offline tasks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the traditional method of waiting for a service group to be completely offline before bringing it back online is used, then system stability is maintained, but downtime is extended and service level agreements may be violated

Engineering Contradiction:
Improveservice level agreement complianceVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by bringing the service group online on the failover node before completely taking it offline from the failed node. This allows online tasks to start in advance, reducing the overall downtime and ensuring service level agreement compliance while maintaining system reliability through controlled transition.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the service group failover process into distinct phases: bringing the service group online on the failover node, performing online tasks, and then taking it offline from the failed node. This segmentation allows overlapping of online and offline tasks, reducing total downtime while maintaining system stability.

Inventive Principle:
Principle #1Segmentation

2Productivity

If the service group is brought completely offline before bringing it back online, then resource conflicts are avoided, but the failover process becomes inefficient and time-consuming

Engineering Contradiction:
Improvefailover efficiencyVSAvoidresource management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by initiating the bring-online process on the failover node before completing the take-offline process on the failed node. This allows online tasks to begin in advance, improving failover efficiency and productivity while managing resource conflicts through controlled coordination.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses feedback mechanisms to monitor the status of the service group during failover and coordinate the online/offline tasks appropriately. This feedback control manages resource conflicts while enabling efficient overlapping of tasks, improving overall failover productivity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9195528B1Systems and methods for managing failover clusters
Publication Date: 2015.11.24 VERITAS TECHNOLOGIES LLC
  • US9195528B1 patent drawing
  • US9195528B1 patent drawing
  • US9195528B1 patent drawing

AI summary

A computer-implemented method for managing failover clusters. The method may include maintaining a failover cluster comprising first and second cluster nodes, identifying a first instance of a service group on the first cluster node, and initiating failover of the first cluster node to the second cluster node. The method may also include bringing at least a portion of a second instance of the service group online before taking the first instance of the service group completely offline. Various other methods, systems, and computer-readable media are also disclosed.