Abstract: Providing continuous replication for container management system that allows configuration of a volume as a replicated network block device (NBD) volume to an actual backend volume. The system configures a pod with an NBD container running and with the actual backend volume device attached. An NBD server intercepts all I/O data arriving to the NBD volume and a filter driver intercepts writes to the NBD volume and writes them to the actual backend volume. The intercepted I/O data is also sent to a remote replication server container with persistent and journal volumes. The data is applied to the replication volume using the journal as a recover point for recovery for any point in time.

Abstract: An overlay snap is generated by generating a snapshot of a logical storage volume, writing a data stream to the overlay snap, generating pointers indicating locations of new data written to the overlay snap, and generating null pointers for locations that do not have new data written to the overlay snap. The overlay snap comprises the pointers and the null pointers. The overlay snap may be applied to a volume to generate a current snapshot of the volume. The overlay snap may be used maintain write order fidelity during continuous data replication by creating a copy of a snapshot on a target storage device and writing new data to an overlay snap on the target storage device.

Abstract: Data protection appliances are provided for the protection of at least one virtual machine. A plurality of snapshots of at least one virtual machine are obtained. Each snapshot comprises (i) production data of the virtual machine, and (ii) a fine granularity data structure for changed data that is maintained in volatile memory and records metadata for input/output (I/O) operations corresponding to changed data. A metadata differential is generated by aggregating, for example, the fine granularity data structures for any time intervals since the prior snapshot that were flushed to a storage volume and included in the prior snapshot. The storage volume is replicated using the metadata differential. The snapshots optionally further comprise a coarse granularity bit map for changed data indicating whether corresponding blocks of data have changed.

Abstract: Dynamic memory allocation is provided using containers and overlay snaps. A first container is generated to receive a first data stream, and an associated overlay snap is generated to which the data of the first container is transmitted. In response to a storage capacity of the first container reaching a threshold, a second container is generated to receive a second data stream. A second overlay snap associated with the second container is generated, and data of the second container is transmitted to the second overlay snap.

Abstract: Providing continuous replication for container management system by automatically configuring a pod having a network block device (NBD) container maintained by an NBD server, attaching a back-end device to the NBD server as a persistent volume on a software-defined storage, intercepting input/output (I/O) communication to the NBD server to expose a volume over the NBD, intercepting writes to the exposed volume and writing them to the persistent volume; and sending the intercepted I/O communication to a journal volume and a remote replication server container which has the persistent volume attached thereto. Further identifying a pod that is intended to be replicated is identified, and encapsulating a volume that the pod is meant to write to with the NBD container so that the identified pod can interact with an NDB volume of the NBD container.

Abstract: A method, system, and computer program product for intercepting IO to a virtual machine file system by a storage based splitter, replicating, via a replication appliance, the IO to a replica of the image; the replica of the image containing a replica of the virtual machine file system, and periodically mounting the replica of the virtual machine file system to create entries for a database tracking information about the virtual machines running in the hypervisor.

Abstract: In one embodiment, a method includes intercepting a write command to write to a volume at a production site, saving data from the write command to a cache, sending metadata from the write command to a data protection appliance (DPA), writing the data to the volume, receiving a request for the data in the cache, sending the data from cache to a data protection appliance (DPA) at the production site and sending the data from the DPA to the replication site.

Abstract: In one aspect, a method includes storing a virtual machine disk in a first logical unit stored on a data store; replicating the first virtual machine disk used by a first virtual machine at a second virtual machine disk stored on a second logical unit on a cloud array storage device; storing changes to the first virtual machine disk on a journal stored on the data store; periodically rolling each virtual machine disk of virtual machines on the second logical unit to a same-point-in-time using the journal and taking a snapshot of the second logical unit at the same point-in-time and sending the snapshots to a cloud storage network.

Abstract: A method, system, and computer program product for intercepting IO to a virtual machine file system by a storage based splitter, replicating, via a replication appliance, the IO to a replica of the image; the replica of the image containing a replica of the virtual machine file system, and periodically mounting the replica of the virtual machine file system to create entries for a database tracking information about the virtual machines running in the hypervisor.

Abstract: A method, system, and computer program product for intercepting IO to a virtual machine file system by a storage based splitter, replicating, via a replication appliance, the IO to a replica of the image; the replica of the image containing a replica of the virtual machine file system, and periodically mounting the replica of the virtual machine file system to create entries for a database tracking information about the virtual machines running in the hypervisor.