Certain embodiments described herein relate to an improved block-level replication system. One or more components in an information management system may receive a request to perform a block-level replication between a source storage device and a destination storage device, and depending on the specific replication mode requested, (i) store block-level changes directly to the destination storage device or (ii) first to a recovery point store and then later to the destination storage device.

A storage manager for an information management system determines whether one or more predetermined conditions have been met for transferring metadata of previously performed backup jobs stored in a first management database. A backup job may correspond to a backup operation of a primary storage device of a first client computing device. In response to a determination that one or more of the predetermined conditions have been met, the storage manager may transfer metadata for a second plurality of backup jobs to a second management database of a recovery manager. The recovery manager may receive a request to restore data to the primary storage device of the first client computing device based on the metadata of the second plurality of backup jobs. A media agent managed by the recovery manager may then restore the requested data to the primary storage device of the first client computing device.

The present disclosure provides a cleaning and recovery method and device for a heterogeneous executor in a mimic switch, and a mimic switch, the method includes: a mimic scheduler determining a designated heterogeneous executor that needs to be cleaned, marking the designated heterogeneous executor that needs to be cleaned as in a cleaning state, and sending a cleaning instruction to the designated heterogeneous executor; the designated heterogeneous executor sending a normal protocol negotiation message to the mimic scheduler to try to interact with the mimic scheduler; the mimic scheduler receiving the protocol negotiation message and detecting whether the designated heterogeneous executor is in the cleaning state; if in the cleaning state, the mimic scheduler; constructing a training message, and sending the training message to the designated heterogeneous executor for protocol training; repeating sending and processing the protocol negotiation message until the designated heterogeneous executor is in a normal state.

A distributed database system, a data disaster backup exercise method and a non-transitory computer-readable storage medium are disclosed. The distributed database system may include a local computer room (110) and an offsite computer room (120), where the local computer room (110) includes a local management node (111) and a local database cluster (112), the offsite computer room (120) includes an offsite management node (121), an offsite exercise database cluster (123) and an offsite synchronization database cluster (122); where the local database cluster (112) and the offsite synchronization database cluster (122) are both connected with the local management node (111); the offsite exercise database cluster (123) is configured for: establishing a first connection with the offsite management node (121); and receiving a test service sent by a service layer.

Disclosed are techniques for coordinating distributed backup data protection sites for alternating recording of point in time copies. For a monitored volume, or pool of monitored volumes, periodic point in time copies are recorded upon data storage capabilities of rotating backup data storage sites as each period elapses. Upon recording a point in time copy at a given backup data storage site, the given site broadcasts to other sites metadata about the point in time copies recorded by each of the backup data storage sites for the monitored volume. As subsequent periods elapse, a rotation of sites are cycled through for selection to record point in time copies for the given period such that point in time copies of the monitored volume are recorded across multiple backup data storage sites, with each backup data storage site recording point in time copies of the monitored volume snapshotted to different times.

Maintaining a synchronous replication relationship between two or more storage systems, including: receiving, by at least one of a plurality of storage systems across which a dataset will be synchronously replicated, timing information for at least one of the plurality of storage systems; and establishing, based on the timing information, a synchronous replication lease describing a period of time during which the synchronous replication relationship is valid, wherein a request to modify the dataset may only be acknowledged after a copy of the dataset has been modified on each of the storage systems.

Replication of a filesystem or a mount point or share may replicate all data that it consists of irrespective of where the data is stored. Replication protects data irrespective of location. One method is to replicate the filesystem namespace as is while skipping the data outside of the appliance/machine so that replication cost and time are reasonable. The data outside of the machine, like cloud/tape data is protected differently. One example method includes a data protection operation configured to replication a namespace associated with multiple data tiers. During replication, data from one of the tiers is skipped while all of the namespace metadata is replicated. The recovery restores the namespace metadata and the data that was replicated from the other tier. This may be performed in connection with cyber security, for example when replicating multi-tier data to a vault.

An illustrative method includes accessing, by a controller operating within a global control plane, a recovery policy that specifies parameters for generating recovery data associated with one or more resources of a first cluster comprising a first one or more containers, wherein the first cluster comprises a first local control plane separate from the global control plane; determining, by the controller and based on the recovery policy, a second cluster comprising a second one or more containers, wherein the second cluster comprises a second local control plane separate from the global control plane; and generating, by the controller and with respect to the second cluster, the recovery data associated with the one or more resources of the first cluster.

A data management platform may receive, from a user of a data management platform, a first job request to perform a backup of data from a data source to a database managed by the user. In some examples, the database may be configured as a set of database instances running on a set of computing nodes of a computing cluster. The data management platform may store a backup load indication that indicates which computing node is assigned to perform the backup of the data based on receiving the first job request. The data management platform may receive one or more second job requests subsequent to receiving the first job request and may determine a backup load for one or more computing nodes of the set of computing nodes. The data management platform may then assign one or more target computing nodes for performing the one or more second job requests.

Replicated instances in a database environment provide for automatic failover and recovery. A monitoring component can periodically communicate with a primary and a secondary replica for an instance, with each capable of residing in a separate data zone or geographic location to provide a level of reliability and availability. A database running on the primary instance can have information synchronously replicated to the secondary replica at a block level, such that the primary and secondary replicas are in sync. In the event that the monitoring component is not able to communicate with one of the replicas, the monitoring component can attempt to determine whether those replicas can communicate with each other, as well as whether the replicas have the same data generation version. Depending on the state information, the monitoring component can automatically perform a recovery operation, such as to failover to the secondary replica or perform secondary replica recovery.