MySQL Forums
Forum List  »  Backup

Re: InnoDB understand cool backups.
Posted by: Rick James
Date: July 17, 2014 04:29PM

Steps 2,3,4 should be simply "Copy the entire mysql tree". That way, you don't leave out any ancillary files. In particular, if you have innodb_file_per_table, you would have failed to copy any of the data!

Recovery of a single database (or table) is trickier. In particular, your technique (and my improvement on it) cannot achieve this task.

To recover (and, hence, to dump) a particular database or table requires one of these techniques:

* mysqldump instead of copying files. You could, for example, mysqldump each database, one at a time.

* See if your version includes "transportable tablesets", then follow the rules for using such. Frankly, I am not convinced that this technique will even be possible. (You drifted into an area where I am not proficient. Oh, no! I flunked your test! (cry))

Options: ReplyQuote

Written By
July 15, 2014 11:15AM
Re: InnoDB understand cool backups.
July 17, 2014 04:29PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.