When creating a new machine an Option to select an backup for restore would be great.1,249 votes
Currently it's not possible to exclude Disks from a Hyper-V VM backup. (except using the Exclude Pagefile Disk workaround) to exclude single disks from the backup.
The possibility to exclude disks from a hyper-v vm backup would be a great improvement in case you've really large fileservers or other workloads where another backup mechanism is in place or you simply dont want a backup because of temp data etc.305 votes
Exclude disk functionality for Write accelerator(WA) enabled disks is available now. No action is required from the user. During VM backup, Azure backup service automatically excludes the WA enabled disk and backs up the rest of the disks in a VM.
It would be ideal if we could push the Azure backup of our Azure IaaS Vms to a different region. This would give people a lot more peace of mind in the event of a datacentre failure.269 votes
Please add the capability of changing the managed disk name.
Fixed name makes it difficult to manage.49 votes
If I backup an IaaS VM, I can't delete the vault for 14 days due to the soft-delete feature.
I can understand the motivation - to avoid accidental deletion.
However, this is a huge pain point in testing / training scenarios. We need the ability to fully clean up a test / training environment and start over.47 votes
Provide functionality for Recovery Services to execute Pre and Post scripts during a backup snapshot. This could allow applications and databases to be consistently quiesced on non-VSS enabled operating systems like Linux. Perhaps this could be built into the WAAgent Backup Extension and provide accompanying templates scripts to guide users through the process.46 votes
Add an option to delete individual recovery points. Alternatively if that is not possible add option to continue purging old backups according to the backup policy after server has been deleted\renamed\migrated (VNET migration).36 votes
If scale sets are used by in Azure IAAS, it should be supported to back up its instances or single instance at least through Azure Backup service in same or other regions in a recovery vault.33 votes
You have GOT to be kidding me, you can ONLY backup an Azure VM ONCE a day?! What the heck Microsoft?! We MUST have the option to backup a VM as MANY TIMES A DAY as we choose. We are paying for the backup, the storage, and the VM so why do you guys prevent this? I feel like I am dealing with a new company in the 90's but no, its Microsoft the biggest bunch of backwards thinking company there is. This is why I go open source, only MS for clients. Because of this backwards design, my client lost TWO DAYS of work because we can only backup a VM once a day. Windows updates applied on a Friday evening, killing the machine, non-boot, so it went by until Monday, guess what, we had to RECOVER back to the day prior, losing anything on Friday and over the weekend. Thankfully the weekend was no work because the office was closed for the weekend, but we lost ALL of Friday!!! I was ashamed to tell my client this, they "thought" it was "safe" in Microsoft cloud, YEAH RIGHT! Sorry, client, because of a faulty update, and because of the dumb design, you lost 3 days of VM backups! I know it was an update that crushed the VM because I opened and escalated a ROOT CAUSE from the Azure team, they confirmed it.
You have GOT to be kidding me, you can ONLY backup an Azure VM ONCE a day?! What the heck Microsoft?! We MUST have the option to backup a VM as MANY TIMES A DAY as we choose. We are paying for the backup, the storage, and the VM so why do you guys prevent this? I feel like I am dealing with a new company in the 90's but no, its Microsoft the biggest bunch of backwards thinking company there is. This is why I go open source, only MS for clients. Because of this backwards design, my client…31 votes
If you lock a resource group containing VMs as ReadOnly, VMs in that resource group will fail to backup because they are locked.
Please provide an option to bypass ReadOnly locks for recovery services backup jobs.30 votes
[Azure Backup] Want to specify Backup Schedule Policy of Azure VM Backup at "local time" using Azure PowerShell
At present, backup schedule of backup policy using Azure PowerShell, we need to specify the "time", "time zone" in UTC.
Therefore, please add the function to be able to specify the "local time" (UTC + N) using Azure PowerShell.29 votes
Currently, encrypted VMs are not eligible for "Replace Disk" as described in the following public information.
Title: Restore Azure VMs
Replace existing is supported for unmanaged managed VMs. It is not supported for unmanaged disks, generalized VMs, or for VMs created using custom images.
From the security point of view as well, it is possible that the number of encrypted VMs will increase in the future, so there is a need for an easier recovery method.
Currently, encrypted VMs can only be restored from "disk restores". We should also implement VM restoration with "disk replacement" of encrypted VMs.28 votes
Azure backup supports up to 16 data disks attached to an Azure virtual machine for backup. Please remove the restriction or match the max data disks for G series26 votes
Allow file-level restores of Encrypted Azure VMs without MARS22 votes
Currently, we should specify the Storage Account for staging purpose to restore the VMs with managed disk.
But the advantage of the managed disk is that we don't have to inform and control storage account permissions for the end users. The required RBAC permission for this operation is Storage Account Contributor which means the restore operator can perform anything for the storage account.
This prevents the customer from being free from Storage Account management.22 votes
When we run on-demand vm backup, the retention period is not shown in any UI (e.g. Azure Portal, Azure PowerShell, Azure CLI, Azure REST API) currently.
If the retention period is queryable, backup data management will be more easier and convenient.19 votes
Currently Recovery Services "Restore disks" restores all disks. It would be great if you could only restore selected individual disks.
E.g., right now I'm waiting for 128+50+1023 GB VHDs of a single VM being restored, and I wouldn't need the 1023GB one, so I have plenty of time to write this suggestion :)17 votes
Azure IaaS VM Backup has to wait for the previous backup to be completed when successively triggering backups using "backup now" on the same VM.
If we try to get backups before and after maintenance, this specification is very painful.
At least, Azure IaaS VM Backup should be able to run the second backup immediately after the first snapshot is completed.15 votes
The daily limitation of Azure Virtual Machine backups is very restrictive. It makes it difficult to meet any reasonable RPO from a backup strategy.
Even if our RPO is 24 hours, that means we have to have 100% backup success in order to maintain SLA.
Being able to back up more frequently would allow better RPO or greater achievement of SLA with managed risk of failed backups.
I really want to avoid using the in-VM agent to complete this task as it doesn't scale which is the whole point of using Azure Backup!15 votes
We want to use backups made in classic mode available after switching to Resource Manager mode.
Now, When we move a VM from classic to Resource Manager mode, backups taken prior to migration will not migrate to newly migrated Resource Manager VM.15 votes
- Don't see your idea?