Abstract: A method, article of manufacture, and apparatus for restoring data. In some embodiments, this includes determining an object to be recovered, determining a representation of the object, and requesting the representation of the object from a data resource system. In some embodiments, the representation of the object is a hash value of the object. In some embodiments, the representation of the object is a segment of the object.

Abstract: A method, article of manufacture, and apparatus for accessing data during data recovery. In some embodiments, this includes sending an I/O request from an application to an object, wherein the object is being recovered, establishing an I/O intercept, intercepting the application's I/O request with the I/O intercept, and redirecting the I/O request based on the status of the object's sub-objects.

Abstract: Locking allocated data space is disclosed. An indication is received that certain previous version data is required to be retained. A map of metadata records, each associated with a journaling process write of previous version data which write includes previous version data required to be retained, is built. In some embodiments, the map associates a write time with each record in the map. A reclamation process checks to determine whether any storage proposed to be reclaimed is included in the map of record identifiers. In some embodiments, the determination is made based at least in part on the write time associated in the map with at least a first record identifier in time-sorted order.

Abstract: Locking allocated data space is disclosed. An indication is received that certain previous version data is required to be retained. A map of metadata records, each associated with a journaling process write of previous version data which write includes previous version data required to be retained, is built. In some embodiments, the map associates a write time with each record in the map. A reclamation process checks to determine whether any storage proposed to be reclaimed is included in the map of record identifiers. In some embodiments, the determination is made based at least in part on the write time associated in the map with at least a first record identifier in time-sorted order.

Abstract: An amount of storage to reclaim is determined based at least in part on a write size of new previous version data written most recently to a data region. The determined amount of storage is reclaimed.

Abstract: An indication to allocate storage is received, where the storage is to be used to store previous version data associated with a protected data set. One or more storage groups are allocated of at least a prescribed allocation group size and comprising a set of physically contiguous storage locations.

Abstract: Locking allocated data space is disclosed. An indication is received that certain previous version data is required to be retained. A map of metadata records, each associated with a journaling process write of previous version data which write includes previous version data required to be retained, is built. In some embodiments, the map associates a write time with each record in the map. A reclamation process checks to determine whether any storage proposed to be reclaimed is included in the map of record identifiers. In some embodiments, the determination is made based at least in part on the write time associated in the map with at least a first record identifier in time-sorted order.

Abstract: Locking allocated data space is disclosed. An indication is received that certain previous version data is required to be retained. A map of metadata records, each associated with a journaling process write of previous version data which write includes previous version data required to be retained, is built. In some embodiments, the map associates a write time with each record in the map. A reclamation process checks to determine whether any storage proposed to be reclaimed is included in the map of record identifiers. In some embodiments, the determination is made based at least in part on the write time associated in the map with at least a first record identifier in time-sorted order.

Abstract: An indication to allocate storage is received, where the storage is to be used to store previous version data associated with a protected data set. One or more storage groups are allocated of at least a prescribed allocation group size and comprising a set of physically contiguous storage locations.

Abstract: An indication to allocate storage is received, where the storage is to be used to store previous version data associated with a protected data set. One or more storage groups are allocated of at least a prescribed allocation group size and comprising a set of physically contiguous storage locations.

Abstract: A first contiguous group of one or more storage locations to be virtually reclaimed is determined, where the first contiguous group is smaller than a minimum allocation group size and the storage locations are used to store previous version data. The first contiguous group is virtually reclaimed. A second contiguous group of one or more virtually reclaimed storage locations to be made available for reuse is determined, where the size of the second group is greater than or equal to the minimum allocation group size. The second contiguous group is made available for reuse.

Abstract: Previous version data is copied to a location in a collection of snapshot data, wherein the collection of snapshot data represents a state of a protected data set at a baseline time associated with a snapshot. Once the previous version data has been copied to the location in the collection of snapshot data, an index is updated to associate the location in the collection of snapshot data with the previous version data. A data region storage location from which the previous version data was copied to the location in the collection of snapshot data is making available for reuse once the index has been updated.

Abstract: An amount of storage to reclaim is determined based at least in part on a write size of new previous version data written most recently to a data region. The determined amount of storage is reclaimed.

Abstract: An amount of storage to reclaim is determined based at least in part on a write size of new previous version data written most recently to a data region. The determined amount of storage is reclaimed.