Abstract: An improved backup utility allows the ability to maintain full backup and incremental backup log chains, even when databases which are part of a clustered database group are backed up from different database nodes and instances. In these embodiments, this is implemented by storing the backup of the databases from both primary and secondary (failover) nodes under a single backup client which is the cluster identifier. The backup is indexed against a constant database instance based on a user configured save set. In other words, regardless of which node is primary at the time of the backup, the backup is made against a constant backup instance.

Abstract: A distributed systems backup configuration wizard is described. A computer executes a wizard. The wizard receives an identifier of a distributed setup for backup configuration via a user interface. The wizard identifies each system which comprises the distributed setup. The wizard retrieves information associated with each system for configuring backup of the distributed setup. The wizard outputs configuration options based on retrieved information via the user interface. The wizard configures backup of the distributed setup based on the retrieved information and user selected configuration options received via the user interface.

Abstract: Methods and systems for performing an item level restore from a backup are described herein. A method starts by mounting files of content databases from storage device on management server. Content databases from storage device are from the backup. New database is created in relational database server with the mounted files of the content databases. Unattached database object is then created which includes pointing to the new database. Unattached database is not related to the content databases from the storage device. Unattached database object is then searched for source item selected for restore from content databases. Selected source item is exported from new database to a source item location in management server. Data from selected source item is then restored by importing data from the source item location to a target item location in management server.

Abstract: Identifying preferred nodes for backing up availability groups is described. A system logs in to a structured query language instance on an active node. The system identifies a primary replica for an availability group identified for backup. The system identifies a backup preference for the availability group based on the primary replica. The system identifies the backup preference as a preferred node for backing up the availability group if the backup preference is on-line.

Abstract: A high-availability cluster includes a subset of nodes having database instances where each database instance hosts a primary replica having primary databases or a secondary replica having corresponding secondary databases. An availability group includes a primary replica hosted by one database instance on one node and at least one secondary replica hosted by another database instance on another node, the secondary replica being a failover for the primary replica. A first backup preference is determined for a first availability group to identify a first preferred node for a first backup. A second backup preference is determined for a second availability group to identify a second preferred node for a second backup. The backups are triggered on the preferred nodes and the backups can proceed in parallel.

Abstract: Federated restores of availability groups are described. A system backs up an availability group from a node in a cluster of nodes based on an identifier of the cluster of nodes. The system outputs information associated with at least one database replica in any availability group which is backed up based on the identifier of the cluster of nodes in response to a user request for the information. The system restores a user-selected database replica to a user-selected node in the cluster of nodes based on a user selecting at least some of the information.

Abstract: Federated back up of availability groups is described. A system identifies multiple availability groups scheduled for backup. The system logs in to a structured query language instance on an active node, identifies a primary replica for the first availability group, identifies a backup preference for the first availability group based on the primary replica for the first availability group, and identifies the backup preference for the first availability group as a preferred node for backing up the first availability group if the backup preference for the first availability group is on-line. The system configures backup storage based on a name of a cluster of nodes associated with the availability groups. The system backs up the first availability group based on the preferred node for the first availability group in parallel with backing up the second availability group based on a preferred node identified for the second availability group.

Abstract: This disclosure relates to a method, article of manufacture, and apparatus of performing backup in a failover cluster. In some embodiments, this includes determining whether a repository is part of a failover cluster, based on a determination that the repository is part of the failover cluster, analyzing a role associated with the repository, upon a determination that the role indicates the repository is a failover candidate within the failover cluster, triggering a secondary backup of the repository, and upon a determination that the role indicates the repository is a primary repository within the failover cluster, triggering a primary backup of the repository.

Abstract: Displaying configuration test results by leveraged data protection software is described. A memory location is read where a display file is stored for a software installer. A configuration checker is executed for the computer. Results are read from executing the configuration checker. The results are written to the memory location. A leveraged software creation tool is prompted to display the display file via an output device. The leveraged software creation tool lacks the capability to dynamically load the display file.