Currently, a restore VM will start automatically, which will cause the restored data to change since applications / jobs will run. And it can cause conflicts if that system tries to interact with other systems.1 vote
while azure supports upto 4 TB, we are seeing limit as 1 TB in portal. This needs to be fixed1 vote
Here's an idea...how about you make restoring an existing VM one-click?
I know..revolutionary idea.
The amount of unnecessary complexity involved in restoring a VM is simply ridiculous.
Im guessing 99.99% of users would just want to rollback an existing VM to a previous version.
They dont want to create a new VM. They dont want to create new disks in a different storage account.
They dont want to spend an hour in powershell trying to get blob copy to work puzzling over cryptic error messages.
How about you simplify the restore process because the current process is simply dreadful.1 vote
The backup vault has this nice feature to autodiscover and deploy the backup agents to the VM on the same subscription (no need to get the credential and install the agent the VM like with the on-prem scenario)
A good practice is to secure the backup vault in a dedicated subscription (to save backups not at the same place ad the VM) but in that case the autodiscovery" feature does not work anymore.
It would be great to be able to autodeploy agents on VM from other subscriptions1 vote
Dear Team, With Azure we have solution to backup on-premise Physical/Virtual Machines in Azure Storage Account but we want a solution to restore same backup on Azure VM rather then bringing our onpremise server up and restore the data. Please work on this idea as this will really help in additional manual work.1 vote
- Don't see your idea?