Ask the Community
Groups
Hot Backup Copy (Replication) is slow - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Steps to debug poor Hot Backup Copy (Replication) performance.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>Replication is slow, but, pipe speed over the VPN conduit seems to be good. (VPN performance can be tested using iPerf or by copying large files through the conduit)<br><br>After basic analysis no errors are found in logs, and database performance on the source and target units does not appear impacted, yet replication is still slow. <br><br>For more information on Hot Backup Copy (Replication) issues see <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013257518">Unitrends KB 5030 - Hot Backup Copy (Replication) Overview, Setup and Error Troubleshooting</a></p> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p>Connect to the appliance via SSH and open /usr/bp/bpinit/master.ini </p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> vi /usr/bp/bpinit/master.ini</pre> <br>In the [Debugging] section on the source unit: <ul><li>Set the VCD logging level to either 0 or 1 by adding or editing the following line:</li></ul><pre class="code codeBlock" spellcheck="false" tabindex="0"> vcd=0</pre> <div>If the VCD log level is set higher than 1, replication performance will suffer, dramatically. </div> <div> <br>In the [Debugging] section on the target unit: <ul><li>Set the VaultServer logging level to either 0 or 1 by adding or editing the following line:</li></ul><pre class="code codeBlock" spellcheck="false" tabindex="0"> vaultServer=0</pre> <div>If the vaultServer log level is set higher than 1, replication performance will suffer, dramatically. </div> <br>In the [Replciation] section (on the source unit):</div> <ul><li> <div>Ensure localBlockElimination=True or the localBlockElimination (LBE) line is not present at all. LBE set to false will cause unnecessary overhead on synthetic full and differential processing, and cause long replication windows. </div> </li></ul><div> <pre class="code codeBlock" spellcheck="false" tabindex="0"> localBlockElimination=True</pre> </div> <div> <ul><li>if the VCD log level was 2 or higher, it is practice to set ThreaddedSendBlocks=0 in the [replication] section of the master.ini. This needs to be removed. If you find the following line in the [Replication] section of the source master.ini, delete it: </li></ul><pre class="code codeBlock" spellcheck="false" tabindex="0"> ThreadedSendBlocks=0 </pre> <div> </div> <div><b>Important: Never set the VCD log level above 1 unless ThreadedSendBlocks=0 is set. </b></div> <div>Once the VCD log level is reduced back to 0 or 1 Remove the line item for ThreadedSendBlocks from master.ini.</div> <br> </div> </article> </main>