Hello,
On 08.11.2005 18:06, Stephan Ebelt wrote:
Hello,
I do not have a problem in the sense that something does not work - I
just would like to hear some opinions as I am not sure how fool proof my
solution is:
I *love* fool proof solutions :-)
SITUATION
There are multiple clients and I like to have one fileset for all of
them. As they are quite similar. Each one looks like
/u01
/u02
...
/u09
/u10
...
/uNN
Interesting setup...
the number of /uNN directories is variable. But not more than 2 digits.
Each /uNN directory is a mountpoint. It is never NFS. Always local disks.
I want to avoid the
File = "\\|sh -c \"<some-shell-command>" "
approach as it would IMHO cause me a headache to write a shell command
that works on all my OSes with different shell/find/awk/... versions.
Well, with different OSes and shells and tools that would be an
interesting exercise. Or, in other words, I understand why you don't
want that way.
MY SOLUTION
Make the fileset with 'onfs=no' and include '/'. Then use regular
expressions to exclude everything but the things I want. Here is what I
have so far:
FileSet {
Name = "Data-UNIX-FileServer"
Ignore FileSet Changes = yes # can't effort a full right now
Include {
Options {
signature=MD5
onefs = no # cross all filesystems
fstype = ext2 # should avoid possible NFS mounts?
You might want to add other FSes as well, depending on the possibility
that you also have to back up BSD or Mac or Sun or whatever systems.
regex = "^\/u[0-9]{2}" # /u01 to /uNN directories
Anchored RE - good idea :-)
}
Options {
# exclude just everything
exclude = yes
regex = ".*"
}
# the regular expressions will filter things
File = /
}
}
this seems to work so far. I tested it with estimate listing on 1.38.0
(FD, Dir, SD) and the list looks very promising. I did not actually run
a backup job yet.
Well, I didn't try your fileset, but it does look promising. It seems
that you understood the two options blocks - default and more detailed
ones - correctly which I never did :-)
can anyone see any problems with this procedure?
No. Definitely not. You approach looks like one of the solutions I try
to keep in mind.
Maybe beside possible mount-loops because of onefs=yes. I tried to limit
that possibility further down by adding fstype=ext2. Is that supposed to
work as I expect?
It should. But it would still allow loop devices...
a side note: when adding 'Include=yes' to the first options resource
bacula gives me a syntax error saying that this is not known at this
position. According to one sample in the manual it /should/ be valid?
However I can not find the include option mentioned in the options list
- so I would guess that the FileSet example is outdated.
Quite possible, considering the number of possible ways to use options
blocks in filesets. I fact I suspect that Kern himself doesn't fully
understand the implications of options with includes and exludes and REs
and whatnotelse ;-)
That said, once you prooved that your fileset works, it would be a good
contribution to the manual.
Arno
best regards,
Stephan
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
