IP Library Granted Patent US 10,884,875
Granted Patent B2
US 10,884,875 · App. 15/839,746 · Granted Jan 5, 2021

Incremental backup of computer data files

Inventor: Thomas Petracca (New York, NY)
Assignee: Palantir Technologies Inc.
G06F11/1469G06F11/1451G06F11/1471
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,884,875
App. No.
15/839,746
Granted
Jan 5, 2021
Kind
B2
Abstract

Systems and methods are provided for database or data file backup. The system may comprise one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the system to identify a list of data files required for restoring the database or data files, create a backup comprising copies of a subset of the data files that are created or modified after a preceding backup, and back up the database, wherein the backup includes an identification to the preceding backup.

Claims (58)

1. A method for creating an incremental backup of a database following a preceding backup, being implemented by a computing system including one or more physical processors and storage media storing machine-readable instructions, the method comprising:

accessing a schema of the database;

identifying, in the schema, a list of data files required for restoring the database, the data files being immutable and the list excluding data files that have been replaced by updated data files;

determining whether a preceding backup exists;

in response to determining that the preceding backup does not exist:

creating a first backup comprising the list of the data files; and

creating first metadata of the first backup comprising:

a first backup identification reference; and

an identification representing a state of the preceding backup set to be equal to the first backup identification reference; and

in response to determining that the preceding backup exists:

creating a second backup comprising copies of a subset of the data files that have been created or modified after the preceding backup; and

creating second metadata of the second backup comprising:

a second backup identification reference;

a parent backup identification reference referring to the preceding backup; and

the list of the data files, wherein the creating the second backup comprises:

determining the subset of the data files as comprising files from the list not present in a list of data files required for restoring the database created during the preceding backup; and

backing up the database, wherein the backup includes the subset of the data files.

2. The method of claim 1 , wherein the database constitutes a keyspace of a larger database.

3. A system for creating an incremental backup of a database following a preceding backup, the system comprising:

one or more processors; and

a memory storing instructions that, when executed by the one or more processors, cause the system to perform:

accessing a schema of the database;

identifying, in the schema, a list of data files required for restoring the database, the data files being immutable and the list excluding data files that have been replaced by updated data files;

determining whether a preceding backup exists; in response to determining that the preceding backup does not exist:

creating a first backup comprising the list of the data files; and

creating first metadata of the first backup comprising:

a first backup identification reference; and

an identification representing a state of the preceding backup set to be equal to the first backup identification reference; and

in response to determining that the preceding backup exists:

creating a second backup comprising copies of a subset of the data files that have been created or modified after the preceding backup; and

creating second metadata of the second backup comprising:

a second backup identification reference;

a parent backup identification reference referring to the preceding backup; and

the list of the data files, wherein the creating the second backup comprises:

determining the subset of the data files as comprising files from the list not present in a list of data files required for restoring the database

created during the preceding backup; and backing up the database, wherein the backup includes the subset of the data files.

4. The system of claim 3 , wherein the database constitutes a keyspace of a larger database.

5. The system of claim 3 , wherein a state of the data files is unchanging from an external point of view.

6. A non-transitory computer readable medium for creating an incremental backup of a database following a preceding backup, the medium comprising instructions that, when executed, cause one or more processors to perform:

identifying, in a schema of the database, a list of data files required for restoring the database, the data files being immutable and the list excluding data files that have been replaced by updated data files;

determining whether a preceding backup exists;

in response to determining that the preceding backup does not exist:

creating a first backup comprising the list of the data files; and

creating first metadata of the first backup comprising:

a first backup identification reference; and

an identification representing a state of the preceding backup set to be equal to the first backup identification reference; and

in response to determining that the preceding backup exists:

creating a second backup comprising copies of a subset of the data files that have been created or modified after the preceding backup; and

creating second metadata of the second backup comprising:

a second backup identification reference;

a parent backup identification reference referring to the preceding backup; and

the list of the data files, wherein the creating the second backup comprises:

determining the subset of the data files as comprising files from the list not present in a list of data files required for restoring the database

created during the preceding backup; and

backing up the database, wherein the backup includes the subset of the data files.

7. The non-transitory computer readable medium of claim 6 , wherein the database constitutes a keyspace of a larger database.

8. The non-transitory computer readable medium of claim 6 , wherein the data files are immutable.

9. The non-transitory computer readable medium of claim 8 , wherein the list does not include data files in the database that have been replaced by updated data files.

Assignments (8)
ASSIGNMENT OF INTELLECTUAL PROPERTY SECURITY AGREEMENTS Recorded Jul 3, 2022
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: WELLS FARGO BANK, N.A.
Reel/Frame 060572/0640 →
SECURITY INTEREST Recorded Jul 3, 2022
From: PALANTIR TECHNOLOGIES INC.
To: WELLS FARGO BANK, N.A.
Reel/Frame 060572/0506 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOUSLY LISTED PATENT BY REMOVING APPLICATION NO. 16/832267 FROM THE RELEASE OF SECURITY INTEREST PREVIOUSLY RECORDED ON REEL 052856 FRAME 0382. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST. Recorded Aug 26, 2021
From: ROYAL BANK OF CANADA
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 057335/0753 →
SECURITY INTEREST Recorded Jun 4, 2020
From: PALANTIR TECHNOLOGIES INC.
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 052856/0817 →
RELEASE OF SECURITY INTEREST Recorded Jun 4, 2020
From: ROYAL BANK OF CANADA
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 052856/0382 →
SECURITY INTEREST Recorded Jan 27, 2020
From: PALANTIR TECHNOLOGIES INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 051713/0149 →
SECURITY INTEREST Recorded Jan 27, 2020
From: PALANTIR TECHNOLOGIES INC.
To: ROYAL BANK OF CANADA, AS ADMINISTRATIVE AGENT
Reel/Frame 051709/0471 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 20, 2019
From: PETRACCA, THOMAS
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 049235/0036 →
Cited By (1)
US 12,265,720