This topic provides an overview of what backup set is. It also provides instructions to add and delete a backup set attached to the instances or availability groups (AG).
Overview
A backup set is a combination of backup content and backup policy. A backup set is defined for an instance or AG. You can attach multiple backup sets to the instances or AGs of the MS-SQL server. You can add a backup set from the All SQL Resources page under Protect > MS-SQL servers.
This topic describes the following sections:
Add a backup set recovery points
You can create multiple backup sets to back up different instances and availability groups, following different schedules. Before you create a backup set, review the following:
You can create only one MS-SQL backup set per instance or AG.
If you do not need distinct backup retention for different data on the physical server, do not create separate backup sets.
Ensure that you do not create multiple backup sets with overlapping backup content. The overlapping content gets backed up multiple times.
You can create any number of backup sets to configure with a physical server. However, the Hybrid Workloads agent can simultaneously back up three backup sets.
You can create a backup set for an instance or an AG from the All SQL Resources page under Protect > MS-SQL servers. For more information on creating backup sets, see:
View details of the backup sets
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization that has the MS-SQL server instances and availability groups, and then select the workload.
In the navigation pane on the left, click SQL Backup Sets. The SQL Backup Sets page lists all the backup sets created for all instances and AGs. You can also search for the backup set, instance, AG or DB from the SQL Backup Sets page using the search box.
Click the instance or AG whose backup set details you want to view.
The information on the SQL Backup Sets details page is divided into the Summary and Backups tab. The Summary tab lists the Backup Configuration, Backup Content, and trends.
The Backups tab lists all the recovery points associated with the backup set.
Edit a backup set
You can modify the backup settings and the backup content and backup policy applied to the MS-SQL backup set. However, you cannot edit the name of the instance or availability group.
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization that has the MS-SQL server instances and availability groups, and then select the workload.
In the navigation pane on the left, click SQL Backup Sets.
In the right pane, click the backup set to view backup set details. You can also search for the backup set from the SQL Backup Sets page using the search box.
On the SQL Backup Sets details page, in the top right corner, click more options, and click Edit.
In the Edit Backup Set window, you can edit all fields except the Storage field. Storage once assigned cannot be changed. To know more about the fields available in the Edit Backup Set wizard, see Configure MS-SQL instance or AG for backup.
📝 Notes
If you add a database to your SQL Server, and it is not a part of an existing backup set, yet it qualifies for configuration because it matches an include substring, Druva includes the database for backup in the oldest backup set that has the inclusion filter.
If one SQL backup set has the Select all databases checkbox selected, while another backup set of the same SQL server has a specific pattern, then newly added databases that have the specified substring in their name will automatically get included in the backup set with the specific pattern, while the remaining databases will get included in the backup set with the Select all databases checkbox selected. The backup set with a specific substring gets priority during the automatic addition of new databases.
If a database is a part of backup set, Druva cannot attach it to another backup set.These databases are greyed out and cannot be selected in a second backup set.
On the Backup Content screen, edit the database selection, rule, and include and exclude patterns and click Next. For more information, see Configure MS-SQL instance or AG for backup
The Configuration Pre-Checks window is displayed with the following validations:
To prevent any future failures in your backups due to misconfigured settings, Druva broadly performs these validations while editing a backup set:
Sysadmin privileges for the user account: Transaction Log and VDI differential backups require the assigned SQL server user login to have the ‘Sysadmin’ role. This validation ensures that the same is provided.
Database mirroring check: Druva supports backup of mirrored databases with some limitations. This validation ensures that mirroring is disabled for all the selected databases. For more information, see System requirements for MS-SQL servers.
Database recovery model check: Databases in Simple recovery model do not support Transaction Log backups.
If the backup set is configured for Transaction Log backups, this validation ensures that at least one of the selected databases is in the Full recovery model.
For more information about validation checks, see Configure MS-SQL instance or AG for backup.
If a check to create a backup set fails, then fix the issue and re-run the checks. If all the checks are successful, then the Summary screen is displayed.
If a check fails and you still want to proceed, then click Proceed Anyway.On the summary screen, verify all the details, and click Save.
📝 Note
Ensure that the Include Pattern fields in your backup sets have appropriate substrings so that Druva can automatically detect newly added databases and attach them to the backup set.
Disable and enable backup of backup set
You can enable or disable backup of backup sets. Backups of disabled backup sets stop temporarily. The disabled backups resume after you enable the backup.
📝 Notes
The most recent recovery point cannot be deleted as long as the MS-SQL server exists in the Management Console, regardless of whether the MS-SQL server is marked as inactive or disabled.
The retention period would not be honored for the most recent recovery point when an MS-SQL serveris disabled.This allows you to restore the latestrecovery point later if required.
You can enable or disable backups of a backup set from:
SQL Backup Sets page
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization that has the MS-SQL server instances and availability groups, and then select the workload.
In the navigation pane on the left, click SQL Backup Sets.
In the right pane, select the backup set of the instance or AG , click more options, and then click Enable Backup to enable backups of that backup set.
Click Disable Backup to disable backups of an enabled backup set.
All SQL Resources page
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization that has the MS-SQL server instances and availability groups, and then select the workload.
In the navigation pane on the left, click All SQL Resources.
In the right pane, click the instance or AG whose backups you want to enable or disable.
In the All SQL Resources details page, in the Configured Backup Sets section, select the backup set, click more options, and then click Enable Backup to enable backups of that backup set. Click Disable Backup to disable backups of an enabled backup set.
📝 Note
The Enable Backup option is available only for the backup sets whose backup is currently disabled. Similarly, the Disable Backup option is available only for backup sets whose backup is currently enabled. You can continue to restore servers whose backups have been disabled.
Delete recovery points
If you are a cloud administrator, you can delete warm recovery points from the MS-SQL backup sets that you no longer require. If you are a group administrator, you can delete warm recovery points for MS-SQL backup sets belonging to the administrative groups that you manage. After you delete a recovery point, Druva purges the recovery point data from the warm storage, thus freeing up space.
Procedure
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization that has the MS-SQL server instances and availability groups, and then select the workload.
In the navigation pane on the left, click SQL Backup Sets.
In the right pane, click the backup set whose recovery points you want to delete.
In the SQL Backup Sets details page, click the Backups 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.
Delete a backup set
If you are a cloud administrator, organization administrator, group administrator, or a derived custom, organization, or group administrator, you can delete a backup set created for the instance or AG. When you delete a backup set, Druva deletes all the recovery points corresponding to that backup set. However, Druva retains the jobs, reports, and alerts corresponding to the deleted backup set.
Log in to the Management Console.
Select the workload from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization that has the MS-SQL server instances and availability groups, and then select the workload.
In the navigation pane on the left, click SQL Backup Sets.
In the right pane, click the backup set that you want to delete.
In the SQL Backup Sets details page, in the top right corner, click more options, and then click Delete.
📝 Note
If you want to reuse the databases attached to a backup set, you must detach all required databases from the backup set before deleting the backup set. If you fail to do so, then those databases cannot be attached to a new backup set until the old backup set is permanently deleted.
A confirmation dialog is displayed. Provide a reason in the Reason for deletion box and click Delete. Druva deletes the backup set associated with the instance or the AG. The reason is required to confirm your action and to prevent any accidental deletion. This is a mandatory field, and you can use a minimum of 10 characters and a maximum of 150 characters to provide the reason for deletion. Note that all deletion requests with a reason will be reported to the Audit Trails.
For more information, see View Admin Audit Trails page.