Hello,
On Wednesday 18 January 2006 06:34, Jo Rhett wrote:
Oh, no. /d is a new filesystem on the freshly built server, and
'/d/restores' is the directory I'm bextracting to.
Any thoughts on this problem? Any debug I can get for you?
The output you are showing is very strange. I've never
On Tuesday 17 January 2006 05:41, Jo Rhett wrote:
Nope. These are freebsd filesystems from the bacula server itself. There
are windows backups on different tapes, none on these tapes.
I guess I was incorrectly interpreting the /d/restores as a Win32
directory ...
On Mon, Jan 16, 2006 at
Nope. These are freebsd filesystems from the bacula server itself. There
are windows backups on different tapes, none on these tapes.
On Mon, Jan 16, 2006 at 03:51:18PM +0100, Kern Sibbald wrote:
It appears that you are dealing with a Win32 client. One important
consideration here is that
FreeBSD 6.0p2 with Bacula 1.36.3 stock compile options. It's a DDS-3 tape
drive. The other threads talk about not being able to do a restore from
the catalog is the same thing.
Anyway, I'm pretty sure this is a bug now. Why? Because I get exactly one
each time it changes directory, in or out.
On Monday 16 January 2006 08:06, Jo Rhett wrote:
FreeBSD 6.0p2 with Bacula 1.36.3 stock compile options. It's a DDS-3 tape
drive. The other threads talk about not being able to do a restore from
the catalog is the same thing.
Anyway, I'm pretty sure this is a bug now. Why?
It appears
So I'm successfully restoring from bextract, but it shows this...
bextract: drwx-- 2 501 500 512 2005-10-09 20:37:09 *none*
bextract: drwx-- 3 501 500 512 2005-10-05 23:31:50 *none*
bextract: drwx-- 3 501 500 512 2005-10-05 23:31:50
