There is a shared script called "Do not fetch MySQL snapshot"
available on Scalr.net.
But in this case you should take care of mounting EBS volume with
MySQL datadir.

On Feb 5, 12:50 am, danny <[email protected]> wrote:
> Sorry I'm new to all this...can you explain how to follow your
> instructions?
>
> Are we supposed to add a new script template with the name "Do not
> fetch MYSQL snapshot" and then have that executed by the mysql role
> OnHostInit? If so, what is the content of the script. I'm missing
> something here...
>
> Thanks
>
> On Dec 14 2008, 1:08 am, Alex Kovalyov <[email protected]>
> wrote:
>
> > Here's a workaround to make mysql master skip snapshot download and
> > deployment:
>
> > Simply add a script called "DonotfetchMySQL snapshot" on hostInit
> > for
> > mysql role.
>
> > It creates a file, which is being checked by updated mysql-init.sh
>
> > On 10 дек, 23:13, Ken M <[email protected]> wrote:
>
> > > I've set up anEBSvolume and attached it themysqlrole.  All of thedatais 
> > > on theebs.  I need thedatato persist between instances, but
> > > I only want to backup the volume periodically.
>
> > > As it is now, when themysql-master instance attaches theebsvolume,
> > > it immediately downloads the most recent snapshot of thedatafrom S3,
> > > overwriting the more currentdatathat is already on theEBS(which
> > > was written after the last S3 backup).
>
> > > Is there a way to have themysql-master attach theEBSwithout
> > > overwriting the most currentdatawith the last .tar backup on S3?
>
> > > Slave instances ofmysql, however, will need to use the most recent
> > > backup, before synchronizing with the master, I suppose.
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to