Abstract: A method and system for efficient virtual machine operation while recovering data. Specifically, the disclosed method and system enable the activation of virtual machines while virtual machine data, pertinent to the virtual machines, may concurrently be undergoing restoration. By activation, virtual machines may be permitted to issue input-output operations targeting their respective virtual machine data. Further, whether or not the sought virtual machine data has been recovered, fulfillment of the input-output operations may entail accessing virtual machine data either stored locally or retained remotely on a backup storage service.

Abstract: An efficient method for optimizing long-term retention backup policy within recovery point objectives (RPO). Specifically, the disclosed method proposes a dynamic promotion scheme through which short-term retention backup copies, in compliance with specified long-term retention RPOs, may be promoted to render long-term retention backup copies. Further, the disclosed method not only looks to past and/or presently dated short-term retention backup copies, but also looks to prospective (or future) dated short-term retention backup copies, which are expected or predicted to be produced, for promotion. Moreover, in circumstances where there are no appropriate past, present, or future dated short-term retention backup copies to promote, the disclosed method triggers new backup operations to acquire the long-term retention backup copies necessary to maintain the specified long-retention RPOs.

Abstract: A efficient method for long-term retention backup policy within recovery point objectives (RPO). Specifically, the disclosed method proposes a dynamic promotion scheme through which short-term retention backup copies, in compliance with specified long-term retention RPOs, may be promoted to render long-term retention backup copies. Further, the disclosed method not only looks to past and/or presently dated short-term retention backup copies, but also looks to prospective (or future) dated short-term retention backup copies, which are expected or predicted to be produced, for promotion. Moreover, in circumstances where there are no appropriate past, present, or future dated short-term retention backup copies to promote, the disclosed method triggers new backup operations to acquire the long-term retention backup copies necessary to maintain the specified long-retention RPOs.

Abstract: A method and system for efficient virtual machine operation while recovering data. Specifically, the disclosed method and system enable the activation of virtual machines while virtual machine data, pertinent to the virtual machines, may concurrently be undergoing restoration. By activation, virtual machines may be permitted to issue input-output operations targeting their respective virtual machine data. Further, whether or not the sought virtual machine data has been recovered, fulfillment of the input-output operations may entail accessing virtual machine data either stored locally or retained remotely on a backup storage service.

Abstract: A remote agent for providing backup services to applications includes a persistent storage and a backup manager. The persistent storage stores backup policies for the applications. The backup manager identifies an application of the applications for providing the backup services; generates an application backup template based on a backup policy of the backup policies for the application; sends the generated application backup template to a production host that hosts the application; and makes a determination that the backup policy has been triggered. In response to the determination, the backup manager initiates a native data extraction from the application using the application backup template to obtain a native data dump; stores the native data dump in backup storage; and indexes the stored native data dump as a backup.

Abstract: First and second types of weighted values are assigned to graph edges of a directed acyclic graph representing versions of a software product. The first type of weighted values indicate a degree of stability associated with upgrading the product. The second type of weighted values indicate an estimated time for the upgrading. A first upgrade path through the graph is generated using the first type of weighted values and corresponds to a first upgrade plan that minimizes risks associated with the upgrade. A second upgrade path through the graph is generated using the second type of weighted values and corresponds to a second upgrade plan that minimizes the estimated upgrade time. An upgrade package is created for one of the first or second upgrade plans. The upgrade package includes the desired version, intermediate versions, and a sequence indicating an order in which the intermediate versions should be installed.

Abstract: Software product versions installed on clients are detected. At least a subset of clients have different versions. Directed acyclic graphs are built specific to a client based on a particular version of the software product installed. Weighted values are assigned to edges in each graph. The weighted values indicate a degree of stability associated with upgrading the software product or an estimated time associated with the upgrading. Upgrade paths present in each graph are traversed to calculate sums of the weighted values. Based on the sums, recommended upgrade paths for the clients are identified, each recommended upgrade path is specific to a respective client. Upgrade packages, corresponding to the recommended upgrade paths, are created for the clients. Each upgrade package is specific to the respective client, includes the desired version of the software product, intermediate versions, and a sequence indicating an order in which the intermediate versions should be installed.

Abstract: First and second types of weighted values are assigned to graph edges of a directed acyclic graph representing versions of a software product. The first type of weighted values indicate a degree of stability associated with upgrading the product. The second type of weighted values indicate an estimated time for the upgrading. A first upgrade path through the graph is generated using the first type of weighted values and corresponds to a first upgrade plan that minimizes risks associated with the upgrade. A second upgrade path through the graph is generated using the second type of weighted values and corresponds to a second upgrade plan that minimizes the estimated upgrade time. An upgrade package is created for one of the first or second upgrade plans. The upgrade package includes the desired version, intermediate versions, and a sequence indicating an order in which the intermediate versions should be installed.

Abstract: Software product versions installed on clients are detected. At least a subset of clients have different versions. Directed acyclic graphs are built specific to a client based on a particular version of the software product installed. Weighted values are assigned to edges in each graph. The weighted values indicate a degree of stability associated with upgrading the software product or an estimated time associated with the upgrading. Upgrade paths present in each graph are traversed to calculate sums of the weighted values. Based on the sums, recommended upgrade paths for the clients are identified, each recommended upgrade path is specific to a respective client. Upgrade packages, corresponding to the recommended upgrade paths, are created for the clients. Each upgrade package is specific to the respective client, includes the desired version of the software product, intermediate versions, and a sequence indicating an order in which the intermediate versions should be installed.

Abstract: A remote agent for providing backup services to applications includes a persistent storage and a backup manager. The persistent storage stores backup policies for the applications. The backup manager identifies an application of the applications for providing the backup services; generates an application backup template based on a backup policy of the backup policies for the application; sends the generated application backup template to a production host that hosts the application; and makes a determination that the backup policy has been triggered. In response to the determination, the backup manager initiates a native data extraction from the application using the application backup template to obtain a native data dump; stores the native data dump in backup storage; and indexes the stored native data dump as a backup.