Minimizing data loss in asynchronous replication solution using distributed redundancy
First Claim
1. A computer-implemented data management system, comprising:
- a history component for maintaining a history of changes made by clients to backend servers;
a storage component for storing the history of the changes for resubmission of the changes in response to a lossy failover of the backend servers;
a pruning component for pruning outdated history items from the history based in part on a replication feedback channel; and
a processor that executes computer-executable instructions associated with at least the history component.
2 Assignments
0 Petitions
Accused Products
Abstract
Architecture that reduces data loss resulting from failover in an asynchronous log shipping deployment, but leveraging mid-tier and frontend servers to fill in lost data. In an asynchronous log shipping operation, a replication component asynchronously replicates messaging data to a backend server in accordance with one or more replication operations, which can be updates to databases on the backend server. These databases can include messaging data, such as email address books, mailboxes, etc. A history component maintains a history of replication operations on a frontend server. In the event of a lossy failover, a replay component is used for replaying the replication operations from the history to the backend server.
-
Citations
20 Claims
-
1. A computer-implemented data management system, comprising:
-
a history component for maintaining a history of changes made by clients to backend servers; a storage component for storing the history of the changes for resubmission of the changes in response to a lossy failover of the backend servers; a pruning component for pruning outdated history items from the history based in part on a replication feedback channel; and a processor that executes computer-executable instructions associated with at least the history component. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A computer-implemented data management system, comprising:
-
a history component for maintaining a history of recent changes made by clients to mid-tier and/or frontend servers, the history includes changes related to update of an existing messaging object, the changes and backend version information of the object are stored in the history; a failover detection component for detecting lossy failover of asynchronous replication of data to backend servers; a resubmission component for requesting resubmission of the recent changes from the history to fill in the changes lost during the replication; and a processor that executes computer-executable instructions associated with at least one of the history component, the failover detection component, or the resubmission component. - View Dependent Claims (12, 13, 14, 15)
-
-
16. A computer-implemented method of data management, comprising acts of:
-
maintaining a recent history of client changes at a server location including changes in the history related to creating a new messaging object and updating an existing messaging object; detecting lost replication data during lossy failover of backend servers; requesting resubmission of the changes from the history of the server location to the backend servers; resubmitting the changes from the history to the backend servers to replace the lost replication data; and utilizing a processor that executes instructions stored in memory to perform at least one of the acts of maintaining, detecting, requesting, or resubmitting. - View Dependent Claims (17, 18, 19, 20)
-
Specification