Abstract: An agent for managing virtual machines includes a persistent storage and an application agent manager. The persistent storage stores backup policies. The application agent manager identifies a new virtual machine instance and, in response to identifying the new virtual machine instance, performs proxy agent based analysis of the new virtual machine instance to generate a data loss threat profile of the new virtual machine instance; remediates the new virtual machine instance by instantiating application agents for the new virtual machine instance based on the data loss threat profile and a portion of the backup policies associated with the new virtual machine instance; updates at least one of the backup policies based on the instantiated application agents; and performs an application backup session for the new virtual machine instance using the instantiated application agents.

Abstract: A backup storage includes persistent storage and a backup manager. The persistent storage stores backups of entities and an entity list that lists the entities. The backup manager obtains a restoration availability request from a user; filters the entity list based on an identity of the user to obtain an available entity list; identifies, based on user input obtain based on the available entity list, an entity of the entities; and restores the entity using the backups.

Abstract: A method and system for capturing asset protection metadata pertinent to analytics. Specifically, the disclosed method and system entail aggregating and maintaining asset protection metadata—i.e., metadata descriptive of performed asset backup and recovery operations—in a central location. The asset protection metadata may include information relevant to backup and recovery analytics and reporting, while the maintaining said metadata in the central location facilitates access of the metadata by third-party analytics services.

Abstract: A method and system for optimizing backup and backup discovery operations using change based metadata tracking (CBMT). Specifically, the disclosed method and system entail eliminating the storage and subsequent transmission of redundant asset metadata information to a central coordination point during backup discovery operations, which may strain central coordination point resources, as well as client device resources. Accordingly, rather than re-sharing the same asset metadata information every time a backup discovery initiates, the client device tracks, maintains, and transmits only changes in asset metadata, thereby conserving resource utilization.

Abstract: A method and system for intelligently migrating to a centralized protection framework. Specifically, the disclosed method and system entail redirecting the target of asset backup operations for any given asset from one or more legacy backup devices to a centrally-managed backup device.

Abstract: An intelligent log gap detection to ensure necessary backup promotion. Specifically, a method and system are disclosed, which entail determining whether to pursue a differential database backup or promote the differential database backup to a full database backup, in order to preclude data loss across high availability databases. The deduction pivots on a matching or mismatching between log sequence numbers (LSNs).

Abstract: A method for managing backups that includes generating a full backup of a database and, after generating the full backup, generating N incremental backups of the database and generating a first differential backup of the database after the N incremental backups have been generated, wherein the first differential backup is generated relative to the full backup.

Abstract: An improved backup utility allows the ability to maintain full backup and incremental backup log chains, even when databases which are part of a clustered database group are backed up from different database nodes and instances. In these embodiments, this is implemented by storing the backup of the databases from both primary and secondary (failover) nodes under a single backup client which is the cluster identifier. The backup is indexed against a constant database instance based on a user configured save set. In other words, regardless of which node is primary at the time of the backup, the backup is made against a constant backup instance.

Abstract: A method and system for enabling data backups for virtual machines reliant on raw data mapping (RDM) disks to store their state and/or data. Traditional virtual machine backup methodologies pivot on the generation and storage of virtual machine snapshots as copies of a virtual machine disk file, which store the state and/or data of a virtual machine at various given points in time. However, these traditional virtual machine backup methodologies, at least at present, do not support the generation and storage of virtual machine snapshots for virtual machines that particularly access and consolidate information on RDM disks. Accordingly, the method and system disclosed herein facilitate the backup of state and/or data pertaining to virtual machines reliant on RDM disks.

Abstract: A backup storage includes a persistent storage and a backup manager. The persistent storage stores backups of entities and a global application data map. The backup manager obtains a restoration request for restoration of an application hosted by an entity of the entities; makes a determination to accelerate the restoration based, at least in part, on the application; in response to the determination: identifies a virtual disk level backup of the entity that is associated with the application using the global application data map; obtains the virtual disk level backup from the backups of the entities; and restores the application using the virtual disk level backup.

Abstract: A backup storage includes persistent storage and a backup manager. The persistent storage stores backups of entities and an entity list that lists the entities. The backup manager obtains a restoration availability request from a user; filters the entity list based on an identity of the user to obtain an available entity list; identifies, based on user input obtain based on the available entity list, an entity of the entities; and restores the entity using the backups.

