1202 m6 Slides v1 1s0 I82onzn

How To Make The Best Use Of Live Sessions
• Please log in 10 mins before the class starts and check your internet connection to avoid any network issues during the LIVE
session
• All participants will be on mute, by default, to avoid any background noise. However, you will be unmuted by instructor if
required. Please use the “Questions” tab on your webinar tool to interact with the instructor at any point during the class
• Feel free to ask and answer questions to make your learning interactive. Instructor will address your queries at the end of on-
going topic
• We have dedicated support team to assist all your queries. You can reach us anytime at: support@edureka.co
• Your feedback is very much appreciated. Please share feedback after each class, which will help us enhance your learning
experience
Copyright © edureka and/or its affiliates. All rights reserved.

Microsoft Azure Administrator
Certification (AZ-104)
COURSE OUTLINE
MODULE 06
01. Managing Azure Subscriptions And 11. Implementing And Managing Hybrid
Resource Groups Identities
02. Azure Virtual Networks And Network

10. Manage Azure Active Directory (AD)
Security
03. Overview Of Azure Virtual Machines 09. Monitoring And Access Management
For Cloud Resources
08. Integrate On-premises Network With

04. Overview Of Azure Storage Services
Azure Virtual Network
07. Network Traffic Distribution And

05. Secure And Manage Azure Storage Connectivity
06. Configure Virtual Machines For High

Availability
Recap

Module 6 – Configure Virtual Machines
For High Availability

Topics
Following are the topics covered in this module:
▪ Azure Virtual Machine Storage

▪ Azure Virtual Machine Availability
▪ Fault and Update Domains
▪ Azure Load Balancer
▪ Automatic Scaling of Azure VMs
▪ VM Scale Sets
▪ Azure VM Backup
▪ Azure VM Monitoring with Azure Diagnostics Extension
▪ Azure Advisor

Objectives
After completing this module, you should be able to:
▪ Configure VM storage options
▪ Implement VM high availability
▪ Configure load balancer
▪ Implement scalability of VMs
▪ Backup and restore VMs
▪ Monitor and diagnose VM health
▪ Understand Azure Advisor

Azure Virtual Machine Storage

Azure Virtual Machine Storage
Just like any other computer, virtual machines in Azure use disks as a
place to store an operating system, applications, and data
All Azure VMs have at least two disks – a Windows OS disk and a temporary disk
The OS disk is created from an image, and both the OS disk and the image are
virtual hard disks (VHDs) stored in an Azure storage account
VMs also can have one or more data disks, that are also stored as VHDs

Disks Used By VMs
Operating System Disk
Disk 1 Disk 2 Disk 3
Temporary Disk
OS Disk Temporary Disk Data Disk
Maximum capacity of 2048 GB (Contents can be lost)
Data Disk Attach SSD/HDD up-to 4TB
SSD/HDD and size depends
and These are .vhd files
on VM chosen
Disk Cache
Azure Blob
Max size of single blob container 500 TB storage

Disks Used By VMs – OS Disk
Operating System Disk Every VM has one attached OS disk that is
registered as a SATA drive and labelled as the C: drive by default
Temporary Disk
This disk has a maximum capacity of 2048 gigabytes (GB)

Data Disk
Disk 1
OS Disk
Maximum capacity of
2048 GB
Disk Cache

Disks Used By VMs – Temporary Disk
Each VM contains a temporary disk that provides short-term storage for applications
and processes and is intended to only store data such as page or swap files
Temporary Disk
The temporary disk is labelled as the D: drive by default and it used for storing
Data Disk pagefile.sys
Data on the temporary disk may be lost during a maintenance event or when
you redeploy a VM but should persist during a standard reboot
Disk 2
Temporary Disk
(Contents can be lost)
SSD/HDD and size

depends on VM chosen

Disks Used By VMs – Data Disk
A data disk is a VHD that is attached to a VM to store application data,
or other data you need to keep
Temporary Disk
Data Disk Each data disk has a maximum capacity of 4095 GB
The size of the VM determines how many data disks you can
attach to it and the type of storage you can use to host the disks
Disk 3
Data Disk
Attach SSD/HDD up-to 4TB

