John Kodis writes:
I'd guess that either you've changed something in your filesystem --
touched most of the files, or changed where a large filesystem is
mounted -- or that Bacula overrode your request.
Can't really imagine any of the above.
Anyone could confirm that this sequence works for them:
+ Create full job
+ Change job to incremental
+ Do estimate on job (and estimate will show only changed files)
Even if you specify
an incremental, Bacula will perform a full backup if there's no
suitable full backup found.
Full backup finished without problems. Got email with status and I don't
recall seeing any problems.
And if the bacula-dir did die, will running backups stop?
Yup. Even if you're sure that your configuration files are correct,
I'd be surprised if the Bacula director could survive the type of
mid-job restart the you seem to be contemplating.
I really should have written "if bacula-dir will die after doing a reload
if there are any syntax errors"
I have no idea, nor any reason to care as the database stuff has
always just worked. Are you just curious, or is there some other
issue that you're chasing?
It is actually a possible PostgreSQL performance issue. If each new record
is inserted independantly, the inserts will be slower than if
you have many inserts/updates within a single transaction.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
