In this guide, I am going to show you how to setup and configure Azure backup. Backup is a service offered by Microsoft Azure that we can use to backup our data to the Microsoft Azure cloud. We can use it for Azure-hosted virtual machines (VMs) and on-premises. Backup is founded on the MARS (Microsoft Azure Recovery Services) agent and uses as Backup Service Vault, connected to Azure storage services.
Azure Backup is often used in combined with Azure Site Recovery. Site Recovery is a service we can use to duplicate your data across regions for disaster recovery. Together, Backup and Site Recovery can help us create a comprehensive data loss protection plan.
In the article, we will be seeing the concept of how to create an internal load balancer in Microsoft Azure in between two VM which are hosted in the same network. The reason behind the creation of a load balancer in the VM is to handle the huge number of requests which are given to a virtual machine when it becomes difficult for the VM to handle these.
Once we create two different virtual machines in the same virtual network, proceed to create and configure the load balancer with its set of rules.
Internal Load Balancer in Microsoft Azure
Azure internal load balancer is used to manage & divert the requests from the clients to different virtual machines (VMs) which are discovered in the same network. When a virtual machine receives many requests from the client, there will be some conjunction happening in the VM. To control this conjunction, we can make use of the internal load balancer conception where the requests from the users will be reciprocally shared in between the two different virtual machines which are configured in the VNet. The appeal will be shared in between the VMs position on the configuration set by us when we design a load balancer.
On the Azure portal, select Azure menu bar and then select Virtual Network.
2- Click on create virtual network.
3- Select your subscriptions, to create a resource group then click on create new.
4- Type a recourse group name (rg-loadbalancer) and then click ok.
5- Instance details type a virtual network name (myvnet) select regions (east US) and then click Next : IP Address >.
6- IP Addresses tab, enter 10.0.0.0/8 for the IPv4 Address Space field. Click the + Add subnet button below.
7- Add subnet wizard; enter a Subnet Name (mysubnet) and type 10.0.0.0/24 for Subnet Address range and then click Add.
8- Select Review + Create.
9- Select Create.
10- Virtual network successfully created.
Create Virtual Machines
Create a VM in the virtual network so that we can communicate between them.
1st VM
1- Azure portal menu tab and then choose Virtual machines.
2- Select the + Add button to create virtual machine.
3- Resource group select (rg-loadbalancer).
4- Instance details
Enter a virtual machine name (myvm1) Region select (East US) Availability options select Availability set. Availability set select to create new. Type a name (myavailabilityset) and then click ok.
5- Image select Windows Server 2019 Datacenter. You can choose a different operating system, but the remaining steps assume you selected Windows Server 2019 Datacenter.
6- Administrator account
Enter a username (jamil), Password. Public inbound ports choose to allow selected ports. Select inbound ports (HTTP, HTTPS, RDP) Click Next : Disks > and then click Next + Management >
7- Choose boot diagnostics (off) and then click Review + create.
8- Select create.
Create the second VM
Complete steps 2-8 again, with the following changes.
Name
Value
Resource group
rg-loadbalancer
Virtual machine name
myvm2
Region
(US) West US
Availability options
Availability set
Availability set
myavailabilityset
Image
Windows Server 2019 Datacenter
Administrator account
username password
Public inbound port
allow selected ports
Select inbound ports
HTTP, HTTPS, RDP
Management
boot diagnostics off
Create
Create the third VM
Complete steps 2-8 again, with the following changes.
Name
Value
Resource group
rg-loadbalancer
Virtual machine name
myvmtest
Region
(US) West US
Availability options
Availability set
Availability set
myavailabilityset
Image
Windows Server 2019 Datacenter
Administrator account
username password
Public inbound port
allow selected ports
Select inbound ports
HTTP, HTTPS, RDP
Management
boot diagnostics off
Create
The VMs take a few minutes to complete. Now the VMs (myvm1, myvm2, myvmtest) successfully created.
Now we need to install Web Server IIS roles on VMs (myvm1, myvm2).
Enter the name of Load Balancer (webserverlb) Region (East US) Type Internal and SKU Basic. Virtual network (myvnet) IP address assignment (dynamic) Select Review + create >.
5- Click on Create.
6- Now you can see load balancer successfully created, select your load balancers.
Backend Pools
1- Now click on Backend Pools and then click on + Add.
2- Add backend pool wizard, Type a name Virtual network (rg-loadbalancer) Associate to select virtual machines and then click the add button under a virtual machine.
3- Add virtual machine to backend pool wizard; Select the VMs (myvm1, myvm2) and then click add. The third VM (myvmtest) is for testing Internet load balancing.
4- After selecting the virtual machine, then click on Add.
5- So the backend pool has been configured successfully. Then inside Load Balancer, select Health Probes.
Health Probe
1- Click on + Add.
2- Enter a name to the Health Probe. Protocol (HTTP) The interval shows that it is going to make a probe attempt at 5-second intervals. And the unhealthy threshold shows that after 2 failed probe attempts, it is going to declare it as an unhealthy server. Click ok.
3- Health probe successfully created, click on Load Balancing Rules.
Load Balancing Rules
1- Click on + Add button
2- Add load balancing rule wizard, enter a name The IP version is IPv4 Select frontend IP Address Protocol is TCP, port number is 80 Backend port 80, backend pool is the one that we have just created & the health probe is the one that we have just created. By default Session persistence is none & idle timeout is 4 minutes. Floating IP disabled. Click on OK.
Test Internal Load Balancer in Microsoft Azure
1- Click on load balancer (webserverlb)
2- In the Load Balancer, I have my Private IP address. Copy it and then paste it in the explorer address bar using the third VM (myvmtest).
3- On the first hit, it has taken me to myvm1 server.
4- Wait for 4 minutes then hit enter again, it is take you to myvm2 server.
In this guide, I will show you how to restore/migrate VM Veeam Backup for Microsoft Azure data to the original location. In the previous blog, we restore a virtual machine to a different location. Veeam enables to recover a virtual machine to Azure from the latest recovery point. The main purpose of this feature is disaster recovery. In case of disaster, you can restore virtual machines in Azure.
Restore/Migrate Veeam Backup for Microsoft Azure
Recover Through the Appliance
The auto backup aspect creates snapshots of the instance (virtual machine) that hosts the Veeam Backup for Microsoft Azure solution based on the user-defined schedule. If the present Veeam Backup for Microsoft Azure instance is still recoverable, it can be used to restore from the auto backup snapshot.
Recover Veeam Backup for Microsoft Azure instanceto original location.
1- Choose the Protected Data under management and find the Veeam Backup for Microsoft Azure virtual machine. Choose the Veeam Backup for Microsoft Azure virtual machine; click the Restore tab and then VM Restore on the toolbar.
In this guide, I will explain how to Recovery/Migration VM Veeam Backup for Microsoft Azure data to a new instance. Veeam Backup enables us to restore of a VM (virtual machine) to Azure from the latest recovery point. The main goal of this feature is disaster recovery. In case of failure, you can restore VMs in Azure.
Recover Through the Appliance
The auto backup feature creates snapshots of the instance (VM) that hosts the Veeam Backup for Microsoft Azure solution based on the user defined schedule. If the currently Veeam Backup for Microsoft Azure virtual machine is still useable, it can be used to recover from the auto backup snapshot.
Recovery/Migration Veeam Backup for Microsoft Azure
Restore Veeam Backup for Microsoft Azure instance (virtual machine).
1- Select Protected Data under management and find the Veeam Backup for Microsoft Azure virtual machine.
2- Restore virtual machine wizard, confirm the operation and then click next.
3- I am going to restore to a new location with different settings. Click next.
4- Specify subscription and location, and then click next.
3- Enter a Name for this repository, and then click Next.
Add External Repository; add your Microsoft Azure account for connecting to Azure blob storage container. In this new External Repository step, remember to have correctly configured the network setting of your storage account.
4- Click Add.
5- Type your Azure credentials and then click ok.
6- Select region and then click next.
7- Add the Azure blob storage container that you wish to connect to, click the browse button to select the folder.
8- Click Next.
9- New External Repository click next.
10- Review the configuration under the summary page and then click Finish.
11- Under External Repositories, we can see the newly created repository. As you did not start the policy in the last step of the previous section, we won’t see the VMs that are protected under the policy. In a real organization, all the protected VMs are listed under the repositories.
In this article, I’m going to discuss How to do Veeam Backup to Azure by doing all steps practically. If you are struggling to know the backup process, this article is going to be very helpful for you.
Veeam Backup to Azure is a solution developed for protection & disaster recovery tasks for Microsoft Azure environments. With Veeam Backup and Replication for Microsoft Azure, we can create image level backups of Microsoft Azure VM (Virtual Machines) and then keep them in the Microsoft Azure storage accounts for long-term storage, cost-effective and high availability. Additionally, to image-level backups, we can protect our data by creating and maintaining a chain of cloud-native snapshots of Microsoft Azure VMs.
Veeam Backup for Microsoft Azure features and more details please visit Veeam
How to deploy and setup Veeam Backup to Azure
In this part, we are presenting a complete step by step procedures on the Veeam Backup to Azure. There are 3 critical areas to take action, at Microsoft’s Azure Portal, to deploy the appliance, the Veeam Backup for Microsoft Azure appliance, to configure & enable the services, & finally, the Veeam Backup & Replication console, to connect the service with an on-premise platform if required.
First of all, make sure to create and configure an Azure Storage account, as is required to create the backup containers. One more critical thing to do is to enable the Client IP address to permit access from Veeam to the Azure service. At the end, this configuration is going to permit Veeam to archive on-premises data to Azure. Further specifically, to the Microsoft Azure Blog Storage service.
Microsoft Azure Portal for Veeam Backup
First, we need to log into your Azure account. We are moving to have some options to deploy the Veeam Backup and Replication for Microsoft Azure appliance/VM. 1- Microsoft Azure portal type Veeam backup in the Azure search box and then select the Veeam Backup to Microsoft Azure Free Edition option.
2- Veeam Backup for Microsoft azure free edition, click on the Create button to deploy this Veeam appliance.
3- Select your subscription and a resource group (existing my-rg). If you don’t have created a resource group, then click on create new.
4- Instance details
Virtual machine name – type a name (Veeam server) Region – Select a region Image – select Veeam Backup for Microsoft Azure free edition
Administrator account
Authentication type – select password Username – type a username (Jamil), password and then click Next: Disks >
5- Leave as default in Azure Backup and then click Next: Networking >.
6- Networking tab in Microsoft Azure, choose the options based on your Virtual Network, Subnet, and Public IP. NIC network security group – select advanced and then click Next: Management >
7- Management tab, Monitoring option select boot diagnostics off and then click Review + create for Veeam to Azure Backup.
8- Click Create to start deploying the appliance.
9- Now we see the new Veeam appliance created and then click Go to resource.
10- Copy the public IP address.
11- VM details, properties, monitoring and etc.
Veeam Backup for Azure Appliance
1- Copy its Public IP address (we already copied it). Open your web browser tab and then paste this IP address to access the appliance. Click advanced and then proceed for Veeam to Azure Backup (Ignore the security warning by the web browser).
2- Insert the credentials we previously configured during the creation of this appliance.
3- Accept the Veeam license for Backup
4- This is the first time we access this appliance, we are going to be welcomed by the Getting Started page. There are 4 initial steps that we want to configure to make our Veeam backup service ready to roll. As follows are Add Azure Connection, Workers Configuration, Add Repository, and then create your first policy.
How to Add Azure Account
1- Select Account
2- Select the + Add to start the Add Azure Account wizard.
3- Enter a name this service account, description and then click next.
4- Click next.
5- Copy code and then click on this link to sign in.
6- Paste code here and then click next.
7- Select your Microsoft Azure account.
8- After successfully login to your Azure account, click next.
9- Click next.
10- Review the account summary and then click next.
11- Azure account has been added.
Veeam Backup for Microsoft Azure – Configure a Repository
1- Select Repository under administration.
2- Select the + Add button, to start the Add Repository wizard.
3- Veeam add azure account repository and then click next.
4- Select the cloud account and then click next.
5- Select the storage account and then click next.
6- Select container and click next.
7- You can use an existing folder, in this guide, I am creating a new folder name (Veeam) click next.
8- If you want to enable encryption you can or click next.
9- Review the add repository summary and click finish After these steps, the new Repository is created.
10- Click go to sessions.
11- Review the sessions log.
How to Add Veeam Azure Workers
Under the Getting Started option, is to add workers (as we don’t have any at the moment). Veeam Azure Workers are supplementary Linux-based machines deployed for the scaling purposes and transfer fee reduction.
1- Select Workers and then click on + Add, to add a new worker.
2- New Region Specific Worker Configuration. Follow the below steps to configure this worker. Select region, number of workers instances and click next.
3- Specify network settings, Virtual network, Subnet, network security, and then click Next.
4- Review the workers summary and then click finish.
5- Workers configuration.
How to create first backup policy
1- In this final step, under the Getting Started page need to create a policy click on Create your first policy.
2- Policies page, select the + Add button to start the Add Policy wizard.
3- Type a name of your policy, and click next.
4- Directory, select an Azure Active Directory and then click next.
5- Under the Region tab, select + Add to select the regions we want to back up.
6- This first policy will only be able to backup resources from the selected region here Select a region and then click Next.
7- Click next.
Specify Resources tab, we can either choose all the resources or select specific resources. In these specific resources, we can set a very granular backup.
8- Select + Add and then resource group.
9- Select your resource group and then click next.
10- We have selected our Resource Group as the resource we want to protect during this example. Click next.
11- Exclude Resources step, click the + add button.
12- This option is ideal if we selected a subscription containing several VMs in the previous step, and we do not want to protect all these VMs. Click add.
13- Click next.
Snapshot Settings
14- Snapshot Settings tab, you can enable the creation of snapshots, set the number of restore points, and configure the snapshot schedule. These specify snapshots are suitable when rapid recovery points are needed, as these can be rolled-back quickly. Click next.
15- Backup Settings, we are going to have more configurations to protect our data using the Azure Blob Storage service. For this choice, remember to have the Azure storage account adequately configured. Then, we must select a Backup Repository and configure a schedule. Click on select next to backup repository.
16- Select repository and then click Apply.
17- Click next.
18- Cost Estimation tab, you can have a reasonable assumption and understanding of what is going to be the overall cost based on the amount of time that we are going to keep our backup. Click next.
19- Policy Settings option, an Email notification can be set here. Click next.
20- Review the Summary, check all the policy properties and then click Finish.
Start Backup Job
21- Now our new policy has been created. Some of these steps are optionally such as snapshots and backup settings. Therefore, you can be allowed to create an elegant policy (or policies) that fits our backup needs. The new policy is visible under Management – Policies, Notice that this policy is only rolled out once you click on the Start button. You also have some other options for the policy, Stop, Enable, Disable, Edit, Remove, and etc.
22- It’s in running status.
23- Now the policy is marked now as a Success in Veeam Backup for Azure.
24- Now you can see in the azure portal under you storage container.
Once this appliance is successfully configured, it can be integrated into Veeam Backup & Replication. This consolidation one that provides a single platform for hybrid cloud organizations to manage and migrate cloud workloads.
In this article, I will explain how to create an Azure Storage Account, Container adding this to your Veeam Backup & Replication, and creating a Scale-Out Backup Repository with a performance tier and capacity tier. This new storage tier is called Capacity Tier and it can be coupled with a Scale-Out Backup Repository, which then is the Performance Tier of the tiered solution. Actually, Veeam does not use the new Capacity Tier as a direct target for backup and backup copy jobs, fairly a new mechanism has been introduced. Let see how it works & how then a service provider can design his storage with this new capability. Veeam Cloud Tier enables institutions to natively tier backup files to Microsoft Azure Blob, providing the ability to scale infinitely and leverage the simplicity and elasticity of object storage.
Archive Veeam on-premise data to Azure Blob
Veeam Capacity Tier Cloud Tier
First, we need to create a Microsoft Azure Storage Account to create the cloud repository
How to Add Storage Account as backup repository in Veeam
1- Open the Veeam console, select Backup Infrastructure. Select Backup Repositories and then select Add Backup Repository.
1- In the Veeam console, select Scale-Out Backup Repository and then select Add Scale-Out Backup Repository.
2- Enter a name, a description for this SOBR (Scale-out backup repository) and click on Next.
3- In the performance tier option, click the add button to add your On-Premise backup repositories.
4- I have already created a local backup repository name (Backup Repository cloud). Select your local backup repository and then click OK.
5- Click next.
6- Select Data locality as a placement policy and click next.
7- Choose Azure object storage repository as object storage. Then select the file ages to be moved in Microsoft Azure. Click override.
8- Also you can move files depending on the used space. Choose your choice, click ok and then Apply.
9- Review the summary and click finish
10- Now you can see scale-out backup repository
Create a Backup Job Veeam
1- To create a Backup Job to take advantage of the Immutability feature. Choose the home tab, select backup job, and then virtual machine.
2- Type backup job name and then click next.
3- Virtual machine to backup click the add button
4- Select the object (virtual machine) to backup and then click add
5- Click next
6- In the configuration wizard select from the Backup repository drop-down menu the just created Scale-out Repository (local backup repository) and click next.
7- Click next
8- Click apply
9- Click finish
10- During the first operation, a Full Backup is being performed.
Move backups to Azure Object Storage
If you would like to test the archival process, after the initial Full Backup previously processed, you should perform some additional backups. At least three additional Incremental Backups and one more Active Full Backup.
1- In this picture you can find 2 full backups 3 increments backup.
2- To move backups immediately to the selected Azure Object Storage. Select your Azure scale-out repository and then click edit scale-out repository.
3- Select Capacity Tier option, select Move backup files older than field set to 0, and then click finish.
4- Keep the CTRL button and right-click on your Azure Scale-out Backup Repository and then select Run tiering job now.
5- The offload process is performing and backups are moved to Azure Object Storage. I am testing in my home lab so I am stopping it.
6- Login to Azure Portal and access the Bucket used as Backup Repository. As expected, backup files have been stored in the configured blob storage.
Install Web Server IIS, in this article I going to show you how to install the webserver (IIS) Internet Information Services in Microsoft Windows Server 2019 operating system. Install Web Server IIS, in this article I going to show you how to install the webserver (IIS) Internet Information Services in Microsoft Windows Server 2019 operating system.
Install Web Server IIS
1- Click on Windows start menu and then select Server Manager.
2- Server Manager, Dashboard select Add roles and features.
7- A new window will popup that additional features are required, simply click the Add Features button to install these as well.
8- Select server roles web server iis selected click next.
9- We will not be installing any additional features at this stage click next on the Select features window.
10- Click next
11- Enable webserver IIS Select role services, the window you can install additional services for IIS if required. then Click Next.
12- Confirm installation selections, review the items that are to be installed and then click Install when you are ready to proceed with installing the IIS web server.
13- No reboot required, the installation has succeeded, then click the close button.
Enable IIS Web Server With PowerShell
1- Use the Windows PowerShell command line interface (CLI) instead, follow these steps. Open the PowerShell with admin rights and then run the Install-WindowsFeature cmdlet as shown below. Install-WindowsFeature –name Web-Server -IncludeManagementTools
2- IIS Web Server start installation
3- Web Server feature successfully enabled
Its include the management tools so that we can manage IIS on this server
Public Load Balancers in this blog I am going to show you how to set up a public load balancer in Azure. Distribute the incoming traffic over multiple servers. Here, it will divide up the load over two Virtual Machines.
Create Virtual Machines
Create VMs in each virtual network (VNet) so that we can communicate between them.
1st VM
1- On the Azure portal menu tab, select Virtual machines
4- Type resource group name (rg-web) and then click OK.
5- Instance details Enter a virtual machine name (web1) Region select (East US) Availability options – select Availability set. Availability set select to create new.
6- Enter a Availability set name (loadbalanceset) and then click OK.
7- Image select Windows Server 2019 Datacenter.
You can select a various operating system, but the remaining steps assume you selected Windows Server 2019 Datacenter.
8- Administrator account Enter a username (jamil), Password. Public inbound ports choose to allow selected ports. Select inbound ports (HTTP, HTTPS, RDP) and then click on Review + create >
9- Select create
Create the second VM
10- Complete steps 2-9 again, with the following changes:
Name
Value
Resource group
rg-web
Virtual machine name
web2
Region
(US) West US
Availability options
Availability set
Availability set
loadbalanceset
Image
Windows Server 2019 Datacenter
Administrator account
username password
Public inbound port
allow selected ports
Select inbound ports
HTTP, HTTPS, RDP
Create
11- The VMs take a few minutes to create. Now the both VMs (web1, web2) successfully created.
Create Network Load Balancer
1- Select Microsoft Azure menu bat and then select Load Balancers
4- Enter the name of Load Balancer, select Region (East US), keep it Public and SKU Basic. Set the Public Address. Create new, enter a name (lbpublicip) keep it dynamic and then select Review + create >.
5- Click on Create.
6- Now you can see load balancer successfully created, click on (lbweb)
First, I am going to configure Health Probes for our Load Balancer. So, we want to specify how many servers we want to make the Load Balancer. In the Backend Pools, we specify the servers which we are going to use in the Load Balancer.
Backend Pools
7- Click on Backend Pools and then click on + Add.
8- Add backend pool wizard, Type a name Virtual network (rg-web) Associate to select virtual machines and then click the add button under a virtual machine.
9- Add virtual machine to backend pool wizard; Select the VMs and then click add.
10- After selecting the VMs, then click on Add.
11- The backend pool has been configured successfully. Inside Load Balancer, go to Health Probes
12- Click on Add.
13- Enter a name to the Health Probe. Protocol (HTTP) The interval shows that it is going to make a probing attempt at 5-second intervals. The unhealthy threshold shows that after 2 attempts failed probe, it is going to declare it as an unhealthy server. Click ok
14- Health probe successfully created, click on Load Balancing Rules.
15- Click on + Add button
16- Add load balancing rule wizard, The IP version is IPv4 Select frontend IP Address The protocol is TCP, the port number is 80 Backend port is 80, the backend pool is the one that we have just created and the health probe is the one that we have created. Session persistence is by default – None Idle timeout is by default – 4 minutes. Floating IP disabled. Click on OK.
17- Load Balancing Rule has been created.
Now we need to install Web Server IIS roles on both the VMs (web1, web2)
in this article, I will explore how to connect virtual networks in different Azure regions. This connection is called VNet-to-VNet. VNet-to-VNet connectivity utilizes the Azure virtual network gateways to connect with different Azure regions called (Global VNet peering).
Virtual network connection with different Azure regions
Creating two virtual networks Creating two virtual network gateway Deploy a virtual machine (VM) into each vnet Creating connection with two virtual network gateway Communicate between VMs
4- Instance details Enter a virtual machine name (vmeast) Region select (East US) Image select Windows Server 2019 Datacenter. You can use a different operating system, but the remaining steps assume you selected Windows Server 2019 Datacenter.
5- Administrator account Enter a username (jamil), Password. Public inbound ports choose to allow selected ports. Choose inbound ports (HTTP, RDP) and then click Next : Disks >
6- Click Next : Networking >.
7- Under networking tab, network interface select virtual network (vnet-east) Subnet (east-subnet) and then select the Review + Create button.
8- Click Create.
Create the second VM
Complete steps 2-8 again, with the following changes:
Name
Value
Resource group
rg-vnet
Virtual machine name
vmwest
Region
(US) West US
Image
Windows Server 2019 Datacenter
Administrator account
username password
Public inbound port
allow selected ports
Select inbound ports
HTTP, RDP
Virtual network
vnet-west
Subnet
east-subnet (192.168.1.0/24)
Create
The VMs take a few minutes to create. Now the both VMs successfully created.
Azure Virtual Network Gateway Connection
1- Select Azure menu bar, search virtual network gateway and then click on vng-east.
2- Under Settings Select Connections, and then click + Add, as shown in the below picture.
3- Add Connection wizard, Type a name (east2west) under Name. Under connection type choose VNet-to-VNet. Select second virtual network gateway
4- Choose 2nd virtual network gateway (vng-west).
5- Under Shared key (PSK) type test1 and then click OK.
6- Click on the virtual network gateway to setup connection for 2nd virtual network gateway.
7- Select vng-west 2nd virtual network gateway.
8- Select Connection tab under settings and then click on + Add
9- Add Connection wizard, Type a name (west2east) under Name. Under connection type choose VNet-to-VNet. Select second virtual network gateway
10- Choose virtual network gateway (vng-east).
11- Under Shared key (PSK) type test1 and then click OK.
Note: shared key should be same for both connection.
12- Now you can see both virtual network gateway connections shows connected
If you didn’t see the status connected, click refresh. Note: it will take 15 to 20 minutes.
Communicate Between VMs
Please connect your both VMs (vmeast – vmwest) and then login using your credentials.
Now we need to disable Windows defender firewall on the both VMs. Type Windows defender firewall in Windows Server search bar and then select it.
Select Turn Windows defender firewall on or off.
Turn off private – public network settings and then click OK.
Open command prompt, type ipconfig command to find the first VM (vmeast) IP Address. You can see the IP address is 10.0.1.4 IP Address vmwest (192.168.1.4) pinging from vmeast
Open command prompt, type ipconfig command to find the 2nd VM (vmwest) IP Address. You can see the IP address is 192.168.1.4 IP Address vmesst (10.0.1.4) pinging from vmwest
Virtual Network Peering VNet, in this article, I will explain how to configure virtual network peering within the same Azure region. We can connect VNets to each other with virtual network peering. These vnet to vnet peering can be in the same region or across regions (Global VNet peering).
Virtual network peering – (Connecting virtual networks within the same Azure region) Global virtual network peering – (Connecting virtual networks different Azure regions)
Virtual network peering within same networks
Creating two virtual networks Deploy a virtual machine (VM) into each vnet Connect two VNet with a virtual network peering Communicate between VMs Create virtual networks Create the first vnet
4- Instance details, enter a virtual machine name (vm1), Region (East US), and then choose Image Windows Server 2019 Datacenter. You can choose a different operating system, but the remaining steps assume you selected Windows Server 2019 Datacenter.
5- Administrator account, enter a username (jamil), Password. Public inbound ports choose to allow selected ports. Select inbound ports (HTTP RDP) and then click Next : Disks >
6- Click Next : Networking >
7- Under the Networking tab, network interface select virtual network (vnet1) and then select the Review + Create button.
8- Click Create.
Create the second VM
Complete steps 2-8 again, with the following changes
Name
Value
Resource group
rg-peering
virtual machine name
vm2
region
(US) East US
Image
Windows Server 2019 Datacenter
Administrator account
username password
Public inbound port
allow selected ports
Select inbound ports
HTTP, RDP
virtual network
vnet2
Create
The VMs take a few minutes to create. Now the both VMs successfully created.
Peering Virtual Networks
1- Select Azure menu bat and then select Virtual networks.
2- Click on vnet1
3- Under Settings Select Peerings, and then click + Add, as shown in the below picture.
4- Add peering wizard, Type a name (vnet1tovnet2) under Name of the peering from vnet1 to vnet2. Under Virtual network deployment mode choose Resource manager. Select your subscriptions Under virtual network select vnet2. Under Name of the peering from vnet2 to vnet1, enter a name (vnet2tovnet1)
5- Configure virtual network access settings and then click ok.
6- Vnet1 peering status connected to vnet2
Vnet2 peering status connected to vnet1.
If you don’t see the status connected, click refresh.
Communicate between VMs
1- Select Azure menu bat, then select Virtual machine and then select vm1.
2- Select Connect button and the RDP.
3- Click Download RDP file.
4- To connect to the VM, open the downloaded RDP file and click Connect.
5- Enter the user name and password you specified when creating the VM and then select OK.
6- Select Yes.
7- Click Windows button and click Control panel.
8- Select network and sharing center
9- Select Ethernet
10- Select Details
11- Now you can see vm1 private IP Address.
12- Vm2 IP Address.
We can use the ping command to communicate with the vm2 VM from the vm1 VM. Ping command uses the Internet Control Message Protocol (ICMP), which is disabled through the Windows Firewall, by default.
Disable Windows defender firewall follow the below steps.
1- Under network and sharing center click on Windows defender firewall.
2- Select Windows defender firewall on or off.
3- Turn off private network, public network settings and then click OK.
