# US 2019/0377642 A1 · Decoupled backup solution for distributed databases across a failover cluster

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

- Number: US 2019/0377642 A1
- Document ID: US20190377642A1
- Status: Published application
- Kind: A1
- Application number: 16/003,966
- Filed: 2018-06-08
- Published: 2019-12-12
- Earliest claimed: 2018-06-08
- Assignees: EMC IP Holding Company LLC
- Applicants: EMC IP Holding Company LLC
- Inventors: Asif Khan; Matthew Dickey Buchman; Tushar B. Dethe; Deepthi Urs; Sunil Yadav; Mahesh Reddy AV; Swaroop Shankar D H; Shelesh Chopra
- Web page: https://patentgrep.com/patent/US20190377642A1

## CPC

- G06F 11/1464: {for networked environments}
- G06F 11/1448: {Management of the data involved in backup or backup restore}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1471: involving logging of persistent data for recovery
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/2041: {with more than one idle spare processing component}
- G06F 11/2048: {where the redundant components share neither address space nor persistent storage}
- G06F 11/2097: {maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups)}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 2201/80: Database-specific techniques
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A decoupled backup solution for distributed databases across a failover cluster. Specifically, a method and system disclosed herein improve upon a limitation of existing backup mechanisms involving distributed databases across a failover cluster. The limitation entails restraining backup agents, responsible for executing database backup processes across the failover cluster, from immediately initiating these aforementioned processes upon receipt of instructions. Rather, due to this limitation, these backup agents must wait until all backup agents, across the failover cluster, receive their respective instructions before being permitted to initiate the creation of backup copies of their relative distributed database. Subsequently, the limitation imposes an initiation delay on the backup processes, which the disclosed method and system omit, thereby granting any particular backup agent the capability to immediately (i.e., without delay) initiate those backup processes.

## Claims

### Claim 1

A method for optimizing distributed database backups, comprising:
receiving, at a secondary node, a secondary data backup request from a primary node; and
while at least one other secondary node has yet to receive another secondary data backup request from the primary node:
initiating, in response to the secondary data backup request, a secondary data backup process on the secondary node.

### Claim 2 (depends on 1)

The method of claim 1, wherein the secondary data backup process, comprises:
creating a backup copy of a passive database copy (PDC) that is one selected from a group consisting of hosted on and operatively connected to, the secondary node; and
submitting the backup copy for remote consolidation on a cluster backup storage system (BSS).

### Claim 3 (depends on 2)

The method of claim 2, wherein the backup copy is one selected from a group consisting of a full database backup, a differential database backup, and a transaction log backup.

### Claim 4 (depends on 2)

The method of claim 2, wherein the PDC is a standby database copy of an active database copy (ADC).

### Claim 5 (depends on 4)

The method of claim 4, wherein the ADC is one selected from a group consisting of hosted on and operatively connected to, the primary node.

### Claim 6 (depends on 1)

The method of claim 1, wherein the secondary node and the at least one other secondary node are standby nodes for the primary node.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
generating a data backup report based on an outcome of the secondary data backup process; and
issuing the data backup report to the primary node.

### Claim 8

A system, comprising:
a plurality of database failover nodes (DFNs);
a primary backup agent (PBA) executing on a first DFN of the plurality of DFNs; and
a secondary backup agent (SBA) executing on a second DFN of the plurality of DFNs,
wherein the SBA is operatively connected to the PBA, and programmed to:
receive a secondary data backup request from the PBA; and
while at least one other SBA has yet to receive another secondary data backup request from the PBA:
initiate, in response to the secondary data backup request, a secondary data backup process on the second DFN.

### Claim 9 (depends on 8)

The system of claim 8, further comprising:
a third DFN of the plurality of DFNs,
wherein the at least one other SBA executes on the third DFN, and is operatively connected to the PBA.

### Claim 10 (depends on 8)

The system of claim 8, further comprising:
a passive database copy (PDC) that is one selected from a group consisting of hosted on and operatively connected to, the second DFN,
wherein the secondary data backup process comprises creating a backup copy of the PDC.

### Claim 11 (depends on 8)

The system of claim 8, wherein the PBA is programmed to:
prior to the SBA receiving the secondary data backup request:
receive a first data backup request; and
in response to the first data backup request:
initiate a primary data backup process on the first DFN; and
issue, after initiating the primary data backup process, at least one secondary data backup request to at least one SBA,
wherein the at least one secondary data backup request comprises the secondary data backup request and the another secondary data backup request,
wherein the at least one SBA comprises the SBA and the at least one other SBA.

### Claim 12 (depends on 11)

The system of claim 11, further comprising:
a cluster administrator client (CAC) operatively connected to the PBA,
wherein the first data backup request is received from the CAC.

### Claim 13 (depends on 12)

The system of claim 12, wherein the PBA is further programmed to:
obtain a first outcome based on performing the primary data backup process;
receive, from the SBA, a data backup report specifying a second outcome based on a performance of the secondary data backup process; and
receive, from the at least one other SBA, at least one other data backup report specifying at least one other outcome based on at least one other performance of at least one other secondary data backup process;
generate an aggregated data backup report based on the first outcome, the second outcome, and the at least one other outcome; and
issue the aggregated data backup report to the CAC.

### Claim 14 (depends on 11)

The system of claim 11, further comprising:
an active database copy (ADC) that is one selected from a group consisting of hosted on and operatively connected to, the first DFN,
wherein the primary data backup process comprises creating a backup copy of the ADC.

### Claim 15 (depends on 8)

The system of claim 8, further comprising:
a database failover cluster (DFC) comprising the plurality of DFNs.

### Claim 16 (depends on 8)

The system of claim 8, further comprising:
a cluster backup storage system (BSS) operatively connected to the plurality of DFNs,
wherein the secondary data backup process comprises creating a backup copy and consolidating the backup copy in the cluster BSS.

### Claim 17

A non-transitory computer readable medium (CRM) comprising computer readable program code, which when executed by a computer processor, enables the computer processor to:
receive, at a secondary node, a secondary data backup request from a primary node; and
while at least one other secondary node has yet to receive another secondary data backup request from the primary node:
initiate, in response to the secondary data backup request, a secondary data backup process on the secondary node.

### Claim 18 (depends on 17)

The non-transitory CRM of claim 17, wherein the secondary data backup process, comprises enabling the computer processor to:
create a backup copy of a passive database copy (PDC) that is one selected from a group consisting of hosted on and operatively connected to, the secondary node; and
submit the backup copy for remote consolidation on a cluster backup storage system (BSS).

### Claim 19 (depends on 17)

The non-transitory CRM of claim 17, wherein the secondary node and the at least one other secondary node are standby nodes for the primary node.

### Claim 20 (depends on 17)

The non-transitory CRM of claim 17, further comprising computer readable program code, which when executed by the computer processor, enables the computer processor to:
generate a data backup report based on an outcome of the secondary data backup process; and
issue the data backup report to the primary node.
