there is new EBS support for mysql. You need to select the EBS storage engine for the Mysql settings and in the EBS tab....leave "Do not use" selected.
Then you will automatically have a maser with EBS persistence and slave replicated from it (with no EBS). I guess older docs are irrelevant now. On Sun, Mar 29, 2009 at 3:47 AM, kenhawkins <[email protected]> wrote: > > Just a general question as I get my head around this cloud.... > > When you bring up a mysqlvm instance you have a mapped mount to /mnt/ > mysql-data and you have LVM snapshot-ing going on (if you enable it) > however, all the older doc's point to using an EBS type of solution in > (say) /mnt/storage for database persistence. I noticed that the above > solution with proper backups can accommodate most small instance > scenarios however, what are most persons doing? I can move the mysql > data over to /mnt/storage and that would take care of things if I > moved it from farm to farm but is there any real reason that for a > moderate production db to be housed in the EBS vs. snapshot-ing to S3? > mind you this is a mysqlvm and not a 64 coutnerpart. > > thanks for the thoughts ahead of time. > > ken; > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
