[innobackupex with --no-lock] replication MySQL

tdelnattetdelnatte EntrantCurrent User Role Participant
I tried to perform a backup with --no-lock and still get binary log pos of xtrabackup_logfile to initiate mysql replication.
I tried to do exactly what is described in this post below but i didn't manage to get binary log pos after the prepare step

http://codeascraft.com/2012/08/07/no...th-xtrabackup/

Is it possible?

Any way to perform a backup with no lock and still be able to resync master and slave?

Comments

  • mirfanmirfan Database Administrator Inactive User Role Mentor
    As --no-lock describes use this option if you don't care backup binary log position so backup doesn't contains xtrabackup_binlog_info file if backup is created with --no-lock option because --no-lock prevents FTWRL which is required to get consistent positions for binary log. If you are taking backup from master to provision new slave i suggest to do during offpeak time. This should help you regarding provisioning new slave http://www.percona.com/doc/percona-xtrabackup/2.1/howtos/setting_up_replication.html
  • tdelnattetdelnatte Entrant Current User Role Participant
    It seems there is no workaround to do this without downtime :(
  • mirfanmirfan Database Administrator Inactive User Role Mentor
    If all your database tables are InnoDB then surely no downtime because as i said it will only take FTWRL for very short time to copy .frm files. On the other hand if you using MyISAM tables then FTWRL blocks the all tables to copy .MYD, .MYI, .FRM files
  • tdelnattetdelnatte Entrant Current User Role Participant
    Oh sorry,

    you are right.
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.