Book Image

Microsoft Azure Infrastructure Services for Architects

By : John Savill
Book Image

Microsoft Azure Infrastructure Services for Architects

By: John Savill

Overview of this book

With Microsoft Azure challenging Amazon Web Services (AWS) for market share, there has been no better time for IT professionals to broaden and expand their knowledge of Microsoft’s flagship virtualization and cloud computing service. Microsoft Azure Infrastructure Services for Architects: Designing Cloud Solutions helps readers develop the skills required to understand the capabilities of Microsoft Azure for Infrastructure Services and implement a public cloud to achieve full virtualization of data, both on and off premise. Microsoft Azure provides granular control in choosing core infrastructure components, enabling IT administrators to deploy new Windows Server and Linux virtual machines, adjust usage as requirements change, and scale to meet the infrastructure needs of their entire organization. This accurate, authoritative book covers topics including IaaS cost and options, customizing VM storage, enabling external connectivity to Azure virtual machines, extending Azure Active Directory, replicating and backing up to Azure, disaster recovery, and much more
Table of Contents (18 chapters)
Free Chapter
About the Author
End User License Agreement

Availability 101

There are many aspects to availability and it’s important to understand how the aspects fit together to architect the right solution for your organization.

Distinguishing High Availability vs. Disaster Recovery vs. Backup

Before examining solutions for availability, it’s important to understand which type of availability we need and the architectural decisions and technologies that will be leveraged. Note that we often don’t pick; we often need all three of the types of resiliency I am going to cover. You will hear about RPO and RTO when discussing backups, high availability, and disaster recovery, which relate to:

Recovery Point Objective (RPO) The recovery point in the event of an incident—i.e., how much data can be lost, e.g., 30 minutes (for unplanned incidents; planned incidents ideally would suffer no data loss)

Recovery Time Objective (RTO) The amount of time it takes to activate the resiliency and be up and running—that is...