My apologies. run the director in -d100 mode: /etc/bacula/bacula
> 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 system is in use?
>
>
>
> mc1:/data/mysql/mysql root# /sbin/bacula-fd -c /etc/bacula/bacula-
> fd.conf -d 100
> mc1:/data/mysql/mysql root# mc1-fd: bsys.c:393 Could not open state
> file. sfd=-1 size=188: ERR=No such file or directory
> mc1-fd: filed.c:256 filed: listening on port 9102
> mc1-fd: bnet_server.c:89 Addresses host[ipv4:0.0.0.0:9102]
> mc1-fd: bnet.c:950 who=client host=0.0.0.16 port=9102
> mc1-fd: find.c:79 init_find_files ff=0x400aa8
> mc1-fd: job.c:193 <dird: Hello Director db3-dir calling
> mc1-fd: job.c:209 Executing Hello command.
> mc1-fd: job.c:209 Executing JobId= command.
> mc1-fd: job.c:193 <dird: fileset
> mc1-fd: job.c:209 Executing fileset command.
> mc1-fd: job.c:701 I
> mc1-fd: job.c:701 O M
> mc1-fd: job.c:701 N
> mc1-fd: job.c:701 F /var/mysql
> mc1-fd: job.c:701 F /Volumes/app01
> mc1-fd: job.c:701 N
> mc1-fd: job.c:701 E
> mc1-fd: job.c:701 F /proc
> mc1-fd: job.c:701 F /tmp
> mc1-fd: job.c:701 F /.journal
> mc1-fd: job.c:701 F /.fsck
> mc1-fd: job.c:701 F /lost+found
> mc1-fd: job.c:701 N
> mc1-fd: job.c:193 <dird: level = incremental mtime_only=0
> mc1-fd: job.c:209 Executing level = command.
> mc1-fd: job.c:212 Quit command loop due to command error or Job done.
> mc1-fd: job.c:280 Calling term_find_files
> mc1-fd: job.c:282 Done with term_find_files
> mc1-fd: job.c:284 Done with free_jcr
>
>
>
> ---------- Original Message -----------
> From: "Alex Kittenplan" <
alex@...>
> To:
bacula-users@...
> Sent: Thu, 9 Feb 2006 09:52:47 -0500
> Subject: [Bacula-users] OSx and backup levels
>
> >
> > Is the lack of levels other than FULL in the bacula OSx port a
> "bug" in the port or a lack in OSx. I do have dull, differential,
> and incremental levels in the schedule. Full backups run
> successfully, but either scheduled or hand-selected differential
> or incremental backups fail.
> > Alex Kittenplan
> >
> > 09-Feb 00:00 db3-dir: Start Backup JobId 22,
> Job=mc1.2006-02-09_00.00.00
> > 09-Feb 00:00 db3-dir: Created new Volume
> "mc1.2006-02-09_00.00.00" in catalog.
> > 09-Feb 00:00 mc1-fd: mc1.2006-02-09_00.00.00 Fatal error: job.c:
> 1093 Unknown backup level: incremental
> > 09-Feb 00:00 db3-dir: mc1.2006-02-09_00.00.00 Fatal error: Socket
> error on Level command: ERR=No data available
> > 09-Feb 00:00 db3-dir: mc1.2006-02-09_00.00.00 Error: Bacula
> 1.38.5 (18Jan06): 09-Feb-2006 00:00:04
> > JobId: 22
> > Job: mc1.2006-02-09_00.00.00
> > Backup Level: Incremental, since=2006-02-05 00:19:52
> > Client: "mc1-fd" powerpc-apple-darwin7.6.0,darwin,7.6.0
> > FileSet: "MC1 Set" 2006-02-02 11:50:35
> > Pool: "Default"
> > Storage: "File"
> > Scheduled time: 09-Feb-2006 00:00:00
> > Start time: 09-Feb-2006 00:00:02
> > End time: 09-Feb-2006 00:00:04
> > Priority: 10
> > FD Files Written: 0
> > SD Files Written: 0
> > FD Bytes Written: 0
> > SD Bytes Written: 0
> > Rate: 0.0 KB/s
> > Software Compression: None
> > Volume name(s):
> > Volume Session Id: 1
> > Volume Session Time: 1139423650
> > Last Volume Bytes: 0
> > Non-fatal FD errors: 0
> > SD Errors: 0
> > FD termination status:
> > SD termination status: Waiting on FD
> > Termination: *** Backup Error ***
> ------- End of Original Message -------
>
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!