Abstract: A backup manager for managing backup services includes persistent storage and a backup analyzer. The persistent storage includes a backup data repository and protection policies. The backup analyzer identifies a new backup stored in backup storage; performs a backup compatibility analysis on the new backup to determine inter-backup compatibility of the identified new backup; updates the backup data repository based on the inter-backup compatibility to obtain an updated backup data repository; and modifies a backup schedule using the updated backup data repository to meet a requirement of a protection policy of the protection policies.

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 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 manager for providing services to clients includes persistent storage and an orchestration manager. The persistent storage includes protection policies. The orchestration manager obtains a backup from a client of the clients based on a protection policy of the protection policies; makes a determination that an application catalog associated with the client is not stored in backup storages; in response to making the determination: obtains the application catalog from the client; stores the application catalog in the backup storages; and stores the obtained backup in the backup storages.

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: A backup storage for managing backups of clients includes persistent storage and a backup analyzer. The persistent storage includes the backups, protection policies, and an early deletion schedule. The backup analyzer obtains a request to analyze a protection policy of the protection policies; in response to obtaining the request: obtains backup data information associated with the protection policy; makes a determination, based on the backup data information and the protection policy, that a portion of the backups associated with the protection policies overprotect a client of the clients associated with the protection policy; and modifies the early deletion schedule based on the determination to obtain a modified early deletion schedule.

Abstract: A backup storage for managing backups of clients includes persistent storage and a backup analyzer. The persistent storage includes the backups, protection policies, and an early deletion schedule. The backup analyzer obtains a request to analyze a protection policy of the protection policies; in response to obtaining the request: obtains backup data information associated with the protection policy; makes a determination, based on the backup data information and the protection policy, that a portion of the backups associated with the protection policies overprotect a client of the clients associated with the protection policy; and modifies the early deletion schedule based on the determination to obtain a modified early deletion schedule.

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 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 manager for managing generation of backups for clients includes persistent storage and a backup manager. The persistent storage stored protection policies associated with the clients and native backup functionality information associated with the clients. The backup manager programmed obtains a portion of the native backup functionality information from a client of the clients; obtains at least one protection policy of the protection policies that is associated with the client; makes a determination that the at least one protection policy and the portion of the native backup functionality information are unique; in response to the determination: generates modifier data based on: the portion of the native backup functionality information and the at least one protection policy; and generates a backup for the client using a modifier associated with the modifier data.

Abstract: A backup manager for managing backup services includes persistent storage and a backup analyzer. The persistent storage includes a backup data repository and protection policies. The backup analyzer identifies a new backup stored in backup storage; performs a backup compatibility analysis on the new backup to determine inter-backup compatibility of the identified new backup; updates the backup data repository based on the inter-backup compatibility to obtain an updated backup data repository; and modifies a backup schedule using the updated backup data repository to meet a requirement of a protection policy of the protection policies.

Abstract: A manager for providing services to clients includes persistent storage and an orchestration manager. The persistent storage includes protection policies. The orchestration manager obtains a backup from a client of the clients based on a protection policy of the protection policies; makes a determination that an application catalog associated with the client is not stored in backup storages; in response to making the determination: obtains the application catalog from the client; stores the application catalog in the backup storages; and stores the obtained backup in the backup storages.

Abstract: A method and system for efficiently handling backup discovery operations. Specifically, the disclosed method and system entail enhancing breadcrumbs—e.g., persistent files that store status and other metadata information respective to performed asset backup operations—to further include unique transaction identifiers. These transaction identifiers may serve as markers for distinguishing which subset of breadcrumbs (rather than all breadcrumbs) to forward to a central management system during asset backup discovery operations. The disclosed method and system also implement batch processing architecture to regulate resource consumption on both the client and manager sides.

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: A method and system for efficiently handling backup discovery operations. Specifically, the disclosed method and system entail enhancing breadcrumbs—e.g., persistent files that store status and other metadata information respective to performed asset backup operations—to further include unique transaction identifiers. These transaction identifiers may serve as markers for distinguishing which subset of breadcrumbs (rather than all breadcrumbs) to forward to a central management system during asset backup discovery operations. The disclosed method and system also implement batch processing architecture to regulate resource consumption on both the client and manager sides.

Abstract: A method and system for SharePoint single web application recovery. Specifically, the method and system disclosed herein overcome the existing problem of data loss that incurs when a SharePoint farm (SPF) (i.e., or more specifically, the configuration database within the SPF) is restored due to the failure of just a single web application that executes therein. The data loss transpires because restoring the SPF leads to the overwriting of data associated with all web applications, and not just the failed web application, that executes on the SPF. The method and system disclosed herein addresses this dilemma through the assembly of web application topology metadata pertinent to recovering any web application periodically prior to a web application failover event, determining that a web application has entered a failed state and, subsequently, triggering and executing the restoration of just the failed web application based on the determining.

Abstract: A method and system for SharePoint single web application recovery. Specifically, the method and system disclosed herein overcome the existing problem of data loss that incurs when a SharePoint farm (SPF) (i.e., or more specifically, the configuration database within the SPF) is restored due to the failure of just a single web application that executes therein. The data loss transpires because restoring the SPF leads to the overwriting of data associated with all web applications, and not just the failed web application, that executes on the SPF. The method and system disclosed herein addresses this dilemma through the assembly of web application topology metadata pertinent to recovering any web application periodically prior to a web application failover event, determining that a web application has entered a failed state and, subsequently, triggering and executing the restoration of just the failed web application based on the determining.