Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot and finalizes and performs garbage collection with respect to segments allocated to the previous snapshot. Subsequent write requests to the storage volume are then performed on the segments allocated to the new snapshot. An orchestration layer implements a multi-role application that is provisioned with virtualized storage and computation resources. A snapshot of the application may be created and used to rollback or clone the application. Clone snapshots of storage volumes may be gradually populated with data from prior snapshots to reduce loading on a primary snapshot.

Abstract: A bundled application includes a plurality of entities such as logical storage volumes, application instances, pods, clusters, and computing nodes that are dependent on one another. Dependencies of the bundled application on individual entities is determined and quantified. Impact of failure of an entity may be determined using the dependencies. Dependency may be determined with reference to redundancy among entities. Usage of an entity by other entities and potential redistribution may be determined.

Abstract: A KUBERNETES installation processes a script and invokes a scheduling agent in response to encountering an instruction to create a pod. The scheduling agent is an agent of an orchestrator and performs tasks such as identifying a selected node, creating multiple interface objects with multiple IP addresses, and creating storage volumes in coordination with the orchestrator. Upon creation, the pod may call a CNI that is an agent of the orchestrator in order to configure the pod to use the multiple interface objects. The pod may call a CSI that is an agent of the orchestrator in order to bind a storage volume to the pod. The scheduling agent may coordinate with the orchestrator to implement affinity and anti-affinity rules for placement of pods and storage volumes. The script may also be transformed by the orchestrator in order to insert instructions implementing affinity and anti-affinity rules.

Abstract: Disclosed are methods and the like that provide for transforming replicated data for consumption in the cloud, for example. Such methods can include attaching a target gateway node at a secondary site to a storage device at the secondary site, searching for an identifier stored in the storage device, and storing replicated data in the replication volume. The identifier is associated with an offset stored in the storage device, and the offset identifies a starting location of a replication volume in the storage device. The replicated data is received by the target gateway node from a source gateway node at a primary site. A starting location is received with the replicated data. The target gateway node stores the replicated data at a first location in the storage volume, and the first location is determined based, at least in part, on the starting location and the first storage location.

Abstract: A bundled application includes a plurality of entities such as logical storage volumes, application instances, pods, clusters, and computing nodes that are dependent on one another. Dependencies of the bundled application on individual entities is determined and quantified. Impact of failure of an entity may be determined using the dependencies. Dependency may be determined with reference to redundancy among entities. Usage of an entity by other entities and potential redistribution may be determined.

Abstract: A KUBERNETES installation processes a script and invokes a scheduling agent in response to encountering an instruction to create a pod. The scheduling agent is an agent of an orchestrator and performs tasks such as identifying a selected node, creating multiple interface objects with multiple IP addresses, and creating storage volumes in coordination with the orchestrator. Upon creation, the pod may call a CNI that is an agent of the orchestrator in order to configure the pod to use the multiple interface objects. The pod may call a CSI that is an agent of the orchestrator in order to bind a storage volume to the pod. The scheduling agent may coordinate with the orchestrator to implement affinity and anti-affinity rules for placement of pods and storage volumes. The script may also be transformed by the orchestrator in order to insert instructions implementing affinity and ant-affinity rules.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot and finalizes and performs garbage collection with respect to segments allocated to the previous snapshot. Subsequent write requests to the storage volume are then performed on the segments allocated to the new snapshot. An orchestration layer implements a multi-role application that is provisioned with virtualized storage and computation resources. A snapshot of the application may be created and used to rollback or clone the application. Clone snapshots of storage volumes may be gradually populated with data from prior snapshots to reduce loading on a primary snapshot.

Abstract: Disclosed are methods and the like that provide for transforming replicated data for consumption in the cloud, for example. Such methods can include attaching a target gateway node at a secondary site to a storage device at the secondary site, searching for an identifier stored in the storage device, and storing replicated data in the replication volume. The identifier is associated with an offset stored in the storage device, and the offset identifies a starting location of a replication volume in the storage device. The replicated data is received by the target gateway node from a source gateway node at a primary site. A starting location is received with the replicated data. The target gateway node stores the replicated data at a first location in the storage volume, and the first location is determined based, at least in part, on the starting location and the first storage location.

Abstract: Presented herein is functionality for using a recovery computing system to perform a failover where the recovery computing system is communicatively coupled to a homogeneous and/or heterogeneous primary computing system. In one embodiment, this functionality allows the recovery computing system to disconnect a first recovery application node from a contiguous storage volume after the contiguous storage volume had been created by the first recovery application node, and to then use a recovery gateway node to store replicated data on the continguous storage volume, where the recovery gateway node and the contiguous storage volume are both coupled to the recovery computing system. In response to detecting a failure on the primary computing system, performing a failover to the recovery computing system, where performing the failover comprises attaching the contiguous storage volume to a second recovery application node and bringing the second recovery application node online.

Abstract: A new snapshot of a storage volume is created by suppressing write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot. Subsequent write requests to the storage volume are then performed on the segments allocated to the new snapshot. An orchestration layer implements a bundled application that is provisioned with storage volumes and containers. A snapshot of the application may be created and used to rollback or clone the application. The amount of processing cores, memory, and containers may be increased or decreased based on usage. Amount of storage allocated to a storage volume may be augmented by a snapshot reservation ratio. The snapshot reservation ratio is adjusted over time according to usage.

