It seems as if I am the one and only person using cpanel/whm for the web hosting solution and at the same time have a MySQL database with 5+mio records.

During the backup process cpanel simply truncates the results at a few hundred K records… what a mess… and it put's the server under unnecessary load by compressing the file on the fly… what a mess…

After some weeks of research with ThePlanet support we came to a simply and effective solution…

</p>

	<p>time mysqldump -l -uroot database_name > database_dumpfile.sql</p></p>

	<p><p>real 1m19.625s </p>

	<p>user 0m11.890s </p>

	<p>sys 0m17.600s</p></p>

	<p><p>root@xeon1 [/usr/mysqlbackup]# ls -lah database_dumpfile.sql </p>

	<p><del>rw-r—r-</del> 1 root root 390M Mar 4 13:54 database_dumpfile.sql</p></p>

	<p><p>root@xeon1 [/usr/mysqlbackup]# grep -c "reallyhugetable"  database_dumpfile.sql </p>

	<p>4513227</p></p>

	<p><p>mysql> select count(*) from reallyhugetable</p>

	<p>-> ; </p>

	<p><ins>—————</ins> </p>

	<p>| count(*) | </p>

	<p><ins>—————</ins> </p>

	<p>| 4513224 | </p>

	<p><ins>—————</ins> </p>

	<p>1 row in set (0.00 sec)</p></p>

<p>

As you can see this only took about a minute to dump the 4 mio records into an ASCII dump (a SQL file to recreate the whole table)