IP Library › Granted Patent US 12,332,754
Granted Patent B2
US 12,332,754 · App. 18/228,395 · Granted Jun 17, 2025

Increased replication for managed volumes

Inventors: Markus Behrens (Berlin, DE); Reiner Singer (Schriesheim, DE); Werner Thesing (Lautertal, DE); Yue Zhu (Heidelberg, DE); Mitja Kleider (Heidelberg, DE); Omran Saleh (Wiesloch, DE); Timo Sulg (Frankfurt, DE); Marcel Birn (Stuttgart, DE); Christoph Roterring (Sinsheim, DE)
Assignee: SAP SE
G06F11/2041G06F11/1612G06F11/2082
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 12,332,754
App. No.
18/228,395
Granted
Jun 17, 2025
Kind
B2
Abstract

A scale-out computing cluster may include a large number of computing servers and storage devices. In order to provide high reliability, the computing cluster must be able to handle failures of individual devices. Reliability of the computing cluster may be improved by providing a standby server for each active server in the computing cluster. If any active server fails, the corresponding standby server is activated. The failed server may be brought back online or replaced, at which time the restored server becomes the standby server for the now-active original standby server. During the restoration period, if any other active server fails, the standby server for that active server is immediately activated. As a result, the recovery ability of the computing cluster is only challenged if both servers of an active/standby pair fail during the restoration period, substantially improving reliability.

Claims (46)

1. A system comprising:

a first computing cluster located in a first geographic region, the first computing cluster comprising an active index server that accesses data from a corresponding first set of data volumes;

a first application server located in the first geographic region, the first application server hosting an application;

a second computing cluster located in a second geographic region different from the first geographic region and comprising a standby index server for the active index server, the standby index server accessing data from a corresponding second set of data volumes;

a second application server located in the second geographic region; and

a name server configured to perform operations comprising:

detecting a failure of the active index server; and

in response to the detected failure, updating a name table to redirect future data access requests from the failed active index server to the standby index server for the failed active index server;

wherein the application:

detects that the name table was updated to direct future access requests to the standby index server in the second geographic region; and

in response to the detecting that the name table was updated to direct future access requests to the second computing cluster, transfers execution of itself from the first application server to the second application server.

2. The system of claim 1 , wherein the active index server is configured to perform operations comprising:

receiving data access requests;

in response to each of the data access requests:

accessing data from the corresponding first set of data volumes; and

forwarding the data access request to the standby index server.

3. The system of claim 1 , wherein the name server is further configured to perform operations comprising:

detecting a resumption of service of the failed active index server; and

in response to the detected resumption of service, updating the name table to use the failed active index server as a standby index server.

4. The system of claim 1 , further comprising:

a second standby index server for the active index server, the second standby index server accessing data from a corresponding third set of data volumes;

wherein the name server is further configured to perform operations comprising:

in response to detecting a failure of the standby index server for the failed active index server, updating the name table to direct future access requests from the standby index server for the failed active index server to the second standby index server for the failed active index server.

5. The system of claim 1 , wherein after the application is transferred to the second application server, the application accesses data by communicating within the second geographic region with the standby index server.

6. A non-transitory computer-readable medium that stores instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

accessing, by an application, an index server that accesses data from a corresponding first set of data volumes, the index server being located in a first geographic region, the one or more processors also being located in the first geographic region;

detecting that a name table was updated to direct future access requests to a second index server located in a second geographic region different from the first geographic region; and

in response to the detecting that the name table was updated to direct future access requests to the second index server, transferring execution of the application to an application server located in the second geographic region.

7. The non-transitory computer-readable medium of claim 6 , wherein after the application is transferred to the application server in the second geographic region, the application accesses data by communicating within the second geographic region with the second index server.

8. A method comprising:

detecting, by one or more processors of a name server, a failure of an active index server located in a first geographic region, the active index server accessing data from a corresponding first set of data volumes, the active index server having a corresponding standby index server located in a second geographic region, the standby index server accessing data from a corresponding second set of data volumes;

