US 10,771,551 B2Granted

Dynamic topology switch for data replication

AssigneeSap SE

InventorsZheng-Wei Wang, Jian Luo, Yi Chen, Weizhong Qiu, Huizi Liu, Du Xue

Life of this patent

Estimating the term…

Loading patent…

Abstract

The present disclosure involves systems, software, and computer implemented methods for performing dynamic topology switch in a failover operation. In one example, a failover of a first node is determined. The first node includes a first data server and a first replication server. At least one user application connects to the first data server prior to the failover of the first node. In response to the determined failover, the at least one user application is connected to a second data server of a second node. The second node includes the second data server and a second replication server. Prior to the failover of the first node, a data replication topology of the second node is a remote topology. During the failover, if the first replication server on the first node is down, the data replication topology of the second node is switched from the remote topology to a local topology.

Claims18

Dependent claims

A non-transitory computer storage medium encoded with a computer program, the program comprising instructions that, when executed by one or more computers, cause the one or more computers to perform operations comprising:

determining a failover of a first node, wherein the first node includes a first data server and a first replication server, and wherein at least one user application connects to the first data server prior to the failover of the first node;
in response to the determined failover of the first node including a failure of the first replication server:
connecting the at least one user application to a second data server of a second node, wherein the second node includes the second data server and a second replication server, and wherein a data replication topology of the second data server is a remote topology;
and
in response to connecting the at least one user application to the second data server of the second node, switching the data replication topology of the second data server from the remote topology to a local topology, wherein, in the remote topology, replication data of the second data server in the second node is routed from the second data server in the second node through the first replication server in the first node to an external replication system, wherein, in the local topology, replication data of the second data server in the second node is routed from the second data server in the second node through the second replication server in the second node to the external replication system, and wherein prior to the failover of the first node, replication data of the first data server in the first node is routed from the first data server in the first node through the second replication server in the second node to the external replication system;
and
in response to the determined failover of the first node not including a failure of the first replication server:
connecting the at least one user application to the second data server of the second node, wherein the second node includes the second data server and the second replication server, and wherein the data replication topology of the second data server is a remote topology;
and
in response to connecting the at least one user application to the second data server of the second node, maintaining the data replication topology of the second data server as the remote topology, wherein, in the remote topology, replication data of the second data server in the second node is routed from the second data server in the second node through the first replication server in the first node to an external replication system.

7 more elements

A computerized method performed by one or more processors, the method comprising:

determining a failover of a first node, wherein the first node includes a first data server and a first replication server, and wherein at least one user application connects to the first data server prior to the failover of the first node;
in response to the determined failover of the first node including a failure of the first replication server:
connecting the at least one user application to a second data server of a second node, wherein the second node includes the second data server and a second replication server, and wherein a data replication topology of the second data server is a remote topology;
and
in response to connecting the at least one user application to the second data server of the second node, switching the data replication topology of the second data server from the remote topology to a local topology, wherein, in the remote topology, replication data of the second data server in the second node is routed from the second data server in the second node through the first replication server in the first node to an external replication system, wherein, in the local topology, replication data of the second data server in the second node is routed from the second data server in the second node through the second replication server in the second node to the external replication system, and wherein prior to the failover of the first node, replication data of the first data server in the first node is routed from the first data server in the first node through the second replication server in the second node to the external replication system;
and
in response to the determined failover of the first node not including a failure of the first replication server:
connecting the at least one user application to the second data server of the second node, wherein the second node includes the second data server and the second replication server, and wherein the data replication topology of the second data server is a remote topology;
and
in response to connecting the at least one user application to the second data server of the second node, maintaining the data replication topology of the second data server as the remote topology, wherein, in the remote topology, replication data of the second data server in the second node is routed from the second data server in the second node through the first replication server in the first node to an external replication system.

7 more elements

A system comprising:

one or more processors;
and
a computer-readable medium storing instructions executable by the one or more processors to perform operations comprising:
determining a failover of a first node, wherein the first node includes a first data server and a first replication server, and wherein at least one user application connects to the first data server prior to the failover of the first node;
in response to the determined failover of the first node including a failure of the first replication server:
connecting the at least one user application to a second data server of a second node, wherein the second node includes the second data server and a second replication server, and wherein a data replication topology of the second data server is a remote topology;
and
in response to connecting the at least one user application to the second data server of the second node, switching the data replication topology of the second data server from the remote topology to a local topology, wherein, in the remote topology, replication data of the second data server in the second node is routed from the second data server in the second node through the first replication server in the first node to an external replication system, wherein, in the local topology, replication data of the second data server in the second node is routed from the second data server in the second node through the second replication server in the second node to the external replication system, and wherein prior to the failover of the first node, replication data of the first data server in the first node is routed from the first data server in the first node through the second replication server in the second node to the external replication system;
and
in response to the determined failover of the first node not including a failure of the first replication server:
connecting the at least one user application to the second data server of the second node, wherein the second node includes the second data server and the second replication server, and wherein the data replication topology of the second data server is a remote topology;
and
in response to connecting the at least one user application to the second data server of the second node, maintaining the data replication topology of the second data server as the remote topology, wherein, in the remote topology, replication data of the second data server in the second node is routed from the second data server in the second node through the first replication server in the first node to an external replication system.

10 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/471,294Filed 28 Mar 2017
Published: US 2018/0288146 A14 Oct 2018
Granted: 8 Sep 2020
Term ends: Not estimatedThe source records don’t support an estimate.

Classification5 codes

H04L 67/1095
In which an application is distributed across nodes in the network: replication or mirroring of data, e.g. scheduling or transport for data…
H04L 41/0663
Using network fault recovery: performing the actions predefined by failover planning, e.g. switching to standby network elements
H04L 41/12
Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks: discovery or management…
H04L 69/40
Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass: for…

Family

US 2018/0288146 A1Pre-grant publication · published 4 Oct 2018
US 10,771,551 B2This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key