Due to a copy/paste error, a FileSet on one of my Bacula installations (Director & SD Bacula 5.2.6 on CentOS 6, FD Bacula 5.2.6 on Windows Server 2003) initially read:
FileSet {
Name = "Galadriel Archive"
Include {
Options {
signature = MD5
Exclude = yes
IgnoreCase = yes
}
File = "H:/Public/Archive"
}
}
which did of course back up nothing at all. After removing the spurious
"Exclude = yes" line, I was surprised to find that the next job wasn't
promoted from Incremental to Full, and indeed only backed up those files
which were touched since the preceding "empty set" backup. Is it
possible that this particular modification of the FileSet definition is
not detected as a change by Bacula?
--
Tilman Schmidt
Phoenix Software GmbH
Bonn, Germany
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
