Abstract: Agent lifecycle management for backup and restore applications is described. A system enables selection of application hosts, each of which meets installation requirements for installing instances of application agents from a backup and restore application, then downloads, in parallel, the instances of the application agent to the corresponding selected application hosts. The system installs, in parallel, the instances of the application agent in the corresponding selected application hosts, then registers, in parallel, the instances of the application agent with the backup and restore application. The system subsequently initiates sessions which download and install, in parallel, an update in instances of the application agent in in corresponding application hosts. The system unregisters at least one of the instances of the application agent, in at least one application host, from the backup and restore application.

Abstract: Automatically updating agents from backup and restore applications is described. A system enables selection of application hosts which meet update requirements, then downloads an update for instances of an application agent corresponding to selected application hosts. The system puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. The system initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions did not fail to install update in any of instances of application agent in cluster of application hosts, then the system stores the updated instances of the application agents in a non-volatile storage.

Abstract: System enables selection of application hosts which meet update requirements, then downloads update for instances of application agent corresponding to selected application hosts. System puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. System creates copy of instructions, which when executed, installs update in instance of application agent in one of application hosts, and reports on update process to server which communicates with application hosts. System launches worker process from copy of instructions. System initiates update sessions which install update in instances of application agent corresponding to selected application hosts.

Abstract: Automatically updating agents from backup and restore applications is described. A system enables selection of application hosts which meet update requirements, then downloads an update for instances of an application agent corresponding to selected application hosts. The system puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. The system initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions did not fail to install update in any of instances of application agent in cluster of application hosts, then the system stores the updated instances of the application agents in a non-volatile storage.

Abstract: Agent lifecycle management for backup and restore applications is described. A system enables selection of application hosts, each of which meets installation requirements for installing instances of application agents from a backup and restore application, then downloads, in parallel, the instances of the application agent to the corresponding selected application hosts. The system installs, in parallel, the instances of the application agent in the corresponding selected application hosts, then registers, in parallel, the instances of the application agent with the backup and restore application. The system subsequently initiates sessions which download and install, in parallel, an update in instances of the application agent in in corresponding application hosts. The system unregisters at least one of the instances of the application agent, in at least one application host, from the backup and restore application.

Abstract: System selects application hosts which meet update requirements, then downloads update for instances of application agent corresponding to selected application hosts. System puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. System creates backup copy of state of instances of application agent. System generates installation instructions that, when executed by update sessions to install update, enable roll back from updated instances of application agent to state of instances of application agent recorded in backup copy. System initiates update sessions which install update in instances of application agent corresponding to selected application hosts.

Abstract: Selecting, authenticating, and installing individual components of agent software stacks is described. A system enables a selection of a component of an application agent software stack from a backup and restore application, from displayed components of multiple application agent software stacks. The system downloads the selected component of the application agent software stack from the backup and restore application. The system downloads a digital certificate from a vendor of the backup and restore application or the backup and restore application. The system uses a public key from the downloaded digital certificate to authenticate the selected component of the application agent software stack. The system installs an instance of the authenticated component of the application agent software stack in an application host, which executes the instance of the authenticated component to create a backup copy of data generated by an application executed by the application host.

Abstract: Updating application hosts in a cluster are described. A system enables a selection of an application host which meet update requirements, and then determines whether the selected application host is in a cluster of application hosts. If the selected application host is in a cluster, then the system determines whether each application host in the cluster is selected for updating. If each application host in the cluster is not selected for updating, then the system enables the selection of all application hosts in the cluster for updating. If each application host in the cluster is selected for updating, then the system initiates update sessions which install updates in components of the cluster. If at least some of the application hosts in the cluster are not updated, then the system rolls back all updated application hosts in the cluster to previous conditions of the updated application hosts.

Abstract: A system enables selection of application hosts which meet update requirements, then downloads an update for instances of an application agent corresponding to selected application hosts. The system puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. The system creates backup copy of configuration files used to configure instances of application agent. The system initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions failed to install update in any of instances of application agent in cluster of application hosts, then system restores configuration files which were used to configure instances of application agents.

