New answers tagged mysqldump
Someone sent me a compressed gtar. Wasn't even too familiar with gtar, but it is another compression format. $ file core_production-1432173533.sql.gtar core_production-1432173533.sql.gtar: gzip compressed data, from Unix, last modified: Wed May 20 21:59:31 2015 However, I was able to decompress it the same as usual: tar -zxvf ...
If your big tables are innodb, you can use --single-transaction to not lock the table. Other possibility is Percona XtraBackup Or pt-archiver (again Percona)
performance_schema: Not necessary. It may contain performance metrics that are only good for the time you were using the instrumentation. It would serve no purpose to load collected metrics from the past into another MySQL instance or into the same MySQL instance at a much later time. mysql : BE VERY CAREFUL HERE !!! If you backup mysql, you can only reload ...
Well, I figured out that if you use the backticks ("`") around the table name (like mysqldump uses in the comment-separator sections, e.g. `call`), it works as expected. So, the above should look like: -- -- Table structure for table `call` -- DROP TABLE IF EXISTS `call`; CREATE TABLE `call` ( path varchar(255) NOT NULL default '', call_num int(12) ...
Sometimes this error comes when you have the following command in your sql dump without any insert LOCK TABLES `table_name` WRITE; Just remove the above line and it will resolve the issue for you. Hope it helps Cheers S
I've been having the exact same issues on my OpenVZ VPS's recently. Both running Debian 7 (official OpenVZ template), both with MySQL 5.6.23 from the Dotdeb repository. Random InnoDB corrupted tables, with the dump in the error log showing strange data that is definitely not part of any of my own databases, nor any files stored in my container. Both started ...
Not real sure but you could try to use the Linux version of mysqldump in a Cygwin or similar interface. It has a cleaner output file than the windows version.
Top 50 recent answers are included