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.267 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.257 votes
The preview for Azure Backup Reporting only supports exporting data to a storage account in the same tenant. This means that MS partners cannot use the solution - in most cases each managed customer has their own tenant.
The alternative approach, creating multiple instances in Power BI and pinning duplicate reports to a single dashboard will not work.
Please make it possible to export RSV data to a storage account in another tenant, e.g. storage account name + access key.251 votes
Many use cases for DR-BCP involve recovery testing on quarterly or biannual basis. Having access to a RA-GRS recovery vault in paired region would enable these BCP best practices for recovery from backups as a DR strategy.82 votes
It should be great if you show progress in Bar format too. So, that user can know how much backup is completed.49 votes
Competion on Sep 2018
Many customers do not want to grant their IaaS VMs direct access to the internet. Forced tunneling prevents the Azure Backup Service from protecting Azure IaaS VMs. If the Azure Backup VM Extension was allowed to talk directly the Recovery Service Vault through internal traffic in the datacenter, VMs would not need Internet access for backups to complete successfully.24 votes
When you want to seed your initial backup using the Azure Import Service you have to do a backup to a disk first (obviously). However, this is a 2 step process:
1 - The backup is done to a Staging area
2 - The backup is then copied to the disk you want to ship to Microsoft
Why do we have to stage the backup first? Why can't the backup be done straight to the disk you want to send to Microsoft?
When you are working with terabytes of data this is very time consuming.23 votes
We are working on a solution that will remove the need to use an intermediate staging location. If you are interested to try this out write to us at AskAzureBackupTeam@microsoft.com
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 series22 votes
- Don't see your idea?