Microsoft Technology Licensing, LLC

Emc Corporation

Kevin Farlee

Richard Reitmeyer

William Maruyama

Balan Sethu Raman

Rohan Kumar

Robin Dhananjay Dhamankar

Pradeep Madhavarapu

Michael Warmington

Kapil Gupta

Michael J Purtell

Andrew Jason Cherry

Lin Chan

Archiving a database and point in time recovery of the database. A method includes taking a first snapshot of a database. The first snapshot of the database includes a first snapshot of the data in the data storage and a first snapshot of the log records in the log storage. The method further includes taking a second snapshot of the database. The second snapshot of the database includes a second snapshot of the data in data storage and a second snapshot of the log records. The method further includes restoring the database to a particular point by applying the first snapshot of the data in the data storage to the database, applying the first snapshot of the log records in the log storage to the database and applying a portion of the second snapshot of the log records in the log storage to the database.

Point in time database restore from storage snapshots

A distributed database transaction coordination manager's outcome store may be unavailable to resolve in-doubt transactions locally, e.g., after an unclean detach, during an outcomes store restore, or during a logical database restore. To facilitate transactional consistency, AGEs and values based on them are used. Some code avoids reformatting any closed physical portion for reuse based on the segment's most recently received minimum of persisted AGEs. Some code commits any in-doubt transactions that appear on an aggregate list and aborts any not on the aggregate list. Some code writes each segment's transaction commit records to persistent storage until the segment's persisted-AGE is not less than a common-restore-AGE, and some code resolves any in-doubt transactions based on a harvested outcomes list. Outcomes may reside in a log or a persisted transactions table. A restore checkpoint may include harvested outcomes. Segments may reside on cloud nodes and/or in a shared nothing database system.

Consistent database recovery across constituent segments

Data is processed by receiving a list of one or more file system elements in a level of a file system or a portion thereof. The list is sorted based at least in part on whether a file system element is a file or a directory. A sorted list is obtained. The file system elements in the level are backed up according to the order of the sorted list.

Traversing data in a repeatable manner

Embodiments described herein are directed to the accessing remotely stored binary object data in a binary object store. In one embodiment, a computer system receives a request for a portion of binary object data, sends a query to a database server requesting access to the binary object data, and receives a binary object reference. The binary object reference includes binary object identification data and use characteristics specific to the binary object store. The computer system sends a binary object data access request based on the binary object reference to the binary object store using a binary object store interface, and receives the binary object data corresponding to the binary object data access request. The binary object data comprises a portion of data files. The computer system also sends the received binary object data to the user.

Remote storage and management of binary object data

Traversing hierarchical data is disclosed. A first list of items in a first level of the data is received and sorted in an order. The data of the first level is processed in the order of the sorted first list. If any other level of data is encountered during processing, another list of items in the encountered level is received and sorted in an order. The data is processed in the order of the list.

Growing community of inventors

Maple Valley, WA, United States of America

Kevin Farlee