Veeam Backup for Microsoft Azure vs Kasten

[BostjanUNIJA]

Hi.

I need some 'hints' how to setup best backup strategy for creating backups of resources in Micorost Azure.

Current backup policy:

Local Vmware Servers, where we backup with 3-2-1 strategy all the local resources (strategy includes: backup copies, surebackups, backup to tapes, etc).
Now we have also some resources on Microsoft Azure and we have decided that we wish to backup that data also locally to tapes.
After initial investigation of what resources we have in cloud we thought that's gonna be easy, just by adding Microsoft Azure object into VBR and start making backups by selecting Resource groups.
After more detailed research (by having some conversation with our development team) we realised that in Microsoft Azure besides SQL databases we also have Kubernetes environment, Docket images...

QUESTIONS:
1. Is it possible to backup entire Microsft Azure Resource group (that would include everything; Azure SQL databases, network settings, storages AND also Kubernetes&Docker) with VBR, or do we need to implement additional Veeam solution (Kasten) which seems rocket science to me, as we haven't get into details of that product yet but it looks 'scary' to study?

2. If Microsoft Azure objects (especially Azure SQL databases) are already backed up with some Microsoft Azure built-in backups policy, probably those tasks are doing some dumping of transcation logs, right? Where can we check if SQL dumping transcation logs are being done?
If we switch to VBR backup (with application awareness enabled) of Microsot Azure SQL, then we would probably break backup policy (if) built-in backup task is doing dump of transaction logs.

[Mildur]

Hi Bostjan

1. Is it possible to backup entire Microsft Azure Resource group (that would include everything; Azure SQL databases, network settings, storages AND also Kubernetes&Docker) with VBR, or do we need to implement additional Veeam solution (Kasten) which seems rocket science to me, as we haven't get into details of that product yet but it looks 'scary' to study?

For Azure workloads you can use Veeam Backup for Microsoft Azure. Veeam Backup for Microsoft Azure needs to be managed by your Veeam Backup & Replication server to gain access to all features.

With this combination, you can protect:
- Azure VMs, Azure SQL Databases, Azure Cosmos DB Accounts, Azure File Shares, Azure Virtual Network Configurations.
The most recent list is always available in our help center.

Backup Copy + Tape is available through VBR, but limited to VM workloads.

storages

I assume you mean Data on Azure Blob? You can use our "Object Storage to Tape" feature from Veeam Backup & Replication to backup your Azure Blob container directly to a Tape.

or do we need to implement additional Veeam solution (Kasten) which seems rocket science to me, as we haven't get into details of that product yet but it looks 'scary' to study?

For Kubernetes environments, you'll need to deploy Veeam Kasten. However, it's important to note that Kasten does not support Docker. Currently, we do not offer a dedicated backup solution for Docker. However, if your Docker containers are running on Azure VMs that you've deployed, you might consider backing up those VMs using Veeam Backup for Microsoft Azure to protect your Docker machine.

If we switch to VBR backup (with application awareness enabled) of Microsoft Azure SQL, then we would probably break backup policy (if) built-in backup task is doing dump of transaction logs.

Can you elaborate what you mean by "VBR backup with application awareness enabled"? Do you mean Agent backup jobs? Cloud machine agent or managed by VBR agent?

And what AzureSQL database service? There are a few ways to consume Azure SQL databases within Azure (SQL Server on Azure VM, Managed SQL instance, your own deployed MS SQL Azure VM). Whatever you mean with "VBR backup with application awareness enabled", it will not be possible to use it for every Azure offering.

If Microsoft Azure objects (especially Azure SQL databases) are already backed up with some Microsoft Azure built-in backups policy, probably those tasks are doing some dumping of transcation logs, right? Where can we check if SQL dumping transcation logs are being done?

I'm not an expert on Azure SQL Databases. And we don't know what Azure Service you use for your databases. If you can't any indicator of log truncation on Azure Management Portal, then I suggest to ask this question in a Microsoft forum.

Best,
Fabian