On Fri, Sep 4, 2009 at 7:35 AM, Joshua Russo<josh.r.ru...@gmail.com> wrote: > The reason I was looking at the dump data instead of a MySQL backup is > because it was more obvious to automate. I'm going to take a closer look at > the MySQL backup though.
I run on PostgreSQL rather than MySQL, but for what it's worth my backup scheme is just a little bash script, which runs as a cron job each night and: 1. Runs pg_dump. 2. Compresses the result. 3. Puts a copy in a local backups directory, and pushes copies to two off-site backup systems. Restoring from this is trivial; all I have to do is create an empty database, and pip the dump file to it. The only time I ever used fixtures for a dump/restore was when migrating across database platforms (e.g., away from MySQL a couple years ago), and that was really more of a special case. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
