SureBackup Job w/ Replica's and Re-IP

[mwpreston]

Hi,

Is there any current support of future intentions of using the Re-IP functionality inside of the SureBackup job when dealing with replica's? Problem is we have a live DC at our DR site and I would like to use either a replica or backup of it for authentication inside of our virtual labs - however all VMs inside the app group still maintain their IP and DNS settings from the prod site - I'd like to have all of the Re-IP functionality take place (to point to my DR DC) just as it does during a failover....

Or if anyone has any ideas on how else I can achieve this I'd love to know...aside from scripting a DNS change inside of the SureBackup script test I'm not sure what else I can do....

Thanks...
Mike

[honeybadgerIT]

I have been playing with the SureReplica as well and I am trying to setup a DR sandbox with the VM's that we replicate to our DR site. It's a different subnet on the DR side, which I have in the re-ip of the replication job. I was actually surprised that when I tried to run the SureBackup with the replicas that it was trying to use the IP from production, and then failing the ping test.

It would be very handy to have them boot with the IP that they would have in DR. I guess I will be manually changing them for all 8 servers.

[Vitaliy S.]

Hi Mike,

I have heard a similar queries from our SE team, so thanks for the feedback. As a workaround for now you can backup the production DC and use it in SureReplica jobs.

Thanks again!

[dave_lub]

As this post is fairly old, is there already a solution to apply the re-ip rules in a surebackup job?

[foggy]

No, SureBackup/SureReplica do not support re-IP, re-IP rules are applied during failover/failback only.

[jim3cantos]

No, SureBackup/SureReplica do not support re-IP, re-IP rules are applied during failover/failback only.

Just discovering this now. As said above, It would be very handy to have the replicas boot with the IP that they would have in DR.

[Vitaliy S.]

Hi Jose, thanks for your FR. Right now, you may want to consider changing the IP address via a SB script after the initial boot of the VM.

[Cragdoo]

I have a successful replication job running, and part of the job is to re-ip the Prod VMs. I am now trying to setup a SureBackup job over at the DR side, and wondering if the VMs will have the 'new' IP applied when they power up, as part of the SureBackup Job , or will they still have the 'old' IP addresses ?

[veremin]

"Old" IP addresses.

[Cragdoo]

Thanks Vladimir ...chalk me down for a +1 on the re-ip for SureReplica request

[HannesK]

+1 from me.

[skrause]

I would like to add to this FR.

I am currently in the process of replicating all of my production VMs back from my DR site after two weeks running in DR due to a major network/hardware failure in the production site and would like to make sure that all my Re-IP rules work as intended and that the VMs are usable when the time comes to do the Permanent Failback.

[skrause]

So I am in the gloriously un-fun process of copying back all of my application servers from my DR site to my Production site and need to run Sure Replica jobs against the replica VMs to make sure that they are functioning as best I can before we can fail back.

As I am setting these up I am running into a problem. I understand that Re-IP is part of the failover plan and not the replication job. That is fine, I can live with that. But the fact that the network adapter change is part of the replication job means that I have no way of doing any ping related tests without manual intervention. I had initially had the nifty idea of adding a network mapping for the original site into the virtual lab configuration so the IP on the VM would work, but that doesn't work because the VM is mapped to the other network. My workaround now will probably be to change the IP/gateway settings on the Virtual Lab to reflect the incorrect network for this testing purpose.

What would be nice is an option to either run a Re-IP script during a sure-replica job or one to map the NICs on the VMs in the job to a specific "test" network so that the verification steps can be done.

[micoolpaul]

As I haven't found anything newer saying this is a feature, are there any intentions for this? Would be incredibly handy for customers that have failover plans but want to confirm their failover plan will work as expected (no host files/static IP address bindings to services etc).

Sorry for reviving such an old topic...

[foggy]

Hi Michael, this is currently not high enough on the priority list. But thanks for the feedback anyway.

[gummett]

FYI I understand labs in Veeam Availability Orchestrator do use the DR-site IPs, if that helps

[lukejf]

Yep, +1 for this. Just came across this today and would be a very handy feature.