In this video, you can understand the mechanisms that Microsoft uses to protect your data and which data you are responsible for protecting in Azure.
- [Presenter] Before jumping into the course I would like to spend a few minutes on Azure Recovery Solution Considerations. Basically, what you need to aware of when using Azure for your recovery solutions and some of the limitations of the more popular Azure infrastructure services. The first item I want to focus in on is the SLA, or service level agreement, for Azure virtual machines. Microsoft clearly states that for all internet-facing virtual machines that have two or more instances deployed in the same availability set, we guarantee you will have an external connectivity at least 99.95% of the time.
So what does this mean? Well, it means that a single virtual machine will not be protected by default in Azure if you have not configured an availability set with two or more virtual machines. This also means there'll be an increased cost as you now have to have two virtual machines running. Also, if you have your virtual machines in an availability set you will not be notified of disruptions. So keep that in mind. And having your virtual machines in an availability set does not protect you from fat finger deletes, bad patches, or funky software updates.
You are still responsible for backing up your data. And in this course we'll show you various ways to do so. Next, we have SQL virtual machines, and as before, you're responsible for protecting the data. And you can do that by a backup, by log shipping. You can still use database mirroring, but keep in mind this will be deprecated in SQL Server 2016. Or you can set up failover clustering for high availability. Next, we have Azure SQL databases.
The nice thing with these databases is Microsoft already provides geo-redundant backups and this is automatically done. You don't have to worry about it. These backups provide a point-in-time restore, and the retention period is based on the service tier. If you're using an Azure SQL database that is at the basic tier your backup is only for seven days. If you move into a standard and premium tier that backup is 35 days. Now, keep in mind that you cannot restore a database from a deleted SQL server.
Again, it's up to you to maintain those backups. And next we have storage, and again, Microsoft has considered this. Data in your storage account is replicated already. If you're using locally redundant storage you have three copies of your data within the same region. You also have zone redundant storage, and geo-redundant storage. Geo-redundant storage provides for three copies of your data in one region and three copies in another, providing six copies in total.
And you'll also have read-access geo-redundant storage. This data is only readable and you cannot write to it. Now that you know what is and is not protected you can then build your Azure recovery solutions to best meet your needs. We'll be exploring and configuring Azure backup and Azure site recovery as possible solutions for you during this course.
- Creating a Recovery Services vault for Azure Backup
- Protecting virtual machines, files and folders, databases, workloads, and file shares
- Restoring virtual machines, files and folders, databases, workloads, and file shares
- Azure Site Recovery scenarios
- Running failover and failback tests
- Replicating an Azure virtual machine