Feature Request: Allocate IP for VM on restore into Azure

[Nicholasbird]

Hope i am posting the correct place.

I would like to be able to specify the ip address of the vm once it is restored in azure.

I would like to be able to script the restore of the multiple vms into azure with defined ip addresses, as a DR solution.

Does anyone know of any workarounds?

thanks for considering

[veremin]

Are you talking about private or public one? Must be the latter one, but I thought it wouldn't harm to double check. Thanks.

[Nicholasbird]

thanks,
i want to be able to configure the private ip adress, so the restored vms have exactly the same ip configuration as they do on premise.
eg 10.0.0.102 on premise, 10.0.0.102 in azure

The restored subnet of vms is entirely separate from production (on premise) (i dont expect coexistence, i dont expect to move workloads into azure and have on premise access them, this is solely for DR when on premise is completely kaput). The intention would be to DR into azure and swap over some public dns records with a few hours of downtime, and all our (citrix users) access (citrix) services running in azure accross the public internet.

in time i might set up a site to site veeampn configuration and routing so we can have some workloads on premise and some in azure at same time, but that is not what this post is about.

[veremin]

Then, my suggestion would be to leverage Azure PowerShell. Just get an appropriate VM, based on a name given to it during restore, and assign a private IP to one of its network interfaces, using this approach. Thanks.

[Nicholasbird]

Yes, this is where I got too, a prepared powershell script which resets all the ips of all the vms and removes the public ip addresses, and put a default dns on the vnet.

whilst this works..the feature request stills stands, would be great to define the ip at the point of restore if azure allows that.

thanks for help.

[veremin]

Sure, consider your vote counted - I was just trying to provide a workaround. Thanks!

[Huaner]

Add to this:

1. The ability to not add a private IP address
2. The ability to leave the machine powered off
3. The ability to nominate an NSG or not as the case maybe.

[veremin]

1.2. Request noted.
3. Already added in Update 4.

Thanks!

[andre.ri]

Add to this:

1. The ability to not add a private IP address
2. The ability to leave the machine powered off
3. The ability to nominate an NSG or not as the case maybe.

I really would like to see point 1 and 2 in a future release of Veeam. Would be handy to configure that directly in the restore wizard.

[fcompaired]

1.2. Request noted.
3. Already added in Update 4.

Thanks!

Hello, I'd like to add my votes to these requests.

[veremin]

We've already implemented request 3 (check Update 4).

As to request 1 and 2, we're aware of them and actively working on adding these features to our product; stay tuned.

Thanks!

[PXAbstraction]

Hey all. Forgive me if this has been answered, but I couldn't find a conclusive answer on it.

Short explanation of the scenario: We have a client with an on-prem B&R server that makes on-prem backups and also uses Backup Copy jobs to keep 7 days worth in Azure for DR purposes. When they are restored in Azure, they are restored in an isolated environment and we want the VMs to have the same IP addresses as their on-prem versions because they have toold that are tied to specific IPs.

Right now, when I restore these machines in Azure, they are defaulting to a dynamic IP, so they aren't all getting the same IPs they had on-prem. Is there any way to ensure that they do? This is rather critical to our client's needs. I found some old threads from years ago saying this feature was coming to a future release of Veeam, but if it has, I haven't seen it.

Thanks.

[HannesK]

Hello,
I moved the other thread from the locked forum into this one and merged your request.

We count your the request +1, but there is no timeline we can provide on this feature request.

Best regards,
Hannes