Currently, our VA and IQService are hosted in a separate VNet, isolated from the rest of our company resources. We’ve now been asked by our organization to migrate both servers into the same Azure Virtual WAN (vWAN) environment where the rest of our resources reside.
Has anyone implemented a similar setup? If so, could you please share any key considerations or potential pitfalls we should be aware of before proceeding?
Additionally, we’d like to confirm whether it’s possible to move the existing VA into the vWAN. From what I understand, this might require deploying a new VA instance within the vWAN and reconfiguring it from scratch.
Any insights or suggestions would be greatly appreciated
When migrating a Virtual Appliance (VA) and IQService to an Azure Virtual WAN environment, there are several important considerations to keep in mind:
Migrating existing VAs to a different deployment method or location is not supported. Instead, you will need to create new VAs in the Azure environment.
It’s recommended to maintain a 1:1 ratio of VA to VM to avoid a single point of failure in your environment.
After setting up the new VA in Azure, you’ll need to configure it for your environment, including setting up TLS communication between the VA and IQService if required. Remember to update any necessary configurations, such as source connections and network settings, to reflect the new Azure Virtual WAN environment.
We are planning to deploy a new Virtual Appliance (VA) along with a new service, using a fresh IQService installation on a new server while keeping the existing setup unchanged. This way, if the new setup does not perform as expected, we’ll have the option to revert to the original configuration.
Reason for deploying a new IQService:
With the new VA, the IQService server and the VA will be located in different zones or networks. If we were to move the existing IQService and encounter issues, it could be challenging to roll back to the old setup.
Please let us know if this approach seems appropriate to you.