Create a New Backup Scope for Azure SQL Backup

To create a new backup scope for Azure SQL, follow the steps below:

1. Go to the Backup page on the new UI.
2. Click on the Azure SQL service tile or click the More actions () button on the upper-right corner of the Azure SQL service tile and click Configure backup scope from the drop-down list.
3. In the Configure backup scope for Azure SQL page, all the existing backup scopes for Azure SQL are listed in the table. You can use the search box to search for the backup scopes by name and manage the columns to adjust the view of the backup scopes.
   Note: You can click the Refresh () button in the upper-right corner of this page to retrieve the latest data list for Azure SQL databases. The Last refreshed time is displayed next to the Refresh () button.
4. Click the Create button and select Azure SQL backup. The Create backup scope panel appears.
5. In the Select databases step, select the tenant and the databases that you want to add to the backup scope.
   • Manually select – Select the databases that you want to add to the backup scope. You can use Filters to find the databases you want to protect or use the Search box to search for the databases via the keywords in the name. The number of your selection will be displayed on the row of the tenant name.
   • Copy from existing native Azure SQL backup monitoring backup scope – Select the backup scopes from the native Azure SQL backup monitoring backup scopes drop-down list.
6. Click Next, and you will go to the Configure storage based on region step to configure a storage profile for each region. You can select a storage type and then select storage profiles. You can use an existing storage profile or create a new storage profile to store the backup data for the databases in the same region. For details on configuring storage location, refer to Manage Your Storage.
   Note: If you have enabled a firewall for your Azure SQL databases, you need to add the IBM® Storage Protect for Cloud IP addresses to your Azure SQL database account firewall or configure the firewall to allow IBM Storage Protect for Cloud agent servers running on a dedicated ARM Vnet subnet to access your storage location. For details, refer to Allow IBM Storage Protect for Cloud Agent Servers to Access Your Storage Account.
7. After you finish the storage configuration for each region, click Next to configure the scope information, schedule, and data retention settings. Refer to the following:
   • Scope information – Enter a name and description for the scope you are creating. The description is optional.
   • Schedule – Select days, weeks, months,oryears as the unit of time for the backup interval, enter a number in the text box after Every, and then configure the start time for your first backup job.
     Note: The days option is only available if you use your own storage to store backup data.
   • Notification policy – Check the notification profiles which will be applied to the backup scope.
   • Retention policy – Configure the retention period to keep the backup data in the storage.
     Note: For existing backup scopes with the legacy retention policy, you can click Switch to modern retention policy to configure the new retention period.
     • Daily recovery point – Enter a number in the text box and select days or weeks from the drop-down list. The retention period must be between 7 and 28 days.
     • Weekly recovery point – Enter a number in the text box and select weeks or months from the drop-down list. The retention period must be between 2 and 12 weeks.
     • Monthly recovery point – Enter a number in the text box. The retention period must be between 1 and 12 months.
     • Yearly recovery point – If you are using IBM default storage with unlimited retention period, the Unlimited option is selected automatically. If you want to use a custom retention period, select Custom.
8. Click Next to review your settings.
9. Click Save to save this backup scope. The backup for the databases in this backup scope will roll out as scheduled. For more details about monitoring the backups, refer to Monitor Your Backup.