I strongly recommend Affa.
It simply uses rsync and manages the process so that you have control over how many backups to keep (daily, weekly, monthly, yearly)
Additionally, *If* you use a dedicated backup server, you can "rise" it to become any of the backed-up systems -- in your case this is less useful since "rising" server B would give you a running version of server A, but now you're still down one server (server B).
Just because you're not planning to use the "rise" feature doesn't mean the other features aren't valuable.
So, in your case, you can think of Affa as:
- a simple way to setup public/private key encryption for ssh
- a secure way to do incremental rsync backups from one system to another
- a simple way to manage your backup policies
Note: if you tell Affa that the server at the other end is a SME server, then by default it only backs up the standard SME backup locations (taken from /usr/lib/perl5/site_perl/esmith/Backup.pm):
'home/e-smith',
'etc/e-smith/templates-custom',
'etc/e-smith/templates-user-custom',
'etc/ssh',
'root',
'etc/sudoers',
'etc/passwd',
'etc/shadow',
'etc/group',
'etc/gshadow',
'etc/samba/secrets.tdb',
'etc/samba/smbpasswd',
'etc/smbpasswd'
This list includes all locations where a virgin SME server stores data, but if you have installed any contribs that store data in /opt, or in any other non-standard locations, you'll need to set Affa's Include[0], Include[1], etc. appropriately.