Azure SQL DB backup - backup copy not supported

[sumeet]

Hello,

For Azure VMs backup, backup copy is supported, allowing us to get a copy of the VM out of Azure.

We understand that for Azure SQL DB backup - backup copy not supported.
The backup is only in the Azure local repository, but cannot be replicated out to on-prem VBR server/repository.

For the requirement to have a copy outside of Azure, we want to understand the following

To be able to get a copy of Azure SQL DB backup outside of azure, what if we backup the StorageAccount which is the backup repository for Azure SQL DB backup. Since the retention period is small for the local backups in Azure, this repository will not be huge. Also will create a separate repository for Azure VMs backup, so that these two remain separate.

Understand that if there is a restore required from StorageAccount backup - a full restore of the storage account needs to be done.

What I'm not sure of is does Veeam backup for Azure appliance have a capability to scan a new repository and understand that the repository has existing backups for Azure SQL DB? Similar to on-prem VBR server, when adding a repository, there is a check box which says, scan the repository for existing backups.

If this is not clear on what I'm trying to get too, we can discuss in a call.

[nielsengelen]

Hi Sumeet,

If you add a repository to another VBAz installation, VBAz will take ownership of that repository so that is possible today.

What is unclear to me is this part: "what if we backup the StorageAccount which is the backup repository for Azure SQL DB backup". How do you plan to back up that storage account? This will help me in providing a better answer.

[sumeet]

Hi Niel,

Thanks for the confirmation.
We plan to use on-prem VBR to backup StorageAccount as Unstructured Data - https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

1. Setup a new SA as backup repository in VBAz - https://helpcenter.veeam.com/docs/vbazu ... ml?ver=8.1
2. While creating a backup schedule for Azure SQL backup, specify this repository - https://helpcenter.veeam.com/docs/vbazu ... ml?ver=8.1
- The schedule will be for few dailys and weeklys
3. Wait for the first full backup to complete
4. Setup the SA in step #1 as source for unstructured data backup in on-prem VBR - https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
5. Understand that the first full backup copy will be a full data backup - https://helpcenter.veeam.com/docs/vbazu ... ml?ver=8.1
- the retention will be longer few weeklys and monthlys - and then off to tape
6. The subsequent backups will be incremental
7. If there is a full data loss in Azure, worst case scenario, where in SQL DB is lost, VBAz is lost and so is the repository in Azure - then once Azure is back online, restore the whole/full SA from on-prem VBR, deploy VBAz appliance, restore the VBAz configuration, add the restored SA to VBAz, let VBAz rescan the SA and allow us to use a restore point to restore SQL DB in Azure
8. If the restore is for testing purpose and requires a copy from 1 year ago, then create a new SA in Azure (cannot use the existing SA, as it is used for daily backup), then restore the whole/full SA from on-prem VBR using a restore point from tape, which is a year ago, add this SA to existing VBAz, let it rescan and allow us to select a restore point to restore a copy of the SQL DB in a different SQL server

This is at a high-level, but does this make sense?