This has come up again, and I wanted to post the answer here to help future 
searchers. The real problem was bacula can't back up symlinks, yet the data 
behind them could physically move across disks etc but in reality remain 
unchanged.

What I didn't know then is that linux can mount one folder to another using 
"mount -o bind". So, you can create a kind of virtual filesystem where the 
branches all point to where you'd otherwise have symlinks, but it still appears 
to bacula as single filesystem which it can then backup with no trouble, since 
there are no symlinks. The only thing to bear in mind is your FileSet Options 
needs to have the "onefs=no" entry (the default is "yes") otherwise it will not 
traverse the new "virtual" filesystem fully.

Also, be sure to "move" the branches if you do any maintenance after the Full 
backup has been performed rather than "copy" or it will think the data has 
changed. Its a neat system.

+----------------------------------------------------------------------
|This was sent by bill.damage AT yahoo DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------



------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users