Abstract: A production host includes a persistent storage and a backup manager. The persistent storage stores virtual machine data and a service group list associated with an application service group. The backup manager obtains a backup generation request for the application service group that includes virtual machines, and each of the virtual machines uses a copy of the virtual machine data; in response to obtaining the backup generation request: identifies a first virtual machine the virtual machines that is prioritized for generating a backup for the application service group based on the service group list; attempts to generate the backup using the first virtual machine and the copy of the virtual machine data; and stores the backup in backup storage.

Abstract: A method for providing an application service to clients includes identifying a failure of the application service that causes the application service to be suspended; in response to identifying the failure: instantiating an instance of an application for providing the application service in a production host; identifying at least one virtual disk level backup that is: associated with the application and is a portion of deduplicated backups; extracting the at least one virtual disk level backup from deduplicated backups to obtain a copy of the at least one virtual disk level backup; identifying application data associated with the application within the copy of the at least one virtual disk level backup; transitioning an application service session for a client of the clients to the instance of the application; and resuming the application service for the client using the instance of the application and the application data.

Abstract: A backup storage includes a persistent storage for storing backups of entities and a backup data map. The backup storage also includes a backup manager that obtains a search request for data; obtains at least two data maps associated with at least two of the entities; generates the backup data map using the at least two data maps; searches the backups for the data using the backup data map to identify a copy of the data; and provides the copy of the data in response to the search request.

Abstract: A backup storage includes a persistent storage and a backup manager. The persistent storage stores virtual machine level backups and application level backups. The backup manager obtains a request for a point in time restoration of an application; identifies, based on the application, a virtual machine level backup of the virtual machine level backups that is associated with: a virtual machine that hosted an instance of the application and a first point in time prior to a restoration point in time specified by the request for the point in time restoration; identifies, based on the application, an application level backup of the application level backups that is associated with the restoration point in time; generates a point in time backup using: the identified virtual machine level backup, and the identified application level backup; and services the request using the point in time backup.

Abstract: An intelligent log gap detection to prevent unnecessary backup promotion. Specifically, the method and system disclosed herein entail determining whether to pursue a requested database backup type or to promote the requested database backup type to another database backup type, in order to preclude data loss across high availability databases. When a decision is made to pursue the requested database backup type, storage space, intended for backup consolidation on a backup system or media, is saved for future backup requests rather than being consumed as would be the case would the requested database backup type had been promoted.

Abstract: A method for managing backups that includes generating a full backup of a database and, after generating the full backup, generating N incremental backups of the database and generating a first differential backup of the database after the N incremental backups have been generated, wherein the first differential backup is generated relative to the full backup.

Abstract: A backup agent for orchestrating backups of production hosts includes a persistent storage that stores backup policies and a backup manager that obtains a backup analysis request for a virtual machine hosted by the production hosts; generate a dependency graph based on: backups associated with the virtual machines, and the backup policies associated with the backups; and displays a graphical user interface, using the dependency graph, including user interactive markers based on the backups and dependency indicators interconnecting the user interactive markers. While the graphical user interface is displayed, the backup manager obtains a potential backup policy update based on a user interaction with one of the user interactive markers. After obtaining the potential backup policy update, the backup manager updates the graphical user interface to reflect the potential backup policy update. After updating the graphical user interface, the backup manager initiates generation of the backup.

Abstract: An intelligent log gap detection to ensure necessary backup promotion. Specifically, a method and system are disclosed, which entail determining whether to pursue a differential database backup or promote the differential database backup to a full database backup, in order to preclude data loss across high availability databases. The deduction pivots on a matching or mismatching between log sequence numbers (LSNs).

Abstract: An intelligent log gap detection to prevent unnecessary backup promotion. Specifically, the method and system disclosed herein entail determining whether to pursue a requested database backup type or to promote the requested database backup type to another database backup type, in order to preclude data loss across high availability databases. When a decision is made to pursue the requested database backup type, storage space, intended for backup consolidation on a backup system or media, is saved for future backup requests rather than being consumed as would be the case would the requested database backup type had been promoted.