Hello!
Currently we are in a middle of a project, that include VMs Migration to Azure via public endpoints.
If I configured Express Route right now with Microsoft and Private Peering, then is this going to effect my replication job, and future Failover test?
If you have any article that can save my life while configuring expressroute or confirm my fear so I can share it with customer to delay the process.
Hi @JanNuaman-2253 ,
how are you migrating the VMs to Azure via public endpoints (which replication technology/feature are you using)?
The Express Route is a new on? Or are modifying/changing an existing ExpressRoute?
In various migration projects with customers we used Azure Migrate for VM migration. We never had a conflict/issue with the ExpressRoutes and Azure Migrate replication.
Just be a little bit careful if you work on routing tables and routes ;-)
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
@AndreasBaumgarten
I am using Azure Migration Appliance to Migrate VMs on non-supported hosts and Physical Servers.
I didn't create the ExpressRoute, but our customer want to enable it today.
So as I understood from you, enabling ExpressRoute now and providing SKey to circuit provider will not cause replication issue. However, after creating the ExpressRoute, I should be careful when configuring Private & Microsoft Peering?
Hi @JanNuaman-2253 ,
as long as the routing of the Azure Migration Appliance is still take the same route as before there should be no difference if the ExpressRoute Circuit is active or not.
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
25 people are following this question.
