Regarding the blob, geo-replication is very cool for the HA side, but it is not a backup.

It would be nice to be able to backup a blob storage on another blob storage, to cover against an accidental deletion of the storage account via the portal, or from the code by an error of a programmer by the use SDK (call API) that does not control recursion (and delete calls).

Now view time spent on Azure Backup in Azure portal
Checking the status of Azure backup using Azure PowerShell can be used to schedule the time of Buckup subtask, but it is inconvenient so please display the time taken for Buckup and its subtask from Azure portal. .

How to know the individual storage usage of a VM or server in a Vault?

MARS Agent backup time is delayed There are many problems. Many of the causes are processing time before data transfer. I think This can be a take snapshot, checksum process, and queue time. If the performance before data transfer improves, I think that one of the problems of delay in backup time will be solved.

We can check from Azure Portal whether Azure Backup is completed.
However, we cannot see how far it is going at this time.

Our customers want us to implement visualization of the percentage currently being achieved by Azure Portal.

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.

From the portal.azure.com web interface we can see the type of consistency for a backup. We would like to have visibility into this information through the PowerBI reports and powershell commands.

I want to on-premises backup SQL DBs to Azure and test the sanity of the backup point by restoring it to an Azure IaaS VM which has SQL server installed in it

If a customer wants to backup or restore the contents of a key vault, the customer is forced to export/import keys, secrets and certificates one by one.

There should be an Azure CLI command to export a Key Vault in its entirety, and the same with import, something like:

az keyvault backup --file <FileName> --vault-name <VaultName>

az keyvault restore --file <FileName> --vault-name <VaultName>

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.

I want to be able to exclude certain folders from backups by default and I want to be able to use wildcards to do it. Right now this is a nightmarish thing to do and the documentation is very scarce.

Examples:

c:\users*\sources\repos*.git\
c:\users*\sources*\node_modules\
c:\users*\sources*\obj\
c:\users*\sources*\packages\
c:\users*\sources*.vs\
c:\users*\sources\workspaces*\tf$\

c:\users*\Dropbox\
c:\users*\OneDrive\
c:\users*\Google Drive*\

Having to manually configure these or to have scripts that try to continuously update the backup schedules on machines is madness.

There are instances whereby we want a complete/selective deletion of backup data without the 14 days retention policy. Currently, when I choose to backup a particular folder on my server using the MARS agent, and decide that I want a complete wipe of that data from Azure, I have to stop the backup policy and wait for 14 days for total deletion. In-between these 14 days, I'm stuck without an option to backup to Azure if I require a clean slate.

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.

Currently, encrypted VMs are not eligible for "Replace Disk" as described in the following public information.

Title: Restore Azure VMs

Address: https://docs.microsoft.com/en-us/azure/backup/backup-azure-arm-restore-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.

We have Azure Backup (MARS) deployed to 150+ servers across the globe and we would like to see a mechanism whereby we can make a global change across all servers e.g. Group Policy.

For example, we now need to add a file exclusion to every job on the 150+ servers and as far as I'm aware this means connecting to each server individually and making the change.

Allow file-level restores of Encrypted Azure VMs without MARS

In the MARS backup, if you change the daily schedule to Weekly Schedule, all previous points marked as 'Daily Points' are deleted after updating the policy.
At this time, there is no warning screen.
For example, schedule Daily & 365 days retention to Weekly & 53 weeks retention.

Warnings should be displayed!!

Azure Backup successful backup email notification.

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 series