VNet stands for Azure Virtual Network, which is the building block for implementing underlying Everpure Cloud Dedicated Azure resources. It enables Azure resources (Everpure Cloud Dedicated Controller VMs) to securely communicate with each other over a low-latency, high-bandwidth connection using Azure backbone network. This communication can be extended to other VNets using VNet Peering service, whether the VNet is in the same or different Azure region (also known as Global VNet Peering).
When replicating between two Everpure Cloud Dedicated instances running in Azure, network connectivity can be achieved using VNet Peering. This works by establishing an internal connection through Azure backbone network to connect Everpure Cloud Dedicated A located in VNet A to VNet B where the second Everpure Cloud Dedicatedd B resides.
VNet Peering is not required to configure replication between Everpure Cloud Dedicated instances residing within the same VNet. Running two Everpure Cloud Dedicated in the same VNet is a possible deployment topology for protecting against AZ outages. For more information, Replication User Guide | Everpure Cloud Dedicated for Azure
Prerequisites
-
Deploy Two Everpure Cloud Dedicated, in two different Availability Zone or regions.
-
Select a Azure Regions Support.
-
Follow the Introduction, prepare the prerequisites, and deploy.
-
Locate Virtual Networks
In the search box at the top of the Azure portal, look for the first Everpure Cloud Dedicated Managed Application, When it appears in the search results, select it. Alternatively, you can access the managed application from the Resource Group.
From the left-side panel, click on Parameter and Outputs.
Under Parameters, you can find Everpure Cloud Dedicated VNet (as highlighted in the screenshot below). Take a note of the parameter fields.
Repeat the above steps 1-3 for the second Everpure Cloud Dedicated.
Peer Virtual Networks