The best Azure learning site: Azure Documentation Center / Microsoft Learning
What is Azure Backup
Under normal circumstances, when operation and maintenance personnel maintain an application system, in addition to ensuring that the system can run stably and continuously provide external services, they also need to ensure data security. For example, when data is damaged or business data is lost (erroneously deleted) and important data is locked by a virus, the data can be recovered as quickly as possible, thereby reducing the company's losses. There are many ways to protect data security, and perhaps the most common way is to back up. Backup is like buying an insurance for your data. Maybe it can't completely save you from loss, but it can reduce our loss to a minimum in the event of a problem or poisoning.
In traditional operation and maintenance scenarios, it is troublesome to back up data. We need to purchase expensive storage devices and backup software, and we need to continuously monitor the storage usage. So when we migrate the application system to the cloud, how should we deal with the data backup problem? In fact, each cloud provides a corresponding solution. Here we will take Azure as an example to introduce.
Azure provides us with a service called Azure Backup for us to back up data to Azure cloud. Why is the data backed up to the Azure cloud? This service can not only back up resources such as VMs in Azure, but also back up VM resources in local data centers or other clouds. Using Azure Backup we can build a simple, safe and cost-effective backup solution. For more information, please refer to the following link:
https://docs.microsoft.com/en-us/azure/backup/backup-overview?WT.mc_id=AZ-MVP-5002232
What can be backed up
Using Azure Backup, you can back up the following:
Local: Use the Microsoft Azure Recovery Services (MARS) agent to back up files, folders, and system state. Or, use DPM or Azure Backup Server (MABS) agents to protect local VMs (Hyper-V and VMware) and other local workloads
Azure VM: Back up the entire Windows/Linux VM (using the backup extension), or use the MARS agent to back up files, folders, and system state.
Azure File Storage Share: Back up Azure File Storage Share to a storage account
SQL Server in Azure VM: Back up the SQL Server database running on Azure VM
SAP HANA database in Azure VM: Back up SAP HANA database running on Azure VM
Azure Database for PostgreSQL Server (Preview): Back up Azure PostgreSQL database and keep the backup for up to 10 years
Why use Azure Backup
Granular backup
When using Azure Backup to create a backup, a backup file that can be finely restored will be created. In other words, we can restore a single file or the entire computer according to actual needs. The ability to carefully select the files to be restored allows us to prioritize the restoration process and eliminate wasted work. In addition, it can also prevent the operation and maintenance personnel from restoring the entire system to its previous state.
When you need to restore a file, you only need to connect the recovery point to the target computer to easily restore it. After connection, we only need to copy the file backup to the computer.
Multiple storage options
Azure Backup provides users with three types of storage, namely local redundant storage (LRS), remote redundant storage (GRS) and zone redundant storage (ZRS). The specific use depends on our needs and budget.
LRS stores three copies of the data in the same area as the metadata to prevent damage or loss. But we have no way to access the stored copy of the data unless it is restored in this area. LRS is a low-cost option to protect data from local hardware failures.
GRS is the default and recommended replication option. The entire option allows us to store the backup and source data in different areas, so that the backup can be used as a backup in the event of a regional outage or failure. The cost of GRS is higher than that of LRS, but GRS provides higher data durability, even if there is a regional service interruption.
ZRS refers to copying data between available zones, thereby ensuring the ability to reside and recover data in the same zone. ZRS will not cause downtime. Therefore, it can be backed up in ZRS for critical workloads that require data to reside and there must be no downtime.
Multiple interfaces
We can access and manage backup services in multiple ways:
Azure Portal: A browser-based dashboard that can be used to manage backups and other Azure services. It includes functions for reporting, monitoring, configuration and access to support services
Azure Cloud Shell: Browser-based CLI that can simulate Bash or PowerShell.
Azure PowerShell: Group cmdlet, which can be used directly from PowerShell CLI to control Azure services (including backup).
Portal provides a more user-friendly interface, which is very suitable for users who are not familiar with the command line. The Shell option is less user-friendly, but it can integrate backup management into existing workflows. Shell tools can also use custom scripts and API calls to automate backup management.
Built-in security
When used in conjunction with Recovery Services Vault, Backup can provide access to several built-in security features. These measures include alerting, incident prevention and recovery.
Event prevention function: The authentication layer can be applied to high-risk functions. For example, pass phrase modification or backup deletion. Authentication can ensure that only allowed users can access the backup, thereby reducing the chance of accidental modification or destruction by the hacker.
Alert function: E-mail notifications can be set for events that affect the availability of backups. For example, if the backup is moved or data is deleted. These alerts allow you to better track the status of the backup and audit who made changes to the data.
Recovery function: You can restore accidentally or maliciously deleted backups. Once the backup is deleted, it will be kept for 14 days and then permanently deleted. This way, you can easily restore the backup as needed.
Uninstall local backup
Azure Backup provides a simple solution to back up local resources to the cloud. Obtain short-term and long-term backups without the need to deploy complex local backup solutions.
Zoom easily
Using Azure Backup, we do not need to maintain the underlying storage and other backup equipment. Azure Backup utilizes the basic functions of Azure cloud and unlimited scaling to achieve high availability without maintenance and monitoring overhead.
Azure Backup pricing model
To ensure that backups are managed as cost-effectively and efficiently as possible, it is important to understand the pricing model used by Azure. Pricing is based on the following elements:
Fixed service pricing: Fixed pricing related to the use of Backup with specific services. This is applied on a per-instance or database basis according to the size of the resource.
Bandwidth cost: Azure Backup does not limit the amount of inbound or outbound data transferred, and does not charge data transfer fees.
Outbound data refers to the data transferred from the Recovery Services vault during the restore operation.
If you use the Azure Import/Export service to perform offline initial backups to import large amounts of data, inbound data will incur costs.
Storage space: The cost of storage space required to store backups. This is affected by the frequency of creating backups, the number of copies stored, and the duration. Which storage tier is used is also a factor.
At this point, I believe you all have a preliminary understanding of Azure Backup. In the follow-up articles, we will show you how to use Azure Backup to back up cloud and local resources. Please pay more attention to it.