We've written a custom php script that exports, compresses and uploads our db to S3 with a datestamp embedded somewhere in the filename. Every time we push a new backup to S3 we delete the oldest.
In terms of tools that's mysqldump, gzip and a basic S3 php library I found here I was able to get the gist of and start using in about 30 minutes (the very best kind... :-]):
On Thu, Feb 25, 2010 at 3:25 AM, Johnny Cupcake <sparkleware@hotmail.com> wrote:
Do go on...is there a "Cake-friendly method" for automated daily DB
backups? How do you accomplish it?
On Feb 24, 8:26 am, Christian Leskowsky
<christian.leskow...@gmail.com> wrote:
> For backups you should be taking full mysql backups of your database nightly
> - at least while that's feasible - and storing them offsite. (S3 is what I
> personally use.) Keep at least a week's worth of backups in case you
> accidentally "drop table" or something equally terrible happens. Make sure
> you test restoring from your backup too... regularly. What often happens is
> you may very well have an ironclad backup strategy but when it comes time to
> actually restore your data after an outage the backup doesn't work.
>
> Other things you should think about backing up: any content uploaded by
> users including photos, video, text, etc. You should be backing up source
> code, your project management tool if you're using one and anything else
> you'd really hate to lose.
>
> Good luck!
>
>
>
> > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others> On Tue, Feb 23, 2010 at 11:58 AM, WebbedIT <p...@webbedit.co.uk> wrote:
> > I think the OP put the main emphasis on legal requirements himself,
> > but fair point he did mention running the site as well as
> > administrative and technical issues.
>
> > I think the subject matters are little too general to be able to
> > recommend a selection of books that will be ideal for you. I am
> > guilty of not reading enough books myself, which further diminishes my
> > ability to make good recommendations.
>
> > I would say the first thing you need after launching a site is quality
> > traffic, so the first 6 months is likely to be spent on writing good
> > content that sets your website apart form the rest and then carrying
> > out SEO (possibly SEM depending on your budget) efforts to make sure
> > people know it exists. An important part of this process is
> > statistical analysis of your traffic and you can't go far wrong if
> > using Google Analytics. I bought 'Web Analytics: An Hour A Day' which
> > is highly recommended nut haven't had the time to read it in detail
> > and can;t remember if it is software specific or general?!?
>
> > Once you have traffic you then need to be concerned about supporting
> > your users and correcting any identified bugs, keeping an eye on user
> > generated content, managing relationships between site members if you
> > have any social networking features and controlling comment spam.
>
> > Your technical issues all really lie with whoever you host your
> > website with, so choose them carefully. Do a lot of research and make
> > sure whoever you go with will be available and willing to help when
> > you do encounter issues with your hosting. It's also a good idea do
> > go with a host who provides you with a high quality Control Panel, SSH
> > access and phpMyAdmin etc. as this allows you to do a lot of tweaks
> > and fixes yourself. Other stuff to consider is how often does the
> > host upgrade their server software such as updates to the Control
> > Panel, MySQL, PHP, Anti-Virus, Webmail etc.
>
> > It all sounds a lot when you right it down, but really running a
> > website is not overly time intensive, unless you;re running a highly
> > successful site, and that would be nice, but is unlikely to happen
> > over-night.
>
> > Launch it and tackle the issues head on as the arise, but most of all
> > enjoy it, it sure beats a 9-5 desk job if it can replace the wage!
>
> > Paul.
>
> > with their CakePHP related questions.> > cake-php+unsubscribe@googlegroups.com<cake-php%2Bunsubscribe@googlegroups.com>For more options, visit this group at
>
> > You received this message because you are subscribed to the Google Groups
> > "CakePHP" group.
> > To post to this group, send email to cake-php@googlegroups.com
> > To unsubscribe from this group, send email to
> >http://groups.google.com/group/cake-php?hl=en
>
> --
> -
>
> "You can't reason people out of a position they didn't use reason to get
> into."
>
> Christian Leskowsky
Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
--
-
"You can't reason people out of a position they didn't use reason to get into."
Christian Leskowsky
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
No comments:
Post a Comment