Hello folks,

we are using Bacula since June and are really happy with it. Thanks
to all the Developers for this great peace of software.

Now our issues ... first, since 1.38.0, we got the following Messages
from every client (which of course varied from system to system):
paul-fd:      Filesystem change prohibited. Will not descend into /var
paul-fd:      Filesystem change prohibited. Will not descend into /opt
paul-fd:      Filesystem change prohibited. Will not descend into /net
paul-fd:      Filesystem change prohibited. Will not descend into /home
paul-fd:      Filesystem change prohibited. Will not descend into /xfn
paul-fd:      Filesystem change prohibited. Will not descend into /vol
paul-fd:      Filesystem change prohibited. Will not descend into /var/run

First of all, this message is a bit misleading, because some filesystems
are of course backed up (I checked that) - as the configuration defines
it:
# Standard Solaris fileset
FileSet {
   Name = "Full Solaris Set"
   Include {
       Options { signature = MD5 }
       File = /
       File = /opt
       File = /var
   }
   Exclude {
       File = /cdrom
       File = /dev
       File = /devices
       File = /export
       File = /floppy
       File = /mnt
       File = /proc
       File = /tmp
       File = /var/tmp
   }
}

I also don't get why f. e. /net and /home are considered as own
filesystems - see the df -k output from the same machine:
paul:/# df -k
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/md/dsk/d0       2053055  756420 1235044    38%    /
/proc                      0       0       0     0%    /proc
mnttab                     0       0       0     0%    /etc/mnttab
fd                         0       0       0     0%    /dev/fd
/dev/md/dsk/d30      1500471  101531 1338922     8%    /var
swap                 1903288      24 1903264     1%    /var/run
swap                 1903264       0 1903264     0%    /tmp
/dev/md/dsk/d50      3010326 2153786  796334    74%    /opt


The second issue is a little bit tricky. ;) I tried to truss and
strace down the problem but wasn't successful so far:
08-Nov 01:09 filer-fd:      Could not stat : ERR=No such file or directory

This messages isn't thrown by all clients and I think it's totally
harmless - it's only annoying and leads to:
Termination:            Backup OK -- with warnings

This is the fd-configuration for such a client:
#
# Bacula File Daemon Configuration file
#

# List Directors who are permitted to contact this File daemon
Director {
   Name = mw-hh-dir
   Password = "foobar"
}

# "Global" File daemon configuration specifications
FileDaemon {
   Name = filer-fd
   FDPort = 9102
   Working Directory = /opt/local/bacula/var/working
   Pid Directory = /opt/local/bacula/var/run
   Maximum Concurrent Jobs = 5
}

# Send all messages except skipped files back to Director
Messages {
   Name = Standard
   Director = mw-hh-dir = all, !skipped
}

The directories /opt/local/bacula/var/working and
/opt/local/bacula/var/run are of course existing and writeable
for the daemon.

Thanks in advance,
Volker

--
Volker Dierks
Metaways Infosystems GmbH
Pickhuben 4
20457 Hamburg
Germany

E-Mail: mailto:[EMAIL PROTECTED]
Web:    http://www.metaways.de
Tel:    +49 (0)40 317031-13
Fax:    +49 (0)40 317031-73
Mobile: +49 (0)151 17414364


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to