Hi Henri, That's not something I'd looked into, so you're very likely right.
I'll check in with the site next week and see if it indeed rings true with this backup system. Regards, Michael On 31/05/2012, at 8:42 PM, henri wrote: > From my research LBackup will backup across file system boundaries (I believe > this is what are trying to do). I found some comments in the source code > mentioning wheather the -x option should be passed to LBackup. It was decided > at some point that the -x should not be passed to rsync because it was deemed > that some people may want to do exactly what (I belive you are trying to do > at the moment). > > On Mac OS X the directory /Volumes is hidden. As such, when LBackup is used > to create a backup of this directory it becomes hidden in the backup as well. > > I performed a test using "/" as the source directory and use the excludes > approach listed at the following URL : > http://www.lbackup.org/developer/advanced_excludes_file_examples > > An example exlcudes.txt file I used is quoted below : > >> + Applications >> + Applications/Address Book.app/*** >> + Volumes >> + Volumes/750GB >> + Volumes/750GB/sos/*** >> - * > > > Basically, this resulted in the backup containing "Applications" and > "Volumes" at the root level of "Section.0". However, the "Volumes" directory > was hidden. > > There are a number of options with regards making access to the "Volumes" > directory within the backup directory simple. Just one example is outlined > below using a symbolic link. First you could make a symbolic link to > "/Volumes" directory using the command below : > > cd / ; ln -s ./Volumes ./volumes.link > > Then it is simply a matter of adding this link "voluems.link" to the backup > (via the excludes file). There is an example quoted below : > >> + Applications >> + Applications/Address Book.app/*** >> + Volumes >> + Volumes/750GB >> + Volumes/750GB/sos/*** >> + volumes.link >> - * > > > If you have any issues, then please let me know. > > There are various other approaches including some sort of pre-action script. > > If you have any troubles / suggestions then let me know. > > Another approach would be to have two or more backups (as many as required to > cover all the source directories you wish to backup). > > Hope this helps. > > > > _______________________________________________ > lbackup-discussion mailing list > http://www.lbackup.org > > Change options or unsubscribe : > http://lbackup.org/mailing_lists > _______________________________________________ lbackup-discussion mailing list http://www.lbackup.org Change options or unsubscribe : http://lbackup.org/mailing_lists
