# US 2023/0401230 A1 · Database systems and related replication monitoring methods

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0401230 A1
- Document ID: US20230401230A1
- Status: Published application
- Kind: A1
- Application number: 17/806,235
- Filed: 2022-06-09
- Published: 2023-12-14
- Earliest claimed: 2022-06-09
- Assignees: Salesforce, Inc.
- Applicants: Salesforce, Inc.
- Inventors: Bharath Vissapragada; Rushabh Shah
- Web page: https://patentgrep.com/patent/US20230401230A1

## CPC

- G06F 16/273: {Asynchronous replication or reconciliation}
- G06F 9/4887: {involving deadlines, e.g. rate based, periodic}
- G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)}
- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- G06F 11/1446: Point-in-time backing up or restoration of persistent data
- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G06F 16/2365: {Ensuring data consistency and integrity}
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- G06F 2201/80: Database-specific techniques
- G06F 2201/81: Threshold
- G06F 2201/835: Timestamp
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Devices, systems and methods are provided for monitoring a replication service replicating data from a source database system to a destination database system. One method involves receiving, at the destination database system from the replication service over a network, a set of database transactions at the source database system, determining an expected tracking entry subsequent to the set of database transactions based at least in part on the one or more tracking entries in the set of database transactions, detecting an anomaly associated with replicating the data from the source database system in response to an absence of receiving, from the replication service, a subsequent set of database transactions at the source database system that includes the expected tracking entry within a threshold period of time, and initiating a remedial action in response to detecting the anomaly.

## Claims

### Claim 1

A method of monitoring a replication service replicating data from a source database system to a destination database system, the method comprising:
receiving, at the destination database system from the replication service over a network, a set of database transactions, wherein the set of database transactions includes one or more tracking entries inserted into a log of database transactions at the source database system;
determining, at the destination database system, an expected tracking entry subsequent to the set of database transactions based at least in part on the one or more tracking entries in the set of database transactions;
detecting, at the destination database system, an anomaly associated with replicating the data from the source database system in response to an absence of receiving, from the replication service, the expected tracking entry in a subsequent set of database transactions at the source database system; and
initiating a remedial action in response to detecting the anomaly.

### Claim 2 (depends on 1)

The method of claim 1, further comprising determining an expected timestamp to be associated with the expected tracking entry based at least in part on respective timestamps associated with the one or more tracking entries, wherein detecting the anomaly comprises detecting the anomaly in the absence of receiving a tracking entry associated with the log of database transactions within a threshold period of time of the expected timestamp.

### Claim 3 (depends on 1)

The method of claim 1, further comprising determining an expected timestamp to be associated with the expected tracking entry based at least in part on an insertion criterion associated with a tracker insertion service at the source database system inserting the one or more tracking entries into the log of database transactions, wherein detecting the anomaly comprises detecting the anomaly in the absence of receiving a tracking entry associated with the log of database transactions within a threshold period of time of the expected timestamp.

### Claim 4 (depends on 1)

The method of claim 1, further comprising determining an expected timestamp to be associated with the expected tracking entry, wherein detecting the anomaly comprises detecting the anomaly in response to the absence of receiving the expected tracking entry within a threshold period of time comprising the expected timestamp plus a buffer amount of time.

### Claim 5 (depends on 1)

The method of claim 1, wherein:
the one or more tracking entries include an identifier associated with the log of database transactions; and
detecting the anomaly comprises:
monitoring the subsequent set of database transactions for the expected tracking entry including the identifier associated with the log of database transactions; and
detecting the anomaly when the subsequent set of database transactions does not include an entry including the identifier associated with the log of database transactions within a threshold period of time after receiving the set of database transactions.

### Claim 6 (depends on 1)

The method of claim 1, wherein:
the log of database transactions comprises a write ahead log (WAL) at the source database system;
determining the expected tracking entry comprises determining a subsequent tracking entry including an identifier associated with the WAL at the source database system is expected to be received at the destination database system based at least in part on the one or more tracking entries including the identifier associated with the WAL in the set of database transactions; and
detecting the anomaly comprises detecting the anomaly associated with replicating the WAL from the source database system to the destination database system in response to the absence of receiving the subsequent tracking entry including the identifier associated with the WAL within a threshold period of time.

### Claim 7 (depends on 6)

The method of claim 6, wherein initiating the remedial action comprises initiating replication of at least a portion of the WAL at the source database system following a most recent tracking entry of the one or more tracking entries.

### Claim 8 (depends on 1)

