501
edits
Changes
From SME Server
Jump to navigationJump to search→Example setups
# Standard setup<br>...
# Standard setup<br>...
# Chained setup<br>...
# Chained setup<br>...
==== Backup a single ibay ====
Suppose you want to backup the ibays 'staff1' and 'staff2' on your production server with WAN IP 82.123.1.1 to an Affa server in a different location over the internet every night at 2:30am.
# log into the Affa server and install the packages as described above.
# generate the DSA keys and send the public key to the production server<br><code># affa --send-keys 82.123.1.1</code>
# copy the config helper script sample<br><code># cp /usr/lib/affa/jobconfig-sample.pl /root/ibay-staff-job.pl </code>
# edit /root/ibay-staff-job.pl and set<br><code>my $jobname='ibay-staff';</code><br>and<br><code>'remoteHostName‘=>'82.123.1.1',</code><br><code>'TimeSchedule'=>'0230',</code><br><code>'SMEServer'=>'no',</code><br><code>'Include[0]'=>'/home/e-smith/files/ibays/staff1',</code><br><code>'Include[1]'=>'/home/e-smith/files/ibays/staff2',</code>
# write the configuration<br><code># /root/ibay-staff-job.pl</code>
# check next morning<br><code># affa --status</code><br><code># ls /var/affa/ibay-staff</code>
==== Two production servers backup each other ====
==== Two production servers backup each other ====
===== Limitations =====
===== Limitations =====
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.
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.
=== Restore ===
=== Restore ===