and these are .vhd files

What Are Virtual Hard Disks (VHDs)?
The VHDs used in Azure are .vhd files stored as page blobs in a standard or
premium storage account in Azure
Azure VHD files used as a source to create disks or images are read-only, except
the .vhd files uploaded/copied to Azure storage by the user
When A VM is created from an image, Azure creates a disk for the VM that
is a copy of the source .vhd file
To delete a .vhd file that is being used by a VM as an OS disk, you can delete
the VM, the OS disk, and the source .vhd file all at once
To delete a .vhd file that’s a source for a data disk first requires you to detach
the disk from the VM, then delete the disk, and then delete the .vhd file

Types Of Disks
Standard HDD Disks Standard SSD Disks Premium SSD Disks
Can be replicated locally in one datacenter, Offer more consistent performance, Backed by SSDs, and delivers high-
or be geo-redundant with primary and reliability and a cost-effective solution than performance, low-latency disk support for
secondary datacenters HDD, currently only available with the locally VMs running I/O-intensive workloads
redundant storage (LRS) resiliency type
Unmanaged Disks Managed Disks Standard HDD Disks
Create your own storage account and These handle the storage account
specify it when you create the disk, creation/management in the background for
maximize the use of storage accounts to get you, so you do not have to worry about the
the best performance out of your VMs scalability limits of the storage account

Demo 1: Attach A Managed Data Disk To
A Windows VM
Note: Refer to Module-6 Demo1 Document on LMS for all the steps in detail

Demo 2: Initialize A New Data Disk

Azure Virtual Machine Availability

Storage Availability
Depending on the storage type, you have different available storage replication options:
Azure Managed Disks Locally-redundant storage (LRS)
Storage Account-based Disks Locally-redundant storage (LRS)
Zone-redundant storage (ZRS)
Geo-redundant storage (GRS)
Read-access geo-redundant storage (RA-GRS)

Storage Costs
Prices vary depending on the storage type and availability that you select.
• Premium Managed Disks are backed by Solid-State Drives (SSDs)

Azure Managed Disks • Standard Managed Disks are backed by regular spinning disks
• Both are charged based on the provisioned capacity for the disk
• Premium storage is backed by Solid-State Drives (SSDs) and is

charged based on the capacity of the disk
Azure Unmanaged Disks
• Standard storage is backed by regular spinning disks and is charged
based on the in-use capacity and desired storage availability.

Understanding VM Reboots
There are three scenarios that can lead to virtual machine in Azure being impacted:
Unplanned Hardware Unexpected Planned

Maintenance Downtime Maintenance Events
• Occurs when the Azure • Occurs when the physical • Periodic updates made by
platform predicts that a infrastructure for the VM fails Microsoft to Azure platform to
component, is about to fail unexpectedly improve overall reliability,
• When predicted, it will issue • When detected, Azure platform performance, and security of the
an unplanned hardware automatically migrates (heals) infrastructure that VMs run on
maintenance event to reduce your VM to a healthy physical
the impact to the VMs machine in the same datacenter

What Are Availability Sets?
They are logical grouping of VMs within a datacenter that allows Azure to
understand how your application is built to provide for redundancy and availability
They don’t cost anything itself, you only

pay for each VM instance that you create
Each set has additional groupings that protect against hardware failures
and allow updates to safely be applied: Fault Domains and Update Domains
Each VM in an availability set is assigned a different fault and update domain

Introduction To Fault Domains
Fault domains define the group of virtual machines that share a common power
source and network switch
By default, the VMs configured within your availability set are separated across
up to three fault domains for Resource Manager deployments

Fault Domains
▪ Consider there are two Fault Domains and two separate VMS are deployed on them
▪ As you boot VMs in to an availability set, they get allocated like this – FD0, FD1, FD0, FD1, FD0, FD1 and so on
FAULT DOMAIN FAULT DOMAIN

RACK RACK
VM VM
Availability Set
IIS1 IIS2
VM VM
Availability Set SQL1
SQL1

