DATA CONSISTENCY AND ROLLBACK FOR CLOUD ANALYTICS

• US 20140229423A1
• Filed: 02/11/2013
• Published: 08/14/2014
• Est. Priority Date: 02/11/2013
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Bengali, Ketan, Mandal, Kaniska, Chen, Alex J.
• Granted Patent: US 9,141,680 B2
• Time in Patent Office: Days
• US Class Current: 707/602
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 2201/80 Database-specific techniques

Abstract

An extract-transform-load (ETL) platform fetches consistent datasets in a batch for a given period of time and provides the ability to rollback that batch. The batch may be fetched for an interval of time, and the ETL platform may fetch new or changed data from different cloud/on-premise applications. It will store this data in the cloud or on-premise to build data history. As the ETL platform fetches new data, the system will not overwrite existing data, but rather will create new versions so that change history is preserved. For any reason, if businesses would like to rollback data, they could rollback to any previous batch.

Claims

1. A method for collecting data, comprising:

collecting a first batch of data by a server from one or more tenant applications and associated with a first period of time;

collecting a second batch of data by the server from the one or more tenant applications and associated with a second period of time subsequent to the first period of time;

marking the second batch of data as the current batch of data;

detecting a rollback event; and

marking the first batch of data as the current batch of data after the rollback request.

2. The method of claim 1, wherein the first batch of data and the second batch of data include the same data objects.

3. The method of claim 1, further comprising creating a batch log.

4. The method of claim 3, the batch log including a unique identifier for each batch.

5. The method of claim 3, further comprising creating a new batch entry for each batch including changed data.

6. The method of claim 3, the batch log including a staging database identifier and ETL server identifier for each batch.

7. The method of claim 1, further comprising logging a subsequent batch as failed when the subsequent batch fails to load into a collection server.

8. The method of claim 1, wherein the rollback event is a request to perform a rollback to a previous batch.

9. The method of claim 1, wherein the rollback event is automatically generated when data fails to load in a database.

10. A computer readable non-transitory storage medium having embodied thereon a program, the program being executable by a processor to perform a method for collecting data, the method comprising:

collecting a first batch of data from one or more tenant applications and associated with a first period of time;

collecting a second batch of data from the one or more tenant applications and associated with a second period of time subsequent to the first period of time;

marking the second batch of data as the current batch of data;

detecting a rollback event; and

marking the first batch of data as the current batch of data after the rollback request.

11. The method of claim 10, wherein the first batch of data and the second batch of data include the same data objects.

12. The method of claim 10, further comprising creating a batch log.

13. The method of claim 12, the batch log including a unique identifier for each batch.

14. The method of claim 12, further comprising creating a new batch entry for each batch including changed data.

15. The method of claim 12, the batch log including a staging database identifier and ETL server identifier for each batch.

16. The method of claim 10, further comprising logging a subsequent batch as failed when the subsequent batch fails to load into a collection server.

17. The method of claim 10, wherein the rollback event is a request to perform a rollback to a previous batch.

18. The method of claim 10, wherein the rollback event is automatically generated when data fails to load in a database.

19. A system for collecting data, comprising:

a memory;

a processor; and

one or more modules stored in memory and executable by the processor to;

collecting a first batch of data from one or more tenant applications and associated with a first period of time;

collecting a second batch of data from the one or more tenant applications and associated with a second period of time subsequent to the first period of time;

marking the second batch of data as the current batch of data;

detecting a rollback event; and

marking the first batch of data as the current batch of data after the rollback request.