BTW....if I start a slave now will it synchronize ok? since it has no current s3 backup to start from....
On Tue, Jan 20, 2009 at 7:04 PM, Arie Fishler <[email protected]> wrote: > Oh....(cold sweat following...) > > When I started using scalr I saw that note next to the mysqllvm about > stability issues and therefore skipped using it...so maybe you can tell me > how usable is it. > > What is my best migrating strategy now? > > Going to mysqllvm if possible? Which steps are needed? > > Attaching an EBS and backing up on the EBS? Again...which steps do I need > to apply to make sure I have a usable backup? > > > > > On Tue, Jan 20, 2009 at 6:49 PM, Alex Kovalyov <[email protected]>wrote: > >> >> Arie, >> >> Currently only mysqllvm role splits snapshots into chunks. >> Regular mysql roles will be splitting snapshots after Jan/09 release. >> >> On Jan 20, 12:45 pm, afishler <[email protected]> wrote: >> > Checking the logs of the backup I have seen that the s3 backup fails >> > due to file being too big. >> > >> > I see that the backup file is 7GB and I understand s3 is limited to 4 >> > or 5 GB only. >> > >> > This is a critical issue since on this occasion I have no db backup. >> > >> > I assumed that the backup script knows to break the file into valid >> > pieces....isn't it? >> > >> > Please advice. >> > >> > Arie. >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
