I don't know if the community will find this patch useful but it fills a need for me.
I have a number of domains on a shared server and running Drupal (both v5 and v6) from a common codebase. The domains are set up as separate accounts under Cpanel and the shared codebase directories are set up under the main server account. Because of the number of domains involved, it can become quite time consuming to run around making regular backups of the individual databases.
I have developed a patch for backup_migrate 6.x.1.2 that allows you to define a base directory for backups. (Patch attached to this issue.)
Any number of server accounts running Drupal can then be configured to save backups in a unique subdirectory (eg account name) off a common backup directory, making all backups accessible to, and downloadable from, a single FTP session.
Note that if a value is NOT entered for the base directory, backup_migrate will place the backups in sites/default/files/backup_migrate as per current normal behaviour.
A side effect of this approach is that it allows a neat solution to the security issue noted on the backup_migrate project homepage as it is now possible to set the backup directory to a location outside of the web root, and hence inaccessible to the web server.
I am intending to re-do the patch for version 5.x.1.2 sometime in the next week or so to handle the domains still running Drupal 5 as it will take some time to upgrade them all to Drupal 6.
If the interest is there, I will look into applying the patch to the development versions.
Comments
Comment #1
ronan commentedThanks for the patch.
This feature is available in the 2.x branch of the module (as well as offsite backups via ftp or S3) but this could be a good solution for anybody who doesn't want to make the move to an unstable branch of the module.
I'm not going to apply this to the 1.x branch as I'm considering that feature stable (so I can concentrate on bug fixes and make sure it remains totally stable while I work on 2).
Thanks again
Ronan
Comment #2
alansch commentedThis patch, as it applies to backup_migrate version 5.x-1.2 may now be found here.
Comment #3
ronan commentedClosing this in to clean up old tickets. Please reopen if it's still applicable.
Comment #5
ivnish