![]() If we use snapshot, we should do it manually. ![]() If we use snapshot and want to restore VM, we have to use snapshot to create OSdisk and then use this OSdisk to create new VM.īy the way, we can set backup jobs in Azure Backup, so Azure can run backup by backup policy. ![]() The biggest difference is that, we can use Azure Backup to restore VM directly. Snapshots of OS Disk and data disk of azure VM via "az vm" cli How using 'Azure backup' to backup a VM is different from taking the You are right, Azure backup will take snapshots first, then upload them to backup vault. I read that Azure backup takes snapshots and then uploads them to the In the azure portal, snapshots, what is "snapshot state"? Why is the snapshot state "Unattached" for me even after spinning off a VM from the snapshot disk? Is there an advantage of using one over the other?Īre the Snapshots of OS disk taken in Azure, global in nature or are they in any way associated with a region? If a region is down, do they become unavailable? If both the options are similar, i.e using azure backup or taking a snapshot of OS disk/Data disks. Which is better cost wise, azure backup or osdisk snapshots? What exactly is the vault here? Is it internally implemented as a storage account with blob container or is it something similar to the Glacier in AWS? I'm trying to understand how using 'Azure backup' to backup a VM is different from taking the snapshots of OS Disk and data disk of azure VM via "az vm" cli commands? I read that Azure backup takes snapshots and then uploads them to the vault. Please help me in understanding it better. My questions are specific to backing up Linux VMs in Azure. ![]() ![]() I'm an azure newbie and just trying to understand Azure better. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |