+2  

...but I also throw in a "lazy" replication in my environment by delay the 
replication for 1 hours using mk-slave-delay. We'll just switch over the server 
as primary immediately after he/she dropped the database :)


-----Original Message-----
From: [email protected] [mailto:[email protected]] 
On Behalf Of Edward Ned Harvey
Sent: Monday, May 07, 2012 4:03 PM
To: 'Anton Cohen'; Jonathan Bayer
Cc: [email protected]
Subject: Re: [lopsa-discuss] How do you backup your VMs

> From: [email protected] [mailto:discuss-
> [email protected]] On Behalf Of Anton Cohen
>  
> Side note, MySQL replication isn't backup, you still need to backup the DB
> (with mysqldump or LVM snapshots).

+1

mysql replication is redundancy, not backup.  If some script or a bad admin
goes haywire and issues the "drop database" command somehow, then it gets
dropped from both systems simultaneously.

_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
 http://lopsa.org/
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to