List:Replication« Previous MessageNext Message »
From:Johan De Meersman Date:September 13 2013 8:06am
Subject:Re: MySQL Master and Slave Replication
View as plain text  
----- Original Message -----

> From: "Kaushal Shriyan" <kaushalshriyan@stripped>
> Subject: Re: MySQL Master and Slave Replication

I don't have Alexander's email, but that's the right link, yes. 

The simple explanation is that the binary logs keep track of every change that happens on
the master, so if you know at what log position a full backup is made, you can restore
that full backup and then re-apply the changes from the binary logs until the point just
before where a mistake was made. 

Those pages should have a more complete explanation, but you can see how that could be
useful :-) 

-- 

Unhappiness is discouraged and will be corrected with kitten pictures. 

Thread
MySQL Master and Slave ReplicationKaushal Shriyan13 Sep
  • Re: MySQL Master and Slave ReplicationJohan De Meersman13 Sep
    • RE: MySQL Master and Slave ReplicationAndrew Morgan13 Sep
      • Re: MySQL Master and Slave ReplicationManuel Arostegui13 Sep
        • Re: MySQL Master and Slave ReplicationKaushal Shriyan14 Sep
          • Fwd: MySQL Master and Slave ReplicationValerie Parham-Thompson14 Sep
    • Re: MySQL Master and Slave ReplicationKaushal Shriyan13 Sep
      • Re: MySQL Master and Slave ReplicationJohan De Meersman13 Sep
Re: MySQL Master and Slave ReplicationKaushal Shriyan13 Sep
  • Re: MySQL Master and Slave ReplicationKaushal Shriyan13 Sep
Re: MySQL Master and Slave ReplicationJohan De Meersman15 Sep