Alan_ORiordan wrote:After undoing failover all returned to normal, the replica was powered down by Veeam and DNS was sorted out at the LIVE (source) site and DR site. I had to power back on the source VM presumably because that was the state it was in when it was failed over.
Also why did the failed over DNS A record not replicate back to Live if it was in the DR DC's AD integrated DNS forward lookup file?
Alan_ORiordan wrote:I used undo failover on this occasion. I will test failback to production next. I need get a feel for how long it will take to failback production machines following our first DR test using Veeam over a 10MBit link.
Alan_ORiordan wrote:I can understand that the server would register its Re-IP'd settings on it's boot up at DR but not why that change would then not be replicated back to other sites DNS servers just removed? Perhaps that is an issue for my own separate research, it's just when you said i should "configure DNS on failover manually" that had me wondering what you meant, I understood that as manually re-creating new A records for failed over machines which could get messy if not careful.
rstuart wrote:Do you mean adding a second static DNS record for the each VM?
Users browsing this forum: Bing [Bot], Google [Bot] and 25 guests