Abstract: File system data that was backed up from a source system to a storage system is determined to be archived. The storage system maintains a tree data structure that enables the backed up file system data to be located. A portion of the tree data structure and the file system data are serialized into a first flat set of data. A first data block associated with the first flat set of data includes a file offset to a first data block associated with a second flat set of data corresponding to a previous archive of the file system data. The first flat set of data is archived to an archival storage.

Abstract: A backup of a current state of a storage is determined to be initiated. A previous state of the storage storing key-object entries is analyzed to identify parallelization partition identifiers. At least a portion of the partition identifiers is used as boundaries between subgroups of the key-object entries processed in parallel to perform the backup of the current state of the storage.

Abstract: A request to obtain an identified content item is received. It is determined that the identified content item is stored in a plurality of locations. It is determined to obtain the identified content item from a first storage location storing a first serialized representation of a file system snapshot that includes the identified content item and a second storage location storing a second serialized representation of the file system snapshot that includes the identified content item based on available resources associated with the plurality of locations. The identified content item is extracted from the first serialized representation at the first storage location and from the second serialized representation at the second storage location including building a stubbed tree data structure using the first serialized representation and the second serialized representation. The extracted identified content item is provided using the stubbed tree data structure.

Abstract: A specification of content to be stored in a cloud storage is received at a client-side component. A first portion of the content is divided into a plurality of data chunks. One or more data chunks of the plurality of data chunks that are to be sent via a network to be stored in the cloud storage are identified. It is determined whether a batch size of the one or more identified data chunks does not meets a threshold size. One or more data chunks of a second portion of the content that are to be stored in the cloud storage are identified. It is determined that a size of a second batch of data chunks that includes the one or more identified data chunks of the first portion of the content and the one or more identified data chunks of the second portion of the content does not meet the threshold size. It is determined that a batch period is greater than or equal to a batch threshold period. The second batch of data chunks is written to a storage of a cloud server included in a data plane.

Abstract: A backup of a current state of a storage is determined to be initiated. A previous state of the storage storing key-object entries is analyzed to identify parallelization partition identifiers. At least a portion of the partition identifiers is used as boundaries between subgroups of the key-object entries processed in parallel to perform the backup of the current state of the storage.

Abstract: At least a portion of data of a tree data structure is serialized into a first set of flat data. At least a portion of a structure of the tree data structure is serialized to reproduce at least the portion of the structure in a second set of flat data. It is determined to access a desired data of the tree data structure from an archive. The second set of flat data is read to reconstitute at least the portion of a structure of the tree data structure. The reconstituted structure of the tree data structure is used to determine a data offset associated with the first set of flat data, wherein the data offset corresponds to the desired data. The desired data is accessed using the data offset associated with the first set of flat data.

Abstract: A request to access one or more files associated with a particular pint in time that are archived at a cloud storage is received. A file system metadata tree data structure based on metadata associated with the one or more requested files that is obtained from the cloud storage is partially restored at a storage system. The partially restored file system metadata tree data structure includes one or more stub nodes associated with one or more non-requested files. Access to the one or more requested files is provided using the partially restored file system metadata tree data structure. Metadata associated with the one or more non-requested files is prefetch from the cloud storage. A portion of the file system metadata tree data structure corresponding to the one or more non-requested files is restored in part by replacing the one or more stub nodes associated with the one or more non-requested files with metadata corresponding to the one or more non-requested files.

Abstract: An instruction to generate a cloud instantiation of a secondary storage system is provided. One or more secondary storage clusters are virtually rebuilt in the cloud instantiation of the secondary storage system. A new cloud instance of a user virtual machine is deployed based on at least a portion of data stored in the one or more rebuilt secondary storage clusters of the cloud instantiation of the secondary storage system. A version of at least the portion of the data of the one or more rebuilt secondary storage clusters is provided to a cloud deployment server.

Abstract: A specification of content to be stored in a cloud storage is received at a client-side component. A portion of the content is divided into a plurality of data chunks. One or more data chunks of the plurality of data chunks that are to be sent via a network to be stored in the cloud storage are identified. It is determined whether a batch size of the one or more identified data chunks meets a threshold size. Based on the determination of whether the batch size meets the threshold size, a cloud storage destination among a plurality of different cloud storage destinations associated with different performance tiers is selected.

Abstract: An archival storage of data backed up from a repository storage of a primary storage is maintained. Access to data stored in archival storage is limited by one or more access policies based on whether a corresponding data restore has been authorized. A request for specific data stored in the archival storage is received. The one or more access policies are automatically managed based on status and timing of one or more data restore authorizations for the specific data stored in the archival storage.

Abstract: It is determined that an expiration date for an object associated with a first archive that includes a chunk object that includes a plurality of data chunks has expired. The first archive is stored in a first cloud performance storage class according to an archive tiering policy. It is determined that the archive tiering policy indicates migrating the plurality of data chunks included in the chunk object from the first cloud performance storage class to a second cloud performance storage class. In response to determining that the archive tiering policy indicates migrating the plurality of data chunks included in the chunk object from the first cloud performance storage class to the second cloud performance storage class, the plurality of data chunks included in the chunk object are migrated from the first cloud performance storage class to the second cloud performance storage class.

