On Tue, Dec 6, 2011 at 7:00 PM, Jeff Schnitzer <[email protected]> wrote: > On Tue, Dec 6, 2011 at 1:00 PM, Niklas Rosencrantz <[email protected]> > wrote: >> >> >> eg. backup where phpMyAdmin you just push the button and you get a backup >> in zipped SQL of your whole database and no need to worry.
The idea of downloading a multi-gigabyte backup with phpMyAdmin, is kinda funny. > > > I found backing up a production mysql system with significant data size to > be a huge pain in the ass. Backups invariably ended up locking large > sections of the database and freezing the frontends for unacceptable lengths > of time. The only solution was to set up a slave and run all backups off of > the slave. > > InnoDB's awful locking policy is why I will never run MySQL in production > ever again. If I need an RDBMS in production, I'll use Postgres. > > This brings up an interesting question. Without a full-database MVCC > system, how do you backup the whole database? Especially with multigroup > transactions, there's no way to guarantee an isolated snapshot. Depending > on how your application works, getting a consistent backup might be > impossible. ... without a readonly period - ie downtime. Even youtube, goes readonly sometimes... (like right now) http://www.google.com/support/youtube/bin/answer.py?answer=1751921&topic=16550 > > Jeff > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
