Changes

# Ask all your users to log off. To ensure, that no data will be modified from now on, you may want to stop a couple of services on the 'prodbox‘, e.g. qpstmpd, qmail, crond (because of fetchmail), smb, atalk, httpd. Don't stop mysqld, as this service is required by mysqldump in the pre-backup event.

# Ask all your users to log off. To ensure, that no data will be modified from now on, you may want to stop a couple of services on the 'prodbox‘, e.g. qpstmpd, qmail, crond (because of fetchmail), smb, atalk, httpd. Don't stop mysqld, as this service is required by mysqldump in the pre-backup event.

# Run the job again<br><code># affa --run prodbox</code><br>This run should be completed quickly, as only the differences compared to the last run are backuped.

# Run the job again<br><code># affa --run prodbox</code><br>This run should be completed quickly, as only the differences compared to the last run are backuped.

# When this final run has finished, powerdown the 'prodbox‘ and rise the Affa box to a 'prodbox‘ clone.<br><code># affa --rise prodbox</code><br>

# When this final run has finished, powerdown the 'prodbox‘ (old hardware) and rise the Affa box (new hardware) to a 'prodbox‘ clone.<br><code># affa --rise prodbox</code><br>

# Reboot the server. Your users can now re-logon.

# Reboot the server. Your users can now re-logon.

With this method you should be able to move even a typical 50 Gbyte sized server to a new hardware with downtime less than 20 minutes. The rise time does not really depend on the total files size, but on the number of files and directories.

With this method you should be able to move even a typical 50 Gbyte sized server to a new hardware with downtime less than 20 minutes. The rise time does not really depend on the total files size, but on the number of files and directories.

==== Use Affa to backup to a NFS-mounted NAS or a local attached USB drive ====

==== Use Affa to backup to a NFS-mounted NAS or a local attached USB drive ====