CDBMS (cloud database management system) distributed logical unit repository

• US 10,311,022 B2
• Filed: 06/12/2014
• Issued: 06/04/2019
• Est. Priority Date: 06/24/2013
• Status: Active Grant

• Current Assignee: K2View Ltd.
• Original Assignee: K2View Ltd.
• Inventors: Itamar, Einav, Rotem, Achi
• Primary Examiner(s): Le, Uyen T
• Application Number:
  US14/894,526
• Publication Number:
  US 20160140134A1
• Time in Patent Office: 1,818 Days
• Field of Search: None
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: G06F 16/1744 using compression, e.g. sparse files
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 21/80 in storage media based on magnetic or optical technology, e.g. disks with sectors preventing unauthorised reproduction or copying of disc-type recordable media G11B20/00

Abstract

Systems and methods may implement database technology using distributed logical unit repositories (DLURs). DLURs may use a database structure related to a specific logical unit such as a customer, employee, or the like. Information used in DLUR database structures may include data, database structure, functions, and the like that helps form a complete model for a logical unit. In one embodiment, queries to a system concerning entities can be answered immediately by accessing a database using DLURs, which obviates the need to consult a number of databases in parallel and greatly reduces memory and time required to provide the requested information.

Claims

1. A system for storing data, comprising:

a processor; and

a logical unit database configured to be accessed by the processor,

wherein the logical unit database contains a plurality of entries for a single logical unit, each entry comprising an identification (ID) and a snapshot data portion,

wherein a first data portion corresponding to a first snapshot data portion of a first entry of the plurality of entries is contained in a first database that is separate from the logical unit database, and

wherein a second data portion corresponding to a second snapshot data portion of a second entry of the plurality of entries is contained in a second database that is separate from the logical unit database and from the first database.

2. The system of claim 1, wherein the snapshot data portion comprises an indicator that indicates a last revision time of the snapshot data portion.

3. The system of claim 1, wherein the snapshot data portion of at least one entry of the plurality of entries comprises multiple snapshots forming a version history of previous snapshots for the at least one entry.

4. The system of claim 1, wherein the snapshot data portion is compressed.

5. The system of claim 4, wherein the compressed snapshot data portion is stored in a binary form.

6. The system of claim 5, wherein the compressed snapshot data portion is stored in an encrypted form.

7. The system of claim 1, wherein the ID is an entry that identifies the corresponding logical unit.

8. The system of claim 1, wherein the ID corresponds to a single customer and the information in the logical unit comprises information for the single customer.

9. The system of claim 1, wherein the logical unit database contains only entries for the single logical unit.

10. The system of claim 1, wherein the first snapshot data portion is configured to be updated when the first database changes the first data portion, and the second snapshot data portion is configured to be updated when the second database changes the second data portion.

11. A method for storing data regarding a logical unit, comprising:

assembling information from a plurality of extant databases, the information including a first data portion from a first database and a second data portion from a second database, wherein the assembled information pertains to a single logical unit;

forming a snapshot of the logical unit using the assembled information, wherein the snapshot is configured to be updated when one or more of the plurality of extant databases changes the information; and

storing the snapshot in a data portion of a logical unit database,

wherein the logical unit database is separate from the extant databases.

12. The method of claim 11, further comprising:

storing multiple snapshots regarding the single logical unit in the data portion, wherein the multiple snapshots form a version history of previous snapshots stored in the data portion.

13. The method of claim 11, further comprising compressing the snapshot.

14. The method of claim 13, wherein the compressed snapshot is stored in a binary form.

15. The method of claim 14, further comprising encrypting the compressed snapshot.

16. A method for retrieving data, comprising:

defining a threshold that specifies an age of data;

receiving a query regarding a single logical unit,

determining whether a data age associated with a snapshot of information pertaining to the single logical unit exceeds the threshold based on an indicator of the logical unit, wherein the indicator reflects when a snapshot of the single logical unit was created or revised, and wherein the information pertaining to the single logical unit is contained in a plurality of databases separate from a database storing the single logical unit;

updating at least one outdated portion of the snapshot when the data age exceeds the threshold, wherein the outdated portion corresponds to a portion of the information pertaining to only the single logical unit contained in the plurality of databases that has changed; and

fulfilling the query based on the snapshot.