Diferencia entre revisiones de «Drush-Based Backup Plan»

De FlossPa Wiki
Saltar a: navegación, buscar
(Offsite Backups)
(SCP latest backup)
 
(No se muestran 2 ediciones intermedias del mismo usuario)
Línea 1: Línea 1:
 
This wiki page will document the design, missing features and implementation plan of a backup plan for Floss-Pa's site based on [http://drupal.org/project/drush Drush]. Feel free to contribute by adding missing steps, better implementation details or by contributing with code.
 
This wiki page will document the design, missing features and implementation plan of a backup plan for Floss-Pa's site based on [http://drupal.org/project/drush Drush]. Feel free to contribute by adding missing steps, better implementation details or by contributing with code.
  
= Ideal Steps =
+
= Offsite Backups =
  
Ideally, the set of steps that should be executed in order to back up the Drupal site should be:
+
It is required to have backups in at least two more (physically) different places. Current list of volunteers to store offline backups are:
  
# Put the site in maintenance mode
+
* [[User:dMaggot|David E. Narváez]]
# Clear cache
+
* [[User:danilo04|Danilo Domínguez P.]]
# 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
+
== Ofssite Backups Plans ==
  
= Offsite Backups =
+
=== Rsync backups folder ===
  
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:
+
In this schema, every volunteer will set up a cron script to run rsync on the backups folder. The location of the backup folder information and credential information will be provided by the admins of the site.
  
* [[User:dMaggot|David E. Narváez]]
+
'''Pros'''
* [[User:danilo04|Danilo Domínguez P.]]
+
* rsync would already know what's the latest backup to download based on the changes
 +
* rsync would automatically deal with removal of old backup files that were previously removed from the server
 +
 
 +
'''Cons'''
 +
* There are security considerations to take care of, since volunteers will have access to an account at Floss-Pa's server, which would probably be a dedicated backup account
 +
 
 +
=== SCP latest backup ===
 +
 
 +
In this schema, every volunteer will set up a cron script to list latest backup file and copy it from Floss-Pa's server to their own server.
 +
 
 +
'''Pros'''
 +
 
 +
'''Cons'''
 +
* Same security considerations of rsync
 +
* All date-related handling like removing old backups and determining which is the latest backup will be done by the script

Revisión actual del 03:00 20 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.

Offsite Backups

It is required to have backups in at least two more (physically) different places. Current list of volunteers to store offline backups are:

Ofssite Backups Plans

Rsync backups folder

In this schema, every volunteer will set up a cron script to run rsync on the backups folder. The location of the backup folder information and credential information will be provided by the admins of the site.

Pros

  • rsync would already know what's the latest backup to download based on the changes
  • rsync would automatically deal with removal of old backup files that were previously removed from the server

Cons

  • There are security considerations to take care of, since volunteers will have access to an account at Floss-Pa's server, which would probably be a dedicated backup account

SCP latest backup

In this schema, every volunteer will set up a cron script to list latest backup file and copy it from Floss-Pa's server to their own server.

Pros

Cons

  • Same security considerations of rsync
  • All date-related handling like removing old backups and determining which is the latest backup will be done by the script