[arch-dev-public] backup strategy for our servers

Dieter Plaetinck dieter at plaetinck.be
Sun Jan 15 13:58:50 EST 2012

On Sat, 14 Jan 2012 22:07:43 +0100
Florian Pritz <bluewind at xinu.at> wrote:

> On 14.01.2012 21:05, Ionut Biru wrote:
> > I was talking today with Florian about implementing a backup
> > strategy, involving master-slave setup and dbs, pulling encrypted
> > snapshots on the box and so on.
> My idea is that we set up mysql slaves (with ssh tunnels) so we have
> live backups that can be restored easily. Everything combined we have
> around 8 write operations per second so that doesn't require powerful
> hardware.

replication != backup.

if you do the wrong query ('drop database', 'drop table', 'delete from', 'truncate table', and so on), it will be executed on all slaves as well.

besides, mysql replication is not very robust, a better way is to make dumps of the database.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://mailman.archlinux.org/pipermail/arch-dev-public/attachments/20120115/c0a4b89f/attachment-0001.asc>

More information about the arch-dev-public mailing list