I've come across the following error when executing a backup job with a few VMs (each VM with 3 disks or more and attached to the same Disk Access resource):
Too many simultaneous imports or exports using disk access object. The current cap is 5. Revoke some active access tokens before creating more access requests
From what I gather, this is a limitation on the Disk Access resource set on the VM disks. Is there a way to increase the limit? Or do I have to create more Disk Access resources and attach them to the VM disks? There's no mention of this in the VBA doc.
This is a private environment, so I would rather not set public access on my VM disks.
You are right. Due to the Microsoft Azure limitation, only five disks or snapshots can be processed at the same time with a single disk access object.
When creating a VM backup, Veeam Backup for Microsoft Azure takes a snapshot of each attached disk and uses disk access resources to process the snapshots. If existing disk access resources are insufficient, new ones must be created automatically by the backup policy. For more details, see the User Guide.
In such cases, you’ll need to add the newly created disk accesses to the private DNS zone, as described here.
Please check the configuration, and if the issue persists, open a support case and share the case ID so we can follow up.
I want to inform you that I created a VM in Azure which initially had 5 disks. After configuring the Disk Access Private Endpoint, the backup was successful. Later, I attached one more disk (making it 6 disks in total), and after that, the backup started failing.
Then, I removed one disk and kept only 4 disks attached to the VM, but I still started getting a disk limit error.
I also followed the guidelines provided in the forums, but the error still persists.
Failed to perform backup of cb-ci-web01 to CB-REPO01. Long running operation failed with status 'Failed'. Additional Info: 'Too many simultaneous imports or exports using disk access object. The current cap is 5. Revoke some active access tokens before creating more access requests. Current resources with active access tokens: '' (trace ID: c7a2f1b2-5879-4d9a-83c7-3a3ef6cbad93)