We run a cron job to backup the database nightly and other ones to make copies of the backup weekly and monthly. I download and keep the two most recent monthly backups on a local disk.
I backup files, images and custom modules by elbow grease, like you said. If this were really a hassle, or if image and file content changed daily, I'd put them on the same backup schedule as the database.
But most importantly, it was a big confidence booster to actually practice the database restoration (and, document the process, um, yeah). Having two sites to work with should make this fun and easy - if you screw up, you can practice re-installing Drupal.
This work is licensed under a Creative Commons Attribution- NonCommercial- ShareAlike 2.5 License.
Whatever works!
We run a cron job to backup the database nightly and other ones to make copies of the backup weekly and monthly. I download and keep the two most recent monthly backups on a local disk.
I backup files, images and custom modules by elbow grease, like you said. If this were really a hassle, or if image and file content changed daily, I'd put them on the same backup schedule as the database.
But most importantly, it was a big confidence booster to actually practice the database restoration (and, document the process, um, yeah). Having two sites to work with should make this fun and easy - if you screw up, you can practice re-installing Drupal.
So far, I've only needed to restore individual tables, and I use a handy shell and perl script combination for this that I found at http://unixnotes.wordpress.com/2006/03/15/restore-single-mysql-table-fro...