I have a database
setup for replication. I used mysqldump --opt db > db.dmp to do the
initial backup of the primary database (after doing a flush tables with read
lock in a seperate session).
I checked the dump
file, and all drop table create table statements are in the file. When I
did a restore to the second database with a mysql --on-database db < db.dmp,
it appears that the tables were not dropped and recreated. No errors were
displayed during this process. After the restore, I was able to start
replication, and replication ran fine, until it encountered an object which was
not in the secondary database which was in the primary.
The schema looks to
be the old schema (pre database restore), and table drops/creates appear to have
been done from the dump file. Any ideas why/how this would be? My
dump file is about 14 Gig.
Confidential
Information.The information contained in or attached to this e-mail
may be confidential information subject to protection by law or terms of
applicable confidentiality agreements, and is intended only for the use of the
individual or entity named above. If the reader of this message is not the
intended recipient, or the employee or agent responsible to deliver it to the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly prohibited. If you
are not the addressee indicated in this message (or responsible for delivery of
the message to such person), you should destroy this message and notify the
sender by reply email.
smime.p7s
Description: S/MIME cryptographic signature
