RECOVERY POINT OBJECTIVE ENFORCEMENT

• US 20140236891A1
• Filed: 02/15/2013
• Published: 08/21/2014
• Est. Priority Date: 02/15/2013
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Talius, Tomas, Nosov, Alexander, Dhamankar, Robin D., Narlapuram, Satyanarayana
• Granted Patent: US 9,805,104 B2
• Time in Patent Office: Days
• US Class Current: 707/613
• CPC Class Codes: G06F 11/00 Error detection; Error correction; Monitoring error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation

Abstract

A maximum lag between data stores can be specified that corresponds to a recovery point objective defined in a service level agreement. Lag can be monitored during a data replication between a primary data store and a secondary data store located in geographically different regions. Activity on the primary data store including incoming data transactions can be throttled as a function of the lag and the maximum lag.

Claims

1. A computer-implemented method, comprising:

monitoring lag between a primary data store located in a first geographic region and a secondary data store located in a second different geographic region during data replication between the primary data store and the secondary data store; and

throttling activity on the primary data store as a function of the lag and a configurable maximum lag.

2. The method of claim 1 further comprises replicating data asynchronously between the primary data store and the secondary data store.

3. The method of claim 1, throttling comprises blocking incoming transactions against the primary data store when the lag is exceeds the maximum lag.

4. The method of claim 3 further comprises blocking the incoming transactions at primary source commit time.

5. The method of claim 3 further comprises spawning an error message in an application supplying a blocked incoming transaction indicating that the lag exceeds the maximum lag.

6. The method of claim 1, throttling comprises reducing a speed at which incoming transactions commit on the primary data store.

7. The method of claim 1, throttling comprises reducing a speed at which incoming transactions are accepted.

8. The method of claim 1 further comprises reporting the lag in response to a request.

9. The method of claim 1 further comprises dynamically changing resource allocation as a function of the lag and the maximum lag.

10. A system, comprising:

a processor coupled to a memory, the processor configured to execute the following computer-executable components stored in the memory;

a first component configured to replicate data asynchronously from a primary data source to a secondary data source, wherein the primary data source and the secondary data source are located in different geographic regions;

a second component configured to monitor lag between one or more transactions committing on the primary data source and the one or more transactions committing on the secondary data source; and

a third component configured to throttle one or more incoming transactions from an application based on the lag and a specified maximum lag.

11. The system of claim 10, the third component is configured to reject the one or more incoming transactions when the lag exceeds the maximum lag.

12. The system of claim 11, the third component is configured to output an error message within the application that indicates the lag exceeds the maximum lag.

13. The system of claim 10, the third component is configured to block the one or more incoming transactions from committing on the primary source at commit time.

14. The system of claim 10, the third component is configured to slow a rate at which the incoming transactions are accepted from the application.

15. The system of claim 10, the third component is configured to slow a rate at which incoming transactions commit on the primary data source.

16. The system of claim 10 further comprising a fourth component configured to report the lag in response to a request.

17. A computer-readable storage medium having instructions stored thereon that enable at least one processor to perform a method upon execution of the instructions, the method comprising:

replicating data asynchronously between a primary data source located in a first geographic region and a secondary data source located in a second different geographic region;

monitoring lag between commit time of one or more transactions on the primary data source and secondary data source; and

aborting one or more incoming transactions on the primary data source when the lag exceeds a configurable maximum value.

18. The method of claim 17 further comprises aborting the one or more incoming transactions at primary data source commit time.

19. The method of claim 17 further comprises spawning an error message indicating that the lag exceeds the maximum value upon aborting one of the one or more incoming transactions.

20. The method of claim 17 further comprises reporting the lag in response to a request.