I think this is not totally accurate. Space wise they are the same since you can easily reconfigure mysql role to work on /mnt for its data dir. The actual limitation is the backup. Backup is handled with a single tar file that has all bundled. If this file is larger than the S3 limit (4 or 5 gb -> dont remember) the backup will not go.
The lvm splits the backup file into chunks suitable for uploading to s3. If you expect your db to go over the S3 limit for a single file you actually have no choice but to use lvm unless you can live with your db not backed up. On Wed, Jan 21, 2009 at 5:32 PM, Frédéric Sidler <[email protected]>wrote: > > 1. the space (you could also use /mnt to store mysql data) > 2. the snapshot of the DB, with mysql is lock the tables, dump the > databases and release the DB. This could take ages for a 10GB database. > With > LVM it takes few seconds to snapshot your DB as it is filesystem based. See > here for infos http://lenz.homelinux.org/mylvmbackup/ > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
