Now that you are familiar with the Replication Wizard, this section will deepen your understanding so you can move on to more advanced configurations. If your replication needs are simple and typical, you may not need to read this section.
If you do not run your backups with the option lateLinks at the moment and want to use replication, you have to enable it when using storeBackup.pl. This means in practice, that you have previously been running something like:
# storeBackup.pl -f stbu.config
Now, and in the future, you will set lateLinks=yes in the configuration file and use these two commands (which could be put into one executable script):
# storeBackup.pl -f stbu.config # storeBackupUpdateBackup.pl -b <dirOfMasterBackup>
Here, storeBackup.pl will create the deltas described above which are stored in your master backup. If you look into this data, you will see that there are e.g., no hard links to already existing files in the previous backup. After running storeBackupUpdateBackup.pl all the ``missing'' steps (like linking, changing permissions) are done. It is nothing else than splitting the work storeBackup.pl does as an all-in-one application into two different steps.
So the result of these two commands will be exactly the same - a full backup like before (when you didn't use option lateLinks and ran one command). The batch above is just a simple example; you can also run storeBackupUpdateBackup.pl e.g., on your server at a later time (see section 7.6 for more information).
Naturally, if you want to use replication, you have to configure it first. The Replication Wizard can do this for you. However, in this section we demonstrate the manual steps.
If we use the simple example above, replication to the backup copy on the external disk works as follows. I assume we have four different directories involved:
backupTreeName=myMasterBackup backupType=master seriesToDistribute=homeBackup deltaCache=/deltaCache
In the master backup configuration file, a value for backupTreeName is only needed for error messages, warnings and so on. it is mostly there for future enhancements, so all directories will have a unique identifier.
You can change the unique identifier for the parameter backupTreeName to whatever you want (here, myMasterBackup was chosen). But you have to set backupType to master!
backupCopy0=myBackupCopy homeBackup ;backupCopy1= ;backupCopy2=
Do not change the other commented keywords backupCopy1 to backupCopy9 because we only one replication. (The delta cache is the central distribution place for all defined replications.) The entry myBackupCopy is just a name (not a path) for the copied backup on your external disk. You can choose any name you want, but it has to be exactly the same as in the configuration file for your backup copy at /extDisk/backupCopy. After ``myBackupCopy'' you have to enter the list of series you want to replicate. It is only the series homeBackup in this example.
backupTreeName=myBackupCopy backupType=copy seriesToDistribute=homeBackup deltaCache=/deltaCache
The name of the backup must be the same as specified in the configuration file of the deltaCache which is loated at /deltaCache/deltaCache.conf. The backupType must be 'copy', so the program storeBackupUpdateBackup.pl knows it has to copy the deltas from the deltaCache.48
After you set up the environment, simply do the following:
to complete your backup copy and to replicate the deltas to the delta cache. The best is to do this directly after the run of storeBackup.pl. If you have an own server it is easy to run this command at night via cron on the server.
When it is ready, umount the external disk and disconnect it from you computer.
Heinz-Josef Claes 2014-04-20