VCC to Azure

[FloMary]

Hello,

I would like to get some informations about Veeam licensing to use VCC to Azure. I can't find the exact answer to my question.

Currently, we have Veeam B&R infrastructure, in Enterprise Plus Edition, and we have Azure infrastructure too.

For one of our site, we would like to make backup copy to Azure. With what i understand on Veeam site, we have to deploy "Veeam Cloud Connect for Enterprise" on our Azure infrastructure. So it will deploy one Windows VM, with VCC. So after configuration, we can add our own Service Provider on B&R console (corresponding to Azure public IP) and configure backup copy to Azure server.
That's right ?

What I don't understand, is how licensing is working in my case ?
VCC is include in all Veeam licence (except free licence), so I will have nothing to pay ? I can deploy VCC free ?

Thanks for your answers

[v.Eremin]

Florian, you are not planning to become cloud provider, you don't need to leverage Cloud Connect Backup.

To achieve what you're after, you will need to:

- Create a VM in Azure
- Add it to a backup console either via IP or DNS name *
- Assign repository role to it
- Point backup job to the newly added repository

Point two might be tricky, since connectivity issues are likely to arise. Those can be addressed by Veeam PN (check this page for more information regarding it).

Thanks.

[FloMary]

Hi Vladimir,
Off course i don't wan't to become cloud provider, so it could be easier just to create backup repository on Azure VM.
I was thinking to VCC, because with VCC we have functionnality like encryption, only one port to open so easier for NAT rules ...

For my personnal knowledge, do you have any idea about my licensing question ?

Thanks a lot for your answer, and for PDF about Veeam PN, i didn't know this Veeam feature.

[v.Eremin]

I was thinking to VCC, because with VCC we have functionnality like encryption

In the scenario I proposed traffic going to Azure will be also encrypted, as data transferred between public networks is encrypted by default. In order to be on the safe you can enable encryption explicitly.

For my personnal knowledge, do you have any idea about my licensing question ?

If you stick to VCC, you will be additionally paying for objects sent to cloud repository, more specifically, number of VMs protected (stored). This will not intersect with your current license for backup server anyhow.

There is no VCC free, only promos and trials, but those won't last forever.

Thanks.

[FloMary]

Ok, thank you Vladimir.

[badooo]

we are planning to backup our vms on-premises and take another copy to the Azure
what are the required steps to setup this configuration to take copy to azure ?

I appreciate any help

[Shestakov]

Hello Mohamed and welcome to the community!
To take copy of backup to Azure you can create VM in Azure and use it as backup job target repository as Vladimir described above:

- Create a VM in Azure
- Add it to a backup console either via IP or DNS name *
- Assign repository role to it
- Point backup job to the newly added repository