<?xml version="1.0"?>
<oembed><version>1.0</version><provider_name>Blog | GitProtect.io</provider_name><provider_url>https://gitprotect.io/blog</provider_url><author_name>Wojciech Andryszek, Technical Content Writer at GitProtect.io</author_name><author_url>https://gitprotect.io/blog/author/wojciech-andryszek/</author_url><title>How to Prevent Backup-related Throttling Without Losing Data (or Mind) - Blog | GitProtect.io</title><type>rich</type><width>600</width><height>338</height><html>&lt;blockquote class="wp-embedded-content" data-secret="3rJLlrCbmI"&gt;&lt;a href="https://gitprotect.io/blog/how-to-prevent-backup-throttling/"&gt;How to Prevent Backup-related Throttling Without Losing Data (or Mind)&lt;/a&gt;&lt;/blockquote&gt;&lt;iframe sandbox="allow-scripts" security="restricted" src="https://gitprotect.io/blog/how-to-prevent-backup-throttling/embed/#?secret=3rJLlrCbmI" width="600" height="338" title="&#x201C;How to Prevent Backup-related Throttling Without Losing Data (or Mind)&#x201D; &#x2014; Blog | GitProtect.io" data-secret="3rJLlrCbmI" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" class="wp-embedded-content"&gt;&lt;/iframe&gt;&lt;script type="text/javascript"&gt;
/* &lt;![CDATA[ */
/*! This file is auto-generated */
!function(d,l){"use strict";l.querySelector&amp;&amp;d.addEventListener&amp;&amp;"undefined"!=typeof URL&amp;&amp;(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&amp;&amp;!/[^a-zA-Z0-9]/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret="'+t.secret+'"]'),o=l.querySelectorAll('blockquote[data-secret="'+t.secret+'"]'),c=new RegExp("^https?:$","i"),i=0;i&lt;o.length;i++)o[i].style.display="none";for(i=0;i&lt;a.length;i++)s=a[i],e.source===s.contentWindow&amp;&amp;(s.removeAttribute("style"),"height"===t.message?(1e3&lt;(r=parseInt(t.value,10))?r=1e3:~~r&lt;200&amp;&amp;(r=200),s.height=r):"link"===t.message&amp;&amp;(r=new URL(s.getAttribute("src")),n=new URL(t.value),c.test(n.protocol))&amp;&amp;n.host===r.host&amp;&amp;l.activeElement===s&amp;&amp;(d.top.location.href=t.value))}},d.addEventListener("message",d.wp.receiveEmbedMessage,!1),l.addEventListener("DOMContentLoaded",function(){for(var e,t,s=l.querySelectorAll("iframe.wp-embedded-content"),r=0;r&lt;s.length;r++)(t=(e=s[r]).getAttribute("data-secret"))||(t=Math.random().toString(36).substring(2,12),e.src+="#?secret="+t,e.setAttribute("data-secret",t)),e.contentWindow.postMessage({message:"ready",secret:t},"*")},!1)))}(window,document);
/* ]]&gt; */
&lt;/script&gt;
</html><thumbnail_url>https://gitprotect.io/blog/wp-content/uploads/2025/11/backups-and-throttling.jpg</thumbnail_url><thumbnail_width>1472</thumbnail_width><thumbnail_height>704</thumbnail_height><description>Consider that your backup is running smoothly. Your dashboards are green. The DevOps team is sleeping peacefully. And yet, behind the calm surface, something is happening. Your API limits are being chewed up, call by call, until you&#x2019;re throttled into silence. Suddenly, your system stalls &#x2013; quietly and invisibly. The irony is, you build a backup system for resilience. Now, it&#x2019;s the vulnerability. There&#x2019;s a quiet assumption built into most backup systems. It&#x2019;ll resolve itself if you just throw enough bandwidth, retries, and threads at the problem. However, in DevOps, it&#x2019;s naive. Dangerous. Throttling in DevOps is not just a [&hellip;]</description></oembed>
