Azure VM restore takes too long

mandania 156 Reputation points
2021-03-01T15:42:46.307+00:00

I am tried to restore a Azure VM which is 9878GB is size. It took around to complete the full restore. I am not sure if this amount of time is correct or i have missed something. I would have expected something most faster. Can it be because i have storage StorageV1 (general purpose v1) and option Blob access tier is set to cold? How can i make the restore go faster because 6 hours in my opinion is quite too long. Any suggestion will be appreciated.

Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,496 questions
{count} votes

Accepted answer
  1. SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator
    2021-03-02T06:11:55.883+00:00

    Hello @mandania - Thank you for reaching out to us.

    It depends on where the restored data was coming from. If the restore was from a VM snapshot (Instant Restore) then 6 hours is much greater than expected but I suspect this data must have come from the vault which means the full 9+ TB of data had to be moved/copied and therefore 6 hours would be expected.

    Azure Instant Restore Capability - Azure Backup | Microsoft Learn

    73293-image.png

    ----------------------------------------------------------------------------------------------------------------------

    If the response helped, do "Accept Answer" and up-vote it


2 additional answers

Sort by: Most helpful
  1. T16 1 Reputation point
    2021-05-02T02:57:58.003+00:00

    Same problem for us restoring back to on-prem VMs from Online backups in the recovery vault.

    A 500Gb VM can take 10 hours, which is ridiculous. I can only assume that in the back end, backup data is the lowest possible priority for Microsoft, therefore when pulling out data in an emergency, you simply do not get the performance you should.

    When starting a restore, I can watch the process pull in NO DATA for about 18mins, then a few Mb, then a few Mb more, sometimes 400Mbits into our DC, then nothing, then a few more. It is so flaky the restore process, I hope MS are taking note. If we had a disaster and needed to restore 10Vms for instance, we would be looking at DAYS of waiting, this is not acceptable for enterprise.

    Please MS, have a look at this for your customers.

    0 comments No comments

  2. Rob Nicholson 66 Reputation points
    2021-07-12T10:40:05.103+00:00

    Similar query here - understand slower speeds when pulling data (0.5TB in our case) from the vault but even restores from snapshot are hardly instant. Is it still copying back the entire 0.5TB from faster local storage or does it do any kind of difference block level copying? For on-premises, I was very impressed with Veeam - it's instant restores of a VM really were near instant as the backup consists of VM-ready storage. It connects the VM to the backup storage in seconds and you're back. Possibly at a lower performance as it's mounted on backup storage but you then transfer from the backup to live storage in the background. You don't care too much how long that takes.

    So a better algorithm for Azure instant restores would be to connect to the snapshot directly and then restore to live storage in the background like Veeam. Just testing a new environment so I'm going to time restoring from snapshot.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.