Abstract: One or more embodiments of the invention improves upon the traditional method of performing a backup, by having a data protection manager or similar component of the system, determine, when a backup is requested, which backup agent should initially perform the backup. That backup agent may then determine among the other applicable backup agents, which backup types are needed and the order each backup agent performs the backup, when more than one backup agent is appropriate. This will allow for a more efficient backup, while avoiding collisions between two or more backup agents trying to simultaneously back up the same data.

Abstract: One or more embodiments of the invention may improve the operation of one or more computing devices in a cluster environment. More specifically, by mapping backups of shared volumes to a cluster client instead of individual data nodes, one or more embodiments of the invention avoid duplicative backups and/or restorations of the same shared assets by the each of the data nodes. Further, if a failure occurs to the particular node the backup may have originated from, in accordance with one or more embodiments of the invention, because the method is agnostic with regards to the individual nodes the backup may have originated from, any remaining data node can discover the backup and perform a restoration or incremental backup. This will provide better protection for the clustered nodes while requiring minimal user/administrator input.

Abstract: Techniques described herein relate to a method for improving the performance of discovery in a failover cluster or similar cluster-based system. More specifically, by mapping shared volumes to a cluster client instead of individual data nodes, one or more embodiments of the invention avoid duplicative backups and/or restorations of the same shared assets by the each of the data nodes. To map the one or more shared volumes to a cluster client, the cluster manager and/or data protection manger must determine which of the volumes in the cluster are associated with either an active/passive shared volume or a cluster shared volume (CSV). Therefore, the cluster environments assets may be efficiently mapped and accessed.

Abstract: A method for backing up standalone data and clustered data on a node, that includes receiving, by a backup agent, a first backup request, making a first determination that a backup process is not active, and based on the first determination, identifying a first type of data specified in the first backup request, where the first type of data is the standalone data, locating, using a first backup policy, the standalone data in the node, begin generating standalone backup data from the standalone data, receiving, by the backup agent, a second backup request, making a second determination that the backup process is active, and based on the second determination, queuing the second backup request.

Abstract: One or more embodiments of the invention have a cluster manager, or other related component, determine upfront which data node should perform a backup of the asset. This is achieved by running a pre-backup step, either periodically or prior to the reception of a backup request, to determine the preferred node for backup. Once the backup request is received, the cluster manager queries the preferred node, if the preferred node is still the best data node to perform the backup, then that data node performs the backup. If, however, the preferred data node no-longer is the best data node for performing the backup, the current preferred data node will signal the cluster manager with an alternative data node that is best data node to perform the backup and the cluster manager will have that alternative data node perform the backup.

Abstract: Techniques described herein relate to a method for managing data protection feature compatibility. The method may include identifying a host data protection feature update event associated with a host; in response to identifying the host data protection feature update event, obtaining host data protection feature information from the host; updating a host data protection feature information repository using the host data protection feature information; updating data protection feature compatibility information using the host data protection feature information and data protection manager data protection feature information; and sending data protection feature compatibility information associated with the host to the host.

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 or more embodiments of the invention allows for a better method of choosing a data node for performing a data protection event such as a backup and/or restoration. The one or more embodiments of the invention allows a user or administrator to choose a preferred data node for performing the data protection event or has a data protection manager or similar component of a system dynamically choses a preferred data node for performing the data protection event based on predetermined criteria. Such predetermined criteria may include each data node's load and workload as well as the type of backup that will be or was performed. This will allow for a more efficient backup and/or restoration, while avoiding overloading and collisions.

Abstract: One or more embodiments of the invention may improve the operation of one or more computing devices in a cluster environment. More specifically, by mapping backups of shared volumes to a cluster client instead of individual data nodes, one or more embodiments of the invention avoid duplicative backups and/or restorations of the same shared assets by the each of the data nodes. Further, if a failure occurs to the particular node the backup may have originated from, in accordance with one or more embodiments of the invention, because the method is agnostic with regards to the individual nodes the backup may have originated from, any remaining data node can discover the backup and perform a restoration or incremental backup. This will provide better protection for the clustered nodes while requiring minimal user/administrator input.

Abstract: One or more embodiments of the invention improves upon the traditional method of performing a backup, by having a data protection manager or similar component of the system, determine, when a backup is requested, which backup agent should initially perform the backup. That backup agent may then determine among the other applicable backup agents, which backup types are needed and the order each backup agent performs the backup, when more than one backup agent is appropriate. This will allow for a more efficient backup, while avoiding collisions between two or more backup agents trying to simultaneously back up the same data.

