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

Florian Pritz bluewind at xinu.at
Sun Jan 15 14:36:24 EST 2012


On 15.01.2012 19:58, Dieter Plaetinck wrote:
> 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.
> 
> 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.
> 

We could just create daily dumps on the slave then. Additionally the
slave would prevent data loss in case the main server crashes and the
database file there is corrupted.

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

Do you have something to back up that claim?

-- 
Florian Pritz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-dev-public/attachments/20120115/ba34bf74/attachment.asc>


More information about the arch-dev-public mailing list