Abstract: One example method includes identifying a data asset for protection, evaluating a configuration of a logical volume group where the data asset is stored, comparing the configuration of the logical volume group with a configuration of a storage array, and based on an outcome of the comparing, selecting a data protection mechanism for the data asset. The data asset may then be tagged with the selected data protection mechanism, and backed up using that selected data protection mechanism.

Abstract: Snapshot capability-aware discovery of tagged application resources is described. A backup server inputs an identifier of an application's resource from the application's host. If the backup server determines that the application resource identifier was input with a snapshot capable tag, and that the application's resource satisfies any of the snapshot policy rules, the backup server identifies the data protection policy for the satisfied snapshot policy rule. The backup server outputs a request to the application's host to use the identified data protection policy to create a snapshot of the application's resource that was input with any associated snapshot capable tag.

Abstract: A method for trusted node election. The method includes: identifying a database cluster implemented on a node subset of a plurality of nodes forming a data center; receiving node state from each node in the node subset; and electing, for the database cluster and from the node subset, a trusted node based on the node state from each node in the node subset and a database cluster type of the database cluster.

Abstract: The present invention provides a system, computer readable code and method for dynamically performing debugging. The system, code, and method store debugging logs throughout an operation. At predetermined points the logs are stored to a cache. Older and/or unnecessary logs are periodically deleted from the cache to ensure that the cache does not grow to be larger than a predetermined size. This avoids the need to re-run a scenario after an error occurs in order to produce troubleshooting/debugging information.

Abstract: One example method includes analyzing a load factor regarding a workload for one or more actors, applying one or more criteria to an output of the load factor analyzing, based on the applying a criterion from the one or more criteria, determining how many actors are needed to perform the workload, when a number of actors needed to perform the workload is determined, spawning the actors and assigning the actors to a pool, throttling the pool, and based on the throttling, load balancing the workload across the actors in the pool.

Abstract: One example method includes analyzing a load factor regarding a workload for one or more actors in a data storage platform, wherein the workload includes a group of two or more connected jobs, applying one or more criteria to an output of the load factor analyzing, based on the applying a criterion from the one or more criteria, determining how many actors should be included in a swarm of actors necessary to perform all of the connected jobs, spawning the swarm of actors, and load balancing the connected jobs across the swarm of actors.

Abstract: One example method includes analyzing a load factor regarding a workload for one or more actors in a data storage platform, applying one or more criteria to an output of the load factor analyzing, based on the applying a criterion from the one or more criteria, determining whether or not any additional actors are needed to perform the workload, when it is determined that one or more additional actors are needed to perform the workload, spawning the additional actors, and load balance the workload across a group that includes both the one or more actors and the additional actors that have been spawned.

Abstract: One example method includes analyzing a load factor regarding a workload for one or more actors in a data storage platform, applying one or more criteria to an output of the load factor analyzing, based on the applying a criterion from the one or more criteria, determining whether or not any additional actors are needed to perform the workload, determining a number of reserve actors, when it is determined that one or more additional actors are needed to perform the workload, spawning the additional actors, and spawning the reserve actors, and load balancing the workload across a group that includes both the one or more actors and the additional actors that have been spawned, and the group does not include the reserve actors. The method also includes temporarily deploying one of the reserve actors to service a high priority workload.

Abstract: The present invention provides a system, computer readable code and method for dynamically performing debugging. The system, code, and method store debugging logs throughout an operation. At predetermined points the logs are stored to a cache. Older and/or unnecessary logs are periodically deleted from the cache to ensure that the cache does not grow to be larger than a predetermined size. This avoids the need to re-run a scenario after an error occurs in order to produce troubleshooting/debugging information.

Abstract: Creating vendor-neutral data protection operations for vendors' application resources is described. Capabilities specified for data protection operations by a vendor of an application are input from a host of the application. Any capabilities specified for the data protection operations are used to create a vendor-neutral version of a data protection operation for a resource of the application. The vendor-neutral version of the data protection operation for the application resource is output to the host. A result of performing the vendor-neutral version of the data protection operation on the application resource is input from the host.

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.