Veeam Recovery Orchestrator • Re: VRO Azure Disks shorten name

Hi Alec

Sorry for the late reply, been out of office for a few days.
In the short term, if VRO would use a shorter UID it would work for us, it shouldn't exceed the 20 characters limit in my opinion, because some organizations themselves have their own naming concepts for Azure Workloads.
In our case the length of the disks is now about 70 characters.
In the long term we'd like to see that these specific details for the Azure VM configuration could be specified in the VRO Job.
These would be:
- Azure VM Name
- Azure Disk Name (per Disk, if not specified, then use the vm name with the uid)
- Azure NIC Name
- Azure NSG Name (it would also be great if the NSG could be excluded from creation, because it is not always needed, especially if the Azure Network is managed by vWan or another firewall solution)

I hope there is a way to implement this UID workaround quickly in VRO because our Disaster Recovery will depend on it and we're using Bicep to manage all of our Azure VMs.

Thanks and Best Regards
Philipp

Statistics: Posted by harbinger — Feb 14, 2024 7:16 am

---