Examples perform live migration of VMs from a source host to a destination host using destructive consistency breaking operations. The disclosure makes a record of a consistency group of VMs on storage at a source host as a fail-back in the event of failure. The source VMs are live migrated to the destination host, disregarding consistency during live migration, and potentially violating the recovery point objective. After live migration of all of the source VMs, consistency is automatically restored at the destination host and the live migration is declared a success.

Technologies for fast distributed storage recovery include a distributed storage system that includes multiple controller nodes and multiple target nodes. Each controller node is coupled to a corresponding target node via a storage fabric. Each target node stores replica data. The system identifies a failed node and a corresponding node that was coupled to the failed node. If the failed node is a controller node, the corresponding node is a target node. If the failed node is a target node, the corresponding node is a controller node. The system instantiates a replacement node, adds the replacement node to the system, and couples the replacement node to the corresponding node. The system may direct a backup target node to copy replica data to the replacement target node via the storage fabric. Other embodiments are described and claimed.

Disclosed are systems and methods of synchronization between a source and a target. The synchronization relationship can be quickly and easily be created for disaster recovery, real-time backup and failover, thereby ensuring that data on the source is fully-protected at an off-site location or on another server or VM, for example, at another data center, a different building or elsewhere in the cloud. Common snapshots available on both the source and target can act as common recovery points. The common recovery points can be used to locate the most recent snapshot in common, between the source and target, to enable a delta sync of all subsequently written data at the source to the target after an offline event.

Availability against hardware failure and availability against maintenance are implemented without using dedicated systems. A system is provided, including: a first host computer to execute a first virtual machine for running a first application; and a second host computer to execute a second virtual machine for running a second application, wherein in a redundant operation mode, the second host computer mirrors an executable image of the first virtual machine to an executable image of the second virtual machine while stopping the execution of the second virtual machine, and in a multi-operation mode, the second host computer mirrors an internal state of the first application to an internal state of the second application while executing the second virtual machine in parallel with the first virtual machine.

An apparatus comprises at least one processing device comprising a processor coupled to a memory; the at least one processing device being configured to: obtain a set of rebuild rate parameters for a given storage device from a storage array comprising a plurality of storage devices; and dynamically regulate a rebuild rate associated with a rebuild process for the given storage device based on the set of rebuild rate parameters obtained from the storage array for the given storage device. For example, the set of rebuild rate parameters include a rebuild capacity parameter and a rebuild time parameter.

A method of controlling resynchronization of a source database and a target database may comprise detecting that a connection between the source database and the target database has been restored. Based on the detecting, the method may also comprise identifying a first edit flag for a first row in a first table on the source database. Based on the identifying, the method may also comprise sending the first row from the source database to the target database. Based on the sending, the method may also comprise clearing the first edit flag for the first row.

One or more techniques and/or computing devices are provided for utilizing snapshots for data integrity validation and/or faster application recovery. For example, a first storage controller, hosting first storage, has a synchronous replication relationship with a second storage controller hosting second storage. A snapshot replication policy rule is defined to specify that a replication label is to be used for snapshot create requests, targeting the first storage, that are to be replicated to the second storage. A snapshot creation policy is created to issue snapshot create requests comprising the replication label. Thus a snapshot of the first storage and a replication snapshot of the second storage are created based upon a snapshot create request comprising the replication label. The snapshot and the replication snapshot may be compared for data integrity validation (e.g., determine whether the snapshots comprise the same data) and/or quickly recovering an application after a disaster.

A containerized environment and application that are configured for component specific continuous replication and granular application level application. A key value store, which stores key values related to configuration data of the containerized application, is replicated continuously to a replicated key value store at a replica site. Persistent volumes may also be replicated to a replica site. The replication can be performed to multiple replica sites in an application specific manner.

One or more techniques and/or systems are provided for identifying configuration inconsistencies between storage virtual machines across storage clusters. For example, a first storage cluster and a second storage cluster may be configured according to a disaster recovery relationship where user data and configuration data of the first storage cluster are replicated to the second storage cluster so that the second storage cluster can takeover for the first storage cluster in the event a disaster occurs at the first storage cluster. Because replication of configuration data (e.g., a name and size of a volume, a backup policy, etc.) may fail for various reasons, configuration of the first storage cluster is compared to configuration of the second storage cluster to identify a configuration difference (e.g., a new size of the volume at the first storage cluster may have failed to be replicated to a replicated volume at the second storage cluster).

A method for resynchronizing data repositories in a high availability storage environment includes maintaining, in a first gateway server, a first journal that records operations that are performed for a first set of objects. The method further maintains, in a second gateway server, a second journal that records operations that are performed for a second set of objects. The method communicates, from the first gateway server to the second gateway server, any operations that are performed by the first gateway server for objects in the second set, so that these operations may be recorded in the second journal. The method further communicates, from the second gateway server to the first gateway server, any operations that are performed by the second gateway server for objects in the first set, so that these operations may be recorded in the first journal. A corresponding system and computer program product are also disclosed.