in response to the detected failure, updating a name table to redirect future data access requests from the failed active index server to the standby index server for the failed active index server;

detecting, by an application that runs in the first geographic region, that the name table was updated to direct future access requests to the standby index server located in the second geographic region different from the first geographic region; and

in response to the detecting that the name table was updated to direct future access requests to the standby index server, transferring execution of the application to an application server located in the second geographic region.

9. The method of claim 8 , further comprising:

detecting a resumption of service of the failed active index server; and

in response to the detected resumption of service, updating the name table to use the failed active index server as a standby index server.

10. The method of claim 8 , further comprising:

in response to detecting a failure of the standby index server for the failed active index server, updating the name table to direct future access requests from the standby index server for the failed active index server to a second standby index server for the failed active index server.

11. The method of claim 8 , further comprising:

receiving, by the active index server, data access requests; and

in response to each of the data access requests:

accessing data from the corresponding first set of data volumes; and

forwarding the data access request to the standby index server for the active index server.

12. The method of claim 8 , wherein the standby index server is a synchronous standby for the active index server.

13. The method of claim 8 , wherein after the application is transferred to the application server in the second geographic region, the application accesses data by communicating within the second geographic region with the standby index server.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 1, 2023
From: BEHRENS, MARKUS; SINGER, REINER; THESING, WERNER; ZHU, YUE; KLEIDER, MITJA; SALEH, OMRAN; SULG, TIMO; BIRN, MARCEL; ROTERRING, CHRISTOPH
To: SAP SE
Reel/Frame 064451/0610 →
Continuity (1)
Related Publication 20250045178A1 · Feb 6, 2025
References Cited (27)
US 9804935B1 · Holenstein et al. · 2017 [cited by applicant]
US 11436097B1 · Kumar · 2022 [cited by examiner]
US 11947555B1 · Mohideen et al. · 2024 [cited by applicant]
US 11966411B1 · Rajgaria et al. · 2024 [cited by applicant]
US 20110173233A1 · Matsumura et al. · 2011 [cited by applicant]
US 20130282666A1 · Mcgee et al. · 2013 [cited by applicant]
US 20150046744A1 · Frerking · 2015 [cited by examiner]
US 20170116232A1 · Marwah et al. · 2017 [cited by applicant]
US 20180074915A1 · Yang et al. · 2018 [cited by applicant]
US 20180246928A1 · Kim et al. · 2018 [cited by applicant]
US 20180336258A1 · Lee et al. · 2018 [cited by applicant]
US 20200097556A1 · Chen et al. · 2020 [cited by applicant]
US 20220030062A1 · Jennings et al. · 2022 [cited by applicant]
US 20220253363A1 · Zhang et al. · 2022 [cited by applicant]
US 20220382742A1 · Procek et al. · 2022 [cited by applicant]
US 20230229363A1 · Karr et al. · 2023 [cited by applicant]
US 20230229572A1 · Murata · 2023 [cited by examiner]
US 20240069779A1 · Nhs et al. · 2024 [cited by applicant]
EP 4083786 · 2022 [cited by applicant]
“SAP HANA System Replication”, SAP HANA Platform 2.0 SPS 04. Document version 1.1-2019-10-31, (Oct. 31, 2019), 286 pgs. [cited by applicant]
“SAP HANA System Replication”, SAP HANA Platform 2.0 SPS 05. Document version 1.1-2021-07-30, (Jul. 30, 2021), 274 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,446, Non Final Office Action mailed Aug. 28, 2024”, 52 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,446, Response filed Nov. 19, 2024 to Non Final Office Action mailed Aug. 28, 2024”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,446, Examiner Interview Summary mailed Nov. 25, 2024”, 3 pgs. [cited by applicant]
“European Application No. 24185975.0 Extended European Search Report mailed on Dec. 4, 2024”, 50 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,446, Final Office Action mailed Dec. 20, 2024”, 59 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,427, Non Final Office Action mailed Jan. 2, 2025”, 9 pgs. [cited by applicant]
Cited By (2)
US 12,645,443 US 12,693,948