Tag Info

New answers tagged

0

write table names in a file and use following command to take backups for i in `cat table_name_file` do mysqldump -uroot -p -T $i done Hope it helps


1

This link sums up your question completely. I quote: If you get this warning when dumping the mysql database, it’s not a bug – MySQL did this on purpose because they wanted people to know that they weren’t dumping the event table. Previous versions did not give the warning. The table itself is used by the MySQL event scheduler. A link to the ...


2

A bit late to the party but as a former mk-parallel-dump user I came across the same question recently. I tried using the parallelism feature of MySQL mysqlimport however that only works for different tables even if you break up the dump files into smaller chunks. Shame. However I then discovered MySQL Data Dumper which is apparently being ...


6

I can only think of three(3) things that can cause a mysqldump to be too large PROBLEM #1 : Disabling Extended Inserts Extended Inserts (--extended-insert) is on by default via the --opt option. If you issue --skip-opt or --skip-extended-insert, every INSERT command will quickly become hundreds or every thousands. Such a mysqldump can still be loaded but ...


1

There are a lot of factors that could come into play. Size of RAM, whether your software is using any timeouts (e.g.: phpMyAdmin), your own patience. In general, though, I would expect a server that can generate a backup should be able to restore it.


1

When you are using mysqldump, you can get the binary logs coordinates of the backup at the point-in-time of the the mysqldump's start. Just add the --master-data option mysqldump --master-data=2 --flush-logs --single-transaction... Using --master-data=2 will record the binary log filename and position in the form of a CHANGE MASTER TO command. It is ...


0

I'm a bit lost in your explanation, but there may not be much of a problem. You have a dump from December? But it is in the 'wrong' directory? The dump was taken using mysqldump? Reloading is nothing more than mysql -uroot -p


0

In the end I couldn't get mysqldump to login as root, it kept trying to login as ODBC. Instead I added this to my my.ini file and ran the command without user/password arguments: [mysqldump] user=root password=XYZ


0

I tried renaming the table via "adminer" (php mysql manager) but even there the table name was not correct (not showing at all, to be honest). I tried renaming but of course I produced a new table column. In the end I had to recreate the table. I managed to get most of the schema from the SHOW CREATE TABLE contabilita_banche\G above. Then I took the dump ...


0

I think the question is about how to restore faster from mysqldump's ceated dump files and not a different backup solution. One of the ways, you can do this is by creating groups of tables in your schema and create a separate DB user for each group and use MySQL permissions to not allow tables to be inserted to using all but one DB user. This is a proven, ...


0

I think the question is about how to restore faster from mysqldump's ceated dump files and not a different backup solution. One of the ways, you can do this is by creating groups of tables in your schema and create a separate DB user for each group and use MySQL permissions to not allow tables to be inserted to using all but one DB user. This is a proven, ...


0

there are two common solution for cannot parse version from mysqldump: the first one you need to make sure path for MySQLDUMP is correct you can check it from the workbench by going to Edit->Preferences->Administrator and the second one the environment variable is not correctly configured on the server.



Top 50 recent answers are included