Fault Domains
You can see IIS1 and IIS2 are the web-front end. They’re both in different fault domains. If something happens to
the power going to rack 1, IIS1 will fail and so will SQL1 but the other 2 servers will continue to operate.
• If more servers are added to each availability set, Azure

FD0 FD1 continues to distribute them across fault domains
RACK RACK
• As shown below, 4 IIS VMs are allocated to FDs in the
VM VM order in which they boot. So if these systems are booted
Availability in reverse order then they’d all be in different FDs
IIS1 IIS2
Set
IIS3 IIS4
VM Fault Domain
VM VM
IIS1 0
SQL1 Availability SQL2
IIS2 1
Set
SQL3 SQL4 IIS3 0
IIS4 1

Introduction To Update Domains
For a given availability set, five non-user-configurable update domains are
assigned by default
The order of update domains being rebooted may not proceed sequentially
during planned maintenance, but only one update domain is rebooted at a time
A rebooted update domain is given 30 minutes to recover before maintenance

is initiated on a different update domain

Update Domains
▪ FDs are assigned in the pattern 0, 1, 0, 1, 0, 1, 0, 1….
▪ UDs are assigned 0, 1, 2, 3, 4, 0, 1, 2, 3, 4, 0, 1, 2, 3, 4….
▪ Both FDs and UDs are assigned in the order that Azure discovers them as they are provisioned
▪ The following table shows machines provisioned in the order Srv0, Srv1, Srv2….
VM Fault Domain Update Domain

Srv0 0 0
Srv1 1 1
Srv2 0 2
Srv3 1 3
Srv4 0 4
Srv5 1 0
Srv6 0 1
Srv7 1 2
Srv8 0 3
Srv9 1 4
Srv10 0 0
Srv11 1 1
You can see that UDs loop around a count of 5 (0, 1, 2, 3, 4)

Microsoft Azure’s Best Practices For High Availability
Configure multiple virtual machines in an availability set for redundancy
Configure each application tier into separate availability sets
Combine a Load Balancer with availability sets
Use Scheduled Events to proactively response to VM impacting events
Use managed disks for VMs in an availability set
Use availability zones to protect from datacentre level failures

Availability Zones
An Availability Zone is a physically separate zone within an Azure region
There are three Availability Zones per supported Azure region –

Each Availability Zone has a distinct power source,
network, and cooling
If one zone is compromised, then replicated apps and data

are instantly available in another zone

Dividing Application Tiers Into Separate Availability Sets
Why A Separate Availability Set is needed ?
▪ If you place two different tiers in the same availability set, all VMs in the
same application tier can be rebooted at once
▪ By configuring at least two VMs in an availability set for each tier, you
guarantee that at least one VM in each tier is available

Azure Load Balancer

What Is A Load Balancer?
A device that acts as a reverse proxy and distributes network or
application traffic across a number of servers
Used to increase capacity (concurrent users) and reliability of applications
Ensures reliability and availability by monitoring the health of applications and

only sending requests to servers that can respond in a timely manner
Improves the overall performance of applications by managing and

maintaining network sessions and performing application-specific tasks Azure Load Balancer

What Is A Load Balancer?
Working of Load Balancer
Layer 4 load balancers act upon data found in network and transport layer
protocols (IP, TCP, FTP, UDP)
Layer 7 load balancers distribute requests based upon data found in

application layer protocols such as HTTP

What Is Azure Load Balancer?
Azure Load Balancer performs Layer 4 load balancing within a virtual network
It delivers high availability and network performance to your applications
It distributes incoming traffic among healthy instances of services

defined in a load-balanced set
It supports two different types: Basic and Standard

Azure Load Balancer

Azure Load Balancer Resources
Frontend IP addresses, known as a virtual IPs (VIPs) that
Front-end IP Configuration
serve as ingress for the traffic to the load balancer
IP addresses associated with the VM Network

Back-end Address Pool
Interface Card (NIC) to which load is distributed
A rule property maps a frontend IP and port combination