Abstract: A list of one or more archives available to be restored is provided to an authenticated user. The list of one or more archives available to be restored is based in part on a credential provided by the authenticated user. The credential provided by the user is linked to a subset of a plurality of snapshot archives associated with an enterprise. A selection of one of the one or more archives and an external target for the selected archive is received. A cloud instantiation of a secondary storage system is utilized to reconstitute a tree data structure based on serialized data included in the selected archive. A request to restore data associated with the selected archive to the external target is received. The requested data associated with the archive is provided to the external target.

Abstract: A cloud server component determines that a size of a first cloud storage element object is at least below a first threshold. In response to the first determination, a client-side component is requested to store additional data in the cloud storage element object including by having the client-side component update the first cloud storage element with an updated version that includes previously existing data of the first cloud storage element and the additional data. The first cloud storage element object is added to a set of one or more cloud storage element objects available for update. The client-side component is configured to generate an updated version of the first cloud storage element object that has a size that is greater than or equal to the first threshold.

Abstract: A first archive of a first snapshot of a source storage is caused to be stored to a remote storage. At least a portion of content of the first archive is stored in data chunks stored in a first chunk object of the remote storage and the first archive is associated with a first data policy. A second archive of a second snapshot of the source storage is caused to be stored to the remote storage. At least a portion of content of the second archive is referenced from data chunks stored in the first chunk object and the second archive is associated with a second data policy. Policy compliance of the chunk object storing data chunks referenced by the first archive and the second archive that are different is automatically managed based on the first data policy and the second data policy that are different.

Abstract: An instruction to generate a cloud instantiation of a secondary storage system is provided. One or more secondary storage clusters are virtually rebuilt in the cloud instantiation of the secondary storage system. A new cloud instance of a user virtual machine is deployed based on at least a portion of data stored in the one or more rebuilt secondary storage clusters of the cloud instantiation of the secondary storage system. A version of at least the portion of the data of the one or more rebuilt secondary storage clusters is provided to a cloud deployment server.

Abstract: A cloud server determines that a size of a first cloud storage element object is at least below a first threshold. In response to the first determination, a client-side component is requested to store additional data in the cloud storage element object including by having the client-side component update the first cloud storage element with an updated version that includes previously existing data of the first cloud storage element and the additional data. The first cloud storage element object is added to a set of one or more cloud storage element objects available for update. The client-side component is configured to generate an updated version of the first cloud storage element object that has a size that is greater than or equal to the first threshold.

Abstract: An indication to store to a remote storage a new archive of a snapshot of a source storage is received. At least one shared data chunk of the new archive is determined to be already stored in an existing chunk object of the remote storage storing data chunks of a previous archive. One or more evaluation metrics for the existing chunk object are determined based at least in part on a retention period associated with one or more individual chunks stored in the chunk object and a data lock period associated with the entire existing chunk object. It is determined based on the one or more evaluation metrics whether to reference the at least one shared data chunk of the new archive from the existing chunk object or store the at least one shared data chunk in a new chunk object of the remote storage.

Abstract: A first archive of a first snapshot of a source storage is caused to be stored to a remote storage. At least a portion of content of the first archive is stored in data chunks stored in a first chunk object of the remote storage and the first archive is associated with a first data policy. A second archive of a second snapshot of the source storage is caused to be stored to the remote storage. At least a portion of content of the second archive is referenced from data chunks stored in the first chunk object and the second archive is associated with a second data policy. Policy compliance of the chunk object storing data chunks referenced by the first archive and the second archive that are different is automatically managed based on the first data policy and the second data policy that are different.

Abstract: An instruction to generate a cloud instantiation of a secondary storage system is provided. One or more secondary storage clusters are virtually rebuilt in the cloud instantiation of the secondary storage system. A new cloud instance of a user virtual machine is deployed based on at least a portion of data stored in the one or more rebuilt secondary storage clusters of the cloud instantiation of the secondary storage system. A version of at least the portion of the data of the one or more rebuilt secondary storage clusters is provided to a cloud deployment server.

Abstract: A request to access one or more files associated with a particular pint in time that are archived at a cloud storage is received. A file system metadata tree data structure based on metadata associated with the one or more requested files that is obtained from the cloud storage is partially restored at a storage system. The partially restored file system metadata tree data structure includes one or more stub nodes associated with one or more non-requested files. Access to the one or more requested files is provided using the partially restored file system metadata tree data structure. Metadata associated with the one or more non-requested files is prefetch from the cloud storage. A portion of the file system metadata tree data structure corresponding to the one or more non-requested files is restored in part by replacing the one or more stub nodes associated with the one or more non-requested files with metadata corresponding to the one or more non-requested files.