Mark,
You already have a placeholder item in the wiki called:
[Todo] Local Affa server plus a Affa server in remote location.
Does this represent an un-umplemented/tested capability, or is it
just a matter of documenting something that already has been proven?
Mark
Originally have planned to implement some kind of 'chained' setup, i.e. the local Affa server triggers the run on the remote Affa server via the PostJobCommand, which backups the just created scheduled.0 archive. You can do this with Affa as it is now, but on the remote all the archives contains the scheduled.0 of the local Affa server. This makes it impossible to switch over to a standard setting, which backups the production server directly. The remote Affa should run with an option to manipulate the pathes, where I haven't solution for, yet. So I have postponed it for the moment.
The idea of a 'chained' setup was to reduce the load on the production server. But on today's hardware with multi core cpus and fast disks one will hardly notice the additional load.
It is exactly how I want to use Affa.
My standard setup for critical servers is a local Affa server with short backup intervals (1 or 2 hours) and a remote Affa server that directly backups the production server nightly (or more frequently if hardware power and bandwidth is sufficient). When you loose your production server you can rise the local Affa server, setup a new Affa hardware and copy the archive from the remote Affe server to it.
When you loose both the production and local Affa server (fire, surge or the like) you still have the Affa server in the remote location. This setup scenario is pretty save, as it's most unlikely that you will loose 3 machines in two independent locations at the same time.
Edit: latest Affa version is 0.6.0