Ask the Community
Groups
Replication not able to keep up with incoming backup volume - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Replication continues to backlog with hundreds of new backups coming in every day. One example of this is a SQL server with multiple DBs performing transaction logs every 15 minutes.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h2 data-id="issue-1">Issue</h2> <p>Customer has hundreds of jobs performed per day. Replication just doesn't seem able to keep up with the volume of jobs.</p> <h2 data-id="resolution">Resolution</h2> <p>In the [Replication] section of the master.ini on the source add the option to disable threaded send for VCD.</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> ThreadedSendBlocks=0 MaxConcurrent=12+ </pre> Alternatively you can lower the number of send threads and still increase the MaxConcurrent count without overloading the system. <pre class="code codeBlock" spellcheck="false" tabindex="0"> SendThreadCount=1 MaxConcurrent=12+</pre> <h2 data-id="cause">Cause</h2> <p>By turning off this option we are able to increase the number of workers much more than we would other wise. The threaded component with a large number or workers could overwhelm an appliance.</p> </article> </main>