Abstract: A method to continuously replay Production Database Workload in near real time using workload capture based on Network or Kernel Capture is provided. The capture of the Server workload is done using Network Capture or using Kernel drivers in a continuous round robin method. The captured data is continuously pre-processed followed by a continuous replay of that data to a Test database system, with the replay lagging the original workload by a fixed initial time delay.

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.