Am 29.10.2011 01:12, schrieb Blake Dunlap:
> Greetings,
> 
> Minor question, figured I'd try the users list first in case you guys could
> help. I have the following directory structure on a server that I back up,
> but there's a minor twist:
> 
> FileSet {
>   Name = "filemonster-fs"
>   Include {
> *snip*
> 
>     File = /etc
>     File = /usr/local/sbin
>     File = /snapshot/webdata
>   }
> *snip*
> 
> }
> 
> 
> That snapshot directory (/snapshot/webdata) is actually a mounted snapshot
> of /data. Ideally, I would like bacula to store this as the actual path, and
> not the path it gets backed up from. It would greatly simplify restores
> among other things.
> 
> I know there is the option of stripping X pieces of the path from a fileset,
> but it is fileset wide to my knowledge. Is the best practice to just add a
> snapshot dir to the beginning and keep the same path structure, and have a
> seperate FileSet for each such item?
> 
> The reason I ask is I am also considering adding a PathReplace directive (or
> something similar) to facilitate the above, and I want to judge input first,
> and see if there is a better design option.
> 
> 
> -Blake

Hi,

I have something similar. I take most of my backups from ZFS snapshots,
which means I have '.zfs/snapshot/backup/' in in the middle of all my
paths. To restore from that, I use 'RegexWhere' in my restore job
definition, to snip that part out.


Regards,
Christian Manal

------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World™ now supports Android™ Apps 
for the BlackBerry® PlayBook™. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to