Abstract: One example method includes copying selected backup data from a secondary storage system to a provisioned primary storage volume, creating a snapshot of the primary storage volume, using the snapshot to create a thin clone volume, masking the thin clone volume, and mounting the thin clone volume, and recovering the backup data from the thin clone volume. The recovered backup data may be made available to a secondary workload that includes an enterprise application.

Abstract: A method for managing file based backups (FBBs) includes obtaining, by a FBB metadata file manager and by an application, a file request for a file stored in a FBB, wherein the FBB is stored in a backup storage system, identifying, using a FBB metadata file of the FBB, a storage location of the file, initiating generation of a temporary storage device, storing a copy of the file in the temporary storage device using the storage location and the FBB, and initiating, after the storing, access to the copy of the file for the application.

Abstract: One example method includes performing delta operations to protect data. During a delta operation, a primary map and a secondary map are processed using bit logic. The bit logic determines how to handle data stored at a location on the volume associated with an entry in the primary map and included in the current delta operation when a new write for the same location is received as the corresponding entry in the primary map is processed.

Abstract: A method for managing file based backups (FBBs) includes obtaining, by a backup agent, a FBB generation request for a file system at a point in time, in response to the FBB generation request: identifying a target backup storage system in which to store the FBB, identifying a target exposed application programming interface (API) associated with the target backup storage system, generating a FBB corresponding to the FBB generation request, wherein the FBB comprises a FBB metadata file, wherein the FBB is in a common data streaming format (CDSF), generating an API command based on the FBB and the target exposed API, and initiating storage of the FBB in the target backup storage system using the API command.

Abstract: One example method includes performing delta operations to protect data. A delta queue is provided that allows a replica volume to be rolled forwards and backwards in time. When rolling the replica volume forward, an undo delta is created such that the replica volume can be moved backwards after being moved forward. When rolling the replica volume backwards, a forward delta is created such that the replica volume can be moved forwards after being moved backwards.

Abstract: A method for managing file based backups (FBBs) includes obtaining, by a FBB metadata file manager, a FBB mount request for a FBB mount of a FBB from an application, wherein the application is executing in a production host environment, in response to the FBB mount request, the FBB metadata file manager: identifies a FBB in a backup storage system, obtains a FBB metadata file corresponding to the FBB from the backup storage system, performs an attribute analysis to identify the storage location attributes in the FBB metadata file, stores a FBB virtual file system in the production host environment using the storage location attributes, and enables access to the FBB virtual file system by the application.

Abstract: Embodiments described herein relate to a method for managing file based backups (FBBs). The method may include obtaining a FBB mount request for a FBB mount of a FBB from an application, wherein the application is executing in a production host environment and the FBB is stored on backup storage; in response to the FBB mount request: capturing an entity context associated with the application; authenticating the entity context; obtaining, when the authenticating is successful, access control information corresponding to the FBB from the backup storage; determining a subset of the FBB for which the access control information indicates the entity context has permission to access; and enabling access to a portion of the FBB by the application.

Abstract: Described is a system (and method) for providing multiple types of granular delete operations for a cloud-based object storage. The system may include a server that acts as an intermediary between a client device and an object storage that stores client data. The server may allow a client to perform a hard delete (or permanent) delete and a soft delete. The server may perform a specialized processing to synthetically create the soft delete feature using a permanent object delete operation provided by the object storage. The specialized processing may include manipulating retention periods associated with objects depending on whether the object is subject to a hard delete or a soft delete. As a result, the server may provide the ability for clients to perform a soft delete at an object level using existing storage level APIs that do not directly support such a feature.

Abstract: One example method includes performing delta operations to protect data. Each delta generated by a data protection operation includes data. The deltas are stored in a delta queue, when moving a current replica to another point in time represented by the selected delta in the delta queue, the deltas are processed so that all relevant data can be applied in a batch. This ensures that when the same extents are represented in multiple deltas, only the oldest version is applied to the replica volume to move the current replica to the selected point in time.

Abstract: Described is a system for synchronizing expiration times for incremental backup data stored on a cloud-based object storage. More particularly, the system may provide a layer of intelligence when updating the expiration times associated with backup data to ensure that a full recovery of the client data to a point-in-time of any incremental backup may be performed. To provide such a capability, the system may maintain specialized metadata identifying expiration times for objects and a list of objects required to perform a full recovery to a point-in-time for each of the performed backups (e.g. full or incremental). The system may access this metadata to identify which objects stored by a previous backup are still referenced by a subsequent backup. Based on the identified objects, the system may synchronize object expiration times to ensure objects are not prematurely deleted from the object storage.

