Abstract: A method for managing a storage includes applying, by a host, a first type of snapshot service to the LU of the storage, wherein the LU is identified by a logical unit number (LUN), in response to applying the first snapshot service, making a first determination that the LU is not visible to the host, wherein the host is operationally coupled to the storage and the first snapshot service continues to be applied to the LU, in response to the first determination, discontinuing applying the first type of snapshot service to the LU, and when the first snapshot service is no longer applied to the LU, applying, by the host, a second type of snapshot service to the LU.

Abstract: A method for managing a storage includes applying, by a host, a first type of snapshot service to the LU of the storage, wherein the LU is identified by a logical unit number (LUN), in response to applying the first snapshot service, making a first determination that the LU is not visible to the host, wherein the host is operationally coupled to the storage and the first snapshot service continues to be applied to the LU, in response to the first determination, discontinuing applying the first type of snapshot service to the LU, and when the first snapshot service is no longer applied to the LU, applying, by the host, a second type of snapshot service to the LU.

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 system identifies availability group database replicas and a single instance database scheduled for backup. The system configures backup storage based on an identifier of a cluster of nodes associated with the availability group database replicas. The system backs up the availability group database replicas based on their corresponding preferred nodes and the single instance database from a node in the cluster of nodes based on the identifier of the cluster of nodes. The system outputs information associated with the single instance database and a database replica in any availability group that 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 single instance database and/or 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: 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: Embodiments for a system and method of performing restores of SQL database data, querying a backup history log to determine a sequence of full and incremental backups of the data, first restoring data from a full backup using a SQL volume shadow service (VSS) writer, placing the database into a recovering mode during the first restoring, and second restoring data from an incremental backup using a SQL virtual device interface (VDI) process while the database is in recovering mode until a stop signal is generated to form a hybrid restore process, where the stop signal comprises a STOPAT clause of the SQL VDI process that restores the database content until a given restore time.

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.