Difference between revisions of "Backup Server"
Line 1: | Line 1: | ||
+ | Everyone has 20GB available space on fallopius. You are responsible for backup up your own data into the space you have allocated on fallopius. There is an old automated backup system that is still in place, but no longer supported. It was written by Halva and uses rdiff-backup. Instructions here: [[Old Backup System (Halva's rdiff system)]]. Good luck. |
||
− | [[Old Backup System (Halva's rdiff system)]] |
||
+ | |||
+ | All data on the iridia server is backed up by a separate (supported) nightly script that uses dar. This is an incremental backup program that is like a network version of tar. The scripts are run by the crontab of the user servicebackup on iridia using the script /home/servicebackup/iridia_service_backup_system/backup.sh. |
||
+ | |||
+ | The backed up data is stored in the directory are stored on fallopius in the directory /home/iridiaserver/service_backup_dar. |
||
+ | To restore data you will need to familiarise yourself with the dar program, or use the script /home/servicebackup/iridia_service_backup_system/restore.sh on iridia. |
||
+ | |||
+ | The data that is backed up is divided into 'services'. A list of these services can be found in the directory /home/servicebackup/iridia_service_backup_system/services. Each service is a directory that must at a minimum contain scripts called <SERVICE_NAME>_backup.sh and <SERVICE_NAME>_restore.sh. These two scripts should make use of the functions provided by the file /home/servicebackup/iridia_service_backup_system/include.sh which provide wrappers around the dar commands. Optionally, inside each service directory there can be scripts called <SERVICE_NAME>_suspend.sh and <SERVICE_NAME>_restore.sh which will be called before and after the backup, and can be used to stop and start any processes that might interfere with the integrity of the backed up data if they are left running. |
Revision as of 13:03, 14 May 2008
Everyone has 20GB available space on fallopius. You are responsible for backup up your own data into the space you have allocated on fallopius. There is an old automated backup system that is still in place, but no longer supported. It was written by Halva and uses rdiff-backup. Instructions here: Old Backup System (Halva's rdiff system). Good luck.
All data on the iridia server is backed up by a separate (supported) nightly script that uses dar. This is an incremental backup program that is like a network version of tar. The scripts are run by the crontab of the user servicebackup on iridia using the script /home/servicebackup/iridia_service_backup_system/backup.sh.
The backed up data is stored in the directory are stored on fallopius in the directory /home/iridiaserver/service_backup_dar. To restore data you will need to familiarise yourself with the dar program, or use the script /home/servicebackup/iridia_service_backup_system/restore.sh on iridia.
The data that is backed up is divided into 'services'. A list of these services can be found in the directory /home/servicebackup/iridia_service_backup_system/services. Each service is a directory that must at a minimum contain scripts called <SERVICE_NAME>_backup.sh and <SERVICE_NAME>_restore.sh. These two scripts should make use of the functions provided by the file /home/servicebackup/iridia_service_backup_system/include.sh which provide wrappers around the dar commands. Optionally, inside each service directory there can be scripts called <SERVICE_NAME>_suspend.sh and <SERVICE_NAME>_restore.sh which will be called before and after the backup, and can be used to stop and start any processes that might interfere with the integrity of the backed up data if they are left running.