Abstract: A process group resource manager for managing protected resources during transaction processing is disclosed. The process group resource manager comprises a first process configured to provide access to a protected resource during one or more transactions, the first process being further configured to construct a transaction record for each respective transaction, wherein each transaction record includes each request message received by the first process and each response message sent by the first process during a particular transaction. The process group resource manager further comprises a second process configured to serially replay the transactions in which the first process participates, the second process being configured to cause a particular transaction to rollback if the replay of that transaction does not match the transaction record constructed by the first process for that transaction.
Type:
Grant
Filed:
April 12, 2002
Date of Patent:
September 30, 2008
Assignee:
724 Solutions Software, Inc
Inventors:
Mark Edward Molloy, Ian McLean Pattison
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.
Type:
Grant
Filed:
June 26, 2008
Date of Patent:
March 15, 2011
Assignee:
Microsoft Corporation
Inventors:
Gregory Thiel, Alexander R. Wetmore, Shawn Bracewell, Rebecca Benfield
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.
Type:
Application
Filed:
June 26, 2008
Publication date:
December 31, 2009
Applicant:
MICROSOFT CORPORATION
Inventors:
Gregory Thiel, Alexander R. Wetmore, Shawn Bracewell, Rebecca Benfield