❗ Important
This feature has limited availability. To know more about limited availability and sign up for this feature, contact your Account Manager.
Create a backup set
A backup set is defined for an instance and is a combination of backup content and backup policy. You can attach multiple backup sets to the instances.
To protect your SQL resources, you must first set up your SQL resources for backup. For this, you must configure your SQL instance for backup by creating a backup set.
See the following procedure to create a backup set for your database instance:
Log in to the Management Console.
On the console, from the top menu, select Organization.
Select Protect > Go to Azure.
In the left navigation pane, select subscription and click SQL.
On the right pane, select a SQL instance and click Create Backup Set.
On the Backup Settings tab, provide the following information and click Next:
Backup Set Name: Enter the backup set name.
Backup Policy: Select or create a new Backup Policy.
On the Backup Content tab, provide the following details and click Next:
Database Name: Select the database(s) that you want to backup. All the databases are selected by default. You can also search for databases on this instance using the Search field. The database search is case-insensitive. If the database name is empdb and you enter EmpDb, Druva will search and list empdb as a choice.
Include Patterns: Enter a database name or substring to include the database in the backup set.
Druva does not support patterns like Emp*, *Emp, or *Emp*.
For example, the pattern Emp includes all databases with the substring Emp in their names. If there are three databases on the instance with the names HREmployees, FinanceEmployees, and EngineeringEmployees, adding the pattern Emp includes all the three databases in the backup set.
The include patterns are case-sensitive. The pattern Emp will include ITEmployees but exclude the database Exemployees in the backup. Druva only includes those databases that have the specified case-sensitive string in their database names. You can enter more than one substring.Exclude Patterns: Enter a database name or sub-string to exclude the database(s) from the backup set. For example, if there are two databases on the instance with the names FormerSystems and FormerSoftware, adding the substring Former in this field excludes both databases from the backup set.
The text inputs in this field are case-sensitive. If you enter Former, Druva excludes databases with the substring in their names and if the substring matches the case of the text you enter. For example, Druva excludes the FormerSystems database, but Druva skips excluding the database formerproducts from the backup set. You can enter more than one substring.
The exclusion filter takes precedence over the inclusion filter. For example, consider a database on the instance called FormerEmployees. You enter the pattern Former in both the Include and Exclude Pattern fields. The FormerEmployees database should be included based on the inclusion filter, however, it should be excluded based on the exclusion filter. In such a case, Druva excludes the database from the backup set.
Note:
Databases that match the Exclude Pattern are greyed out and disabled in the Database Selection. Databases that match the Include Pattern are selected and disabled in the Database Selection.
8. On the Summary tab, verify the information and click Finish.
The configured SQL resource is displayed on the listings page with the configuration status as Configured. You can view the configuration details by clicking the resource.
Next steps
You can back up the configured SQL resource by clicking the Backup Now button on the SQL Resources > SQL Backup Sets tab.
On-demand backup of SQL resources
Once you have configured the SQL resources for backup, you can backup the resources manually on-demand from the Management Console by performing the following steps.
Prerequisites
Ensure the backup prerequisites are met before initiating backups.
Important: Databases that do not have the required configurations will either be skipped from the backup or might fail.
Procedure
Log in to the Management Console.
On the console, from the top menu, select Organization.
Select Protect > Go to Azure.
In the left navigation pane, select a subscription and click SQL.
On the SQL Resources listing page, on the SQL Backup Sets tab, select the configured resource and click Backup Now.
Note: If you are taking backups for the first time, Druva performs a full backup of the SQL resources.
6. Click Yes on the confirmation dialog box to proceed with the backup.
The backup for the selected SQL resource is triggered.
Next steps
You can check the status of the backup on the All Jobs page.
Manage backup sets
You can view the details of the configured SQL resources by clicking the resource name on the SQL Resources listings page. You can see the backup sets configured for that resource by clicking the resource name. The backup set details page has the following two tabs:
Summary: Displays information such as the SQL resource, whether the backup is disabled or enabled, databases, and so on.
Recovery Points: Displays the latest created recovery points that can be used to restore the SQL resource.
You can perform the following actions on a configured backup set:
Restore
Enable/Disable backup
Edit
Delete
See the following procedure to perform these actions.
Procedure
From the Backup Sets listing page, click the required backup set.
On the virtual machines details page, do the following:
To restore the backup set, on the Recovery Points tab, select the required recovery point and click Restore.
To enable or disable the backup, from the Kebab menu on the top right corner, click Enable Backup or Disable Backup respectively.
To edit the backup set, from the Kebab menu on the top right corner, click Edit.
To delete the backup set, from the Kebab menu on the top right corner, click Delete.
Deleting a backup set deletes its recovery points.
Considerations
If a database is a part of a backup set, it cannot be attached to another one. These databases are greyed out and cannot be selected in a second backup set.
The most recent recovery point cannot be deleted as long as the server exists in the Management Console, regardless of whether the server is marked as inactive or disabled.
The retention period would not be honored for the most recent recovery point when an MS-SQL server is disabled. This allows you to restore the latest recovery point later if required.
Delete recovery points
If you are a cloud administrator, you can delete warm recovery points from the backup sets that you no longer require. If you are a group administrator, you can delete warm recovery points for backup sets belonging to your administrative groups. After you delete a recovery point, Druva purges the recovery point data from the warm storage, thus freeing up space.
Procedure
On the Management Console, on the SQL Resources listing page, click the required SQL resource.
On the SQL resource details page, click the backup set whose recovery points you want to delete.
On the SQL Backup Sets details page, go to the Recovery Points tab.
In the Recovery points section, select the recovery points that you want to delete, and then click Delete.
Note:
The last recovery point for a backup set cannot be deleted.