Amazon Technologies, Inc.

Ramesh Chander

Punit Rajgaria

Murali Brahmadesam

Hemanth Satyanarayana

Michael Higgins Dowling

Omar Farhat

Aakash Ashwin Shah

Techniques for fast database recovery in a multi-volume database environment via transactional awareness are described. In the event of a failure associated with a first volume storing database page data, the first volume can be restored to a point in time and transactional metadata from a second volume storing logical change data can be obtained for a limited number of transactions occurring at/after that point in time, as opposed to analyzing extremely large change log files. These transactions can be checked to ensure that they have all been persisted, and if not, change data for those transactions can be obtained from the second volume and used to replay these transactions on the restored first volume.

Fast database recovery in a multi-volume database environment via transactional awareness

Techniques for volume durable log sequence number movement in a multi-volume database environment are described. Blocks of database updates are persisted in an atomic and durable manner, where the blocks may include updates to a first volume, a second volume, or both. Backlinks from one block of updates to the previous block of updates may be set, in addition to backlinks between updates to the first volume and backlinks between updates to the second volume. Upon durably persisting a block, the block backlinks can be followed to help verify that all contiguous blocks—of changes to one or both volumes—have all been persisted. Thereafter, a volume durable log sequence number (VDL) pointer value can be updated to point to a known 'last' durably persisted log update.

Volume durable log sequence number movement in a multi-volume database environment

Growing community of inventors

Santa Clara, CA, United States of America

Ramesh Chander