On Fri, Sep 13, 2013 at 12:00 PM, Johan De Meersman <vegivamp@stripped>wrote:
> ----- Original Message -----
> > From: "Kaushal Shriyan" <kaushalshriyan@stripped>
> > Subject: MySQL Master and Slave Replication
> > I have a question regarding MySQL replication master slave setup. One
> > question is of concern "If data is corrupted, lost or deleted in the
> > master that will be synced to the slave. Restoring the slave to the
> > does not get the data back."? Please suggest.
> Repeat after me: Replication is not backup. RAID is not backup. Only
> backup is backup.
> The point of replication is load distribution, running heavy reporting,
> etc, and/or quick failover in case of *hardware* failure on the master.
> To protect against data corruption, you need to take regular backups of
> your data, using MySQLdump, Xtrabackup, or any of the myriad alternatives;
> and - most importantly - save those backups somewhere else than on the
> server you take them from, ideally even outside of the same datacenter.
Thanks Johan for the explanation. I am not sure i understand about point in
time recovery as per Alexander email. I am referring to
Is that link appropriate to understand more about point in time recovery?
> Unhappiness is discouraged and will be corrected with kitten pictures.