This repository includes a variety of artifacts that can be used to learn and demonstrate a subset of capabilities for Azure Backup. Azure Backup is the native backup solution in the Microsoft Azure cloud. It provides backup functionality for workloads running in Azure or on-premises. A detailed listing of which workloads are supported are documented in the public documentation. This artifacts in this repository cover only the following use cases:
- Azure Virtual Machines
- Azure Managed Disks
- Azure Storage - Blobs
- Azure Storage - File Shares
The artifacts include a PowerPoint overview deck, deployable lab to learn and demonstrate features and capabilities, and a step-by-step guide on how to demonstrate specific features (COMING SOON).
The deployable lab included in this repository is coded using ARM resource templates and uses a combination of PowerShell and Bash scripts and DSC to pre-configure resources deployed.
The resources in this lab are spread across three resource groups spread across the paired regions. The two resource groups deployed in the primary region include the Recovery Services Vault, Backup Vault, VMs, storage accounts, and virtual networks. The third resource group is deployed in the paired secondary region and deploys an empty virtual network that will be used to demonstrate the cross region restore functionality.
Both the Recovery Services Vault and Backup Vault include custom backup policies including a basic VM policy, advanced VM policy, Azure Files policy, Azure Managed Disk policy, and Azure Blob policy. The Linux VM (vml-pri-1-cf) is associated with the basic VM backup policy and the Windows VM (vmw-pri-1-cf) is configured with the advanced VM backup policy and also comes with the MARS agent preinstalled. The third windows VM (vmw-pri-2-ncf) is not configured for any backup policy and is present to allow you to demonstrate association of a backup policy through the Portal.
Two storage accounts are deployed, one used for Azure Files and one used for Azure Blobs. An empty file share named sampleshare is precreated on one storage account and an empty blob container named sampleblobs is configured on the second storage account. You must populate the file share and blob container with your own sample data. You can then associate the file share and blob container with the relevant custom policies in the Recovery Services Vault and Backup Vault.
The MARS agent on the Windows VM (vmw-pri-1-cf) can be setup and integrated with the Recovery Services Vault to demonstrate individual backup and restoration of system state, files, and folders from a Windows VM.
-
You must hold at least the Contributor RBAC role at the subscription scope in the subscription the resources will be deployed to.
-
You must be capable of deploying resources to a set of paired regions. The templates are configured to allow deployment to regions within the US geopolitical region and that have regional pairs. If you wish to deploy to another geopolitical region, you will need to modify the azuredeploy.json template.
Click the Deploy To Azure button below.
-
Set the following variables:
- DEPLOYMENT_NAME - The name of the location
- DEPLOYMENT_LOCATION - The location to create the deployment
- LOCATION - The primary region to deploy resources to
- SEC_LOCATION - The secondary paired region to deploy resources to. This is used to demonstrate the cross region restore feature.
- ADMIN_USER_NAME - The name to set for the VM administrator username
- SUBSCRIPTION- The name or id of the subscription you wish to deploy the resources to
-
Set the CLI to the subscription you wish to deploy the resources to:
- az account set --subscription SUBSCRIPTION
-
Deploy the lab using the command (tags parameter is optional):
- az deployment sub create --name $DEPLOYMENT_NAME --location $DEPLOYMENT_LOCATION --template-uri https://raw.githubusercontent.com/mattfeltonma/azure-labs/main/azure-backup-demo/azuredeploy.json --parameters location=$LOCATION secLocation=$SEC_LOCATION vmAdminUsername=$ADMIN_USER_NAME tags='{"mytag":"value"}'
-
You will be prompted to provide a password for the local administrator of the virtual machine.
Once the lab is deployed, you can RDP or SSH into the virtual machines using Azure Bastion.
It is very important you follow the instructions below when you are done with the lab. If you do not follow these instructions, it could result in shadow resources which will require you to work with support to remove.
-
Follow the instructions here to delete the Recovery Services Vault.
-
Follow the instructions here to delete the Backup Vault.
-
DO NOT proceed to this step until you have done steps 1 and 2. Once those steps are complete and both vaults are deleted, you can delete the resource groups containing the resources created as part of this lab.