The method of claim 1, wherein:
the one or more tracking entries include an identifier associated with a region server at the source database system; and
detecting the anomaly comprises detecting the anomaly with respect to the region server in response to the absence of receiving the expected tracking entry including the identifier associated with the region server.

### Claim 9 (depends on 1)

The method of claim 1, further comprising determining an expected time window when the anomaly occurred based on an expected timestamp for the expected tracking entry and a timestamp associated with a most recent tracking entry of the one or more tracking entries.

### Claim 10 (depends on 1)

The method of claim 1, wherein initiating the remedial action comprises generating a user notification of the anomaly at a client device coupled to the destination database system over the network, wherein the user notification comprises indication of at least one of a first identifier associated with a region server at the source database system and a second identifier associated with the log of database transactions.

### Claim 11

A method of monitoring a replication service replicating data from a source database system to a destination database system, the method comprising:
periodically inserting, at the source database system, a plurality of tracking entries into one or more logs of database transactions at the source database system, wherein the replication service is configurable to replicate the one or more logs of database transactions to the destination database system;
receiving, at the destination database system from the replication service, a first subset of database transactions of the one or more logs of database transactions at the source database system, wherein the first subset of database transactions includes one or more tracking entries of the plurality of tracking entries;
detecting, at the destination database system, an anomaly associated with replicating the data from the source database system in response to an absence of receiving, from the replication service, a subsequent subset of database transactions of the one or more logs of database transactions at the source database system that includes an expected tracking entry within a threshold period of time after receiving the one or more tracking entries; and
initiating a remedial action in response to detecting the anomaly.

### Claim 12 (depends on 11)

The method of claim 11, wherein:
periodically inserting the plurality of tracking entries comprises for each respective tracking entry of the plurality of tracking entries, periodically creating the respective tracking entry in a table of a database at the source database system, wherein the respective tracking entry includes an identifier associated with the source database system; and
detecting the anomaly comprises detecting the anomaly in response to the absence of the expected tracking entry including the identifier associated with the source database system within the subsequent subset of database transactions.

### Claim 13 (depends on 12)

The method of claim 12, wherein:
each respective tracking entry of the plurality of tracking entries includes a log identifier associated with a respective log of the one or more logs of database transactions the respective tracking entry is inserted into; and
detecting the anomaly comprises identifying a first log of the one or more logs of database transactions that is associated with the anomaly based on the log identifier associated with a most recent tracking entry of the one or more tracking entries.

### Claim 14 (depends on 13)

The method of claim 13, wherein initiating the remedial action comprises initiating the replication service replicating at least a portion of the first log from the source database system to the destination database system.

### Claim 15 (depends on 14)

The method of claim 14, wherein:
the most recent tracking entry includes an offset value indicating a location of the most recent tracking entry within the first log; and
the portion of the first log comprises entries having locations within the first log following the location of the most recent tracking entry.

### Claim 16 (depends on 13)

The method of claim 13, wherein initiating the remedial action comprises providing graphical indication of the first log at the source database system associated with the anomaly on a client device coupled to a network.

### Claim 17 (depends on 13)

The method of claim 13, wherein:
the one or more logs of database transactions comprise one or more write ahead logs (WALs) at the source database system; and
identifying the first log comprises identifying a first WAL of the one or more WALs associated with the anomaly.

### Claim 18 (depends on 17)

The method of claim 17, wherein:
the most recent tracking entry includes an offset value indicating a location of the most recent tracking entry within the first WAL; and
initiating the remedial action comprises initiating replication of entries at locations within the first WAL following the location of the most recent tracking entry.

### Claim 19

A computing device comprising:
at least one non-transitory machine-readable storage medium that stores software; and
at least one processor, coupled to the at least one non-transitory machine-readable storage medium, to execute the software that implements a replication monitoring service and that is configurable to:
determine an expected tracking entry expected to be received from a replication service over a network based on one or more tracking entries in a first set of database transactions at a source database system received from the replication service, wherein the first set of database transactions comprises a subset of one or more logs of database transactions at the source database system and the one or more tracking entries are inserted into the one or more logs of database transactions;
detect a replication anomaly in response to an absence of receiving, from the replication service, a subsequent set of database transactions at the source database system that includes the expected tracking entry within a threshold period of time; and
initiate a remedial action in response to detecting the anomaly.

### Claim 20 (depends on 19)

The computing device of claim 19, wherein the one or more logs of database transactions at the source database system comprise one or more write ahead logs (WALs) at the source database system and the one or more tracking entries are inserted into the one or more WALs at the source database system.
