Mandi! Marco Gaiarin
In chel di` si favelave...
> No, i'm still working on snapshotting, next step backup; i've not clear if
> Include{} and Exclude{} fileset directive apply to 'stippath' or
> 'non-strippath' path...
OK, things start working. The script do correctly snapshot; if needed, i can
simply mount the snapshot elsewhere via a simple 'mount -t zfs'.
First note: fileset processing happens *BEFORE* job pre-script, so before
filesystem get actually snapshotted and mounted.
So, script in 'list' mode have to 'blindly' emit mount path, not able to
verify if effectively the FS get snapshotted and mounted.
Only a note.
Second note: path in fileset have to be 'absolute', not 'relative' to
'strippath', and this seems a bit misleading to me; an example fileset will
be:
FileSet {
Name = PVETerzoNodoSVTestSnap
Include {
Options {
accurate = sm
strippath = 4
wildfile = "*.tar"
wilddir =
"/rpool-backup/bacula/snapshots/bacula-FVG-SV-SVPVE3TestSnap/rpool-backup/varie/test/exclude"
Exclude = yes
}
#File = "\\|/root/snapshotBackup %n list"
File =
"/rpool-backup/bacula/snapshots/bacula-FVG-SV-SVPVE3TestSnap/rpool-backup/varie"
}
}
so effectively in 'wilddir' i have to use full path, or probably something
like this:
wilddir = "*/rpool-backup/varie/test/exclude"
but (apart a performace hit, i think) can match also other stuff, so can be
dangerous.
A question; currently i've split the jobs to 'interleave' the use of the
LTO9 unit, so i've different fileset with different path; a fileset for
example is:
FileSet {
Name = PVETerzoNodoSVSedi
Include {
Options {
Signature = MD5
accurate = sm
noatime = yes
}
File = "/rpool-backup/rsnapshot/.sync/FVG_PP"
File = "/rpool-backup/rsnapshot/.sync/FVG_3T"
File = "/rpool-backup/rsnapshot/.sync/FVG_TMS"
}
}
so in some sort of 'positive logic' (eg, listing dirs to backup); now i have
to conver this in 'negative logic', eg:
FileSet {
Name = PVETerzoNodoSVSedi
Include {
Options {
Exclude = yes
wilddir = "*"
}
Options {
Signature = MD5
accurate = sm
strippath = 4
wilddir
"/rpool-backup/bacula/snapshots/bacula-FVG-SV-SVPVE3TestSnap/rpool-backup/rsnapshot/.sync/FVG_PP"
wilddir
"/rpool-backup/bacula/snapshots/bacula-FVG-SV-SVPVE3TestSnap/rpool-backup/rsnapshot/.sync/FVG_3T"
wilddir
"/rpool-backup/bacula/snapshots/bacula-FVG-SV-SVPVE3TestSnap/rpool-backup/rsnapshot/.sync/FVG_TMS"
}
File = "\\|/root/snapshotBackup %n list"
}
}
...seems a bit overcomplicated for me... probably a better approach would be
to save somwhere on client (where /root/snapshotBackup get run) the list of
dirs to backup, for every job %n.
But still this fit not so well if there some complex setup (eg, if there's
specific exclusions inside include dirs...).
I'm a bit confused... thanks.
--
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
