IP Library Granted Patent US 8,429,450
Granted Patent B2
US 8,429,450 · App. 12/790,628 · Granted Apr 23, 2013

Method and system for coordinated multiple cluster failover

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,429,450
App. No.
12/790,628
Granted
Apr 23, 2013
Kind
B2
Abstract

Hyperclusters are a cluster of clusters. Each cluster has associated with it one or more resource groups, and independent node failures within the clusters are handled by platform specific clustering software. The management of coordinated failovers across dependent or independent resources running on heterogeneous platforms is contemplated. A hypercluster manager running on all of the nodes in a cluster communicates with platform specific clustering software regarding any failure conditions, and utilizing a rule-based decision making system, determines actions to take on the node. A plug-in extends exit points definable in non-hypercluster clustering technologies. The failure notification is passed to other affected resource groups in the hypercluster.

Claims (15)

1. A method for coordinating availability of data processing resources between a first cluster of nodes each controlled by a respective first cluster manager and multiple other clusters of nodes each controlled by a respective second cluster manager, the method comprising:

receiving a disruption signal from an exit program of one of the first cluster managers, the disruption signal being representative of a disruption event associated with a specific one of the nodes of the first cluster, the disruption signal being received by a first hypercluster manager of the specific one of the nodes of the first cluster;

deriving a local action code and a hypercluster event code from a hypercluster rules list, the local action code and the hypercluster event code corresponding to the disruption event, the local action code having an associated local cluster activation sequence for regulating the operation of the first cluster of nodes, and the hypercluster event code having an associated cluster activation sequence for regulating the operation of the respective multiple other clusters of nodes;

transmitting the hypercluster event code to the multiple other clusters of nodes, each of the nodes of the multiple other clusters of nodes including a second hypercluster manager for execution of a remote cluster activation sequence thereon;

receiving a token on the first hypercluster manager transmitted thereto in response to a completed execution of the remote cluster activation sequence on a one of the node of the multiple other clusters of nodes; and

executing the local cluster activation sequence on the first cluster of nodes upon receipt of the token;

wherein the first cluster of nodes and the multiple other clusters of nodes each function independent of each other, the nodes of the first cluster of nodes communicate with each other by a first set of messages, and the nodes of a given one of the multiple other clusters of nodes communicate with each other by a second set of messages.

2. The method of claim 1 , further comprising:

synchronizing views of the first and the multiple other clusters of nodes amongst each of the first and the multiple other clusters, view synchrony being determined by another token.

3. The method of claim 2 , wherein deriving the hypercluster event code includes:

translating the disruption event to a universal event code with a translation table, the translation table including a first sequence of disruption events and a second sequence of universal event codes correlated thereto.

4. The method of claim 3 , wherein the universal event code is referenced to derive the hypercluster event code from the hypercluster rules list.

5. The method of claim 2 , wherein the local and remote cluster activation sequences include dependencies therebetween, the dependencies establishing the timing and order of the local and remote cluster activation sequences.

6. The method of claim 5 , wherein transmitting the hypercluster event code to the other clusters of nodes is in response to receiving a confirmation code representative of completion of one step in the cluster activation sequence as defined by the dependencies.

7. The method of claim 2 , wherein the remote cluster activation sequence is being executed on one of the nodes of the multiple other clusters.

