Actually, there is!

A few weeks ago I submitted a patch to Nate Murray's backup gem to  
provide S3 as a method for backups. A sample recipe (run on a cron  
job every night) looks like this:

set :backup_path, "db_backups" # This is the name of the S3 bucket to  
use (your AWS access key is appened to it for namespace)

set :aws_access, 'xxx' # These can also be  set in ENV
set :aws_secret, 'xxx'

action(:content) do
   dump = c[:tmp_dir] + "/databases.sql"
   sh "mysqldump -u root -pxxx --all-databases > #{dump}"
   dump
end

action :deliver,  :method => :s3
action :rotate,   :method => :via_s3

set :son_promoted_on,    :fri
set :father_promoted_on, :last_fri_of_the_month

set :sons_to_keep,         7
set :fathers_to_keep,      5
set :grandfathers_to_keep, 12



On Feb 18, 2007, at 10:12 PM, Chris Grant wrote:

>
> I'm not sure it'd be responsive enough to use as a database store but
> it's definitely well-suited for database backups and such.  I've been
> watching the development of a couple S3-related OS X tools like S3
> Backup ( http://s3bk.com/ ) and S3 Browser ( http://people.no- 
> distance.net/ol/software/s3/
> ) for signs of what you're talking about.  I know that the S3 Backup
> guys are looking at the possibility of using S3 in a similar fashion
> as U3 ( http://www.u3.com/ ) -- storing applications on S3 and running
> them from there.  I just don't think it'll be fast enough for that
> sort of thing but it would certainly be cool.
>
> An automated tool for database backups would rock.  I'm sure something
> like this is on the horizon -- it's too cool not to be.
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to