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: Indexing files to account for snapshots can include generating, based on a scan of the storage system, one or more file records. Each file record of the one or more file records can correspond to a file stored on the storage system at the time of the scan. The file records can be maintained based on one or more notifications received from the storage system. A snapshot list of the storage system can be maintained, the snapshot list having snapshot data corresponding to one or more snapshots stored on the storage system. A search result can be generated that satisfies a search parameter based at least on a) the one or more file records and/or b) the snapshot list.

Abstract: File metadata of a virtual machine can be generated when performing a backup of a virtual machine. A backup copy of the virtual machine and the file metadata can be stored in a backup storage system. The file metadata can be retrieved from the storage system in a manner that is decoupled from the performance of the backup of the virtual machine. The file metadata can be used for searching for files within the backup copy of the virtual machine.

Abstract: The present disclosure relates to a method, apparatus and computer program product for managing a virtual machine. According to example implementations of the present disclosure, there is provided a method for managing a virtual machine. In the method, in response to receiving a backup request for the virtual machine, corresponding metadata of a corresponding object of at least one object in the virtual machine is obtained, the corresponding metadata describing multiple attributes of the corresponding object in a file system of the virtual machine. A corresponding abstract describing a basic attribute of multiple attributes of the corresponding object is generated on the basis of the corresponding metadata. An index of a backup version of the virtual machine is created on the basis of the corresponding abstract, the index comprising a corresponding path of the corresponding object in the backup version of the virtual machine.

Abstract: According to one embodiment, one or more consistent states of a virtual machine (VM) are backed up and stored. An index library is used to extract, from the consistent state(s) of the VM, metadata corresponding to content files captured in the consistent state(s). The extracted metadata is stored into a metadata catalog, where the metadata catalog is subsequently downloaded by an index server to index the content files captured in the consistent state(s).

Abstract: A distributed search framework with virtual indexing is disclosed. According to some embodiments, a virtual index that includes a first physical index is created, where the first physical index includes a first number of shards. A request to index a document is received. In response to the request, whether the first physical index has reached a capacity threshold is determined. In response to determining that the first physical index has reached the capacity threshold, a second physical index is automatically created and added to the virtual index, where the second physical index includes a second number of shards. The document is added into the second physical index.