We’ve deployed Veeam Backup for Azure.
There are polciies in the Azure environment that deny public access to resources. Everything needs to be connected via private endpoints.
The Veeam resources are deployed in a seperate subscription and seperate VNET. This VNET is peered with a hub VNET. Alle the production VNET’s are also peered with the HUB VNET.
Taking backups within the subscription (and VNET) works. By using the disk access resource created by Veeam.
Taking backups of resources (VM’s) in other subscriptions (VNET’s) does not work.
We asume the backup should be done with a disk access resource in the production VNET. But Veeam does not create these disk access resources in the production VNET.
Or the existing Disk access resource (in the Veeam VNET) should have a private endpoint in all the production VNET’s?
Does anyone have experience with a similar private deployment where public access is blocked?
This is the production VM with disabled public and enabled private access requires a disk access resource which is not being created by Veeam.
This is a test VM in the same subscription and resource group. This VM has a disk access created as you can see in the screenshot below.
