Abstract: Enabling scripting language commands to backup/restore databases is described. A system outputs, to a user interface, a backup/restore option for a database. The system generates scripting language commands based on a selection of the backup/restore option received from the user interface. The system outputs, to the user interface, the scripting language commands based on the selection of the backup/restore option. The system enables a scripting language system to execute the scripting language commands based on the selection of the backup/restore option.

Abstract: Enabling point-in-time recovery for databases which change transaction log recovery models is described. If a database is associated with a recovery model that creates independent backups of the database's transaction log, a system identifies most recent backup information and a current transaction log sequence number. If the most recent backup information includes a transaction log sequence number and the current transaction log sequence number is a reset value, the system creates a full backup of the database, without first creating any independent backup of the transaction log. The system creates an independent backup of the transaction log when the independent backup of the transaction log is scheduled next, subsequent to creating the full backup of the database.

Abstract: A method for performing a backup operation includes obtaining a backup request, wherein the backup request specifies a virtual machine (VM) set, and, in response to the backup request: identifying a first set of virtual machines (VMs), wherein the first set of VMs comprises a first portion of the VM set, performing a criticality analysis on the first set of VMs using a machine learning algorithm and a trained machine learning model to obtain an ordered list of critical VMs, performing a non-critical VM prioritization on a second set of VMs using the machine learning algorithm and the trained machine learning model to obtain an ordered list of non-critical VMs, consolidating the ordered list of critical VMs and the ordered list of non-critical VMs to obtain a final list, and initiating a backup of virtual machines using the final list.

Abstract: Techniques to back up data are disclosed. In various embodiments, an indication to perform a differential backup of a database is received. It is verified that a full backup to be referenced by the differential backup is available on backup media. It is determined that no intervening backup was performed subsequent to the full backup that would create a risk of data loss in the event a recovery operation based on the differential backup were performed, including by ignoring any intervening backup that may have been performed but is of a type that would not give rise to such a risk of data loss. The differential backup is performed, without promoting to full backup, based on least in part on said determination.

Abstract: A method for performing a backup operation includes obtaining a backup request, wherein the backup request specifies a virtual machine (VM) set, and, in response to the backup request: identifying a first set of virtual machines (VMs), wherein the first set of VMs comprises a first portion of the VM set, performing a criticality analysis on the first set of VMs using a machine learning algorithm and a trained machine learning model to obtain an ordered list of critical VMs, performing a non-critical VM prioritization on a second set of VMs using the machine learning algorithm and the trained machine learning model to obtain an ordered list of non-critical VMs, consolidating the ordered list of critical VMs and the ordered list of non-critical VMs to obtain a final list, and initiating a backup of virtual machines using the final list.

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: Federated restore of availability group database replicas is described. A system receives a restore request associated with an availability group, and identifies a primary node in a cluster of nodes, the primary node storing a primary database replica associated with the availability group. The system identifies a secondary node in the cluster of nodes, the secondary node storing a secondary database replica associated with the availability group. The system removes the primary database replica and the secondary database replica from the availability group. The system simultaneously restores a backup database replica, associated with the availability group, as the primary database replica in the primary node and the secondary database replica in the secondary node. The system adds the restored primary database replica and the restored secondary database replica to the availability group.

Abstract: A method for performing a restoration operation includes obtaining a restoration request, wherein the restoration request specifies a virtual machine (VM) set to be restored, and in response to the restoration request: identifying a first set of virtual machines (VMs), performing a critical VM prioritization on the first set of VMs using a trained machine learning model to obtain an ordered list of critical VMs, performing a non-critical VM prioritization on a second set of VMs using the trained machine learning model to obtain an ordered list of non-critical VMs, consolidating the ordered list of critical VMs and the ordered list of non-critical VMs to obtain a final list, and initiating a restoration of virtual machines using the final list.

Abstract: Backing up availability group databases configured on multi-node virtual servers is described. A system identifies an availability group scheduled for backup. The system determines whether the availability group is configured on at least one virtual server in a cluster of nodes associated with the availability group. If the availability group is configured on at least one virtual server in the cluster of nodes, the system retrieves information from a server in the cluster of nodes. The system uses the retrieved information to identify a database replica that is preferred for backing up the availability group. The system identifies a virtual server, in the cluster of nodes, that is associated with the identified database replica. The system identifies a node for backing up the availability group by identifying an active node from the nodes in the identified virtual server. The system backs up the availability group via the identified node.

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: Bypassing backup operations for specified database types is described. A system determines whether a database, of multiple databases associated with a database system, corresponds to a database type specified in a configuration file, in response to receiving a backup operation request. The system executes an incremental backup operation on changes made to the database since a selected time, for the backup operation request, if the database does not correspond to the database type specified in the configuration file. The system bypasses executing any backup operation on the database for the backup operation request if the database corresponds to the database type specified in the configuration file.

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: This disclosure relates to a method, article of manufacture, and apparatus of restoring a database allowing simultaneous full and incremental backups. In some embodiments, this includes receiving, by a server, a request for restoring as of a restore point-in-time, in response to the request, retrieving by the server a set of backup objects, sorting the set of backup objects in descending order, locating a first incremental backup in the set of backup objects based on the restore point-in-time and a first incremental backup start time associated with the first incremental backup, locating a full backup in the set of backup objects based on the first incremental backup start time, a full backup start time and a full backup end time associated with the full backup, storing the full backup and the first incremental backup in a list of restoring objects, and sending, by the server, the list of restoring objects.

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: A database management system add-in for third party backup and restore applications is described. An opportunity to select from multiple backup and restore applications is enabled via a user interface of a database management system. A selection of a backup and restore application of the multiple backup and restore applications is received. Multiple options offered by the backup and restore application are displayed. A selection of an option of the multiple options is received. Execution of the option is enabled, wherein the option is unavailable via a native backup and restore application offered by the database management system.