Tag Archives: Azure Backup

Step-by-Step Guide to protect Azure VM using Azure Backup

Azure Backup is capable of replacing typical on-premises backup solutions. It is cloud-based, secure, reliable solution. It has four components which can use to backup different types of data.

Component

Protected data

Can use with On-premises?

Can use with Azure?

Azure Backup (MARS) agent

Files, Folders, System State

Yes

Yes

System Center DPM

Files, Folders, Volumes,

VMs, Applications, Workloads, System State

Yes

Yes

Azure Backup Server

Files, Folders, Volumes,

VMs, Applications, Workloads, System State

Yes

Yes

Azure IaaS VM Backup

VMs, All disks (using PowerShell)

No

Yes

More details about azure backup and components limitations can be find on https://docs.microsoft.com/en-us/azure/backup/backup-introduction-to-azure-backup 

In this article we are going to look in to Azure VM backup (Azure IaaS VM Backup). 

How Azure VM Backup works? 

Azure VM backup doesn’t need any special agent installed in VM. It also does not need to have any additional components (backup server) install either to enable backup. When very first backup job is triggered, it installs backup extension inside the VM. If its Windows VM, it installs VMSnapshot extension and if its Linux VM, it installs VMSnapshotLinux extension. VM must be in running state in order to install extension. After extension in place, it takes point-in-time snapshot of the VM. If VM is not running during backup window, it takes snapshot of VM storage. If its windows VM, backup service uses Volume Shadow Copy Service (VSS) to get consistence snapshot of VM disk. If its Linux VM, users can create custom scripts to run before and after backup job to keep application consistency. Once snapshot is taken it will transfer to the backup vault. Service can identify the recent changes and only transfer the block of data which changed from last backup. Once the data transfer completes snapshot will removed and recovery point will be created. 

vmbackup-architecture

Image Source: https://docs.microsoft.com/en-us/azure/backup/media/backup-azure-vms-introduction/vmbackup-architecture.png 

Performance of backup depends on,

1) Storage account limitations 

2) Number of disks in VM

3) Backup Schedule – if all jobs running in same time it can create traffic jam

According to Microsoft following are recommended when you use Azure backup for Azure VMs. Reference: https://docs.microsoft.com/en-us/azure/backup/backup-azure-vms-introduction 

1) Do not schedule more than 40 VMs to backup same time.

2) Schedule VMs backup when minimum IOPs been used in your environment (In relevant storage accounts). 

3) Better not to back up more than 20 disks in single storage account. If you have more than 20 disks in single storage account spread those VMs across the multiple policies to maintain required IOPS. 

4) Do not restore a VM running on Premium storage to same storage account. Also try to avoid restore while backup process is running on same storage account.

5) For Premium VM backup, ensure that storage account that hosts premium disks has at least 50% free space for staging snapshot for a successful backup.

6) Linux VM needs python 2.7 enabled for backup.

Next step is to see this in action.

1) Log in to Azure Portal as Global Administrator

2) First step is to create Azure Recovery Service Vault. In order to do that, go to All Services and click on Recovery Service vaults under storage section. 

bk1

3) Then click on Add in new window

bk2

4) It will open up wizard and there provide vault name, subscription, resource group and location. Once done, click on Create.

bk3

5) Now we have vault created, next step is to create backup policy. To do that click on vault we just created from the Recovery service vault window.

bk4

6) Then click on Backup Policies 

bk5

7) There is default policy from Azure VM backup. It backup VMs daily and keep it for 30 days.

bk6

8) I am going to create new policy to do backup every day at 01:00 am and keep it for 7 days. To do that click on add option in policy window. 

bk7

9) Then select the policy type. for VMs, it should be Azure Virtual Machine

bk8

10) In next window we can define time and retention period of data. Once done with the details click on Create

bk9

11) Next step of the configuration is to enable backup. In order to do that, go to the VM you like to backup. Then click on the option Backup 

bk10

12) Then in new window select the vault and policy we created before and then click on enable backup

bk11

