| 1 |
********************************************************************
|
| 2 |
D R U P A L M O D U L E
|
| 3 |
********************************************************************
|
| 4 |
Name: Filesystem Backup (fbu) module
|
| 5 |
Author: Robert Douglass <rob at robshouse dot net>
|
| 6 |
Last update: (See CHANGELOG for details)
|
| 7 |
Drupal: CVS
|
| 8 |
Dependencies:
|
| 9 |
* PEAR File_Archive: http://pear.php.net/package/File_Archive
|
| 10 |
* PEAR MIME_Type: http://pear.php.net/package/MIME_Type
|
| 11 |
* Crontabs
|
| 12 |
|
| 13 |
DESCRIPTION
|
| 14 |
********************************************************************
|
| 15 |
The Filesystem Backup module (fbu) simplifies the administrator's
|
| 16 |
job of keeping an offsite backup of the files that make up a Drupal
|
| 17 |
site. The module will send the administrator a series of uniquely
|
| 18 |
numbered archive files (zip, bz2, tgz etc.) that together make a
|
| 19 |
complete copy of your Drupal files.
|
| 20 |
|
| 21 |
FEATURES
|
| 22 |
********************************************************************
|
| 23 |
Mails an entire backup of the document root to the administrator in
|
| 24 |
chunks. The maximum size of each chunk is configurable so that
|
| 25 |
restrictions on email attachment size can be observed.
|
| 26 |
|
| 27 |
Works in batches (cron) so that the drain on system resources can be
|
| 28 |
controlled. The frequency of the backup process is configurable.
|
| 29 |
|
| 30 |
Can archive files to many popular (zip, bz2, tgz) archive types.
|
| 31 |
|
| 32 |
Can be configured to backup the entire filesystem (complete mode),
|
| 33 |
or only those files that are new or modified since the last backup
|
| 34 |
(only new mode).
|
| 35 |
|
| 36 |
|
| 37 |
DEPENDENCIES
|
| 38 |
********************************************************************
|
| 39 |
* PEAR File_Archive: http://pear.php.net/package/File_Archive
|
| 40 |
* PEAR MIME_Type: http://pear.php.net/package/MIME_Type
|
| 41 |
* Crontabs
|
| 42 |
|
| 43 |
INSTALLATION
|
| 44 |
********************************************************************
|
| 45 |
See the INSTALL.txt file in this directory.
|
| 46 |
|
| 47 |
WISH LIST
|
| 48 |
********************************************************************
|
| 49 |
* A way to include/exclude specific directories
|
| 50 |
* Special treatment for the settings folder so that only the current
|
| 51 |
site's settings.php + modules + themes etc. get included
|
| 52 |
* Performance improvements. The current implementation is limited
|
| 53 |
to 50 files per run because the scripts take too long otherwise
|
| 54 |
* Timeout detection; read the max execution time, time the script's
|
| 55 |
runtime, and stop before danger of timing out.
|
| 56 |
* Copy new/modified archives to an FTP directory instead of emailing
|
| 57 |
them.
|
| 58 |
* FTP new/modified archives to a remote server.
|
| 59 |
* Have the option of using Unix commands like cp to do the directory
|
| 60 |
scanning and file copying.
|
| 61 |
|
| 62 |
HOW TO USE THIS MODULES ONCE INSTALLED
|
| 63 |
********************************************************************
|
| 64 |
Read this after installing the module.
|
| 65 |
|
| 66 |
1. Navigate to admin/settings/fbu. Here you will be shown an error
|
| 67 |
message if the File_Archive library hasn't been installed properly.
|
| 68 |
2. Set all configuration options to your liking and press "Save
|
| 69 |
Configuration".
|
| 70 |
3. As long as the field "Automatically backup files every" is set
|
| 71 |
to something larger that 0 seconds, backups will start appearing
|
| 72 |
in your mailbox every cron run. The backups will be numbered
|
| 73 |
sequentially and each one will contain only a portion of the
|
| 74 |
entire backup. To restore a site from the backups files, it
|
| 75 |
would be necessary to extract all of them into the same directory,
|
| 76 |
in the order that they were received.
|
| 77 |
4. Any break in the sequential numbering of the backup files indicates
|
| 78 |
an incomplete backup (due to some sort of failure). If you have
|
| 79 |
an incomplete set of backup files, it is recommended that you
|
| 80 |
change the backups to complete mode and initiate a complete backup.
|
| 81 |
5. A complete backup will generally involve 30 or more chunks,
|
| 82 |
which in turn translates to 30 or more cron runs and emails.
|
| 83 |
If your crontab is set for every hour, then this will obviously
|
| 84 |
take more than a day to complete. After completing a complete
|
| 85 |
backup, the fbu module will then proceed to monitor your filesystem
|
| 86 |
for new or modified files and will mail these to you.
|