Abstract: Vendor-neutral models of vendors' application resources are described. A host outputs capabilities of data protection operations which are specified by a vendor of an application that is installed on the host. The host inputs a vendor-neutral version of a data protection operation, based on any of the capabilities, for a resource of the application. The host uses a vendor-neutral model of the resource of the application to perform the vendor-neutral version of the data protection operation on the application resource.

Abstract: A method for managing applications includes obtaining, by a client in a customer environment, an upgrade issue report for the application, making a first determination that a resynchronization of a client self-healing classification model with the production host environment (PHE) self-healing classification model is required, wherein the PHE self-healing classification model is stored in the PHE, performing the resynchronization with the PHE self-healing classification model to obtain a synchronized client self-healing classification model, applying the synchronized client self-healing classification model to the upgrade issue report to obtain a state of the upgrade issue report, making a second determination that the state indicates a self-healable state, based on the second determination, performing a self-healing process on the application based on the upgrade issue report, and storing a resolution report based on results of the self-healing process, wherein the PHE is operatively connected to the custome

Abstract: A method for managing applications includes obtaining an application resolution report from an administrative system, wherein the application resolution report comprises a customer query and a response, applying a neural network algorithm on a set of tokens associated with the application resolution report to obtain a vector representation of the application resolution report, performing a probability analysis on each vector in the vector representation, based on the probability analysis, identifying an unanswered portion of the application resolution report, and in response to the unanswered portion of the application resolution report, performing a query resolution.

Abstract: A method for managing file based backups (FBBs) includes obtaining, by a backup agent, a backup request for a FBB, in response to the backup request, generating a FBB, generating a FBB metadata file corresponding to the FBB, wherein the FBB metadata file comprises a set of attribute regions, performing, using the set of attribute regions, a deduplication on the FBB metadata file to obtain a deduplicated FBB metadata file, and storing the deduplicated FBB metadata file in a backup storage system.

Abstract: A method for processing backup policy generation requests includes receiving, by a production agent manager, a backup policy generation request, in response to receiving the backup policy generation request: identifying a backup to transfer to a backup storage, wherein the backup comprises a plurality of data blocks, performing a data storage device evaluation on a set of data storage devices to obtain a set of health scores, wherein each health score of the set of health scores corresponds to a data storage device of the set of data storage devices, assigning, based on the set of health scores, a production agent to a data storage device of the set of data storage devices to generate a backup policy, and initiating, based on the backup policy, a deployment of the production agent to the data storage device.

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 (and method) for application-based packing for storing backup data within an object storage. More particularly, the system may efficiently pack backup files into objects having a specialized size by accounting for the source and size of the backup file. For example, the system may determine whether backup files associated with a particular application may be stored within individual objects or packed together within a shared object. Accordingly, by accounting for such criteria the system may perform an intelligent allocation of backup data within a cloud-based object storage. The system may be implemented as part of an incremental backup infrastructure. Accordingly, when allocating the backup files amongst objects, the system may also store specialized metadata to preserve the ability to perform a reconstruction of data (e.g. synthetically) as if a full backup was performed.

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 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: A method and system for leveraging file-based backups to facilitate bare-metal recovery (BMR) and/or system-state recovery (SSR) operations. In leading to a BMR operation (which may include, but is not limited to, data protected under a SSR operation), logical groupings of data, each including multiple files and/or directories that span across one or more file-systems, may be written to backup media to comply with data backup, archiving, and/or disaster recovery strategies. Backing up said logical groupings of data relies on block-based backup technologies, which upon requiring a subset of a given logical grouping of data to be restored, makes the restoration process impossible to fulfill since determining which blocks of data belong to which files and/or directories are not tracked. Accordingly, the disclosed method and system propose an intelligent scheme through which file-based backup technology may be employed to enable BMR and/or SSR from any single BMR-compliant backup copy.

Abstract: In general, the invention relates to a method for backing up data. The method includes receiving a backup instruction from a client device, wherein the backup instruction comprises a backup tag corresponding to a backup operation for a user asset, making a first determination that the backup tag matches a second backup tag specified in a tag file, and in response to the first determination, identifying a checkpoint of a backup associated with the second backup tag, and resuming the backup operation at the checkpoint for the user asset.

Abstract: A method and system for risk score based asset data protection using a conformal framework. Concerning Internet-of-Things (IoT) environments, there is a growing challenge to ensure the availability and continuity of applications executing, as well as relevant application data maintained, on IoT devices, in order to mitigate potential operational failures and/or interruptions. The disclosed method and system address this growing challenge through risk-score assessments of the applications and their respective relevant application data (collectively referred to as assets), as well as the potential degradation of the underlying IoT device hardware. The aforementioned risk-score assessments employ clustering to identify, and a conformal framework to rank, high-risk (for failure) assets, which may subsequently be subjected to backup operations (overriding existing policies) to guarantee asset protection.

Abstract: A method and system for asset protection threat detection and mitigation using interactive graphics. Specifically, the disclosed method and system entail discerning protection vulnerabilities exhibited by assets (or databases) based on maintained backup metadata. These protection vulnerabilities may subsequently be visualized as part of a projected graphical user interface, which may not only disclose the protection vulnerabilities to a user but also may enable the user to rectify the disclosed protection vulnerabilities through on-demand asset backup operations.

Abstract: A method for performing a backup operation includes obtaining, by a backup agent, a backup request for a file system, and in response to the backup request: generating a first application partition for an application associated with the file system, performing a dependency analysis on the application to identify application dependency information, populating a first application partition with a copy of the application dependency information and a copy of application data associated with the application, and initiating a storage of a backup to a backup storage system, wherein the backup comprises the first application partition.

Abstract: A backup manager for providing backup services includes persistent storage and a backup orchestrator. The persistent storage includes protection policies. The backup orchestrator identifies a last backup generation time for a client in response to a protection policy of the protection policies triggering a backup generation for the client; obtains system metadata for the client; identifies a portion of client data that has been modified since the last backup generation time using the system metadata; generates an incremental backup based on the identified portion of the client data; and stores the incremental backup in backup storage.

Abstract: A production host includes storage for storing backup priorities of entities and backup windows during which a system, of which the production host is a member, is predicted to have sufficient computing resources to generate a backup for an entity of the entities and a backup manager that identifies a backup generation event for the entity; in response to identifying the backup generation event: identifying an earliest potential backup window of the backup windows; making a determination that the earliest potential backup window of the backup windows is reserved for a second entity of the entities; in response to making the determination: identifying that a backup priority of the backup priorities that is associated with the entity is greater than a second backup priority of the backup priorities that is associated with the second entity; and providing the backup services to the entity during the earliest potential backup window.

Abstract: A system for providing data protection services for user data generated by an application, includes persistent storage for storing user data backups and a manager. The manager is programmed to identify a backup generation event for user data based on a protection policy, in response to identifying the backup generation event, obtain user data associated with the backup generation event from the application, select a calendar of calendars included in the user data, obtain user metadata associated with the calendar, and generate a user data backup using the user data and the user metadata, in which the user data backup comprises calendar events of the calendar and portions of the user metadata associated with the calendar events.

Abstract: Methods, apparatus, and processor-readable storage media for implementing dual relationship-based hash structures for non-volatile memory technology are provided herein. An example computer-implemented method includes generating a hash storage structure by: creating multiple layers of storage components, wherein a first layers comprise a first number of storage components and at least a second layer comprises at least a second number of storage components less than the first number of storage components; configuring the at least a second layer to share at least a portion of the storage components therein with at least a portion of the storage components in the first layer; partitioning each of the storage components in each of the multiple layers into multiple portions; configuring a respective status value space for each of the multiple portions of each of the storage components in the multiple layers; and implementing the hash storage structure in at least one storage system.

Abstract: Tagging application resources for snapshot capability-aware discovery is described. If an application's host determines that one of an application's resource satisfies any snapshot capability rule, the application's host associates the application resource with a snapshot capable tag. The application's host outputs an identifier of the application resource and any associated snapshot capable tag to a backup server. The application's host inputs a request from the backup server to create a snapshot of the application resource associated with the snapshot capable tag and creates the snapshot of the application resource associated with the snapshot capable tag.

Abstract: In general, embodiments of the invention relate to a method for enabling enhanced logging. The method includes obtaining a historical data for a target entity, determining an error probability of the target entity using the historical data, and enabling, based on the error probability, enhanced logging on the target entity.