Load Balancing Rules
to a set of backend IP addresses and port combination
Keep track of the health of VM instances so that if

Health Probes
a probe fails, the VM instance is taken out of rotation
NAT rules define the inbound traffic flowing through

Inbound NAT Rules
the frontend IP and distributed to the backend IP

Why Do We Need Azure Load Balancer?
You can use Azure Load Balancer to:
▪ Load-balance incoming internet traffic to your VMs
– This configuration is known as a Public Load Balancer
TCP Port 80
80 80 80
This figure shows a load-balanced endpoint for web traffic that is

shared among three VMs for the public and TCP port 80
These three VMs are in a load-balanced set

▪ Load-balance traffic across VMs inside a VNet
– This configuration is known as an Internal Load balancer
Public Load Balancer
Web Tier
Subnet
Internal Load Balancer
DB Tier
This figure shows load balancing multi-tier applications by using Subnet
both public and internal Load Balancer

▪ Port forward traffic to a specific port on specific VMs with
inbound NAT rules
▪ Provide outbound connectivity for VMs inside your VNet by
using a Public Load Balancer
Azure Load Balancer

Features Of Azure Load Balancer
Hash Based Distribution Port Forwarding Source NAT (SNAT)
This algorithm is a 5-tuple hash Provides control over inbound Dynamically maps the private IP
composed of source IP, source communication management that address to a public IP address
port, destination IP, destination includes traffic initiated from when an instance initiates an
port, and protocol type to map Internet hosts, VMs in other cloud outbound flow to a destination in
traffic to available servers services, or VNets the public IP address space
Service Monitoring Automatic

Probes the health of server Reconfiguration
instances and when a probe fails When you scale instances up or
to respond, the load balancer down, Azure load balancer
stops sending new connections reconfigures itself instantly
to the unhealthy instances

Demo 3: Configure Azure Load Balancer

Automatic Scaling Of Azure VMs

Horizontal And Vertical Scaling Of VMs
Horizontal Scaling
Horizontal Scaling
Horizontal Scaling refers to increasing (out) or
decreasing (in) the number of VMs
You scale horizontally by either automatically or manually

changing the capacity or instance count of the scale set
Vertical Scaling
Makes the VMs more (up) or less (down) powerful in attributes
such as memory, CPU speed, or disk space
Dependent on the availability of larger hardware, which

quickly hits an upper limit and can vary by region
Vertical Scaling

What Are Virtual Machine Scale Sets?
Azure VM scale sets let you create Enable large-scale services for
and manage a group of identical, areas such as compute, big data,
load balanced VMs and container workloads
Provide high availability to apps Number of VM instances can

and allow central management, automatically increase/decrease
configuration, and updation with demand or schedule
Virtual Machine
Scale Sets

Benefits Of Using Virtual Machine Scale Sets
Easy to create and manage Provides high availability and

multiple VMs application resiliency
Allows your application to

automatically scale as resource Works at large-scale
demand changes

Demo 4: Create A Virtual Machine
Scale Set

Azure VM Backup

How Backup Process Works?
Service triggers the backup

After the snapshot is taken, the data
extension that is installed
is transferred to the vault
during the first VM backup
01 02 03 04 05
A backup job is initiated for the The backup extension takes a When data transfer is complete,
selected VMs as per the backup storage-level, app-consistent the snapshot is removed and
schedule you specify snapshot a recovery point is created

Service And Subscription Limits
Limit Default
Windows Server/Windows Client/System Center DPM: 50

Servers/machines that can be registered in a vault
IaaS VMs: 1000
54400 GB maximum. The limit doesn't apply to IaaS VM

Size of a data source in vault storage
backup
Backup vaults in an Azure subscription 500 vaults per region
Windows Server/Client: 3 a day

Schedule daily backups System Center DPM: 2 a day
IaaS VMs: Once a day
Data disks attached to an Azure VM for backup 32

Individual data disk attached to Azure VM for backup
4095 GB

Various Backup Considerations
Backup operation optimizes by backing up each of the

Disk Considerations
VM’s disk in parallel
Backup scheduling impacts performance, so to reduce the backup traffic,

