Re: [Bacula-users] Filesystem change prohibited. why?
> On Tue, 22 Aug 2006 21:29:20 -0700, Robert W Hartzell said:
>
> Martin Simmons wrote:
> >> On Mon, 21 Aug 2006 19:27:18 -0700, Robert W Hartzell said:
>
> I think the simplest and best solution is to suppress these messages as
> I
> wrote above if they are in fact backed up somewhere else in the backup.
> This
> will ensure that the messages are printed only if there is a danger that
> the
> user is missing a partition, but it will also require someone to write
> some
> code (well, any solution will). If it bothers you enough and you would
> like
> it fixed, you might try coming up with this kind of code.
> >>> Another workaround is to list the mounted filesystems in an Exclude
> >>> option.
> >>>
> >>> __Martin
> >> This doesn't work on 1.38.6 the messages are still printed.
> >
> > That's strange, because (from the source) it looks like it should work from
> > 1.35.6 onwards. Maybe your Exclude syntax is wrong?
> >
> > __Martin
>
> I think its correct but I haven't looked at it in about a year.
>
> FileSet {
>Name = "ns1-full-set"
>Include {
> Options {
>signature = MD5
> }
> File = /
> File = /export/home
>}
>Exclude {
> File = /export/bacula/*
> File = /export/storage/*
> File = /net/*
> File = /var/run/*
> File = /etc/svc/volatile/*
> File = /proc/*
> File = /system/contract/*
> File = /system/object/*
> File = /tmp/*
> File = /devices/*
> File = /home/*
> File = /vol/*
>}
> }
>
> All of the disk and tmpfs mount points are correctly re-created on restore.
Hmm, I suspect the problem is that Bacula will be looking at "/export/storage"
etc when it prints the message, which doesn't match "/export/storage/*" etc.
Unfortunately, if you instead put "/export/storage" etc in the Excludes then
restore will not re-create these mount points :-(
__Martin
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
Martin Simmons wrote:
>> On Mon, 21 Aug 2006 19:27:18 -0700, Robert W Hartzell said:
I think the simplest and best solution is to suppress these messages as I
wrote above if they are in fact backed up somewhere else in the backup.
This
will ensure that the messages are printed only if there is a danger that
the
user is missing a partition, but it will also require someone to write
some
code (well, any solution will). If it bothers you enough and you would
like
it fixed, you might try coming up with this kind of code.
>>> Another workaround is to list the mounted filesystems in an Exclude option.
>>>
>>> __Martin
>> This doesn't work on 1.38.6 the messages are still printed.
>
> That's strange, because (from the source) it looks like it should work from
> 1.35.6 onwards. Maybe your Exclude syntax is wrong?
>
> __Martin
I think its correct but I haven't looked at it in about a year.
FileSet {
Name = "ns1-full-set"
Include {
Options {
signature = MD5
}
File = /
File = /export/home
}
Exclude {
File = /export/bacula/*
File = /export/storage/*
File = /net/*
File = /var/run/*
File = /etc/svc/volatile/*
File = /proc/*
File = /system/contract/*
File = /system/object/*
File = /tmp/*
File = /devices/*
File = /home/*
File = /vol/*
}
}
All of the disk and tmpfs mount points are correctly re-created on restore.
--
Robert
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
On Tuesday 22 August 2006 11:39, Martin Simmons wrote: > > On Mon, 21 Aug 2006 19:27:18 -0700, Robert W Hartzell said: > > > > Martin Simmons wrote: > > >> On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said: > > >> On Wednesday 16 August 2006 00:33, Jo Rhett wrote: > > On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote: > > It's worth noting, that the messages above don't necessarily mean > > that the > > filesystem mentioned wouln't be backed up at all. > > > > > The message is generated, when a mounted filesystem is met, but the > > filesystem may be backed up anyway if it is specifically included > > in the > > fileset configuration. The message just means, that the mounted > > filesystem > > isn't backed up as a part of the parent directory's backup. > > Personally, I find this a little bit annoying. > > >>> On Aug 13, 2006, at 12:52 PM, Kern Sibbald wrote: > > Well the messages are there to warn the unwarry, but it would be > > nice if > > someone would submit the code necessary to do a "forward and > > backward" look > > through the filesets to see if the filesystem has been specified > > directly > > somewhere else so that the message could be suppressed. > > >>> Or how about an option to disable these messages in the Message > > >>> section? Trust me when I say that we always backup all we care to. > > >>> I never want to see these messages (and have it fact disabled them > > >>> for us by editing the source, which isn't all that portable). > > >> I am not much in favor of an option to disable these messages -- possibly we > > >> could put them into a separate message class, but this is getting to be a bit > > >> overkill, and previous user comments on this list were not too favorable to > > >> that idea. > > >> > > >> I have modified the messages to include the directory from which the > > >> filesystem change is not permitted, which gives the user a bit more > > >> information about what is going on. > > >> > > >> I think the simplest and best solution is to suppress these messages as I > > >> wrote above if they are in fact backed up somewhere else in the backup. This > > >> will ensure that the messages are printed only if there is a danger that the > > >> user is missing a partition, but it will also require someone to write some > > >> code (well, any solution will). If it bothers you enough and you would like > > >> it fixed, you might try coming up with this kind of code. > > > > > > Another workaround is to list the mounted filesystems in an Exclude option. > > > > > > __Martin > > > > This doesn't work on 1.38.6 the messages are still printed. > > That's strange, because (from the source) it looks like it should work from > 1.35.6 onwards. Maybe your Exclude syntax is wrong? What I would worry about in using this technique is that if you are not careful, you could also exclude the *real* backup of those directories. Personally, I cannot get excited about a few extra lines of output in the job report. If someone *really* does not like them, just turn them off in the source, or pass the Job report output through a simple filter. > > __Martin > > - > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
> On Mon, 21 Aug 2006 19:27:18 -0700, Robert W Hartzell said: > > Martin Simmons wrote: > >> On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said: > >> On Wednesday 16 August 2006 00:33, Jo Rhett wrote: > On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote: > It's worth noting, that the messages above don't necessarily mean > that the > filesystem mentioned wouln't be backed up at all. > > > The message is generated, when a mounted filesystem is met, but the > filesystem may be backed up anyway if it is specifically included > in the > fileset configuration. The message just means, that the mounted > filesystem > isn't backed up as a part of the parent directory's backup. > Personally, I find this a little bit annoying. > >>> On Aug 13, 2006, at 12:52 PM, Kern Sibbald wrote: > Well the messages are there to warn the unwarry, but it would be > nice if > someone would submit the code necessary to do a "forward and > backward" look > through the filesets to see if the filesystem has been specified > directly > somewhere else so that the message could be suppressed. > >>> Or how about an option to disable these messages in the Message > >>> section? Trust me when I say that we always backup all we care to. > >>> I never want to see these messages (and have it fact disabled them > >>> for us by editing the source, which isn't all that portable). > >> I am not much in favor of an option to disable these messages -- possibly > >> we > >> could put them into a separate message class, but this is getting to be a > >> bit > >> overkill, and previous user comments on this list were not too favorable > >> to > >> that idea. > >> > >> I have modified the messages to include the directory from which the > >> filesystem change is not permitted, which gives the user a bit more > >> information about what is going on. > >> > >> I think the simplest and best solution is to suppress these messages as I > >> wrote above if they are in fact backed up somewhere else in the backup. > >> This > >> will ensure that the messages are printed only if there is a danger that > >> the > >> user is missing a partition, but it will also require someone to write > >> some > >> code (well, any solution will). If it bothers you enough and you would > >> like > >> it fixed, you might try coming up with this kind of code. > > > > Another workaround is to list the mounted filesystems in an Exclude option. > > > > __Martin > > This doesn't work on 1.38.6 the messages are still printed. That's strange, because (from the source) it looks like it should work from 1.35.6 onwards. Maybe your Exclude syntax is wrong? __Martin - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
Martin Simmons wrote: >> On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said: >> On Wednesday 16 August 2006 00:33, Jo Rhett wrote: On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote: > It's worth noting, that the messages above don't necessarily mean > that the > filesystem mentioned wouln't be backed up at all. > > The message is generated, when a mounted filesystem is met, but the > filesystem may be backed up anyway if it is specifically included > in the > fileset configuration. The message just means, that the mounted > filesystem > isn't backed up as a part of the parent directory's backup. > Personally, I find this a little bit annoying. >>> On Aug 13, 2006, at 12:52 PM, Kern Sibbald wrote: Well the messages are there to warn the unwarry, but it would be nice if someone would submit the code necessary to do a "forward and backward" look through the filesets to see if the filesystem has been specified directly somewhere else so that the message could be suppressed. >>> Or how about an option to disable these messages in the Message >>> section? Trust me when I say that we always backup all we care to. >>> I never want to see these messages (and have it fact disabled them >>> for us by editing the source, which isn't all that portable). >> I am not much in favor of an option to disable these messages -- possibly we >> could put them into a separate message class, but this is getting to be a >> bit >> overkill, and previous user comments on this list were not too favorable to >> that idea. >> >> I have modified the messages to include the directory from which the >> filesystem change is not permitted, which gives the user a bit more >> information about what is going on. >> >> I think the simplest and best solution is to suppress these messages as I >> wrote above if they are in fact backed up somewhere else in the backup. >> This >> will ensure that the messages are printed only if there is a danger that the >> user is missing a partition, but it will also require someone to write some >> code (well, any solution will). If it bothers you enough and you would like >> it fixed, you might try coming up with this kind of code. > > Another workaround is to list the mounted filesystems in an Exclude option. > > __Martin This doesn't work on 1.38.6 the messages are still printed. -- Robert - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
On Wednesday 16 August 2006 18:29, Martin Simmons wrote: > > On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said: > > > > On Wednesday 16 August 2006 00:33, Jo Rhett wrote: > > > > On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote: > > > >> It's worth noting, that the messages above don't necessarily mean > > > >> that the > > > >> filesystem mentioned wouln't be backed up at all. > > > >> > > > >> The message is generated, when a mounted filesystem is met, but the > > > >> filesystem may be backed up anyway if it is specifically included > > > >> in the > > > >> fileset configuration. The message just means, that the mounted > > > >> filesystem > > > >> isn't backed up as a part of the parent directory's backup. > > > >> Personally, I find this a little bit annoying. > > > > > > On Aug 13, 2006, at 12:52 PM, Kern Sibbald wrote: > > > > Well the messages are there to warn the unwarry, but it would be > > > > nice if > > > > someone would submit the code necessary to do a "forward and > > > > backward" look > > > > through the filesets to see if the filesystem has been specified > > > > directly > > > > somewhere else so that the message could be suppressed. > > > > > > Or how about an option to disable these messages in the Message > > > section? Trust me when I say that we always backup all we care to. > > > I never want to see these messages (and have it fact disabled them > > > for us by editing the source, which isn't all that portable). > > > > I am not much in favor of an option to disable these messages -- possibly we > > could put them into a separate message class, but this is getting to be a bit > > overkill, and previous user comments on this list were not too favorable to > > that idea. > > > > I have modified the messages to include the directory from which the > > filesystem change is not permitted, which gives the user a bit more > > information about what is going on. > > > > I think the simplest and best solution is to suppress these messages as I > > wrote above if they are in fact backed up somewhere else in the backup. This > > will ensure that the messages are printed only if there is a danger that the > > user is missing a partition, but it will also require someone to write some > > code (well, any solution will). If it bothers you enough and you would like > > it fixed, you might try coming up with this kind of code. > > Another workaround is to list the mounted filesystems in an Exclude option. That's a very interesting solution :-) > > __Martin > > - > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
> On Wed, 16 Aug 2006 11:08:28 +0200, Kern Sibbald said: > > On Wednesday 16 August 2006 00:33, Jo Rhett wrote: > > > On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote: > > >> It's worth noting, that the messages above don't necessarily mean > > >> that the > > >> filesystem mentioned wouln't be backed up at all. > > >> > > >> The message is generated, when a mounted filesystem is met, but the > > >> filesystem may be backed up anyway if it is specifically included > > >> in the > > >> fileset configuration. The message just means, that the mounted > > >> filesystem > > >> isn't backed up as a part of the parent directory's backup. > > >> Personally, I find this a little bit annoying. > > > > On Aug 13, 2006, at 12:52 PM, Kern Sibbald wrote: > > > Well the messages are there to warn the unwarry, but it would be > > > nice if > > > someone would submit the code necessary to do a "forward and > > > backward" look > > > through the filesets to see if the filesystem has been specified > > > directly > > > somewhere else so that the message could be suppressed. > > > > Or how about an option to disable these messages in the Message > > section? Trust me when I say that we always backup all we care to. > > I never want to see these messages (and have it fact disabled them > > for us by editing the source, which isn't all that portable). > > I am not much in favor of an option to disable these messages -- possibly we > could put them into a separate message class, but this is getting to be a bit > overkill, and previous user comments on this list were not too favorable to > that idea. > > I have modified the messages to include the directory from which the > filesystem change is not permitted, which gives the user a bit more > information about what is going on. > > I think the simplest and best solution is to suppress these messages as I > wrote above if they are in fact backed up somewhere else in the backup. This > will ensure that the messages are printed only if there is a danger that the > user is missing a partition, but it will also require someone to write some > code (well, any solution will). If it bothers you enough and you would like > it fixed, you might try coming up with this kind of code. Another workaround is to list the mounted filesystems in an Exclude option. __Martin - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
On Wednesday 16 August 2006 00:33, Jo Rhett wrote: > > On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote: > >> It's worth noting, that the messages above don't necessarily mean > >> that the > >> filesystem mentioned wouln't be backed up at all. > >> > >> The message is generated, when a mounted filesystem is met, but the > >> filesystem may be backed up anyway if it is specifically included > >> in the > >> fileset configuration. The message just means, that the mounted > >> filesystem > >> isn't backed up as a part of the parent directory's backup. > >> Personally, I find this a little bit annoying. > > On Aug 13, 2006, at 12:52 PM, Kern Sibbald wrote: > > Well the messages are there to warn the unwarry, but it would be > > nice if > > someone would submit the code necessary to do a "forward and > > backward" look > > through the filesets to see if the filesystem has been specified > > directly > > somewhere else so that the message could be suppressed. > > Or how about an option to disable these messages in the Message > section? Trust me when I say that we always backup all we care to. > I never want to see these messages (and have it fact disabled them > for us by editing the source, which isn't all that portable). I am not much in favor of an option to disable these messages -- possibly we could put them into a separate message class, but this is getting to be a bit overkill, and previous user comments on this list were not too favorable to that idea. I have modified the messages to include the directory from which the filesystem change is not permitted, which gives the user a bit more information about what is going on. I think the simplest and best solution is to suppress these messages as I wrote above if they are in fact backed up somewhere else in the backup. This will ensure that the messages are printed only if there is a danger that the user is missing a partition, but it will also require someone to write some code (well, any solution will). If it bothers you enough and you would like it fixed, you might try coming up with this kind of code. > > -- > Jo Rhett > senior geek > Silicon Valley Colocation > > > - > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
> On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote: >> It's worth noting, that the messages above don't necessarily mean >> that the >> filesystem mentioned wouln't be backed up at all. >> >> The message is generated, when a mounted filesystem is met, but the >> filesystem may be backed up anyway if it is specifically included >> in the >> fileset configuration. The message just means, that the mounted >> filesystem >> isn't backed up as a part of the parent directory's backup. >> Personally, I find this a little bit annoying. On Aug 13, 2006, at 12:52 PM, Kern Sibbald wrote: > Well the messages are there to warn the unwarry, but it would be > nice if > someone would submit the code necessary to do a "forward and > backward" look > through the filesets to see if the filesystem has been specified > directly > somewhere else so that the message could be suppressed. Or how about an option to disable these messages in the Message section? Trust me when I say that we always backup all we care to. I never want to see these messages (and have it fact disabled them for us by editing the source, which isn't all that portable). -- Jo Rhett senior geek Silicon Valley Colocation - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
I have a question relating to this one:
Shannon: Filesystem change prohibited. Will not descend into /dev
Don't you need the (link) files in this directory in order to restore your
system? Is it a problem to back it up?
I guess you also need boot?
On Tuesday 08 August 2006 16:47, Marco Strullato wrote:
> hi all,
> do you know why I get Filesystem change prohibited when I run bacula?
>
>
> 08-Aug 16:40 DirectorServer: Start Backup JobId 95,
> Job=BackupShannon.2006-08-08_16.39.58
> 08-Aug 16:40 StorageServer: Volume "centroservizi" previously written,
> moving to end of data.
> Shannon: Filesystem change prohibited. Will not descend into /sys
> Shannon: Filesystem change prohibited. Will not descend into /boot
> Shannon: Filesystem change prohibited. Will not descend into
> /statistiche Shannon: Filesystem change prohibited. Will not descend
> into /package Shannon: Filesystem change prohibited. Will not descend
> into /dev Shannon: Filesystem change prohibited. Will not descend into
> /mnt/backup
>
>
> definitions are:
> Job {
> Name = "BackupShannon"
> Client = Shannon
> JobDefs = "BackupLinux"
> Level= Full
> Storage = StorageServer
> FileSet = "LinuxFileSet"
> Schedule = "WeeklyCycle"
> Priority = 10
> Type = Backup
> Messages = Standard
> }
> Job {
> Name = "RestoreShannon"
> Type = Restore
> Client = Shannon
> FileSet = "LinuxFileSet"
> Storage = StorageServer
> Pool = BackupPool
> Messages = Standard
> Where= /tmp/bacula-restores
> }
> JobDefs {
> Name = "BackupLinux"
> Type = Backup
> Storage = StorageServer
> Level= Incremental
> Schedule = "WeeklyCycle"
> Messages = Standard
> Pool = BackupPool
> Priority = 10
> }
> FileSet {
> Name = "LinuxFileSet"
> Include {
> Options {
> signature = MD5
> compression = GZIP
> }
> File = /
> }
> Exclude {
> File = /proc
> File = /tmp
> File = /.journal
> File = /.fsck
> }
> }
> Client {
> Name = Shannon
> Address = shannon
> FDPort = 9102
> Catalog = MyCatalog
> Password = "password"
> }
>
> -
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
On Mon, 14 Aug 2006, Kern Sibbald wrote: Unfortunately it also doesn't backup the mountpoint as a directory, which makes restoration a bit messy at times. >>> >>> Bacula has backed up mount points for quite some time now, though I don't >>> remember what version it was first implemented in. >> >> It's not doing it here Kern. Is there a flag which needs to be set? > > No. It just works automatically. > Strange. I will investigate further. AB - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
On Monday 14 August 2006 11:29, Alan Brown wrote: > On Sun, 13 Aug 2006, Kern Sibbald wrote: > > >> Unfortunately it also doesn't backup the mountpoint as a directory, which > >> makes restoration a bit messy at times. > > > > Bacula has backed up mount points for quite some time now, though I don't > > remember what version it was first implemented in. > > It's not doing it here Kern. Is there a flag which needs to be set? No. It just works automatically. > > 1.39.11 > > AB > > > - > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
On Sun, 13 Aug 2006, Kern Sibbald wrote: >> Unfortunately it also doesn't backup the mountpoint as a directory, which >> makes restoration a bit messy at times. > > Bacula has backed up mount points for quite some time now, though I don't > remember what version it was first implemented in. It's not doing it here Kern. Is there a flag which needs to be set? 1.39.11 AB - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
On Tuesday 08 August 2006 22:29, Timo Neuvonen wrote: > > Marco Strullato wrote: > > > hi all, > > > do you know why I get Filesystem change prohibited when I run bacula? > > > > > > > > > 08-Aug 16:40 DirectorServer: Start Backup JobId 95, > > > Job=BackupShannon.2006-08-08_16.39.58 > > > 08-Aug 16:40 StorageServer: Volume "centroservizi" previously written, > > > moving to end of data. > > > Shannon: Filesystem change prohibited. Will not descend into /sys > > > Shannon: Filesystem change prohibited. Will not descend into /boot > > > Shannon: Filesystem change prohibited. Will not descend into > /statistiche > > > Shannon: Filesystem change prohibited. Will not descend into > /package > > > Shannon: Filesystem change prohibited. Will not descend into /dev > > > Shannon: Filesystem change prohibited. Will not descend into > /mnt/backup > > > > Those are mounted filesystems. Bacula will not descend into mounted > > filesystems unless you specifically tell it to. (This is safer as there > > might be data mounted over the network, or virtual filesystems that you > > don't want the backup to grab.) > > > > You either have to manually specify all mount points to back up to make > > it descend into them, or use the onefs option in the FileSet (again, be > > > > It's worth noting, that the messages above don't necessarily mean that the > filesystem mentioned wouln't be backed up at all. > > The message is generated, when a mounted filesystem is met, but the > filesystem may be backed up anyway if it is specifically included in the > fileset configuration. The message just means, that the mounted filesystem > isn't backed up as a part of the parent directory's backup. > Personally, I find this a little bit annoying. Well the messages are there to warn the unwarry, but it would be nice if someone would submit the code necessary to do a "forward and backward" look through the filesets to see if the filesystem has been specified directly somewhere else so that the message could be suppressed. > > > Regards, > Timo > > > > - > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
On Tuesday 08 August 2006 18:13, Alan Brown wrote: > On Tue, 8 Aug 2006, Michel Meyers wrote: > > > Those are mounted filesystems. Bacula will not descend into mounted > > filesystems unless you specifically tell it to. > > Unfortunately it also doesn't backup the mountpoint as a directory, which > makes restoration a bit messy at times. Bacula has backed up mount points for quite some time now, though I don't remember what version it was first implemented in. > > AB > > > - > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
> Marco Strullato wrote: > > hi all, > > do you know why I get Filesystem change prohibited when I run bacula? > > > > > > 08-Aug 16:40 DirectorServer: Start Backup JobId 95, > > Job=BackupShannon.2006-08-08_16.39.58 > > 08-Aug 16:40 StorageServer: Volume "centroservizi" previously written, > > moving to end of data. > > Shannon: Filesystem change prohibited. Will not descend into /sys > > Shannon: Filesystem change prohibited. Will not descend into /boot > > Shannon: Filesystem change prohibited. Will not descend into /statistiche > > Shannon: Filesystem change prohibited. Will not descend into /package > > Shannon: Filesystem change prohibited. Will not descend into /dev > > Shannon: Filesystem change prohibited. Will not descend into /mnt/backup > > Those are mounted filesystems. Bacula will not descend into mounted > filesystems unless you specifically tell it to. (This is safer as there > might be data mounted over the network, or virtual filesystems that you > don't want the backup to grab.) > > You either have to manually specify all mount points to back up to make > it descend into them, or use the onefs option in the FileSet (again, be > It's worth noting, that the messages above don't necessarily mean that the filesystem mentioned wouln't be backed up at all. The message is generated, when a mounted filesystem is met, but the filesystem may be backed up anyway if it is specifically included in the fileset configuration. The message just means, that the mounted filesystem isn't backed up as a part of the parent directory's backup. Personally, I find this a little bit annoying. Regards, Timo - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
> On Tue, 8 Aug 2006 17:13:22 +0100 (BST), Alan Brown said: > > On Tue, 8 Aug 2006, Michel Meyers wrote: > > > Those are mounted filesystems. Bacula will not descend into mounted > > filesystems unless you specifically tell it to. > > Unfortunately it also doesn't backup the mountpoint as a directory, which > makes restoration a bit messy at times. Is that still true? I thought it had been fixed long ago. __Martin - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
On Tue, 8 Aug 2006, Michel Meyers wrote: > Those are mounted filesystems. Bacula will not descend into mounted > filesystems unless you specifically tell it to. Unfortunately it also doesn't backup the mountpoint as a directory, which makes restoration a bit messy at times. AB - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
>From the bacula manual:
onefs=yes|no
If set to yes (the default), Bacula will remain on a single file
system. That is it will not backup file systems that are mounted on a
subdirectory. If you are using a *nix system, you may not even be
aware that there are several different filesystems as they are often
automatically mounted by the OS (e.g. /dev, /net, /sys, /proc, ...).
With Bacula 1.38.0 or later, it will inform you when it decides not to
traverse into another filesystem. This can be very useful if you
forgot to backup a particular partition. An example of the
informational message in the job report is:
so add to your FileSet's onefs=no
On 08/08/06, Marco Strullato <[EMAIL PROTECTED]> wrote:
> hi all,
> do you know why I get Filesystem change prohibited when I run bacula?
>
>
> 08-Aug 16:40 DirectorServer: Start Backup JobId 95,
> Job=BackupShannon.2006-08-08_16.39.58
> 08-Aug 16:40 StorageServer: Volume "centroservizi" previously written,
> moving to end of data.
> Shannon: Filesystem change prohibited. Will not descend into /sys
> Shannon: Filesystem change prohibited. Will not descend into /boot
> Shannon: Filesystem change prohibited. Will not descend into /statistiche
> Shannon: Filesystem change prohibited. Will not descend into /package
> Shannon: Filesystem change prohibited. Will not descend into /dev
> Shannon: Filesystem change prohibited. Will not descend into /mnt/backup
>
>
> definitions are:
> Job {
> Name = "BackupShannon"
> Client = Shannon
> JobDefs = "BackupLinux"
> Level= Full
> Storage = StorageServer
> FileSet = "LinuxFileSet"
> Schedule = "WeeklyCycle"
> Priority = 10
> Type = Backup
> Messages = Standard
> }
> Job {
> Name = "RestoreShannon"
> Type = Restore
> Client = Shannon
> FileSet = "LinuxFileSet"
> Storage = StorageServer
> Pool = BackupPool
> Messages = Standard
> Where= /tmp/bacula-restores
> }
> JobDefs {
> Name = "BackupLinux"
> Type = Backup
> Storage = StorageServer
> Level= Incremental
> Schedule = "WeeklyCycle"
> Messages = Standard
> Pool = BackupPool
> Priority = 10
> }
> FileSet {
> Name = "LinuxFileSet"
> Include {
> Options {
> signature = MD5
> compression = GZIP
> }
> File = /
> }
> Exclude {
> File = /proc
> File = /tmp
> File = /.journal
> File = /.fsck
> }
> }
> Client {
> Name = Shannon
> Address = shannon
> FDPort = 9102
> Catalog = MyCatalog
> Password = "password"
> }
>
> -
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
R.I.Pienaar http://www.devco.net
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
In response to "Marco Strullato" <[EMAIL PROTECTED]>: > hi all, > do you know why I get Filesystem change prohibited when I run bacula? > > > 08-Aug 16:40 DirectorServer: Start Backup JobId 95, > Job=BackupShannon.2006-08-08_16.39.58 > 08-Aug 16:40 StorageServer: Volume "centroservizi" previously written, > moving to end of data. > Shannon: Filesystem change prohibited. Will not descend into /sys [snip] Look up "onefs" in the online manual. -- Bill Moran Collaborative Fusion Inc. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Filesystem change prohibited. why?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marco Strullato wrote: > hi all, > do you know why I get Filesystem change prohibited when I run bacula? > > > 08-Aug 16:40 DirectorServer: Start Backup JobId 95, > Job=BackupShannon.2006-08-08_16.39.58 > 08-Aug 16:40 StorageServer: Volume "centroservizi" previously written, > moving to end of data. > Shannon: Filesystem change prohibited. Will not descend into /sys > Shannon: Filesystem change prohibited. Will not descend into /boot > Shannon: Filesystem change prohibited. Will not descend into /statistiche > Shannon: Filesystem change prohibited. Will not descend into /package > Shannon: Filesystem change prohibited. Will not descend into /dev > Shannon: Filesystem change prohibited. Will not descend into /mnt/backup Those are mounted filesystems. Bacula will not descend into mounted filesystems unless you specifically tell it to. (This is safer as there might be data mounted over the network, or virtual filesystems that you don't want the backup to grab.) You either have to manually specify all mount points to back up to make it descend into them, or use the onefs option in the FileSet (again, be careful not to accidentally include something you don't want backed up). Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) - GPGrelay v0.959 iD8DBQFE2KWx2Vs+MkscAyURAixLAKDGfE5Erf1UPFApPwDdAkJ4hs/AIQCfZ2KC QFkt3B3HuhLIzAWiELj+HpQ= =XVc0 -END PGP SIGNATURE- - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Filesystem change prohibited. why?
hi all,
do you know why I get Filesystem change prohibited when I run bacula?
08-Aug 16:40 DirectorServer: Start Backup JobId 95,
Job=BackupShannon.2006-08-08_16.39.58
08-Aug 16:40 StorageServer: Volume "centroservizi" previously written,
moving to end of data.
Shannon: Filesystem change prohibited. Will not descend into /sys
Shannon: Filesystem change prohibited. Will not descend into /boot
Shannon: Filesystem change prohibited. Will not descend into /statistiche
Shannon: Filesystem change prohibited. Will not descend into /package
Shannon: Filesystem change prohibited. Will not descend into /dev
Shannon: Filesystem change prohibited. Will not descend into /mnt/backup
definitions are:
Job {
Name = "BackupShannon"
Client = Shannon
JobDefs = "BackupLinux"
Level= Full
Storage = StorageServer
FileSet = "LinuxFileSet"
Schedule = "WeeklyCycle"
Priority = 10
Type = Backup
Messages = Standard
}
Job {
Name = "RestoreShannon"
Type = Restore
Client = Shannon
FileSet = "LinuxFileSet"
Storage = StorageServer
Pool = BackupPool
Messages = Standard
Where= /tmp/bacula-restores
}
JobDefs {
Name = "BackupLinux"
Type = Backup
Storage = StorageServer
Level= Incremental
Schedule = "WeeklyCycle"
Messages = Standard
Pool = BackupPool
Priority = 10
}
FileSet {
Name = "LinuxFileSet"
Include {
Options {
signature = MD5
compression = GZIP
}
File = /
}
Exclude {
File = /proc
File = /tmp
File = /.journal
File = /.fsck
}
}
Client {
Name = Shannon
Address = shannon
FDPort = 9102
Catalog = MyCatalog
Password = "password"
}
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