Abstract: One example method includes performing delta operations to protect data. During a delta operation, a primary bitmap and a secondary bitmap are processed using bit logic. The delta generated by the delta operation is transmitted to a receiver. The receiver enqueues the delta into a delta queue configured to allow the replica volume at the target site to be moved to any point in time represented by the deltas in the delta queue.

Abstract: Described is a system (and method) for size-based organization of backup files within an object storage for efficient object re-tiering. The system may perform a specialized process to re-tier objects stored within an object storage by organizing backup files into individual or shared objects based on a backup file size. Accordingly, the system may initiate a re-tiering of objects immediately after performing an incremental backup to improve storage efficiency while at the same time retaining the ability to synthetically perform a full restore.

Abstract: Described is a system for rule-based re-tiering of backup data stored on a cloud-based object storage. More specifically, the system may re-tier objects based on one or more storage rules such that the system retains the ability to efficiently perform a full restore of backup data even when incremental backups are performed to a cloud-based object storage. To provide such a capability, the system may maintain a specialized metadata database that stores information indicating the backup time for each backup, and a list of objects required to perform a full restore to each of the backup times. Accordingly, when initiating a re-tiering based on one or more storage rules, the system may intelligently select candidate objects for re-tiering by leveraging the metadata database to ensure that objects that may still need to be referenced are not unnecessarily moved to a lower storage tier.

Abstract: A system for managing composed information handling systems includes information handling systems and a composed information handling system of the composed information handling systems, which includes at least one compute resource set, at least one control resource set, and at least one hardware resource set. The system also includes a system control processor that obtains a bare metal communication from a compute resource set indicating a write of data, writes a first copy of the data in a storage resource of the at least one hardware resource set, writes a second copy of the data in a trace volume, generates a backup of the data using the trace volume, and stores the backup in a storage.

Abstract: Described is a system (and method) for efficient access-based reallocation of backup data stored within an object storage. The system may implement various specialized procedures to efficiently store and manage backup data within the object storage. These procedures may include packing backup data into objects to improve data operation efficiency. The system may also conserve storage space on the object storage by performing an analysis to reallocate backup data as necessary. For example, data may be stored in objects in an immutable manner, and thus, the system may efficiently reallocate data to new objects based on data access patterns. For example, the system may determine an access pattern associated with live data remaining within the first object satisfies a condition, and in response, reallocated the live data to a new object.

Abstract: Described is a system for intelligent re-tiering of backup data stored on a cloud-based object storage. More specifically, the system may re-tier objects such that the system retains the ability to efficiently perform a full restore of backup data even when incremental backups are performed to a cloud-based object storage. To provide such a capability, the system may maintain a specialized metadata database that stores information indicating the backup time for each backup, and a list of objects required to perform a full restore to each of the backup times. Accordingly, when using a threshold time (e.g. expiry) to select object candidates for re-tiering, the system may leverage the metadata database to ensure that objects that may still need to be referenced are not unnecessarily moved to a lower storage tier.

Abstract: Described is a system for managing the expiration of objects storing incremental backup data by leveraging specialized metadata. The system may provide a layer of intelligence when freeing up storage space on an object storage to ensure that a full recovery of client backup data may be performed when storing incremental backup data. The system may maintain metadata indicating the latest and/or earliest backups that reference particular objects. The system may then leverage this information to mark particular objects for removal (e.g. deletion or re-tiering). For example, the system may access the metadata to identify which objects stored by a previous (e.g. expired) backup are still referenced by a subsequent (e.g. non-expired) backup. As a result, the system may ensure that objects are not removed prematurely and that a full recovery of the client data to a point-in-time of any incremental backup may be performed.

Abstract: One example method includes performing delta operations to protect data. Each delta generated by a data protection operation includes data. The deltas are stored in a delta queue, when moving a current replica to another point in time represented by the selected delta in the delta queue, the deltas are processed so that all relevant data can be applied in a batch. This ensures that when the same extents are represented in multiple deltas, only the oldest version is applied to the replica volume to move the current replica to the selected point in time.

Abstract: One example method includes performing delta operations to protect data. During a delta operation, a primary bitmap and a secondary bitmap are processed using bit logic. The delta generated by the delta operation is transmitted to a receiver. The receiver enqueues the delta into a delta queue configured to allow the replica volume at the target site to be moved to any point in time represented by the deltas in the delta queue.

Abstract: One example method includes performing delta operations to protect data. A delta queue is provided that allows a replica volume to be rolled forwards and backwards in time. When rolling the replica volume forward, an undo delta is created such that the replica volume can be moved backwards after being moved forward. When rolling the replica volume backwards, a forward delta is created such that the replica volume can be moved forwards after being moved backwards.