New answers tagged

1

Since I happened to be researching this myself, here's a summary of what I found. According to a 2015 blog post from the MySQL dev team, the main advantages of mysqlpump are that it can use multiple threads in parallel to speed up the dumping and that it doesn't share mysqldump's backwards compatibility requirements, which should open the door for further ...


1

This is age-old scenario I have dealt with before. Would you believe there are times when the checksum of table when dumped and reload on another server simply does not match the checksum of the source DB, regardless how the checksum was evaluated and no matter how you correct it ? Three(3) things can alter the checksum values of tables between source and ...


1

In the file slave.sql, modify the top line, delete -log. Then re-diff your files. If that's the only difference (and it appears to be), then there's no problem - the data part of your mysqldump is identical! (The small "difference" appears to be in the header generated by mysqldump). A checksum will vary greatly even if the file contents differ by only one ...


1

dont use "mysqldump" while restoring backup. Use "mysql". mysqldump is for taking backup, not for restoring.


0

When seeking a dump which provides binlog position you will instruct MySQL to call Flush Tables With Read Lock. The acquisition this lock can block. This where you could impact the system. If you have long running transactions you may see problems but you can check this before starting the dump. Your command looks fine to me.


0

mysqldump -u [username] -p[root_password] --ignore-table=israelca_isr1qaz_2.uc_order_products_pair_vw --ignore-table=israelca_isr1qaz_2.uc_views_marketing_test --ignore-table=israelca_isr1qaz_2.uc_order_products_user_vw --ignore-table=israelca_isr1qaz_2.uc_order_products_qty_vw israelca_isr1qaz_2 > backup.sql; Take backup of only tables and ignore the ...


0

Can you try grant permission on whole database like, GRANT ALL PRIVILEGES ON db.* TO 'username'@'%' IDENTIFIED BY 'yourpass' WITH GRANT OPTION;


0

This seems to be an authorization/rights issue. Please give the necessary grants to the user 'username' as follows: GRANT SELECT ON uc_order_products TO 'username'@'databasename'; OR GRANT SELECT ON uc_order_products TO 'username'; Hope this helps !!


0

I got 2 comments that hinted me that: This problem might not be reproducible again if I do a second mysqldump. The copy of the file from one place to another might have corrupted the file. So then to ensure (1) was not the case, I tried to mysqldump again, and to make sure (2) didn't happen, I compiled the file before transferring it to another computer (...


1

The answer is innodb only estimates number of rows by command show table status. Please refer to http://dev.mysql.com/doc/refman/5.7/en/show-table-status.html for further explanation.


-4

put "", like this mysqldump -u root -p databasename > "c:/home/databasename_bkup.sql"


1

From here, the complete command for a hot backup of a MySQL database using only InnoDB tables is: mysqldump -u user -ppass --single-transaction --routines --triggers --all-databases > backup_db.sql Note the gap between -u and user and the lack of a gap between -p and pass. This is correct - a quirk of MySQL which has caught me on more than one occasion....


1

Is something like this anything like what you want? This is how to run through all the databases in a server and backs them up. #!/bin/bash USER="your_user" PASSWORD="your_password" OUTPUT="/Users/rabino/DBs" rm "$OUTPUT/*gz" > /dev/null 2>&1 databases=`mysql --user=$USER --password=$PASSWORD -e "SHOW DATABASES;" | tr -d "| " | grep -v ...


-1

Jehad Keriaki nailed it. For InnoDB Engine Hot Backup, Percona is having a backup solution called "XtraBackup" which I believe is based on


0

First of all, categorizing the backup into the four mentioned categories is not accurate. You can categorize into (hot, warm, cold), and into (physical, logical). In other words, the backup can be cold and physical, or, hot and physical, etc. It cannot be (physical and logical). Notice please that physical backup is better called "Raw backup", which is a ...


0

Yes it is a hot backup. It is run with the database online, queries operating etc The dump will be consistent and atomic - a snapshot of the database as it looked when you initiated the dump



Top 50 recent answers are included