Scheduling Considerations
back up different VMs at different time of the day, with no overlap
Page blobs
A restore operation consists of two main tasks: copying data back from
Restore Considerations
the vault to the chosen storage account, and creating the VM

Various Backup Considerations
Time Considerations
While most backup time is spent reading and copying data, other operations add to the total time needed to back up a VM:
01 04
Time taken to trigger a snapshot Data transfer time to the
vault storage
03
Time needed to install or update
the backup extension
02 05
Queue wait time for multiple Time needed for initial backup
Backup service processes jobs depending on size of the data

Demo 5: Configure Azure VM Backup

Demo 5: Configure Azure VM Backup
Create a recovery services vault
Set the backup policy
Enable virtual machine backup
Verify virtual machine backup
Azure VM Backup

Demo 6: Start A VM Backup Job

Demo 6: Start A VM Backup Job
You can wait for the default policy to run the backup at the scheduled time
or start it yourself whenever you want
This initial backup job creates a full recovery point
Each backup job after this initial backup creates incremental recovery points
and only transfer changes made since the last backup
Azure VM Backup

Demo 7: Restore An Azure VM From
Recovery Services Vault

Delete A VM
1. After the successful backup of your Virtual Machine, you can Restore it from the Recovery Service vault
You can delete your

VM before you
restore it from your
vault by selecting
your VM and clicking
on delete

Restore The VM From Recovery Service Vault
2. In the Recovery Services vault, click on Backup Items in the menu > then click on the item you want to
restore, that is a Virtual Machine in this case

3. You can see that the VM has been successfully backed up, right-click on it and choose Restore VM

4. In the Restore blade, select the Restore
point(s) > click OK

5. In the Restore configuration blade, select whether you want to
create a new VM or replace existing
6. Select the Restore Type, VM Name, Resource Group, Virtual

Network, Subnet and Storage Account
7. Click OK

Verify The Restore
8. You can check the status of the Restore by going to the Backup
Jobs option on the Recovery Services vault menu

Connect The VM
9. Go to your VM and connect it to further verify that the restore job has been successfully completed

Azure VM Monitoring With Azure
Diagnostics Extension

Azure VM Monitoring And Diagnostics
Azure IaaS monitoring involves:
Providing diagnostic data to help

Collecting and tracking metrics
in troubleshooting 06 01
Triggering alarms when certain 05 02 Analysing log files

conditions are met
04 03
Logging generated by specific
Defining custom metrics
workloads running in VMs

Enable Monitoring On Portal
➢ Select the VM > In the Monitoring section,
click Diagnostics settings > Select the
diagnostics metrics needed > Click Save

Azure Diagnostics Extension
▪ The Azure Diagnostics Extension provides the monitoring and diagnostics capabilities on a Windows-based
Azure VM
▪ Enable these capabilities on the VM by including the extension as part of the Azure Resource Manager
template

Demo 8: Use Linux Diagnostic Extension
To Monitor Metrics And Logs

Demo 9: Enable Azure Diagnostics In
Windows VM With PowerShell

Azure Advisor

What Is Azure Advisor?
Azure Advisor is a personalized cloud service that helps an organisation follow
best practices to optimize Azure deployments
It provides cost saving opportunities by analysing the usage of your resources
It recommends solutions to improve the high availability of your resources
It analyses resource configuration to help upgrade the performance and security

of resources

Getting Started With Azure Advisor
▪ Sign in to Azure Portal and in the left pane, click Advisor
The Advisor dashboard displays personalized recommendations for all your
subscriptions that are divided into four categories

Filter Recommendations
▪ You can filter recommendations by subscription, resource type, or status to drill down to what is most
important to you

Get Advisor Recommendation Details
▪ You can click a category to display the list of recommendations within that category, and select a
recommendation to learn more about it

Postpone Or Dismiss Recommendations
▪ Navigate to the recommendation you want to postpone or dismiss, clock on it > click Postpone
▪ Specify a postpone time period, or select Never to dismiss the recommendation

