G06F11/2069

Synchronous replication

One or more techniques and/or computing devices are provided for synchronous replication. For example, synchronous replication relationships are established between a first storage object (e.g., a file, a logical unit number (LUN), a consistency group, etc.), hosted by a first storage controller, and a plurality of replication storage objects hosted by other storage controllers. In this way, a write operation to the first storage object is implemented in parallel upon the first storage object and the replication storage objects in a synchronous manner, such as using a zero-copy operation to reduce overhead otherwise introduced by performing copy operations. Reconciliation is performed in response to a failure so that the first storage object and the replication storage objects comprise consistent data. Failed write operations and replication write operations are retried, while enforcing a single write semantic. Dependent write order consistency is enforced for dependent write operations, such as overlapping write operations.

GENERATING A CHAIN OF A PLURALITY OF WRITE REQUESTS

Provided are a computer program product, system, and method for generating a chain of a plurality of write requests including a commit wait flag and plurality of write requests. The commit wait flag is set to one of an indicated first value or a second value. The commit wait flag is set to the first value to cause a storage server to process the write requests by requiring a current write request being processed to complete before transferring data for a next write request following the current write request. The commit wait flag is set to the second value to cause the storage server to process the write requests by transferring data for the next write request before completing the current write request preceding the next write request. The write request chain is sent to the storage server to apply the write requests to the storage.

STORAGE SYSTEM
20230168980 · 2023-06-01 ·

A storage system includes: a power source; a drive box that stores a storage apparatus; a storing apparatus having a storage unit in which data regarding devices is stored; a PCIe switch that can switch between a plurality of communication paths, has a communication path connected at least to the storage apparatus, and can further perform I2C communication with the storing apparatus; an auxiliary apparatus that can perform I2C communication with the PCIe switch; and a MOS switch that controls power supply from the power source to the storing apparatus, wherein if timeout of the I2C communication between the PCIe switch and the storing apparatus occurs, the PCIe switch transmits a hard reset command to the auxiliary apparatus; and wherein when the auxiliary apparatus receives the hard reset command, the auxiliary apparatus stops the power supply to the storing apparatus by using the MOS switch and then performs power resupply.

Database segment load balancer

Methods, systems, and computer programs encoded on computer storage media, for implementing MPP relational databases using containers. One example system initiates primary containers to implement database segment instances. Each segment of the database is stored on a respective storage volume. Each storage volume is mounted on a respective primary container. The system detects a failure of a first primary container that is a segment instance of a first database segment. In response to the detection, the system performs a recovery process. The system unmounts, from the failed first primary container, a first storage volume storing the first database segment. The system selects a standby container from a pool of standby containers and mounts the first storage volume on the selected standby container. The system is reconfigured so that it processes queries for the first database segment using the selected standby container instead of the failed first container.

Method, device, and computer program product for managing storage system

The present disclosure relates to a method, a device, and a computer program product for managing a storage system. The storage system includes a first control node, a second control node, and a persistent storage device, the first control node being in an activated state, and the second control node being in a state of transfer from a non-activated state to an activated state. A method includes: loading a first list of page descriptors of the storage system to the second control node to generate a second list of page descriptors at the second control node, the first list including a portion of multiple page descriptors of the storage system that has been modified but has not been flushed to the persistent storage device; receiving a synchronization message from the first control node that indicates that the first list has been modified by the first control node; and updating the second list at the second control node based on the synchronization message. Further, a corresponding device and a corresponding program product are provided. With the example implementations of the present disclosure, the start performance of the control nodes in the storage system can be improved.

VIRTUALIZED FILE SERVER DISASTER RECOVERY

In one embodiment, a system for managing a virtualization environment includes a set of host machines, each of which includes a hypervisor, virtual machines, and a virtual machine controller, and a virtualized file server backup system configured to identify backup data, wherein the backup data comprises data stored on the virtual disks and VFS configuration information, and the first data is identified in accordance with a backup policy, send the backup data to one or more remote sites for storage, and, in response to detection of changes in the backup data, send the changes to the remote sites in accordance with a replication policy. The backup data may be identified based on a protection domain associated with the backup policy. The data stored on the VFS may include one or more storage objects. The storage objects may include shares, groups of shares, files, or directories.

Four site data replication using host based active/active model

A system and method for data replication is provided. A host synchronously replicates data between a first local storage device and a second local storage device, the first local storage device and the second local storage device being coupled to the host. Data is then asynchronously replicated from the first local storage device and the second local storage device to at least one remote storage device. In an embodiment, each of the local storage devices may asynchronously replicate data to remote storage devices located at separate sites to provide four site data replication processing. The system described herein provides for advantageous and efficient swapping of control between hosts and storage devices located in different regions in response to disasters and/or other events affecting data storage in a particular region.

CROSS-PLATFORM REPLICATION

One or more techniques and/or computing devices are provided for cross-platform replication. For example, a replication relationship may be established between a first storage endpoint and a second storage endpoint, where at least one of the storage endpoints, such as the first storage endpoint, lacks or has incompatible functionality to perform and manage replication because the storage endpoints have different storage platforms that store data differently, use different control operations and interfaces, etc. Accordingly, replication destination workflow, replication source workflow, and/or a proxy representing the first storage endpoint may be implemented at the second storage endpoint comprising the replication functionality. In this way, replication, such as snapshot replication, may be implemented between the storage endpoints by the second storage endpoint using the replication destination workflow, the replication source workflow, and/or the proxy that either locally executes tasks or routes tasks to the first storage endpoint such as for data access.

System and Method for Recovering a Storage Array

Systems and techniques for recovering a storage array are disclosed. These systems and techniques include determining a size corresponding to a storage stripe of the storage array. Pieces assigned to the storage stripe are identified. A storage configuration corresponding to the pieces assigned to the storage stripe is detected. Ordinal information and parity information are determined corresponding to the pieces assigned to the storage stripe. The size determined corresponding to the storage stripe, identification of the pieces assigned to the storage stripe, the storage configuration, the ordinal information, and the parity information is stored in a data store to reconstruct lost or corrupted metadata corresponding to the storage array.

Monitoring of replicated data instances

Replicated instances in a database environment provide for automatic failover and recovery. A monitoring component can obtain a lease enabling the component to periodically communicate with, and monitor, one or more data instances in the data environment, where the data instance can be a replicated instance including a primary and a secondary replica. For a large number of instances, the data environment can be partitioned such that each monitoring component can be assigned a partition of the workload. In the event of a failure of a monitoring component, the instances can be repartitioned and the remaining monitoring components can be assigned to the new partitions to substantially evenly distribute the workload.