Assignments (15)
SECOND LIEN GRANT OF SECURITY INTEREST IN PATENTS Recorded Jul 17, 2025
From: PRECISELY SOFTWARE INCORPORATED; VISIONS SOLUTIONS, INC.; PITNEY BOWES SOFTWARE INC.
To: BARCLAYS BANK PLC, AS COLLATERAL AGENT
Reel/Frame 072019/0382 →
FIRST LIEN GRANT OF SECURITY INTEREST IN PATENTS Recorded Jul 17, 2025
From: PRECISELY SOFTWARE INCORPORATED; VISIONS SOLUTIONS, INC.; PITNEY BOWES SOFTWARE INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 072019/0370 →
FIRST LIEN RELEASE OF SECURITY INTEREST IN PATENTS Recorded Apr 26, 2021
From: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
To: VISION SOLUTIONS, INC.; PRECISELY SOFTWARE INCORPORATED (F/K/A SYNCSORT INCORPORATED); PITNEY BOWES SOFTWARE INC.
Reel/Frame 056038/0001 →
SECOND LIEN RELEASE OF SECURITY INTEREST IN PATENTS Recorded Apr 26, 2021
From: GOLUB CAPITAL MARKETS LLC, AS COLLATERAL AGENT
To: VISION SOLUTIONS, INC.; PRECISELY SOFTWARE INCORPORATED (F/K/A SYNCSORT INCORPORATED); PITNEY BOWES SOFTWARE INC.
Reel/Frame 056107/0233 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY NUMBERS SECTION. PATENT NUMBERS 10003946 AND 10119825 WERE INCORRECTLY DESIGNATED AS APPLICATION NUMBERS. PREVIOUSLY RECORDED ON REEL 052323 FRAME 0254. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT OF SECURITY INTEREST IN PATENTS. Recorded Apr 14, 2021
From: BANK OF AMERICA, N.A., AS EXISTING AGENT
To: JEFFERIES FINANCE LLC, AS SUCCESSOR AGENT
Reel/Frame 056304/0891 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY NUMBERS SECTION. PATENT NUMBERS 10003946 AND 10119825 WERE INCORRECTLY DESIGNATED AS APPLICATION NUMBERS. PREVIOUSLY RECORDED ON REEL 052323 FRAME 0304. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT OF SECURITY INTEREST IN PATENTS. Recorded Apr 14, 2021
From: BANK OF AMERICA, N.A., AS EXISTING AGENT
To: GOLUB CAPITAL MARKETS LLC, AS SUCCESSOR AGENT
Reel/Frame 056305/0117 →
ASSIGNMENT OF SECURITY INTEREST IN PATENTS Recorded Apr 6, 2020
From: BANK OF AMERICA, N.A., AS EXISTING AGENT
To: GOLUB CAPITAL MARKETS LLC, AS SUCCESSOR AGENT
Reel/Frame 052323/0304 →
ASSIGNMENT OF SECURITY INTEREST IN PATENTS Recorded Apr 6, 2020
From: BANK OF AMERICA, N.A., AS EXISTING AGENT
To: JEFFERIES FINANCE LLC, AS SUCCESSOR AGENT
Reel/Frame 052323/0254 →
SECURITY INTEREST Recorded Aug 18, 2017
From: VISION SOLUTIONS, INC.
To: BANK OF AMERICA, N.A. AS COLLATERAL AGENT
Reel/Frame 043334/0722 →
SECURITY INTEREST Recorded Aug 18, 2017
From: VISION SOLUTIONS, INC.
To: BANK OF AMERICA, N.A. AS COLLATERAL AGENT
Reel/Frame 043334/0741 →
RELEASE OF SECURITY INTEREST Recorded Aug 18, 2017
From: ANTARES CAPITAL LP AS ADMINISTRATIVE AGENT
To: VISION SOLUTIONS, INC.
Reel/Frame 043333/0576 →
PATENT SECURITY AGREEMENT Recorded Jun 26, 2016
From: VISION SOLUTIONS, INC.
To: ANTARES CAPITAL LP, AS ADMINISTRATIVE AGENT
Reel/Frame 039165/0931 →
PATENT SECURITY AGREEMENT RELEASE AT REEL/FRAME NO. 24723/0992 Recorded Jun 16, 2016
From: JEFFERIES FINANCE LLC
To: VISION SOLUTIONS, INC.
Reel/Frame 039052/0404 →
SECOND LIEN PATENT SECURITY AGREEMENT RELEASE AT REEL/FRAME NO. 26088/0261 Recorded Jun 16, 2016
From: JEFFERIES FINANCE LLC
To: VISION SOLUTIONS, INC.
Reel/Frame 039052/0490 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 8, 2016
From: BROWN, DAVID E.; SIMPSON, SCOTT
To: VISION SOLUTIONS, INC.
Reel/Frame 038842/0475 →