International Business Machines Corporation

Hamdi Roumani

Carlos D Cavanna

Christian Marcelo Garcia-Arellano

Adam J Storm

Ann Corrao

Ronen Grosman

Ao Wan

Robert Francis

Jeffrey Bloom

Rafael Velez

Zixi Gu

Alexander Cheung

David C Kalmuk

Scott Douglas Walkty

Patrick R Perez

Robert C Hooper

Richard Sefton Sidle

Ketan Rampurkar

Examples described herein provide a computer-implemented method for storing data pages of a database in a remote storage. The method includes receiving a write request associated with one or more data pages of the database. The method further includes storing, in a first storage layer having a write ahead log, the write request associated with the one or more data pages. The method further includes storing, in a first write buffer, the received write request associated with the one or more data pages that each include a legacy data page identifier. The method further includes storing, in a second storage layer having a second write buffer, a sorted string table (SST) of the received write request. The method further includes storing, in a top level of a log structured merge (LSM) tree disposed in the remote storage, the SST from the second write buffer.

Storing data pages of a database in a cloud object storage

Described are techniques for creating a point-in-time backup of application data stored on disparate storage systems. The techniques include initiating a snapshot of the first datastore. The techniques further include initiating a suspension of delete operations at the second datastore to preserve immutable application data stored on the second datastore. The techniques further include initiating a background copy of the second datastore. The techniques further include initiating a resumption of the delete operations at the second datastore in response to completion of the background copy of the second datastore.

Point-in-time backup of application data stored on disparate storage systems

Provided are techniques for providing a global unique identifier for a storage volume. Under control of a storage initiator, a Global Universally Unique Identifier (GUUID) is identified for a storage volume of a storage device in a cloud system storing a plurality of storage devices, wherein the GUUID is generated for use with an ATA over Ethernet (AoE) protocol. The GUUID is stored in bytes of a packet header structure. Metadata is stored in remaining portions of the packet header structure. A request with the packet header structure is sent to a storage target.

Providing a global unique identifier for a storage volume

A request for changing data of a file system data structure stored on a shingled magnetic recording (SMR) drive is received. The data change is logged in a log entry of a log structure stored in a non-volatile random access memory (NVRAM). The log entry is added as a new entry at an end of the log structure. The log entry is marked within the NVRAM as modified and a predetermined criterion is determined to be satisfied. Responsive to determining that the predetermined criterion is satisfied, the NVRAM is searched for log entries marked as modified. The modified log entries are stored to the SMR drive.

Shingled magnetic recording drive mapping using nonvolatile random access memory for persistent updates

A current minimum memory requirement for each memory consumer of one or more memory consumers of a primary database system is received. A current memory allocation for a standby database system is received. A set of benefit-to-cost metrics is received. A benefit-to-cost metric is a measure of whether each memory consumer would benefit or would not benefit from additional memory. The set of benefit-to-cost metrics is applied to the standby database system to define an upper bound memory allocation of the standby database system to function in the event of a failover from the primary database system. A scaling factor is determined. In response to receiving an indication of a failover of the primary database system to the standby database system, a ramp up of the standby database system is monitored. The ramp up of the standby database system uses the set of benefit-to-cost metrics and the determined scaling factor.

Optimizing standby database memory for post failover operation

Shingled magnetic recording drive mapping using non-volatile random access memory for persistent updates

Growing community of inventors

Toronto, Canada

Hamdi Roumani