<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure on LittleBeansByt.es</title><link>https://littlebeansbyt.es/tags/azure/</link><description>Recent content in Azure on LittleBeansByt.es</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 18 Sep 2025 08:27:27 +0000</lastBuildDate><atom:link href="https://littlebeansbyt.es/tags/azure/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting ready to test the new mass Instant Recover</title><link>https://littlebeansbyt.es/posts/2025-09-18-3lz3wjtyyik2h/</link><pubDate>Thu, 18 Sep 2025 08:27:27 +0000</pubDate><guid>https://littlebeansbyt.es/posts/2025-09-18-3lz3wjtyyik2h/</guid><description>&lt;p&gt;Getting ready to test the new mass Instant Recovery to #Azure in #Veeam V13? Here&amp;rsquo;s a quick tip. The default settings can cause restores to fail at scale by hitting Azure API throttling limits. 1/2&lt;/p&gt;</description></item><item><title>A new patch 8.0.0.376 for Veeam Backup for Azure a</title><link>https://littlebeansbyt.es/posts/2025-07-15-3ltxnkvyp252g/</link><pubDate>Tue, 15 Jul 2025 00:30:21 +0000</pubDate><guid>https://littlebeansbyt.es/posts/2025-07-15-3ltxnkvyp252g/</guid><description>&lt;p&gt;A new patch (8.0.0.376) for #Veeam Backup for #Azure addresses critical bugs, including data corruption risks and failed infrastructure rescans, while enhancing API handling to reduce Azure costs. More details: buff.ly/HzzqemR
#VeeamVanguard #Veeam100 #VeeamCommunity #MVPBuzz&lt;/p&gt;
&lt;div class="link-fallback"&gt;
&lt;a href="https://buff.ly/HzzqemR" target="_blank" rel="noopener" class="fallback-link"&gt;🔗 https://buff.ly/HzzqemR&lt;/a&gt;
&lt;/div&gt;</description></item></channel></rss>