Comments on: How To: Export/Import Large MySQL Database http://www.devart.com/blogs/dbforge/index.php/how-to-exportimport-large-mysql-database.html Technical notes, articles and tips on database development. Tue, 30 Aug 2011 09:40:18 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Aleksandr Serdyuk http://www.devart.com/blogs/dbforge/index.php/how-to-exportimport-large-mysql-database.html/comment-page-1#comment-1131 Aleksandr Serdyuk Mon, 26 Jul 2010 11:42:07 +0000 http://www.devart.com/blogs/dbforge/?p=1432#comment-1131 I agree with you that in case when you need a regular backup for multi-terabyte database it is faster to suspend MySQL server and dump file system. Because our product is more developer-oriented than DBA-oriented, article merely talks about making development snapshots (i.e. exports). And there are cases when database developer simply is not allowed to accomplish all operations you described. So he must wait for export to complete. I agree with you that in case when you need a regular backup for multi-terabyte database it is faster to suspend MySQL server and dump file system. Because our product is more developer-oriented than DBA-oriented, article merely talks about making development snapshots (i.e. exports). And there are cases when database developer simply is not allowed to accomplish all operations you described. So he must wait for export to complete.

]]> By: Mark R http://www.devart.com/blogs/dbforge/index.php/how-to-exportimport-large-mysql-database.html/comment-page-1#comment-1059 Mark R Fri, 23 Jul 2010 23:18:23 +0000 http://www.devart.com/blogs/dbforge/?p=1432#comment-1059 Importing / Exporting large MySQL databases can't be done at all with mysqldump because it is too slow - especially for restore. This is why any significant sized system needs to do something else - typically either volume snapshots, rsync, filesystem dump from replication slaves, etc. What you're suggesting simply isn't practical with a multi-Tb database server. Importing / Exporting large MySQL databases can’t be done at all with mysqldump because it is too slow – especially for restore.

This is why any significant sized system needs to do something else – typically either volume snapshots, rsync, filesystem dump from replication slaves, etc.

What you’re suggesting simply isn’t practical with a multi-Tb database server.

]]>