Backup / DR / BC
This course provides an introductory tour of Azure Storage Solutions such as its SQL offerings (SQL DB and third-party offerings of MySQL), managed NoSQL databases (DocumentDB and MongoDB), managed Redis Cache service, Azure Backup (backup-as-a-service), Site Recovery (for handling disaster recovery) and StorSimple (a hybrid cloud storage solution).
- Understand what SQL DB is and how to get started using it
- Learn the options offered by Azure for managed MySQL
- Understand what DocumentDB and MongoDB are and how to get started using them
- Learn what Redis Cache is and some cases of when you would use it
- Get an understanding of what Azure Search provides
- Learn how Azure Backup can solve common backup needs
- Understand what role Site Recovery can play in disaster recovery
- Learn how StorSimple can extend your on-premise storage capacity
- This course is for developers or IT professionals looking for an introduction to Azure’s Storage Solutions
- Some familiarity with the Azure platform is helpful, but not required
- Course Introduction
- Azure SQL Database
- What is Azure SQL Database?
- Understanding the service tiers
- Create a SQL Database
- What is a Data Throughput Unit (DTU)?
- Scaling Azure SQL
- Options for Using MySQL in Azure
- Azure CosmosDB DocumentDB API
- What is DocumentDB?
- Azure CosmosDB MongoDB API
- Options for Using MongoDB in Azure
- How does DocumentDB compare to MongoDB?
- Azure Redis Cache
- What is Azure Redis Cache?
- Common scenarios for using Redis Cache
- Understanding the service tiers
- How does Redis work?
- Create and manage a Redis Cache
- Scaling Azure Redis Cache
- Azure Search
- What is Azure Search?
- Indexes and Search Features
- How do you use the Search Service?
- Create a Search Service and Index
- Azure Backup
- What is Azure Backup?
- Backup Scenarios
- Import/Export Service
- What is the Import/Export Service?
- Why would you use Import/Export?
- Site Recovery
- What is Site Recovery?
- Workload recovery scenarios
- What is StorSimple?
- How does StorSimple work?
- Course Summary
- Conclusion and Wrap-Up
Welcome back, we are now ready to look at Site Recovery.
What is Site Recovery?
Site recovery is a disaster recovery-as-a-service product.
Which means it is a platform for you to manage your disaster recovery needs.
We covered Backup earlier, which is about data. Disaster recovery is about resources, systems and what order to stand you systems up when a failover happens.
Site Recovery also is a good tool to use in replicating systems to and recovery in Azure - this could be a DR scenario or maybe even a migration from your on-premise environment to running in Azure.
Site Recovery can also replicate on-premises VMs to Azure.
You can also set your system dependencies to orchestrate the step order your recovery will follow.
Site Recovery allows you to failover from the primary site to Azure or to a secondary site.
Also in the Portal you can monitor the status of replication and backup jobs, letting you know when something is wrong.
Site Recovery is about replicating your primary site and its systems in Azure or to a secondary site.
It can replicate VM's that are On-Premise – VMWare or Hyper-V VMs and even physical machines with either Windows or Linux on them.
If the replicas are going to Azure, they are stored in storage until they need to be brought online, then they are stood up as virtual machines at that time.
Site Recovery has a pretty extensive list of the types of workloads it can replicate.
As you can see, Active Directory, IIS, SQL Server, Sharepoint, Exchange, SAP, File Servers, Oracle, Linux, Citrix and even more.
This means if you have the machine or virtual machine running on-premise there is a good chance Site Recovery can replicate it to Azure for you.
As mentioned earlier, Site Recovery can be a great tool for migrating systems.
You can migrate physical servers or VM's to Azure.
Migrate from one Azure region to another.
Or even migrate AWS windows VMs to Azure – currently you can’t migrate Linux machines from AWS.
Recovery plans allow you to define machines that are related, for example a sharepoint farm will have a sql server and some web servers – which need to be grouped for a recovery scenario.
Once machines are grouped, you can then define the dependencies they may have.
For example, with a Sharepoint farm you would want to bring the database up before the web servers.
Once all the replicas and recovery plans are created you can test the recovery plan and verify the machines work. Then tear them down after you confirm the test is good.
Jason Haley is an independent consultant who focuses on Azure and Angular. He has over 20+ years’ experience architecting, designing, developing and delivering software solutions using mostly Microsoft technologies. Jason recently achieved his MCSE: Cloud Platform and Infrastructure certification in May 2017 (by passing all of the 70-532, 70-533 and 70-534 exams). He is also a Microsoft Azure MVP and leads the North Boston Azure User Group. He frequently speaks at community events on topics relating to Azure.