Abstract: One or more embodiments of the invention have a cluster manager, or other related component, determine upfront which data node should perform a backup of the asset. This is achieved by running a pre-backup step, either periodically or prior to the reception of a backup request, to determine the preferred node for backup. Once the backup request is received, the cluster manager queries the preferred node, if the preferred node is still the best data node to perform the backup, then that data node performs the backup. If, however, the preferred data node no-longer is the best data node for performing the backup, the current preferred data node will signal the cluster manager with an alternative data node that is best data node to perform the backup and the cluster manager will have that alternative data node perform the backup.

Abstract: One or more embodiments of the invention relates to a method of performing a restore, by either allowing a user or administrator to choose a preferred data node for performing a restoration, or by having a data protection manager or similar component of a system dynamically choses a preferred data node for performing a restoration based on predetermined criteria. Such predetermined criteria may include each data node's load and workload as well as the type of backup that was performed to make the backup of the at least one selected asset. This will allow for more efficient restoration, while avoiding overloading when restoring assets from a backup in a data cluster.

Abstract: Techniques described herein relate to a method for improving the performance of discovery in a failover cluster or similar cluster-based system. More specifically, by mapping shared volumes to a cluster client instead of individual data nodes, one or more embodiments of the invention avoid duplicative backups and/or restorations of the same shared assets by the each of the data nodes. To map the one or more shared volumes to a cluster client, the cluster manager and/or data protection manger must determine which of the volumes in the cluster are associated with either an active/passive shared volume or a cluster shared volume (CSV). Therefore, the cluster environments assets may be efficiently mapped and accessed.

Abstract: A method for backing up standalone data and clustered data on a node, that includes receiving, by a backup agent, a first backup request, making a first determination that a backup process is not active, and based on the first determination, identifying a first type of data specified in the first backup request, where the first type of data is the standalone data, locating, using a first backup policy, the standalone data in the node, begin generating standalone backup data from the standalone data, receiving, by the backup agent, a second backup request, making a second determination that the backup process is active, and based on the second determination, queuing the second backup request.

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: Techniques described herein relate to a method for managing data protection feature compatibility. The method may include identifying a host data protection feature update event associated with a host; in response to identifying the host data protection feature update event, obtaining host data protection feature information from the host; updating a host data protection feature information repository using the host data protection feature information; updating data protection feature compatibility information using the host data protection feature information and data protection manager data protection feature information; and sending data protection feature compatibility information associated with the host to the host.

Abstract: In one example, a method can be performed that involves receiving user input concerning a failure of a data protection job, and performing various operations automatically without requiring further user input or action. Such operations include querying a database, based on the user input, to identify a log file, accessing the log file and extracting information from the log file based on the user input, using information extracted from the log file to identify a potential cause of the failure, and generating a report that lists the potential cause of the failure.

Abstract: Initiating backups based on data changes is described. A system identifies an amount of data changed for a client since a previous backup operation for the client. The system determines whether the amount of data changed meets a threshold requirement. The system initiates a backup operation for the client if the amount of data changed meets the threshold requirement.

Abstract: Disclosed are systems and methods relating to the deployment of an application. A plurality of nodes in one or more clusters of nodes may be identified. Inventory information for each of the plurality of nodes may be retrieved. The inventory information may provide configuration and state information associated with each node. For example, the inventory information retrieved from the plurality of nodes may include an internet protocol address or a hostname associated with each the plurality of nodes, and a version of software installed on each of the plurality of nodes. An order for deploying the software application may be determined based on the retrieved inventory information. The order may identify a sequence in which the software application is deployed to at least one of the plurality of nodes. The software application may be deployed to at least one of the plurality of nodes based on the determined order.

Abstract: Disclosed are systems and methods relating to profiling software and configuration information associated with one or more entities. In various implementations, software and configuration information associated with one or more entities may be retrieved. The retrieved software and configuration information may provide state information associated with the one or more entities. The retrieved information may be processed to identify one or more changes in the software and configuration information that is associated with the one or more entities. A report may be generated based on the retrieved information. The report may display identified changes in a state for at least one entity based on the changes in the software and configuration information that were identified during the processing.