Did you ever get a response to your question? I am having the same problem,
although it only is occurring on my Unix machines including Mac OS X. The
windows machines have "incremental" recognized.
-sarah
--
View this message in context:
http://www.nabble.com/OSx-and-backup-levels-t1092861.htm
Sarah,
Never saw a reply.
I've not run into those problems running 1.38.x compiled on 10.4.x (3
machines) and one XP FD backing up to OS X box.
What setup are you running?
Erich
On May 15, 2006, at 9:00 AM, sqe wrote:
Did you ever get your problem fixed? I am having the same problem,
Did you ever get your problem fixed? I am having the same problem, and did
not see a resolution posted anywhere?
-sarah
--
View this message in context:
http://www.nabble.com/OSx-and-backup-levels-t1092861.html#a4392359
Sent from the Bacula - Users forum at Nabble.com.
--
Hey Alex,
My apologies. run the director in -d100 mode: /etc/bacula/bacula
start -d100
Let's look at that file too.
Erich
On Feb 9, 2006, at 9:39 AM, Alex Kittenplan wrote:
Ok, attached is the output of running the fd with -d100. It
connects without a problem, sends the inclusion and ex
Ok, attached is the output of running the fd with -d100. It connects without a problem, sends the inclusion and exclusion lists, and the director sends the file daemon process the incremental level command, at which point the fd fails.
Is the OSx port particular about which type of file syste
Alex,
Stop bacula and restart with debug turned on:
bacula stop
bacula start -d100
That will give a much clearer dump of exactly what is going on.
That'll help narrow it down.
Erich
On Feb 9, 2006, at 8:52 AM, Alex Kittenplan wrote:
Is the lack of levels other than FULL in the bacula O
