Difference between revisions of "Iridia Backup"
From IridiaWiki
Jump to navigationJump to searchChristensen (talk | contribs) |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | ==Strategy== |
||
| + | *Full backup once a month (start of the month) |
||
| + | *Differential backup for the rest of the month |
||
| + | |||
| − | Arrange for permanent my.cnf file. Security password. |
||
| + | ==Locations== |
||
| + | *servicebackup@iridia:/home/servicebackup/iridia_service_backup_system/ |
||
| + | *servicebackup@leibniz:/home/servicebackup/iridia_service_backup_system/ |
||
| + | *iridiaserver@fallopius:/home/iridiaserver/service_backup_dar/ |
||
| + | |||
| + | *Backup system under version control at: |
||
| + | **svn+ssh://rogrady@iridia.ulb.ac.be/usr/local/share/svn_repositories/iridia_service_backup_system |
||
| + | |||
| + | ==Structure== |
||
| + | *Each service has its own directory containing four files: |
||
| + | **<service>_suspend |
||
| + | **<service>_resume |
||
| + | **<service>_backup |
||
| + | **<Service>_restore. |
||
| + | |||
| + | *The idea is that to backup a service you run the scripts: suspend backup resume and to restore a service you run: suspend restore resume |
||
| + | |||
| + | *The scripts backup.sh and restore.sh in the top level directory do this in turn for each service. Backup and restore functions, along with config in the form of environment variables lives in the file include.sh. This gets included from each script. |
||
| + | |||
| + | * If you are running the scripts standalone (not from backup.sh), you must set environment variable SERVICE_BACKUP_SYSTEM_DIR. |
||
| + | ** e.g. export SERVICE_BACKUP_SYSTEM_DIR=/home/servicebackup/iridia_service_backup_system |
||
| + | |||
| + | ==Todo== |
||
| + | * Increase iridiaserver user quota on fallopius (to 250GB?) - Anders -- '''Done. I have removed the quota for user (use edquota)''' |
||
| + | * Enhance backup scripts to delete data older than certain threshold - Rehan |
||
| + | * Alex - Sort out security on backup scripts: mysql passwd |
||
| + | * Put servicebackup@iridia:/home/servicebackup/iridia_service_backup_system/backup.sh into daily cron - Anders |
||
| + | * Make script logging better, so we can see what happens when there is a failure (email alerts?) - Rehan / Alex |
||
| + | * ssh times out on leibniz, interrupting restore - Anders -- '''Need more info on what goes wrong and when''' |
||
| + | |||
| + | ==Dar Stuff== |
||
| + | ;Links |
||
| + | * http://linuxweblog.com/node/283 (Especially comments at end) |
||
| + | * http://gradha.sdf-eu.org/textos/dar-differential-backup-mini-howto.en.html |
||
| + | |||
| + | ==Issues to check== |
||
| + | * Ownership of files (maybe only symlinks), sometimes they are wrong: |
||
| + | ** /home/mbiro/public_html/thesis/index.html - this is a symlink and got the wrong ownership (root) when it was copied from iridia to leibniz. Make sure that the owner is mbiro after a backup has been restored. |
||
Latest revision as of 16:49, 8 August 2006
Strategy
- Full backup once a month (start of the month)
- Differential backup for the rest of the month
Locations
- servicebackup@iridia:/home/servicebackup/iridia_service_backup_system/
- servicebackup@leibniz:/home/servicebackup/iridia_service_backup_system/
- iridiaserver@fallopius:/home/iridiaserver/service_backup_dar/
- Backup system under version control at:
Structure
- Each service has its own directory containing four files:
- <service>_suspend
- <service>_resume
- <service>_backup
- <Service>_restore.
- The idea is that to backup a service you run the scripts: suspend backup resume and to restore a service you run: suspend restore resume
- The scripts backup.sh and restore.sh in the top level directory do this in turn for each service. Backup and restore functions, along with config in the form of environment variables lives in the file include.sh. This gets included from each script.
- If you are running the scripts standalone (not from backup.sh), you must set environment variable SERVICE_BACKUP_SYSTEM_DIR.
- e.g. export SERVICE_BACKUP_SYSTEM_DIR=/home/servicebackup/iridia_service_backup_system
Todo
- Increase iridiaserver user quota on fallopius (to 250GB?) - Anders -- Done. I have removed the quota for user (use edquota)
- Enhance backup scripts to delete data older than certain threshold - Rehan
- Alex - Sort out security on backup scripts: mysql passwd
- Put servicebackup@iridia:/home/servicebackup/iridia_service_backup_system/backup.sh into daily cron - Anders
- Make script logging better, so we can see what happens when there is a failure (email alerts?) - Rehan / Alex
- ssh times out on leibniz, interrupting restore - Anders -- Need more info on what goes wrong and when
Dar Stuff
- Links
- http://linuxweblog.com/node/283 (Especially comments at end)
- http://gradha.sdf-eu.org/textos/dar-differential-backup-mini-howto.en.html
Issues to check
- Ownership of files (maybe only symlinks), sometimes they are wrong:
- /home/mbiro/public_html/thesis/index.html - this is a symlink and got the wrong ownership (root) when it was copied from iridia to leibniz. Make sure that the owner is mbiro after a backup has been restored.
