Line 17:
Line 17:
==== Affa features at a glance ====
==== Affa features at a glance ====
−
* Makes full backups on every scheduled run
+
* Affa is secure: All transfers and connections are made by using the ssh protocol with public/private key authentication
+
* Periodically runs unattended full backups. Only differences to the previous full backup are transferred over the network
+
* Using rsync with optional bandwidth limit and compression allows backups over the internet
+
* Uses hardlink technique, i.e. physical disk space only needed for the differences between two full backups
* Keeps a 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
+
* The archives are browsable. No need to unpack them first.
−
* Uses hardlink technique, i.e. physical disk space only needed for the differences between two full backups
* Backup jobs are started by the cron daemon
* Backup jobs are started by the cron daemon
−
* Backups the default e-smith directories/files, when property SMEServer is set to yes
+
* Interrupted jobs continuing with already tranferred data when restarted
−
* Additional directories/files can be included
+
* Backups the default e-smith directories and files, when property SMEServer is set to yes
−
* Directories/files can be excluded from the backup
+
* Additional directories and files can be included
−
* Non-SME server linuxes can be backuped by setting the SMEServer property to no and using a include list
+
* Directories and files can be excluded from the backup
+
* Non-SME server linuxes can be backuped by setting the SMEServer property to no and using an include list
* Configurable nice level for rsync processes on the 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)
Line 38:
Line 41:
* 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 all existing archives of a job shown date, size, nbr of files and disk usage
* Option to display all existing archives of a job shown date, size, nbr of files and disk usage
−
* Option to send the public key to the source server (SME Server only)
+
* Option to send (and revoke) the public key to the source server (SME Server only)
−
* 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 7 only
−
* The rise feature does not physically move data and therefore is extremly fast and needs (almost) no disk space
+
* The rise feature does not physically move data and therefore is extremly fast and needs (almost) no extra 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 NIC driver configuration 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 more verbosity
+
* Logs to /var/log/affa/JOB.log and /var/log/affa/affa.log with optional debug switch for higher verbosity
* Log files are rotated weekly, with 5 logs kept
* Log files are rotated weekly, with 5 logs kept