Diferencia entre revisiones de «Drush-Based Backup Plan»
| Línea 6: | Línea 6: | ||
# Put the site in maintenance mode | # Put the site in maintenance mode | ||
| + | # Clear cache | ||
| + | # Delete watchdog logs | ||
# Tar and zip the whole drupal installation | # Tar and zip the whole drupal installation | ||
# Dump the SQL Database for the whole drupal installation | # Dump the SQL Database for the whole drupal installation | ||
| Línea 11: | Línea 13: | ||
# Get the site back online | # Get the site back online | ||
# Move all backup data to a specific location | # Move all backup data to a specific location | ||
| − | # Rotate backups | + | # Rotate backups † |
| − | + | † There are widely used rotation tools like log-rotate, so we could eventually check if we could incorporate rotation step as a module | |
= Offsite Backups = | = Offsite Backups = | ||
Revisión del 02:09 18 feb 2011
This wiki page will document the design, missing features and implementation plan of a backup plan for Floss-Pa's site based on Drush. Feel free to contribute by adding missing steps, better implementation details or by contributing with code.
Ideal Steps
Ideally, the set of steps that should be executed in order to back up the Drupal site should be:
- Put the site in maintenance mode
- Clear cache
- Delete watchdog logs
- Tar and zip the whole drupal installation
- Dump the SQL Database for the whole drupal installation
- Tar and zip the SQL dump
- Get the site back online
- Move all backup data to a specific location
- Rotate backups †
† There are widely used rotation tools like log-rotate, so we could eventually check if we could incorporate rotation step as a module
Offsite Backups
The above steps will guarantee backups of the site will always exist on the server, but it is also required to have backups in at least two (physically) more different places. There's no offsite backup plan for the moment. Current list of volunteers to store offline backups are:
