On 11/01/10 07:19, eliassal wrote:
> Hi, I am running a job to backup all my system in order to preapre a full 
> backup for disaster recovery.
> In the job log, I see the following
> 
> Using Device "FileStorage"
> 2010-11-01 10:49:46 bacula-sd Labeled new Volume "DRLocal0016" on device 
> "FileStorage" (/media/Backup).
>                                   Wrote label to prelabeled Volume 
> "DRLocal0016" on device "FileStorage" (/media/Backup)
> 2010-11-01 10:49:46 bacula-fd     /mnt/publiciomega1 is a different 
> filesystem. Will not descend from / into /mnt/publiciomega1
> 2010-11-01 10:49:52 bacula-fd      /proc is a different filesystem. Will not 
> descend from / into /proc
> 2010-11-01 10:54:32 bacula-fd      Could not stat "/home/salam/.gvfs": 
> ERR=Permission denied
> 2010-11-01 10:57:04 bacula-fd      /var/lib/nfs/rpc_pipefs is a different 
> filesystem. Will not descend from / into /var/lib/nfs/rpc_pipefs
> 2010-11-01 11:06:03 bacula-fd      /dev is a different filesystem. Will not 
> descend from / into /dev
>                                                         /media/Backup is a 
> different filesystem. Will not descend from / into /media/Backup
> 
> I have both partitions in ext4 so I really can not understand why I am 
> getting this message and what is its impact on my backup.

Because Bacula will not descent into mounted filesystems that it has not
been specifically told to.  This is a good thing; you do NOT want it to
descend into /proc or /sys, for example, and on modern Linux systems
where /dev is managed dynamically, you almost certainly don't want it to
descend into /dev either.  Neither do you want it to descend into, for
example, NFS or other network-mounted filesystems that are already being
backed up once from their server.

The idea is that you explicitly list each filesystem you want Bacula to
back up, then exclude the directories within those filesystems that you
do not want backed up.

You CAN change this behavior using the onefs directive; by default, this
is set to onefs=yes, which tells Bacula to remain within a single
mounted filesystem.  You CAN explicitly set onefs=no, in which case
Bacula will follow all mount points.  BE VERY CAREFUL about doing this.
 There may be unexpected consequences. On most operating systems, if you
do not have a very good specific reason to do this, it's best not to.
It's certainly not something you should be doing when you're still new
to Bacula.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users