Example 6: Using lateLinks

After reading the previous example, it should not be a problem for you to understand how to configure multiple source directories (see example 2) and how to configure cross linking between to backup (see examples 3 and 4). I now assume, that you generate a configuration file with

# storeBackup.pl -g stbu.conf

• Configure storeBackup to make a backup to your backup directory via NFS. Configure all options in the configuration file stbu.conf and set:

  lateLinks = yes
  lateCompress = yes
  doNotDelete = yes
  

  If you have a high bandwidth line, there is no need to change lateCompress from no to yes. Because of doNotDelete = yes you will not have to wait for the deletion of old backups.

• Make your backup(s). (Like always, the very first backup will be slow.) You do not have to do anything more from your client (NFS client) side.
• Start (via cron) on the server (NFS server = backup server):

  storeBackupUpdateBackup.pl -b <backupDirDir> \
         -l /tmp/stbuUpdate.log
  

  This will generate the missing hard links (and others).
• Start (via cron) on the server:

  storeBackupDel.pl -f <cf1> -b <backupDirDir> \
         --unset doNotDelete
  

  This will overwrite (unset) also the doNotDelete flag in the configuration file.
  You have to set backupDir in the command above to the same location you specified in the configuration file of storeBackup.pl. If it is the same path on the client and on the server, you do not have to overwrite it (you do not have to specify it on the command line of storeBackupUpdateBackup.pl). You can read more about configuration files and command line options in section 7.1.

You can also make the very first backup with the lateLinks option set. Naturally, you have to run storeBackupUpdateBackup.pl to get a complete backup.

Detailed explanations about option lateLinks are available in Using option lateLinks.