New answers tagged restore
mysqldump has an --add-drop-database option that will put those in the file for you. It will add this, before each database in the file: /*!40000 DROP DATABASE IF EXISTS `accounting`*/; For the benefit of anyone unfamiliar with magic comments, this isn't a comment. It's a statement that will be executed by MySQL 4.00.00 and higher, disguised as a ...
Short answer, yes. Longer answer, you'd need to remove database mirroring without bringing the database online. Then it's just a database in NORECOVERY so you can then restore transaction logs to it. Then bring it online and use it as normal.
I think the main problem is that you think that creating the database first will allow you to bypass WITH MOVE. This is not the case. If the destination file paths don't match those contained in the backup file, the presence of a database (and its file locations) aren't going to make a difference. RESTORE is going to look at the file locations specified in ...
PROBLEM You are starting from the wrong log. You should start with mysql-bin.000034 not mysql-bin.000035 The timestamp on each binlog shows the last time a binlog event was written to it mysql-bin.000033 was last written Dec 27 18:26 mysql-bin.000034 was last written Feb 2 18:58. That's 18 hrs 58 min after Feb 2 00:00 mysql-bin.000035 had to be created ...
Top 50 recent answers are included