13) Once it is done we can run backup by going in to same backup window. If you like to take ad-hoc backup, click on Backup Now

bk12

14) We can see the progress of the backup job by clicking View All Jobs

bk13

bk14

15) Once backup jobs completed we can see the status of it in same backup window.

bk15

16) To test the restore I installed Acrobat Reader in this server and created test folder in desktop. 

bk16

17) Now I am going to do a restore to an earlier day. To do that go to VM backup page, then click on Restore VM

bk17

18) In next window it asks which backup to restore. I am selecting back up from 3 days.

bk18

19) In next window it allows me to restore it as new VM or as disk. In here I am going to restore it as new VM

bk19

20) Once selection is done click on Restore to begin the process.

21) We also can check the status of the job using backup job window.

bk20

22) Once restore completed, I can see a new VM. 

bk21

23) Once log in to the VM I can’t see the folder and application I installed, as expected. 

bk22

This marks the end of this blog post. If you have any questions feel free to contact me on rebeladm@live.com also follow me on twitter @rebeladm to get updates about new blog posts.

Azure Backup to Protect your Data from Disaster – Part 1

Data is the value for any organization operations, so it’s important to make sure organization have access to its data in any time. Backup of valued data will ensure seamless access to data in a disaster. Businesses uses different type of backup technologies, tools to backup data. It can be traditional tape backups, on-premises backup, off-shore backup etc. each of these technologies, tools got their own characteristics.

Azure Backup is a solution where you can bring your backups to cloud. Let’s see why it’s different from other solutions.

azurebackupintronew

Zero Capital investment – Disaster recovery solutions are costly. You need to buy additional storages, spaces in remote data centers, software licenses, support contracts etc. when all these adds up its not cheap. But with azure backup you can start the backup without any of the above concerns.   All you need to do is enable the service in azure portal. Then in next minute you can start to back up your data in to the cloud.

Minimum maintenance cost – Maintaining disaster recovery solution is not easy either. When the data grows you need to plan for the expanding your backup infrastructure as well. Also need to consider about software upgrades, staff training etc. But if you use azure backup, Microsoft taking care of all these maintenance problems for you.

Protect Data from anywhere – your data can be in different formats and in different geographical locations. Also some data may in cloud. Azure backup can protect your data from anywhere and all you need is internet access. In disaster it will be available to you from anywhere as well. 

Replacement for Tape – even tapes are old school backup type still organizations are using it for long-term retention. With azure backup you can keep your data up to 99 years. Also it’s available to you in low cost and faster recovery than tapes.

Secure – When people talk about the cloud service a common question you get is how secure it is. With Azure backup, the data will be encrypted before it leaves your infrastructure. Then it will be deliver via secure connection and will be store in azure datacenters as encrypted data.

Reliable – Azure backup will store 3 copies of your data in azure datacenter and in additional you can save copies in remote datacenters in different geographical locations.

Throttling – when you backup data over internet one of the problem people face is bandwidth. With bandwidth throttling we can control the impact of backup jobs to company uplinks. Ideally backup jobs can use the full benefit of bandwidth in off-peak times.

Compression – Data will be compressed before it upload in to azure. So it will use less bandwidth and less storage.

Advanced Workload Protection– Azure backup can integrate with SCDPM (System Center Data Protection Manager) and can use to protect enterprise workload such as SharePoint, exchange, SQL servers, Hyper-V VM. It also gives Granular restore capability such as mailbox recovery for Exchange, DB level recovery for SQL, and ILR for SharePoint. DPM works seamlessly with the Hyper-V Volume Shadow Copy Services (VSS) writer to ensure that consistent versions of virtual machines are captured and protected without affecting virtual machine access.

Offline Seeding – The initial backup for large servers over internet is pain. Azure backup allow you to create initial backup locally and can deliver to the nearest azure datacenter for upload.

In next post let’s see how we can configure azure backup and start protecting data.

If you have any questions feel free to contact me on rebeladm@live.com

Image source: https://azure.microsoft.com/en-us/documentation/articles/fundamentals-introduction-to-azure/