Exclude Recommendations
▪ Go to the Advisor > click Configure in
the action bar > then uncheck any
subscriptions or resource groups for
which you do not want to receive
Advisor recommendations > click on
Apply

Configure CPU Utilisation For Low Usage
▪ Go to the Advisor > click Configure in the action bar > click on Rules > select the subscriptions you’d like to
adjust the average CPU utilization rule for, and then click Edit
▪ Click Refresh recommendations to update your existing recommendations and click Apply

Download Your Advisor Recommendations
▪ Go to the Advisor > click Download as CSV or Download as PDF in the action bar

Summary


1202 m6 Slides v1 1s0 I82onzn

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1202 m6 Slides v1 1s0 I82onzn

Uploaded by

Copyright:

Available Formats

How To Make The Best Use Of Live Sessions

Copyright © edureka and/or its affiliates. All rights reserved.

02. Azure Virtual Networks And Network

08. Integrate On-premises Network With

07. Network Traffic Distribution And

06. Configure Virtual Machines For High

Copyright © edureka and/or its affiliates. All rights reserved.

Copyright © edureka and/or its affiliates. All rights reserved.

▪ Azure Virtual Machine Storage

Copyright © edureka and/or its affiliates. All rights reserved.

▪ Configure VM storage options

▪ Implement VM high availability

▪ Configure load balancer

▪ Implement scalability of VMs

▪ Backup and restore VMs

▪ Monitor and diagnose VM health

▪ Understand Azure Advisor

Copyright © edureka and/or its affiliates. All rights reserved.

Copyright © edureka and/or its affiliates. All rights reserved.

Copyright © edureka and/or its affiliates. All rights reserved.

Copyright © edureka and/or its affiliates. All rights reserved.

This disk has a maximum capacity of 2048 gigabytes (GB)

Copyright © edureka and/or its affiliates. All rights reserved.

SSD/HDD and size

Copyright © edureka and/or its affiliates. All rights reserved.

Data Disk Each data disk has a maximum capacity of 4095 GB

Attach SSD/HDD up-to 4TB

Copyright © edureka and/or its affiliates. All rights reserved.

Copyright © edureka and/or its affiliates. All rights reserved.

Unmanaged Disks Managed Disks Standard HDD Disks

Copyright © edureka and/or its affiliates. All rights reserved.

Copyright © edureka and/or its affiliates. All rights reserved.

Copyright © edureka and/or its affiliates. All rights reserved.

Copyright © edureka and/or its affiliates. All rights reserved.

Azure Managed Disks Locally-redundant storage (LRS)

Storage Account-based Disks Locally-redundant storage (LRS)

Zone-redundant storage (ZRS)

Geo-redundant storage (GRS)

Read-access geo-redundant storage (RA-GRS)

Copyright © edureka and/or its affiliates. All rights reserved.

• Premium Managed Disks are backed by Solid-State Drives (SSDs)

• Premium storage is backed by Solid-State Drives (SSDs) and is

Copyright © edureka and/or its affiliates. All rights reserved.

Unplanned Hardware Unexpected Planned

Copyright © edureka and/or its affiliates. All rights reserved.

They don’t cost anything itself, you only

Each VM in an availability set is assigned a different fault and update domain

Copyright © edureka and/or its affiliates. All rights reserved.

Copyright © edureka and/or its affiliates. All rights reserved.

FAULT DOMAIN FAULT DOMAIN

Copyright © edureka and/or its affiliates. All rights reserved.

• If more servers are added to each availability set, Azure

Copyright © edureka and/or its affiliates. All rights reserved.

A rebooted update domain is given 30 minutes to recover before maintenance

Copyright © edureka and/or its affiliates. All rights reserved.

VM Fault Domain Update Domain

Copyright © edureka and/or its affiliates. All rights reserved.

Configure each application tier into separate availability sets

Combine a Load Balancer with availability sets

Use Scheduled Events to proactively response to VM impacting events

Use managed disks for VMs in an availability set

Use availability zones to protect from datacentre level failures

Copyright © edureka and/or its affiliates. All rights reserved.