A storage system has priority queues for real time-class file system messaging and backup-class file system messaging. The storage system includes servers, coupled as a storage cluster, storage devices and a network coupling the servers and the storage devices. The servers have priority queues. The servers operate the priority queues for messaging from the servers to the storage devices via the network in accordance with a real time-class file system and a backup-class file system. A first subset of the priority queues has higher priority on the network for real time-class file system messaging of at least one type. A second subset of the priority queues has lower priority on the network for backup-class file system messaging of at least one type.

The present technology relates to an electronic device. A storage device according to the present technology includes a memory device including a plurality of logical storage areas, and a memory controller. The memory controller controls the memory device to perform a memory operation on an original storage area of the plurality of logical storage areas according to a request of a host, and to perform a mirroring operation of copying the memory operation which was performed on the original storage area in a backup storage area of the plurality of logical storage areas based on whether the memory device is in an idle state.

A computer-implemented method for seamlessly performing a maintenance operation on a stateful system includes mapping a network address of the stateful system to a primary server that uses a primary database to respond to incoming data requests. In response to receiving a maintenance request, the primary database is replicated to a secondary database of a secondary server. The secondary server is updated according to the maintenance request. The method further includes caching, in a replay buffer of the primary server, incoming data requests during the replicating. After the replicating, the data requests from the replay buffer are executed by the secondary server. Write operations to the primary server are disabled during the replicating, and the network address of the stateful system is mapped to the secondary server. Subsequently, the primary server is updated and reinstated by mapping the network address, and enabling the write operations.

The present disclosure describes example service takeover methods, storage devices, and service takeover apparatuses. In one example method, when a communication fault occurs between two storage devices in a storage system, the two storage devices respectively obtain running statuses of the two storage devices. A running status can reflect current usage of one or more system resources of a particular storage device. Then, a delay duration is determined according to the running statuses, where the delay duration is a duration for which the storage device waits before sending an arbitration request to a quorum server. The two storage devices respectively send, after the delay duration, arbitration requests to the quorum server to request to take over a service. The quorum server then can select a storage device in a relatively better running status to take over a host service.

The present disclosure describes example service takeover methods, storage devices, and service takeover apparatuses. In one example method, when a communication fault occurs between two storage devices in a storage system, the two storage devices respectively obtain running statuses of the two storage devices. A running status can reflect current usage of one or more system resources of a particular storage device. Then, a delay duration is determined according to the running statuses, where the delay duration is a duration for which the storage device waits before sending an arbitration request to a quorum server. The two storage devices respectively send, after the delay duration, arbitration requests to the quorum server to request to take over a service. The quorum server then can select a storage device in a relatively better running status to take over a host service.

Techniques for using data mirroring across regions to reduce the likelihood of losing objects in a cloud object storage platform are provided. In one set of embodiments, a computer system can upload first and second copies of a data object to first and second regions of the cloud object storage platform respectively, where the first and second copies are identical. The computer system can then attempt to read the first copy of the data object from the first region. If the read attempt fails, the computer system can retrieve the second copy of the data object from the second region.

Embodiments of the disclosure provide systems and methods for enabling disaster recovery from a source cluster to a target cluster in a multi-cluster cloud-computing environment. A domain cluster configures a replicated data volume to be updated with data from a data volume of the source cluster, wherein the replicated data volume resides in the target cluster; determines that the target cluster is to replace the source cluster as an active cluster; rebuilds, in the target cluster, a new container instance to replace the container instance on the source cluster; configures the container instance to utilize the replicated data volume in the target cluster; and discontinues recognition of the data volume and container instance on the source cluster as being authoritative.

A method for synchronous replication of stream data includes receiving a stream of data blocks for storage at a first storage location associated with a first geographical region and at a second storage location associated with a second geographical region. The method also includes synchronously writing the stream of data blocks to the first storage location and to the second storage location. While synchronously writing the stream of data blocks, the method includes determining an unrecoverable failure at the second storage location. The method also includes determining a failure point in the writing of the stream of data blocks that demarcates data blocks that were successfully written and not successfully written to the second storage location. The method also includes synchronously writing, starting at the failure point, the stream of data blocks to the first storage location and to a third storage location associated with a third geographical region.

Embodiments of the disclosure provide systems and methods for enabling disaster recovery from a source cluster to a target cluster in a multi-cluster cloud-computing environment. A domain cluster configures a replicated data volume to be updated with data from a data volume of the source cluster, wherein the replicated data volume resides in the target cluster; determines that the target cluster is to replace the source cluster as an active cluster; rebuilds, in the target cluster, a new container instance to replace the container instance on the source cluster; configures the container instance to utilize the replicated data volume in the target cluster; and discontinues recognition of the data volume and container instance on the source cluster as being authoritative.

In a complex system including; one or more storage systems including a cache and a storage controller; and one or more storage boxes including a storage medium, the storage box generates redundant data from write data received from a server, and writes the write data and the redundant data to the storage medium. The storage box transmits the write data to the storage system when it is difficult to generate the redundant data or it is difficult to write the write data and the redundant data to the storage medium. The storage system stores the received write data in the cache.