https://bitecode.blog/categories/tips/Recent content in Tips on Bitecode blogHugoen-usThu, 02 Jun 2016 00:00:00 +0000https://bitecode.blog/2016/05/14/mysql-dump-large-database/Thu, 02 Jun 2016 00:00:00 +0000https://bitecode.blog/2016/05/14/mysql-dump-large-database/<h2 id="problem">Problem</h2> <p>Not going into details of credentials basic mysqldump command looks like this:</p> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>mysqldump database &gt; database_dump.sql </span></span></code></pre></div><p>Dump file size was ~3GB which might take quite long. Especially when the connection to mysql server was not fast enough.</p> <h2 id="solution">Solution</h2> <p>After a few attempts and noticing that it might take too long to fetch all data I found out that there is a nice switch in mysql and mysqldump commands.</p> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>--compress, -C </span></span></code></pre></div><p>Switch will tell mysql server to compress the dump on the fly so you can save a lot of bandwidth. However both sides needs to support the setting. Note that you may also use that switch with mysql command.</p>