We will tend to use binary backups (Xtrabackup) for full consistent dataset
restore (think slave provisioning and disaster recovery) and logical
backups to perform single table restores in the event that a rollback may
need to occur if someone drops a table or carries out an insane update. We
will
Maybe no, as you knew.
> It means that after lock is released, dump is made while the read and
write
> activity is going on. This dump then, would be inconsistent.
Not only binary logs, each tables in your dump is based the time when
mysqldump began to dump *each* tables.
It means, for example,
So, in case of * NOT Innodb * storage engine, say MyISAM, will this dump be
of any useful?
Best Regards,
Geetanjali Mehra
Senior Oracle and MySQL DBA Corporate Consultant and Database Security
Specialist
On Tue, Oct 7, 2014 at 11:55 AM, yoku ts. wrote:
> Hello,
>
> If you use any *NOT InnoDB*
Hello,
If you use any *NOT InnoDB* storage engine, you're right.
mysqldump with --single-transaction doesn't have any consistent as you say.
If you use InnoDB all databases and tables, your dumping process is
protected by transaction isolation level REPEATABLE-READ.
http://dev.mysql.com/doc/refm
It seems to me that once the read lock is acquired, only the binary log
coordinates are read. Soon after binary log coordinates are read, lock is
released. Is there anything else that happens here?
It means that after lock is released, dump is made while the read and write
activity is going on.
Hello Geetanjali,
On 9/23/2014 7:14 AM, geetanjali mehra wrote:
Can anybody please mention the internals that works when we use mysqldump
as follows:
*mysqldump --single-transaction --all-databases > backup_sunday_1_PM.sql*
MySQL manual says:
This backup operation acquires a global read lock
Can anybody please mention the internals that works when we use mysqldump
as follows:
*mysqldump --single-transaction --all-databases > backup_sunday_1_PM.sql*
MySQL manual says:
This backup operation acquires a global read lock on all tables at the
beginning of the dump (using *FLUSH TABLES WI
