Abstract: In accordance with some aspects of the present disclosure, a non-transitory computer readable medium is disclosed. In some embodiments, the non-transitory computer readable medium includes instructions that, when executed by a processor, cause the processor to receive, from a workload hosted on a host of a cluster, first I/O traffic programmed according to a first I/O traffic protocol supported by a cluster-wide storage fabric exposed to the workload as being hosted on the same host. In some embodiments, the workload is recovered by a hypervisor hosted on the same host. In some embodiments, the non-transitory computer readable medium includes the instructions that, when executed by the processor, cause the processor to adapt the first I/O traffic to generate second I/O traffic programmed according to a second I/O traffic protocol supported by a repository external to the storage fabric and forward the second I/O traffic to the repository.

Abstract: In accordance with some aspects of the present disclosure, a non-transitory computer readable medium is disclosed. In some embodiments, the non-transitory computer readable medium includes instructions that, when executed by a processor, cause the processor to receive, from a workload hosted on a host of a cluster, first I/O traffic programmed according to a first I/O traffic protocol supported by a cluster-wide storage fabric exposed to the workload as being hosted on the same host. In some embodiments, the workload is recovered by a hypervisor hosted on the same host. In some embodiments, the non-transitory computer readable medium includes the instructions that, when executed by the processor, cause the processor to adapt the first I/O traffic to generate second I/O traffic programmed according to a second I/O traffic protocol supported by a repository external to the storage fabric and forward the second I/O traffic to the repository.

Abstract: A technique improves storage efficiency of an object store configured to maintain numerous snapshots for long-term storage in an archival storage system by efficiently determining data that is exclusively owned by an expiring snapshot to allow deletion of the expiring snapshot from the object store. The technique involves managing index data structures to enable efficient garbage collection across a very large number of data objects. When a snapshot expires, the technique obviates the need to scan the numerous snapshot data objects to determine which index structures are no longer needed and can be reclaimed (garbage collected). The technique is directed to management of underlying storage based on different sets of policies. When certain snapshots expire and are ready for deletion, the technique is directed to finding those data blocks that are no longer referenced (used) by any valid snapshots.

Abstract: A technique improves storage efficiency of an object store configured to maintain numerous snapshots for long-term storage in an archival storage system by efficiently determining data that is exclusively owned by an expiring snapshot to allow deletion of the expiring snapshot from the object store. The technique involves managing index data structures to enable efficient garbage collection across a very large number of data objects. When a snapshot expires, the technique obviates the need to scan the numerous snapshot data objects to determine which index structures are no longer needed and can be reclaimed (garbage collected). The technique is directed to management of underlying storage based on different sets of policies. When certain snapshots expire and are ready for deletion, the technique is directed to finding those data blocks that are no longer referenced (used) by any valid snapshots.

Abstract: An indexing technique provides an index data structure for efficient retrieval of a snapshot from a long-term storage service (LTSS) of an archival storage system. The snapshot is generated from typed data of a logical entity, such as a virtual disk (vdisk). The data of the snapshot is replicated to a frontend data service of the LTSS sequentially and organized as one or more data objects for storage by a backend data service of LTSS in an object store of the archival storage system. Metadata associated with the snapshot (i.e., snapshot metadata) is recorded as a log and persistently stored on storage media local to the frontend data service. The snapshot metadata includes information describing the snapshot data, e.g., a logical offset range of a snapshot of the vdisk and, thus, is used to construct the index data structure. Notably, construction of the index data structure is deferred until after the entirety of the snapshot data has been replicated and received by the frontend data service.

Abstract: In accordance with some aspects of the present disclosure, a non-transitory computer readable medium is disclosed. In some embodiments, the non-transitory computer readable medium includes instructions that, when executed by a processor, cause the processor to receive, from a workload hosted on a host of a cluster, first I/O traffic programmed according to a first I/O traffic protocol supported by a cluster-wide storage fabric exposed to the workload as being hosted on the same host. In some embodiments, the workload is recovered by a hypervisor hosted on the same host. In some embodiments, the non-transitory computer readable medium includes the instructions that, when executed by the processor, cause the processor to adapt the first I/O traffic to generate second I/O traffic programmed according to a second I/O traffic protocol supported by a repository external to the storage fabric and forward the second I/O traffic to the repository.

Abstract: A method embodiment serves to manage entity names for virtualized entities in a computing system comprising two or more computing nodes that host virtual machines and other virtual entities. The method commences upon receiving a request for identifiers. The request includes an identifier key that is used by a name generator. The name generator implements a deterministic algorithm that will always return the same outputs given the same inputs. The name generator generates a user- or program-specified number of virtualized entity identifiers based on the identifier key. The generated virtualized entity identifiers and corresponding identifier keys are stored in an identifier mapping table that is accessible by the two or more computing nodes. The identifier mapping table describes relationships between the virtualized entity identifiers and corresponding identifier keys. The virtualized entity identifiers are used to create respective virtualized entities.

Abstract: A method embodiment serves to manage entity names for virtualized entities in a computing system comprising two or more computing nodes that host virtual machines and other virtual entities. The method commences upon receiving a request for identifiers. The request includes an identifier key that is used by a name generator. The name generator implements a deterministic algorithm that will always return the same outputs given the same inputs. The name generator generates a user- or program-specified number of virtualized entity identifiers based on the identifier key. The generated virtualized entity identifiers and corresponding identifier keys are stored in an identifier mapping table that is accessible by the two or more computing nodes. The identifier mapping table describes relationships between the virtualized entity identifiers and corresponding identifier keys. The virtualized entity identifiers are used to create respective virtualized entities.

Abstract: A system for managing storage devices, includes a plurality of nodes that implement a virtualization environment, each node of the plurality of nodes comprising a hypervisor, a service virtual machine that sits above the hypervisor, and one or more user virtual machines that sit above the hypervisor; a plurality of storage devices that are accessed by the user virtual machines via the service virtual machines, wherein a first node of the plurality of nodes comprises a first hypervisor, a first service virtual machine and a first set of one or more user virtual machines, wherein a second node of the plurality of nodes comprises a second hypervisor, a second service virtual machine and a second set of one or more user virtual machines, wherein the first hypervisor and the second hypervisor are of different types, and wherein the first virtual machine and the second service virtual machine are of the same type.