Skip to main content
commvault.com commvault.com

Slow restores of entire virtual machines within Azure

  • February 14, 2022
  • 5 replies
  • 1083 views
N
Bit
Forum|alt.badge.img+1

Hello,

We have determined with the help of CV support and Azure support that the fastest possible restore of an entire VM within the Azure environment (even within the same region) is 60Mb/s. The limitation, according to Azure, is that CV writes the VM as a single page blob and the max throughput for that is 60Mb/s.

At this speed, restoring an entire VM of any significant size would take far too long to be acceptable in an emergency situation.

Has anyone run up against this limitation and how have you worked around it? Or does anyone have any suggestions on how we might do so?

Thanks in advance for your suggestions!

If you have a question or comment, please create a topic

5 replies

Mike Struening
Vaulter
Forum|alt.badge.img+23

@Neil Winking , I’m going to convert this to a conversation to encourage more members to contribute their experiences :nerd:

https://www.linkedin.com/in/michael-struening
MichaelCapon
N
2 people like this
  • MichaelCapon
    MichaelCapon
  • N
    Neil Winking
MichaelCapon
Vaulter
Forum|alt.badge.img+15
  • MichaelCaponVaulter
  • Vaulter
  • 352 replies
  • February 15, 2022

Hi @Neil Winking,

 

What Maintenance Release version are you on here? - In V11 FR26 Maintenance Release 11.26.7 contains two HotFixes specifically for this:

Azure full VM restore may extend for a longer duration with low write throughput speed.

 2162

Azure VM restore may be slow.

 2151

 

Also, are you restoring Managed Disks? 

 

Best Regards.

Michael

N
1 person likes this
  • N
    Neil Winking
N
Bit
Forum|alt.badge.img+1
  • Neil Winking
  • Author
  • Bit
  • 2 replies
  • February 15, 2022

Hi @MichaelCapon,

Thanks for the info. We are on LTS V11.24.23 currently. I’m wondering if these HotFixes address a slowness specific to 11.26 or if we would see improved performance from an upgrade.

Yes, we are restoring managed disks.

Thanks again,

Neil

M
Vaulter
Forum|alt.badge.img+4

Hello Neil,

what I did in the past to get around slow restore speeds and recover very large Azure machines quickly was to leverage Commvault IntelliSnap functionality for Microsoft Azure:

Azure IntelliSnap

I created snap_primary copy, set the retention to have e.g. 7 most recent snapshots kept (depending on your requirements), then used the backup copy operations to copy data to Azure storage for longer retentions.

Advantage of this solution was the ability to recover whole VMs in about 10 minutes, no matter the size (I used it for 24TB machines), but only for most recent recovery points. However, usually when we need to restore whole VM due to crash, it’s the most recent copy that we use to restore from.

Best Regards,

Marcin

Damian Andre
L
Michal128
4 people like this
  • Damian Andre
    Damian Andre
  • L
    Laurent
  • Michal128
    Michal128
  • N
    Neil Winking
N
Bit
Forum|alt.badge.img+1
  • Neil Winking
  • Author
  • Bit
  • 2 replies
  • February 16, 2022

Hi @Marcin Dziewanowski,

That’s a good idea. I’m going to look into that and discuss with the team. I think it would meet our needs in most scenarios.

Thank you,

Neil

Mike Struening
M
2 people like this
  • Mike Struening
    Mike Struening
  • M
    Marcin Dziewanowski

Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings