"Graham Sparks" <g...@hotmail.co.uk> kirjoitti viestissä
news:snt109-w122ca2a947f15367ab1a9481...@phx.gbl...
Hello,
I'm a fairly new Bacula user (all daemons running on same machine-Ubuntu804
and a FD on Windows XP Home client). I've set up a Full backup of a drive on
the client that ran on Saturday and have an incremental backup of the same
fileset done on Monday. Having noticed that the file size was large for the
two day's worth of data, I excluded the Windows swap file from the fileset.
Today's incremental however wouldn't run. Bacula insisted on running a new
full backup.
I'm aware that this is because I have changed the fileset, but read about an
option (Ignore FileSet Changes = yes) that is supposed to ignore that fact and
continue to perform incrementals. After adding this and reloading the
configuration, Bacula still won't perform an incremental backup.
Is there a reason why it still refuses to run an incremental backup (I
deleted the JobID for the failed promoted Full backup with the delete JobIB
command)?
Have a try if restarting the director helps.
Reload should be enough, but recently I noticed that 3.0.3 didn't recognize
fileset option changes reliably after reload.
--
TiN
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
