Last few days even I am thinking whats the best option for backing up drupal sites.

Using below 4 modules, one can automate the backup process. You can backup code, files , you can schedule , you can limit the number of backups required (Example: At year end you may like only 1 backup copy per year is required).

http://drupal.org/project/backup_migrate_files
http://drupal.org/project/backup_migrate_prune
http://drupal.org/project/backup_migrate
http://drupal.org/project/backup_migrate_sftp

I have not used it, but planning to explore more on this as I plan for own hosting.

Thanks
Kamal
NECS, Bangalore


On Mon, Oct 8, 2012 at 9:59 PM, Kenneth Jacker <khj@be.cs.appstate.edu> wrote:
Though I am sure that there are more, I can think of at least four ways
to backup a Drupal site:

  * Drush's 'archive-dump' (ard) command

    (Backup your code, files, and database into a single file.)

  * The 'Backup and Migrate' (B&M) module

    (simplifies the task of backing up and restoring your Drupal database)

  * Use a "version control system" (VCS)

  * Use 'rsync'


B&M allows automatic scheduling of backups ... definitely an advantage.
'ard', on the other hand requires manual, 'cron' or scripted invocation.

*I* seem to favor 'ard' since it backs up *code and files* along with
databases.  B&M, apparently, only backs up databases.

Another approach might be using a VCS (e.g., 'git', 'subversion', _et al_)
... or keep synchronized copies with 'rsync'.  (These two, however, seem
more suited for maintaining "development" and "production" versions of a
site than for backing up.)


How do *you* periodically backup your site(s)?


Thanks for your comments!

  -Kenneth
--
Prof Kenneth H Jacker       khj@cs.appstate.edu
Computer Science Dept       www.cs.appstate.edu/~khj
Appalachian State Univ
Boone, NC  28608  USA
--
[ Drupal support list | http://lists.drupal.org/ ]