Incorrect replication coordinates in backup-*_mysql.pos

Bug #682733 reported by Bjunity
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mylvmbackup
New
Undecided
Unassigned

Bug Description

Hello,

i've taken a snapshot backup from a MySQL-Slave (5.1.30) with mylvmbackup.

After restoring the backup on another server and before starting the replication I verified the replication coordinates and i think there are incorrect in the backup-*_mysql.pos - file.

mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State:
                  Master_Host: masterdb
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: db01.002369
          Read_Master_Log_Pos: 45174931
               Relay_Log_File: db03-relay-bin.000881
                Relay_Log_Pos: 44964609
        Relay_Master_Log_File: db01.002369
             Slave_IO_Running: No
            Slave_SQL_Running: No
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table: mysql.%
                   Last_Errno: 0
                   Last_Error:
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 44964469
              Relay_Log_Space: 0
              Until_Condition: None
               Until_Log_File:
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File:
           Master_SSL_CA_Path:
              Master_SSL_Cert:
            Master_SSL_Cipher:
               Master_SSL_Key:
        Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 0
               Last_SQL_Error:

backup-20101128_181332_mysql.pos:

Master:File=db03.000159
Master:Position=420
Master:Binlog_Do_DB=
Master:Binlog_Ignore_DB=
Slave:Slave_IO_State=Waiting for master to send event
Slave:Master_Host=masterdb
Slave:Master_User=repl
Slave:Master_Port=3306
Slave:Connect_Retry=60
Slave:Master_Log_File=db01.002369
Slave:Read_Master_Log_Pos=44964469
Slave:Relay_Log_File=db03-relay-bin.000881
Slave:Relay_Log_Pos=44964609
Slave:Relay_Master_Log_File=db01.002369
Slave:Slave_IO_Running=Yes
Slave:Slave_SQL_Running=Yes
Slave:Replicate_Do_DB=
Slave:Replicate_Ignore_DB=
Slave:Replicate_Do_Table=
Slave:Replicate_Ignore_Table=
Slave:Replicate_Wild_Do_Table=
Slave:Replicate_Wild_Ignore_Table=mysql.%
Slave:Last_Errno=0
Slave:Last_Error=
Slave:Skip_Counter=0
Slave:Exec_Master_Log_Pos=44964469
Slave:Relay_Log_Space=44964801
Slave:Until_Condition=None
Slave:Until_Log_File=
Slave:Until_Log_Pos=0
Slave:Master_SSL_Allowed=No
Slave:Master_SSL_CA_File=
Slave:Master_SSL_CA_Path=
Slave:Master_SSL_Cert=
Slave:Master_SSL_Cipher=
Slave:Master_SSL_Key=
Slave:Seconds_Behind_Master=0
Slave:Master_SSL_Verify_Server_Cert=No
Slave:Last_IO_Errno=0
Slave:Last_IO_Error=
Slave:Last_SQL_Errno=0
Slave:Last_SQL_Error=

I think

incorrect:
Slave:Read_Master_Log_Pos=44964469

correct::
Slave:Read_Master_Log_Pos=45174931

Ok, you don't need this variables for setting up replication (Relay_Master_Log_File / Exec_Master_Log_Pos are needed), but i think it is worth a bug report.

Björn

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.