International Business Machines Corporation

Daniel Gan-Levi

Lior Chen

Ofer Leneman

Ronen Gazit

Ehood Garmiza

Deborah A Messing

Dan Cohen

Nimrod Sapir

Michael Keller

Constantine Gavrilov

Shai M Koffman

Leonid Chernin

A computer-implemented method, according to one embodiment, includes: storing information in a specified system memory location, attaching an external process to the specified system memory location in response to experiencing a system halt event, sending the information stored in the specified system memory location to a memory location associated with the external process, restarting the system in a recovery mode, retrieving the information from the external process, and using the retrieved information to restore the system to a state the system was in when the system halt event occurred. Other systems, methods, and computer program products are described in additional embodiments.

System halt event recovery

A controller-implemented method, according to one embodiment, includes: receiving, by a first controller, data. Metadata associated with the data is stored, by the first controller, in a specified system memory location. Second metadata received from a second controller is also stored, by the first controller, in the specified system memory location, thereby creating combined metadata. In response to the second controller entering a failed state: snapshots of the combined metadata are stored, by the first controller, to resilient storage at a predefined interval. Moreover, additional data continues to be received by the first controller. Metadata associated with the additional data is stored, by the first controller, in the specified system memory location, while changes to the metadata which occur between the snapshots of the combined metadata are also stored by the first controller. According to some approaches, the changes to the metadata are stored in a log structured array.

Method for the implementation of a high performance, high resiliency and high availability dual controller storage system

ID management for a network attached storage system using layered ID mapping virtualization. When a connection request is received at a NAS server, it is determined whether the request is for a new user, and if so, user IDs are created for the new user. External user ID and filesystem user ID are mapped to the internal user ID, and user ID is verified at the NAS server kernel on subsequent logins with an external database. The user IDs are remapped for the changed user account, and updated mappings are transmitted from the NAS server to one or more NAS server kernel repositories.

ID management for a network attached storage system

A mechanism is provided in a data processing system comprising at least one processor and at least one memory, the at least one memory comprising instructions that are executed by the at least one processor and configure the at least one processor to implement a replication protocol for replicating memory from an initiator to a target. The initiator requests one or more pages of memory at the target. Responsive to the initiator receiving a page advertisement from the target, the initiator updates a list of pages at the initiator. The list of pages is replicated at the target. The initiator performs a remote direct memory access (RDMA) write to the one or more pages of memory at the target. Responsive to successful completion of the RDMA write, the initiator updates the list of pages at the initiator. Upon completion of the RDMA write the list of pages is updated at the target.

Persistent memory replication in RDMA-capable networks

A computer-implemented method, according to one embodiment, includes: splitting received information between two controllers of a system in a normal operating mode, the received information including data and metadata; storing the metadata in resilient storage in response to a first of the controllers entering a failed state; updating the first controller with information received while the first controller was in the failed state, the first controller being updated in response to the first controller being repaired; and returning the system to the normal operating mode in response to the first controller being updated. Storing the metadata in resilient storage includes: saving snapshots of the metadata in the resilient storage, and saving changes to the metadata which occur between the snapshots. The changes to the metadata are saved in a log structured array. Moreover, the two controllers store the received information in a specified system memory location.

A computer-implemented method for data mirroring for network attached storage includes duplicating an identity mapping database on a second NAS server and creating a queue of updated data files containing updated elements since a prior synchronization. Data files containing the updated elements are transmitted from the first NAS server to the second NAS server. An updated copy of the identity mapping database from the first NAS server is stored at the second NAS server. The updated data files and metadata information from the first NAS server are written to the second NAS server. The permission entries of the transmitted data files from the first NAS server are translated using the identity mapping databases of the first and second NAS servers, such that the permission entries reflect the local ID mapping database on the second NAS server.

Data mirroring for network attached storage

Provided are a computer program product, system, and method for distributed global data vaulting in a grid of server computers. At each of the server computers, it is determined that there is a system shutdown. For each data element at that server computer, a list of one or more vault devices at other server computers is retrieved from a vault distribution table, and the data element is dumped to the one or more vault devices at the other server computers.

Growing community of inventors

Modiin, Israel

Daniel Gan-Levi