Systems and methods for performing data protection operations including replication management or data copy operations. Agent-less data protections are performed. A management server is configured to perform data operations on a production host without installing an agent on the production host. A driver is adapted to aid in performing the data protection operations and communications between the management server and the driver such as commands are achieved via a storage array.

Techniques are described for providing managed computer networks, such as for managed virtual computer networks overlaid on one or more other underlying computer networks. In some situations, the techniques include facilitating replication of a primary computing node that is actively participating in a managed computer network, such as by maintaining one or more other computing nodes in the managed computer network as replicas, and using such replica computing nodes in various manners. For example, a particular managed virtual computer network may span multiple broadcast domains of an underlying computer network, and a particular primary computing node and a corresponding remote replica computing node of the managed virtual computer network may be implemented in distinct broadcast domains of the underlying computer network, with the replica computing node being used to transparently replace the primary computing node in the virtual computer network if the primary computing node becomes unavailable.

A Disaster Recovery (DR) verification process or system verifies readiness to execute a Disaster Recovery (DR) test. Such DR verification is automatically provided on a regular basis, with minimum impact on both a production and recovery environment. However, DR verification is only enabled at a time when no disaster recovery or DR testing of other sites is already under way. Configuration data needed for DR verification is constantly replicated from production to recovery, by dedicated data movers. DR verification allocates and configures recovery resources in an encapsulated environment, confirms successful their instantiation (such as boot up and network connections), and reports the outcome.

An embodiment includes deriving usage data associated with records of a database by monitoring requests to perform read operations on the records of the database. The embodiment generates record correlation data representative of correlations between respective groups of records of the database by parsing the usage data associated with the records of the database. The embodiment stores a plurality of records received as respective write requests during a first time interval in an intermediate storage medium. The embodiment identifies a correlation in the record correlation data between a first record of the plurality of records and a second record of the plurality of records. The embodiment selects, responsive to identifying the correlation, a first location in the database for writing the first record and a second location in the database for writing the second record based on a proximity of the first location to the second location.

Example embodiments relate generally to systems and methods for continuous data protection (CDP) and more specifically to an input and output (I/O) filtering framework and log management system to seek a near-zero recovery point objective (RPO).

Techniques are provided for metadata management for enabling automated switchover. An initial quorum vote may be performed before a node executes an operation associated with metadata comprising operational information and switchover information. After the initial quorum vote is performed, the node executes the operation upon one or more mailbox storage devices. Once the operation has executed, a final quorum vote is performed. The final quorum vote and the initial quorum vote are compared to determine whether the operation is to be designated as successful or failed, and whether any additional actions are to be performed.

Systems and methods are disclosed herein that enable Time Sensitive Networking (TSN) network or Deterministic Networking (DetNet) network replication function fallback. In some embodiments, a method comprises, at a primary replication function, obtaining a packet in a particular stream, obtaining a sequence number for the packet, generating M copies of the packet each comprising the sequence number, transmitting the M copies, and providing, to a redundancy controller, the sequence number or a next sequence number of a next packet to be transmitted for the particular stream. The method further comprises, at the redundancy controller, receiving the sequence number or the next sequence number and providing the sequence number or the next sequence number to a secondary replication function. The method further comprises, at the secondary replication function, receiving the sequence number or the next sequence number and configuring a sequence generation function with the next sequence number.

In one embodiment, an apparatus comprises a source system comprising a processing device coupled to memory. The processing device is configured to obtain an IO operation corresponding to an address of the source system. The IO operation comprises first user data. The processing device is further configured to store metadata associated with the IO operation in a first journal barrier of a replication journal of the source system and to close the first journal barrier. The processing device is further configured to determine that the first user data associated with the IO operation is missing from the first journal barrier and to obtain second user data from the address. The processing device is further configured to identify an interval from the first journal barrier to a second journal barrier and to provide the first journal barrier and the interval to a destination system.

Initiating recovery actions when a dataset ceases to be synchronously replicated across a set of storage systems, including: receiving, by at least one storage system among a plurality of storage systems implementing a symmetric input/output model for a synchronously replicated dataset, a request to modify the dataset; identifying one or more operations associated with the request to modify the dataset that have not been applied to at least one storage system of the plurality of storage systems; and responsive to a system fault among the plurality of storage systems synchronously replicating the dataset, applying a recovery action based on recovery information that identifies one or more operations that have not been applied to the plurality of storage systems.

A technique creates a compact state of snapshot metadata and associated selected snapshots that are frequently used and maintained in memory of a node of a cluster to facilitate processing of workflow operations associated with a logical entity in a disaster recovery (DR) environment. The compact state represents a minimal subset of snapshot metadata that is frequently used to perform operations in accordance with the DR workflow operations. In addition, metadata associated with the progress of the DR workflow operations processed by the node is periodically consolidated within the compact state. Illustratively, the selected frequently used snapshots of the logical entity include (i) a recently created snapshot; (ii) one or more reference snapshots; (iii) a snapshot scheduled for replication; and (iv) any snapshot that is queued for a current or future-scheduled operation. The technique is also directed to a snapshot and metadata eviction policy that is configured to evict infrequently used snapshots and snapshot metadata to improve memory space consumption of the memory.