New answers tagged

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


1

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


1

This is what I do to start the mysql daemon manually. I've also included my own my.cnf. By specifying the correct corresponding paths in your system, you should be able to do the same thing. I would also point out that this is a source install, but again, it should apply generally. Start the daemon like this: ./bin/mysqld --defaults-file=./my.cnf ...


0

MySQL has replication cabapilities, sure you has revised the MySQL documentation. This means that MySQL copies data from master to slave, not both directions. You proposed "just click a button", if you don't want a "do it yourself" solution maybe can try with a database tool like MySQL workbench. In any case it is dangerous to synchronize two databases ...


0

With the mysql client you can also do: mysql> tee import.log mysql> source .\test.sql then view the import.log file created in the current directory.


0

One can even search and replace each occurrence of Insert into with Insert Ignore into in the mysqldump file.


0

I was also getting the same error while trying to dump 12 GB database. I did the following changes to make it work. configured max_allowed_packet to 1024M configured net_read_timeout to 7200 configured net_write_timeout to 7200 Note: I know the time out values are way too high (7200 seconds i e 20hrs). But I did so itentionally just to rule out any ...


0

In my opinion, the logic is right in your way. I will add a suggestion to make it more practical. Get the backup without routins. --skip-triggers, and don't add -R is it is false by default Make a backup of routines only: --no-create-info --no-data --no-create-db -R Edit the backup file of the routine, and create the user in the new DB Restore the data ...


1

Based on this blog post http://ilikekillnerds.com/2014/08/fixing-sequel-pro-sql-encoding-error-for-imported-sql-files/ When importing your database dump, you need to select Western (Mac OS Roman) as the encoding format for the file to import without issue.


2

MyISAM table is stored as a heap, rows are being placed inside the data file into an empty place they can fit. If you are only inserting then that means appending new rows, but when the rows are being updated or deleted, some gaps are created and then later filled by other rows so the order of full table scan (which is what dump does by default) is not ...


1

--single-transaction is used to ensure the dump is consistent when dumping, it has nothing to do with import/restore. Loading a dump is not generally possible in a single transaction because many CREATE statements do an implicit commit. It is often not even desirable because for a rollback to be possible, the transaction needs to keep undo logs and if you ...



Top 50 recent answers are included