![veeam 10a veeam 10a](https://i1.wp.com/www.checkyourlogs.net/wp-content/uploads/2020/10/100320_1845_HowtoInstal12.png)
![veeam 10a veeam 10a](https://i1.wp.com/www.checkyourlogs.net/wp-content/uploads/2020/10/101620_2304_HowtoInstal29.png)
![veeam 10a veeam 10a](https://i0.wp.com/www.checkyourlogs.net/wp-content/uploads/2020/10/100320_1845_HowtoInstal22.png)
I’m just going to let the numbers speak for themselves from here on is, but suffice to say I was blown away with the improvement and more than ever, this has opened up more doors for Object Storage backed SOBR Extents to be used for recovery and migration. The one issue that I found and reported internally was that restore speeds for Instant Recoveries and general VM Restores where never fully utilising the max speed of the network connection. I even performed an Instant VM Recovery from 40,000 feet off an Amazon S3 backed Capacity Tier Extent which has proven that our innovative approach to the design of this feature has lead to use cases driven by its efficiencies in the way data is transferred. v10 Recovery Speed Improvements Results:Īs mentioned, I have been doing recoveries from Object Storage in varying scenarios for a while now. To prove that, just fire up a copy of the AWS CLI and perform Bucket/Folder copied from one region to another. As an example, not every AWS Region is created equal and Amazon S3 throughput can vary between regions which could also import restore speeds.
#Veeam 10a update#
One of the use cases I’ve been pushing since we released Cloud Tier back in 9.5 Update 4, was the ability to leverage our Scale Out Backup Repository (SOBR) Object Storage Capacity Tier extents for migration and On-Demand Recovery. We always talk about starting with backup… and it is true that you can’t recover unless you have a solid backup, however more and more the recovery of workloads, and the speed at which they are recovered is becoming crucial.