501
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 8:
Line 8: − + Line 15:
Line 15: + + − + − + − + − + − + − + − + − + − + − * Report can be sent to the configured email addresses+ − + − + − − + Line 299:
Line 300: − Whith this kind of setup you cannot use the affa rise feature, as it requires the backup archive to be located on the same fileystem as the server installation. The rise option uses hardlinks, which are not working across filesystems.+
no edit summary
=== Description ===
=== Description ===
The main purpose of this affa package is to turn a SME 7 Server into a dedicated backup box in a few minutes. Affa backups as many as you like SME servers or any other servers which have sshd running and rsync installed. Once it was configured, Affa runs reliable and unattended and send warning message in case of an error.
The main purpose of this affa package is to make a SME 7 Server a dedicated backup box in a few minutes. Affa backups as many as you like SME servers or any other servers which have sshd running and rsync installed. Once it was configured, Affa runs reliable and unattended and send warning messages in case of any errors.
All backup archive are full backups. As Affa make use of the hardlink technique. Therefore a new full backup only needs disk space for the differences plus the filesystem overhead for the hardlinks and directories (which is typically 2-3%).
All backup archive are full backups. As Affa make use of the hardlink technique. Therefore a new full backup only needs disk space for the differences plus the filesystem overhead for the hardlinks and directories (which is typically 2-3%).
A special feature is the rise option, which allows you to rise the backup server to your production server from a backup archive in case of a dead loss of your production server. The rise is executed within a extremly short time, even with huge ammount of data. The rise feature uses hardlinks and therefore does not use up additional disk space.
A special feature is the rise option, which allows you to rise the backup server to your production server from a backup archive in case of a dead loss of your production server. The rise is executed within a extremly short time, even with huge ammount of data. The rise feature uses hardlinks and therefore does not use up additional disk space.
Affa is a command line tool for system administrators and is intentionally designd without a GUI. Therefore it can be efficiently managed on the console and over slow internet connections.
==== Affa features at a glance ====
==== Affa features at a glance ====
* Makes full backups with every scheduled run
* Makes full backups on every scheduled run
* Keeps configurable number of scheduled, daily, weekly, monthly and yearly full backup archives
* Keeps a configurable number of scheduled, daily, weekly, monthly and yearly full backup archives
* Using rsync with optional compression for low traffic allows backups over the internet/VPN
* Using rsync with optional compression for low traffic allows backups over the internet/VPN
* Uses hardlink technique, i.e. physical disk space only needed for the differences between two full backups
* Uses hardlink technique, i.e. physical disk space only needed for the differences between two full backups
* Backup jobs are started by crond
* Backup jobs are started by the cron daemon
* Backups the default e-smith directories/files with property SMEServer set to yes
* Backups the default e-smith directories/files, when property SMEServer is set to yes
* Additional directories/files can be included
* Additional directories/files can be included
* Directories/files can be excluded from the backup
* Directories/files can be excluded from the backup
* Non-SME server linuxes can be backuped by setting SMEServer property to no and using a include list
* Non-SME server linuxes can be backuped by setting the SMEServer property to no and using a include list
* Configurable nice level for rsync processes on backup and source server
* Configurable nice level for rsync processes on the backup and source server
* Optional run of custom programs before and after a job run (e.g. running tape backup)
* Optional run of custom programs before and after a job run (e.g. running tape backup)
* Checks the disk space left after a job run with warning levels strict, normal or risky
* Checks the disk space left after a job run with warning levels strict, normal or risky
* Extensive checking of failure conditions
* Extensive checking of failure conditions
* Sends failure messages to a configurable list of email addresses
* Sends failure messages to a configurable list of email addresses
* Sends warning message, if the backup server run out of disk space
* Sends a warning message, if the backup server run out of disk space
* Installs an optional watchdog on the source server for the case the backupserver fails
* Installs an optional watchdog on the source server for the case the backupserver fails
* Watchdog sends warning, if an expected backup did not run
* Watchdog sends warning, if an expected backup did not run
* Watchdog sends a daily reminder message, if the error continues unchecked
* Watchdog sends a daily reminder message, if the error continues unchecked
* Option to display current status of all jobs showing times of last and next run
* Option to display current status of all jobs showing times of last and next run, size and disk usage
* Status can be mailed on a daily, weekly or monthly schedule
* Status can be mailed on a daily, weekly or monthly schedule
* Option to display reports of all stored backups shown size, tranferred volume, disk usage and more
* Option to display all exiting archives of a job shown date, size, nbr of files and disk usage
* Option to send the public key to the source server
* Option to send the public DSA key to the source server
* Option to rise the backup server to a production server from a backup. For SME 7 only.
* Option to rise the backup server to a production server from a backup. For SME only
* The rise feature does not physically move data and therefore is extremly fast and needs (almost) no disk space
* The rise option does not physically move data and therefore is extremly fast and needs no disk space
* Rise option can be run remotely as the ethernet drivers of the backup server are preserved
* Rise option can be run remotely as the ethernet drivers of the backup server are preserved
* Compares installed RPMs on source with backup server. Sends warning message, if not in sync
* Compares installed RPMs on source with backup server. Sends warning message, if not in sync
* Undo rise option to restore the backup server
* Undo rise option to restore the backup server
* Configurable via a e-smith style db, with one record for each job and a default record for all jobs
* Configurable via a e-smith style db, with one record for each job and a default record for all jobs
* Logs in /var/log/affa with optional debug switch for high verbosity
* Logs in /var/log/affa with optional debug switch for more verbosity
* Log files are rotated weekly, with 5 logs kept
* Log files are rotated weekly, with 5 logs kept
===== Limitations =====
===== Limitations =====
With this kind of setup you cannot use the affa rise feature, as it requires the backup archive to be located on the same fileystem as the server installation. The rise option uses hardlinks, which are not working across filesystems.
===== Automount =====
===== Automount =====
