IP Library › Granted Patent US 12,693,948
Granted Patent B2
US 12,693,948 · App. 19/091,105 · Granted Jul 28, 2026

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,693,948
App. No.
19/091,105
Filed
Mar 26, 2025
Granted
Jul 28, 2026
Kind
B2
Art Unit
2114
USPC
714/4.11
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 (45)

1 . A system comprising:

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

a standby index server located in a second geographic region different from the first geographic region; and

a second application server located in the second geographic region;

wherein the application:

detects that a 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 standby index server, transfers execution of itself from the first application server to the second application server.

2 . 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.

3 . The system of claim 1 , further comprising an active index server located in the first geographic region, the active index server being configured to perform operations comprising:

in response to receiving a data access request:

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

forwarding the data access request to the standby index server.

4 . The system of claim 3 , further comprising:

a second standby index server for the active index server; and

a name server that is configured to perform operations comprising:

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

5 . The system of claim 3 , wherein the standby index server accesses data from a corresponding second set of data volumes.

6 . The system of claim 1 , further comprising a name server configured to perform operations comprising:

detecting a failure of an active index server; and

in response to the detected failure, updating the name table to redirect future data requests from the active index server to the standby index server.

7 . The system of claim 6 , wherein the standby index server is a synchronous standby for the active index server.

8 . The system of claim 1 , wherein the first geographic region comprises a first country and the second geographic region comprises a second country.

9 . 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:

detecting, by an application executing in a first geographic region, that a name table was updated to direct future access requests to an 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 index server, transferring execution of the application to an application server located in the second geographic region.

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

11 . The non-transitory computer-readable medium of claim 9 , wherein, prior to transferring execution of the application to the application server located in the second geographic region, the application sends data access requests to an active index server located in the first geographic region.

12 . The non-transitory computer-readable medium of claim 9 , wherein the index server is a synchronous standby for an active index server.

13 . The non-transitory computer-readable medium of claim 9 , wherein the first geographic region comprises a first country and the second geographic region comprises a second country.

14 . A method comprising:

hosting an application at a first application server in a first geographic region;

detecting, by the application, that a name table was updated to direct future access requests to a standby 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 standby index server, transferring execution of the application from the first application server to a second application server in the second geographic region.

15 . The method of claim 14 , 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.

16 . The method of claim 14 , further comprising:

in response to receiving, by an active index server located in the first geographic region, a data access request:

accessing, by the active index server, data from a corresponding first set of data volumes; and

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

17 . The method of claim 16 , further comprising:

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

18 . The method of claim 16 , wherein the standby index server accesses data from a corresponding second set of data volumes.

19 . The method of claim 14 , further comprising:

detecting, by a name server, a failure of an active index server; and

in response to the detected failure, updating, by the name server, the name table to redirect future data requests from the active index server to the standby index server.

20 . The method of claim 14 , wherein the first geographic region comprises a first country and the second geographic region comprises a second country.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 2, 2025
From: BEHRENS, MARKUS; SINGER, REINER; THESING, WERNER; ZHU, YUE; KLEIDER, MITJA; SALEH, OMRAN; SULG, TIMO; BIRN, MARCEL; ROTERRING, CHRISTOPH
To: SAP SE
Reel/Frame 070710/0257 →
Continuity (2)
Continuation 18228395 · Jul 31, 2023
Related Publication 20250225040A1 · Jul 10, 2025
References Cited (55)
US 9804935B1 · Holenstein et al. · 2017 [cited by applicant]
US 10002247B2 · Suarez et al. · 2018 [cited by applicant]
US 10396997B2 · Brady et al. · 2019 [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 12332754B2 · Behrens et al. · 2025 [cited by applicant]
US 12332913B2 · Behrens et al. · 2025 [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 20190306236A1 · Wiener et al. · 2019 [cited by applicant]
US 20190332269A1 · Greenwood et al. · 2019 [cited by applicant]
US 20190349205A1 · Brady et al. · 2019 [cited by applicant]
US 20200097556A1 · Chen et al. · 2020 [cited by applicant]
US 20210334003A1 · Agrawal et al. · 2021 [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]
US 20240126536A1 · He et al. · 2024 [cited by applicant]
US 20240256572A1 · Toste Gomes et al. · 2024 [cited by applicant]
US 20250045034A1 · Behrens et al. · 2025 [cited by applicant]
US 20250045178A1 · Behrens et al. · 2025 [cited by applicant]
US 20250045296A1 · Behrens et al. · 2025 [cited by applicant]
US 20250045297A1 · Behrens et al. · 2025 [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,395, Non Final Office Action mailed Nov. 20, 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,395, Response filed Dec. 31, 2024 to Non Final Office Action mailed Nov. 20, 2024”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,427, Non Final Office Action mailed Jan. 2, 2025”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,446, Examiner Interview Summary mailed Feb. 3, 2025”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,446, Response filed Feb. 20, 2025 to Final Office Action mailed Dec. 20, 2024”, 14 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,395, Notice of Allowance mailed Feb. 26, 2025”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,427, Response filed Mar. 31, 2025 to Non Final Office Action mailed Jan. 2, 2025”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,446, Notice of Allowance mailed Apr. 16, 2025”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,427, Final Office Action mailed Jul. 1, 2025”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,412, Non Final Office Action mailed Jul. 15, 2025”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,427, Response filed Oct. 1, 2025 to Final Office Action mailed Jul. 1, 2025”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,412, Response filed Oct. 9, 2025 to Non Final Office Action mailed Jul. 15, 2025”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,427, Non Final Office Action mailed Oct. 21, 2025”, 13 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,427, Response filed Jan. 21, 2026 to Non Final Office Action mailed Oct. 21, 2025”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 18/228,412, Notice of Allowance mailed Feb. 2, 2026”, 7 pgs. [cited by applicant]