IP Library Granted Patent US 10,866,864
Granted Patent B2
US 10,866,864 · App. 15/934,440 · Granted Dec 15, 2020

Systems and methods for backing-up an eventually-consistent database in a production cluster

Inventors: Vaijayanti Bharadwaj (Baner, IN); Chirag Dalal (Pune, IN); Vinay Sharma (Pune, IN)
Assignee: Veritas Technologies LLC
G06F11/1464G06F11/1451G06F11/1453G06F11/1456G06F11/1458G06F11/1469H04L67/1097G06F2201/80
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 10,866,864
App. No.
15/934,440
Granted
Dec 15, 2020
Kind
B2
Abstract

The disclosed computer-implemented method for backing-up an eventually-consistent database in a production cluster may include (1) forming, on a production node, a stable copy of production data, (2) provisioning storage on a backup node based on an amount of data in the stable copy and a replication factor, (3) transferring information from the stable copy to a backup copy on the backup node, (4) performing record synthesis on the backup copy to merge record updates into complete backup records, (5) identifying and discarding any stale records and any redundant records in the complete backup records, and (6) transferring the complete backup records from the backup node to a cloud storage device. Various other methods, systems, and computer-readable media are also disclosed.

Claims (53)

1. A computer-implemented method for backing-up an eventually-consistent database in a production cluster, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

forming, on a production node, a stable copy of production data;

provisioning storage on a backup node based on an amount of data in the stable copy and a replication factor;

transferring information from the stable copy to a backup copy on the backup node;

performing record synthesis on the backup copy to merge record updates into complete backup records;

identifying and discarding any stale records and any redundant records in the complete backup records; and

transferring the complete backup records from the backup node to a cloud storage device.

2. The computer-implemented method of claim 1 , further comprising:

identifying a topology of a production cluster of which the production node is a constituent part to identify the production node as requiring backup.

3. The computer-implemented method of claim 1 , further comprising:

determining the amount of data in the stable copy.

4. The computer-implemented method of claim 1 , further comprising:

provisioning the backup node in a backup cluster based on the amount of data in the stable copy.

5. The computer-implemented method of claim 1 , further comprising:

reverting the backup node to a pre-transfer state.

6. The computer-implemented method of claim 1 , wherein a number of production nodes in a production cluster of which the production node is a constituent part does not equal a number of backup nodes in a backup cluster of which the backup node is a constituent part.

7. The computer-implemented method of claim 1 , further comprising:

restoring the backup copy from the cloud storage device to the production node.

8. A system for backing-up an eventually-consistent database in a production cluster, the system comprising:

a forming module, stored in a memory, that forms, on a production node, a stable copy of production data;

a provisioning module, stored in the memory, that provisions storage on a backup node based on an amount of data in the stable copy and a replication factor;

a first transferring module, stored in the memory, that transfers information from the stable copy to a backup copy on the backup node;

a performing module, stored in the memory, that performs record synthesis on the backup copy to merge record updates into complete backup records;

an identifying and discarding module, stored in the memory, that identifies and discards any stale records and any redundant records in the complete backup records;

a second transferring module, stored in the memory, that transfers the complete backup records from the backup node to a cloud storage device; and

at least one physical processor that executes the forming module, the provisioning module, the first transferring module, the performing module, the identifying and discarding module, and the second transferring module.

9. The system of claim 8 , further comprising:

an identifying module, stored in the memory, that identifies a topology of a production cluster of which the production node is a constituent part to identify the production node as requiring backup.

10. The system of claim 8 , further comprising:

a determining module, stored in the memory, that determines the amount of data in the stable copy.

11. The system of claim 8 , further comprising:

a provisioning module, stored in the memory, that provisions the backup node in a backup cluster based on the amount of data in the stable copy.

12. The system of claim 8 , further comprising:

a reverting module, stored in the memory, that reverts the backup node to a pre-transfer state.

13. The system of claim 8 , wherein a number of production nodes in a production cluster of which the production node is a constituent part does not equal a number of backup nodes in a backup cluster of which the backup node is a constituent part.

14. The system of claim 8 , further comprising:

a restoring module, stored in the memory, that restores the backup copy from the cloud storage device to the production node.

15. A non-transitory computer-readable medium comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to:

form, on a production node, a stable copy of production data;

provision storage on a backup node based on an amount of data in the stable copy and a replication factor;

transfer information from the stable copy to a backup copy on the backup node;

perform record synthesis on the backup copy to merge record updates into complete backup records;

identify and discard any stale records and any redundant records in the complete backup records; and

transfer the complete backup records from the backup node to a cloud storage device.

16. The non-transitory computer-readable medium of claim 15 , wherein the computer-executable instructions further cause the computing device to:

identify a topology of a production cluster of which the production node is a constituent part to identify the production node as requiring backup.

17. The non-transitory computer-readable medium of claim 15 , wherein the computer-executable instructions further cause the computing device to:

determine the amount of data in the stable copy.

18. The non-transitory computer-readable medium of claim 15 , wherein the computer-executable instructions further cause the computing device to:

provision the backup node in a backup cluster based on the amount of data in the stable copy.

19. The non-transitory computer-readable medium of claim 15 , wherein the computer-executable instructions further cause the computing device to:

revert the backup node to a pre-transfer state.

20. The non-transitory computer-readable medium of claim 15 , wherein a number of production nodes in a production cluster of which the production node is a constituent part does not equal a number of backup nodes in a backup cluster of which the backup node is a constituent part.

Assignments (12)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 7, 2026
From: VERITAS TECHNOLOGIES LLC
To: COHESITY, INC.
Reel/Frame 075377/0130 →
AMENDMENT NO. 1 TO PATENT SECURITY AGREEMENT Recorded Apr 8, 2025
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 070779/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2025
From: VERITAS TECHNOLOGIES LLC
To: COHESITY, INC.
Reel/Frame 070335/0013 →
RELEASE OF SECURITY INTEREST Recorded Dec 16, 2024
From: ACQUIOM AGENCY SERVICES LLC, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069697/0238 →
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2024
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069634/0584 →
SECURITY INTEREST Recorded Dec 9, 2024
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK. N.A.
Reel/Frame 069890/0001 →
ASSIGNMENT OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Nov 25, 2024
From: BANK OF AMERICA, N.A., AS ASSIGNOR
To: ACQUIOM AGENCY SERVICES LLC, AS ASSIGNEE
Reel/Frame 069440/0084 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS AT R/F 052426/0001 Recorded Nov 30, 2020
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 054535/0565 →
SECURITY INTEREST Recorded Aug 20, 2020
From: VERITAS TECHNOLOGIES LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 054370/0134 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Apr 16, 2020
From: VERITAS TECHNOLOGIES, LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 052426/0001 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Mar 18, 2020
From: VERITAS TECHNOLOGIES LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 052189/0311 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 23, 2018
From: BHARADWAJ, VAIJAYANTI; DALAL, CHIRAG; SHARMA, VINAY
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 045332/0913 →
Continuity (1)
Related Publication 20190294509A1 · Sep 26, 2019