Abstract: A new snapshot of a storage volume is created by suppressing write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot. Subsequent write requests to the storage volume are then performed on the segments allocated to the new snapshot. An orchestration layer implements a bundled application that is provisioned with storage volumes and containers. A snapshot of the application may be created and used to rollback or clone the application. The amount of processing cores, memory, and containers may be increased or decreased based on usage. Amount of storage allocated to a storage volume may be augmented by a snapshot reservation ratio. The snapshot reservation ratio is adjusted over time according to usage.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot and finalizes and performs garbage collection with respect to segments allocated to the previous snapshot. An orchestration layer implements a multi-role application that is provisioned with virtualized storage and computation resources. A snapshot of the application may be created and used to rollback or clone the application. Containers may be loaded with data structures for encrypted and/or authenticated communication. Failed storage volumes may be detected and repaired. Repopulating repaired volumes may be managed by an application or a storage manager implementing a virtualized storage system. An autopilot invokes repair of failed containers and storage nodes in response to detected failures.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. A snapshot of the application may be created and used to rollback or clone the application. Clones snapshots of storage volumes may be gradually populated with data from prior snapshots to reduce loading on a primary snapshot. Components of cloned applications may communicate with one another using addresses of these components in the parent application. Changes to application state may be written to a remote storage volume that may be mounted to a new instance or clone of the application to recreate its state. Jobs to create and execute a bundled application may be referenced with a simulated file system that generates reads to hosts only when the job log file is actually read. Storage nodes may implement interfaces to a SAN or cloud storage system.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot and finalizes and performs garbage collection with respect to segments allocated to the previous snapshot. An orchestration layer implements a multi-role application that is provisioned with virtualized storage and computation resources. A snapshot of the application may be created and used to rollback or clone the application. Containers may be loaded with data structures for encrypted and/or authenticated communication. Failed storage volumes may be detected and repaired. Repopulating repaired volumes may be managed by an application or a storage manager implementing a virtualized storage system. An autopilot invokes repair of failed containers and storage nodes in response to detected failures.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot and finalizes and performs garbage collection with respect to segments allocated to the previous snapshot. Subsequent write requests to the storage volume are then performed on the segments allocated to the new snapshot. An orchestration layer implements a multi-role application that is provisioned with virtualized storage and computation resources. A snapshot of the application may be created and used to rollback or clone the application. Clones snapshots of storage volumes may be gradually populated with data from prior snapshots to reduce loading on a primary snapshot.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. A snapshot of the application may be created and used to rollback or clone the application. Clones snapshots of storage volumes may be gradually populated with data from prior snapshots to reduce loading on a primary snapshot. Components of cloned applications may communicate with one another using addresses of these components in the parent application. Changes to application state may be written to a remote storage volume that may be mounted to a new instance or clone of the application to recreate its state. Jobs to create and execute a bundled application may be referenced with a simulated file system that generates reads to hosts only when the job log file is actually read. Storage nodes may implement interfaces to a SAN or cloud storage system.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot and finalizes and performs garbage collection with respect to segments allocated to the previous snapshot. Subsequent write requests to the storage volume are then performed on the segments allocated to the new snapshot. An orchestration layer implements a multi-role application that is provisioned with virtualized storage and computation resources. A snapshot of the application may be created and used to rollback or clone the application. Clones snapshots of storage volumes may be gradually populated with data from prior snapshots to reduce loading on a primary snapshot.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. A snapshot of the application may be created and used to rollback or clone the application. Clones snapshots of storage volumes may be gradually populated with data from prior snapshots to reduce loading on a primary snapshot. Components of cloned applications may communicate with one another using addresses of these components in the parent application. Changes to application state may be written to a remote storage volume that may be mounted to a new instance or clone of the application to recreate its state. Jobs to create and execute a bundled application may be referenced with a simulated file system that generates reads to hosts only when the job log file is actually read. Storage nodes may implement interfaces to a SAN or cloud storage system.

Abstract: A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot and finalizes and performs garbage collection with respect to segments allocated to the previous snapshot. Subsequent write requests to the storage volume are then performed on the segments allocated to the new snapshot. An orchestration layer implements a multi-role application that is provisioned with virtualized storage and computation resources. A snapshot of the application may be created and used to rollback or clone the application. Clones snapshots of storage volumes may be gradually populated with data from prior snapshots to reduce loading on a primary snapshot.

Abstract: Various systems, methods and apparatuses for replicating data from homogeneous and/or heterogeneous primary computing systems to a single recovery computing system are presented. In one embodiment, the methods, systems and apparatuses described herein allow a computing system to receive information from a remote computing system, where the information contains at least data and a logical storage location corresponding to the location of the data in a logical storage unit of the remote computing system. Upon receiving the data and associated logical storage location, the methods, systems and apparatuses described herein can store the information at a specific location in a storage device such as, for example, a block storage device. The specific location can be determined, for example, based on the logical storage location provided by the remote computing system and an offset associated with the starting location of the relevant logical storage unit on the storage device.