[bareos-users] Re: FIleset
On Friday, November 17, 2017 at 6:18:40 AM UTC-5, Nikitin Artem wrote:
> Hello.
>
> I’m executing a sequence of commands in the Fileset resource (File = “ls –l
> | awk ‘{print $NF}’ etc. . .). I need this, for getting the list
> of files to backup .
>
> The problem is, these commands is executing on Director, not Client.
>
>
> How to execute them remotely (on FIledaemon’s host). Please help.
To run commands client-side, you can use "Client Run Before Job" or "Client Run
After Job". You can also look at "Run Script", although I've never used it. You
can find them on (or near) pages 70 and 80 of the manual, section 9.2.
You could then use this to run a script that creates a list of files and writes
to a file which you might call files.txt. You can then put something like this
in your FileSet:
File = "\\https://groups.google.com/d/optout.
[bareos-users] Re: FIleset
четверг, 30 ноября 2017 г., 11:27:43 UTC+7 пользователь oldt...@gmail.com
написал:
> On Friday, November 17, 2017 at 6:18:40 AM UTC-5, Nikitin Artem wrote:
> > Hello.
> >
> > I’m executing a sequence of commands in the Fileset resource (File = “ls –l
> > | awk ‘{print $NF}’ etc. . .). I need this, for getting the list
> > of files to backup .
> >
> > The problem is, these commands is executing on Director, not Client.
> >
> >
> > How to execute them remotely (on FIledaemon’s host). Please help.
>
> To run commands client-side, you can use "Client Run Before Job" or "Client
> Run After Job". You can also look at "Run Script", although I've never used
> it. You can find them on (or near) pages 70 and 80 of the manual, section 9.2.
>
> You could then use this to run a script that creates a list of files and
> writes to a file which you might call files.txt. You can then put something
> like this in your FileSet:
>
> File = "\\
> See page 94 of the manual about the less-than sign: "<".
>
> Hope this helps,
> oldtechaa
Hello.
Yes, it's good idea. But in my backup system it's not working. "Before job"
script and "after job" script run on client normally and I get "Backup OK"
after job execution, but backup size is 0 bytes.
I start FD with "-d 100" and analyze debug log after backup job show that read
FileSet executing before "client run before job".
Please help!
P.S. Sorry for my English.
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (50): cram-md5.c:68-0 send:
auth cram-md5 <1302898451.1554534993@xen-03> ssl=0
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): cram-md5.c:123-0
cram-get received: auth cram-md5 <1019832112.1554535114@bareos-dir> ssl=0
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (99): cram-md5.c:143-0 sending
resp to challenge: z+/29V/np6lkLA/XpU/UQB
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): dir_cmd.c:497-0 ssl=0
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (99): cram-md5.c:143-817
sending resp to challenge: Z7/rR9pnU5Bl1W/T5/NoZA
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (50): cram-md5.c:75-817 send:
auth cram-md5 <648759753.1554534993@xen-03> ssl=0
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (50): cram-md5.c:94-817
Authenticate OK 33+x6gtIeA8Y8A+3r+/95B
Apr 06 14:16:33 xen-03 bareos-fd[38045]: [179B blob data]
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): dir_cmd.c:508-817
Executing Run command.
Apr 06 14:16:33 xen-03 bareos-fd[38045]: [189B blob data]
Apr 06 14:16:33 xen-03 bareos-fd[38045]: '
Apr 06 14:16:33 xen-03 bareos-fd[38045]: [154B blob data]
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): dir_cmd.c:508-817
Executing Run command.
Apr 06 14:16:33 xen-03 bareos-fd[38045]: [164B blob data]
Apr 06 14:16:33 xen-03 bareos-fd[38045]: '
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): dir_cmd.c:497-817
/tmp/xen-backup.filelist'...
Apr 06 14:16:33 xen-03 bareos-fd[38046]: xen-03 JobId 817: shell command: run
ClientBeforeJob "sh /usr/local/sbin/lvm-make-snapshot.sh vg00/srv-node01 >
/tmp/xen-backup.filelist"
Apr 06 14:16:33 xen-03 bareos-fd[38046]: xen-03 JobId 817: ClientBeforeJob:
Using default stripesize 64.00 KiB.
Apr 06 14:16:33 xen-03 bareos-fd[38046]: xen-03 JobId 817: ClientBeforeJob:
Logical volume "srv-node01-s" created.
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): runscript.c:301-817
runscript OK
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): dir_cmd.c:1088-817 Back
from run_scripts ClientBeforeJob now: OK
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): dir_cmd.c:497-817
Accurate= BaseJob= flags=<-134211120>
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): heartbeat.c:153-817 Send
kill to heartbeat id
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): backup.c:185-817 end
blast_data ok=1
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): dir_cmd.c:511-817 Quit
command loop. Canceled=0
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): runscript.c:264-817
runscript: running a RUNSCRIPT object type=124
Apr 06 14:16:33 xen-03 bareos-fd[38045]: xen-03 (100): runscript.c:271-817
runscript: running 'sh /usr/local/sbin/lvm-remove-snapshot.sh
vg00/srv-node01'...
Apr 06 14:16:33 xen-03 bareos-fd[38046]: xen-03 JobId 817: shell command: run
ClientAfterJob "sh /usr/local/sbin/lvm-remove-snapshot.sh vg00/srv-node01"
Apr 06 14:16:34 xen-03 bareos-fd[38046]: xen-03 JobId 817: ClientAfterJob:
Logical volume "srv-node01-s" successfully removed
Apr 06 14:16:34 xen-03 bareos-fd[38045]: xen-03 (100): runscript.c:301-817
runscript OK
Apr 06 14:16:34 xen-03 bareos-fd[38045]: xen-03 (100): jcr.c:184-81
[bareos-users] Re: Fileset-Problem
Hello Philipp,
no problem with the winbareos-version 13.2.2 32bit r2.1.
The Backup-Job is correct.
And now?
regards, sven
Am Montag, 5. Mai 2014 17:12:00 UTC+2 schrieb Sven Scheidler:
> Hello,
>
> i have a error with the following fileset:
>
> FileSet {
> Name..
> EnableVSS = no
> IgnoreFilesetChanges = yes
> Options {
> compression..
> portable = yes
> recurse = yes
> ignore case = yes
> accurate = m
> }
> Include {
> # Filelist on Win-Client
> File = "\\ }
> Exclude {
> # Filelist on Win-Client
> File = "\\ }
> }
>
> include_1.list:
> C:/
>
> exclude_1.list
> C:/Folder
>
> Job-Message:
> Could not stat "C:/": ERR=Der Prozess kann nicht auf die Datei zugreifen, da
> sie von einem anderen
> Prozess verwendet wird
>
> No error, when i modify the Path in include_1.list from:
> C:/
> to
> C:/Folder2
>
> The Problem is only with a Drive.
> The include_1.list works with Bacula!
>
> Bareos-Dir:
> -Debian7
> - Bareos 14.1.0
>
> Bareos-FD:
> - Windows (XP or Svr2003 or Win7)
> - bareos-fd 14.1.0
>
> No Information in attached Trace-File.
>
> regards,
> Sven
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Re: FIleset
On 06.04.2019 09:25, muravey.novosibi...@gmail.com wrote:
четверг, 30 ноября 2017 г., 11:27:43 UTC+7 пользователь oldt...@gmail.com
написал:
On Friday, November 17, 2017 at 6:18:40 AM UTC-5, Nikitin Artem wrote:
Hello.
I’m executing a sequence of commands in the Fileset resource (File = “ls –l
| awk ‘{print $NF}’ etc. . .). I need this, for getting the list of
files to backup .
The problem is, these commands is executing on Director, not Client.
How to execute them remotely (on FIledaemon’s host). Please help.
To run commands client-side, you can use "Client Run Before Job" or "Client Run After
Job". You can also look at "Run Script", although I've never used it. You can find them on (or
near) pages 70 and 80 of the manual, section 9.2.
You could then use this to run a script that creates a list of files and writes
to a file which you might call files.txt. You can then put something like this
in your FileSet:
File = "\\
Hello.
Yes, it's good idea. But in my backup system it's not working. "Before job" script and "after
job" script run on client normally and I get "Backup OK" after job execution, but backup size
is 0 bytes.
I start FD with "-d 100" and analyze debug log after backup job show that read FileSet
executing before "client run before job".
Please help!
P.S. Sorry for my English.
It's way too complicated. The most important thing for the original
poster is this excerpt from the manual:
"If the vertical bar (|) in front of my_partitions is preceded by a
backslash as in ∖|, the program will be executed on the Client’s machine
instead of on the Director’s machine."
Of course you need to escape the backslash, so you'll probably end up
with something like that (example from one of my configs):
FileSet {
Name = "Local-offline-archives"
Include {
File = "\\| find /srv/archives -type f -not -path '*backup*'
-ctime +365" }
}
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Re: Fileset-Problem
Hello Sven, Am 06.05.2014 11:34, schrieb Sven Scheidler: > Hello Philipp, > no problem with the winbareos-version 13.2.2 32bit r2.1. > The Backup-Job is correct. > > And now? Now you can use Version 13.2.2 :-) And we know that something broke in the changes made since version 13, which is good. Can you please file a bug in our bugtracker on bugs.bareos.org? Then we will track that problem and it will not be forgotten. Also, you will be notified when we fix the problem. Thank you very much! -- Mit freundlichen Grüßen Philipp Storz philipp.st...@bareos.com Bareos GmbH & Co. KG Phone: Phone: +49221630693-92 http://www.bareos.com Fax: +49221630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz, M. v. Wieringen -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[bareos-users] Re: Fileset Accurate-Options
Hello, can anyone help me or do not you use the options? In the manual missing this infos! Regards, Sven -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[bareos-users] Re: Fileset Accurate-Options
Hello, can anyone help me or do not you use this options? in the manual missing this infos! Regards, Sven -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[bareos-users] Re: FileSet Feature Suggestion
On 01.06.2017 at 16:48 wrote Douglas K. Rand: > The number of things I like about Bareos are numerous. But perhaps the > sharpest pinch point that we have with Bareos is the safety feature that > any change to a FileSet causes a full backup to be triggered. > > From the docs: >> Any change to the list of the included files will cause Bareos to >> automatically create a new FileSet (defined by the name and an MD5 >> checksum of the Include/Exclude contents). Each time a new FileSet is >> created, Bareos will ensure that the next backup is always a Full >> save. > > And while I understand the safety aspect of that behavior, for our > moderately large 100+ client configuration we are essentially prevented > from making any changes to the FileSet or facing our next backup window > being disastrously large. > > My suggestion is to allow for that safety feature to be turned off. Two > approaches came to mind: > > The simple approach of having a configuration knob to simply turn off > the behavior of doing a full backup on a FileSet change. This is perhaps > the easiest and also most dangerous. Already there, see http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirFileSetIgnore%20File%20Set%20Changes > The more complicated but less dangerous approach that I came up with > would be to allow users to explicitly version FileSets. You could make > versions integers and anytime the version number increases a full-backup > is kicked off. This would allow admins to decide when a fileset change > warrants such an update. > > For us, we end up with excludes spread all over the place. Some are in > our FileSet from the initial setup of Bareos, before I fully understood > the quote from the docs above. Some in an exclude file on the director, > some in exclude files on clients. We did the last two when we realized > that FileSet changes would be so disruptive. > > Anyway, an idea to drop in the hopper. We also considered to add an option for "Upgrade to Accurate" instead of "Upgrade to Full". regards, Jörg -- Jörg Steffens joerg.steff...@bareos.com Bareos GmbH & Co. KGPhone: +49 221 630693-91 http://www.bareos.com Fax: +49 221 630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Re: FileSet Feature Suggestion
On 06/01/17 10:06, Jörg Steffens wrote: On 01.06.2017 at 16:48 wrote Douglas K. Rand: The number of things I like about Bareos are numerous. But perhaps the sharpest pinch point that we have with Bareos is the safety feature that any change to a FileSet causes a full backup to be triggered. From the docs: Any change to the list of the included files will cause Bareos to automatically create a new FileSet (defined by the name and an MD5 checksum of the Include/Exclude contents). Each time a new FileSet is created, Bareos will ensure that the next backup is always a Full save. And while I understand the safety aspect of that behavior, for our moderately large 100+ client configuration we are essentially prevented from making any changes to the FileSet or facing our next backup window being disastrously large. My suggestion is to allow for that safety feature to be turned off. Two approaches came to mind: The simple approach of having a configuration knob to simply turn off the behavior of doing a full backup on a FileSet change. This is perhaps the easiest and also most dangerous. Already there, see http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirFileSetIgnore%20File%20Set%20Changes Ohh, that is embarrassing. I have read those docs from one end to the other, but clearly my selective memory prevented me from recalling that very important detail. Thanks for the tip! And sorry for the noise. Blush. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Re: FileSet Feature Suggestion
2017-06-01 17:10 GMT+02:00 Douglas K. Rand : > > [...] >> >> Already there, see >> http://doc.bareos.org/master/html/bareos-manual-main-referen >> ce.html#directiveDirFileSetIgnore%20File%20Set%20Changes >> > > Ohh, that is embarrassing. I have read those docs from one end to the > other, but clearly my selective memory prevented me from recalling that > very important detail. > You're not alone :-) The very same facts (need for such a feature + "selective memory" problem) applied also to me :-) Thanks Jörg, for pointing to the doc. Cheers, DV P.S.: And, BTW, thanks to _EVERYONE_ on this list: I personally find it as a list with an optimal SNR :-) -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[bareos-users] Re: FileSet changes with out a new full backup
Am 26.10.2016 um 09:41 schrieb Philipp Storz: > Please read the fine documentation: > > http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirFileSetIgnore > File > Set Changes Besides this, we had also some internal discussion about this. While upgrade to Full is a useful feature, it is normally not required if you use Accurate. Also besides update to Full, an upgrade to Accurate might also be an option. These are thing, we Bareos can be improved. However, time is rare. If you are interested, you might submit it to https://www.bareos.com/en/co-funding.html -- Jörg Steffens joerg.steff...@bareos.com Bareos GmbH & Co. KGPhone: +49 221 630693-91 http://www.bareos.com Fax: +49 221 630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Re: FileSet changes with out a new full backup
On 10/26/16 6:03 AM, Jörg Steffens wrote: Am 26.10.2016 um 09:41 schrieb Philipp Storz: Please read the fine documentation: http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirFileSetIgnore File Set Changes Besides this, we had also some internal discussion about this. While upgrade to Full is a useful feature, it is normally not required if you use Accurate. Also besides update to Full, an upgrade to Accurate might also be an option. These are thing, we Bareos can be improved. However, time is rare. If you are interested, you might submit it to https://www.bareos.com/en/co-funding.html Jorg, you are right about Accurate mode, which is enabled on our File Set. It seems that the rule "any change to a fileset" is a bit heavy handed with Accurate. For now I've reverted my File Set to avoid the problem and pushed the exclude off the the clients via Puppet. I was lucky enough to have file = "\\leveraged that instead of changing the File Set.) I'll noodle about the co-funding. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Re: FileSet changes with out a new full backup
On mercredi, 26 octobre 2016 09.41:25 h CEST Douglas K, Rand wrote: > On 10/26/16 6:03 AM, Jörg Steffens wrote: > > Am 26.10.2016 um 09:41 schrieb Philipp Storz: > >> Please read the fine documentation: > >> > >> http://doc.bareos.org/master/html/bareos-manual-main-reference.html#direc > >> tiveDirFileSetIgnore File Set Changes > > > > Besides this, we had also some internal discussion about this. > > While upgrade to Full is a useful feature, it is normally not required > > if you use Accurate. Also besides update to Full, an upgrade to Accurate > > might also be an option. > > These are thing, we Bareos can be improved. However, time is rare. If > > you are interested, you might submit it to > > https://www.bareos.com/en/co-funding.html > > Jorg, you are right about Accurate mode, which is enabled on our File > Set. It seems that the rule "any change to a fileset" is a bit heavy > handed with Accurate. > > For now I've reverted my File Set to avoid the problem and pushed the > exclude off the the clients via Puppet. I was lucky enough to have file > = "\\ leveraged that instead of changing the File Set.) > > I'll noodle about the co-funding. While the full needs after changes can be a burden, I'm not 100% sure to subscribe to not "forcing it" in a way or another. Every admin will have one day or another a change to setup in its filesets. Accurate will pick that ok, but then the time to restore will come, and I beat on the fact that there will be a lot of complains about why "my files are not there" expectation. The reason will be because at that time, the fileset didn't know about them, and nobody will remember at that time, a change occurs in the fileset, and no full were made again. I'm sorry if I'm not clear enough yet, I would like to see all the real scenario before jumping saying "bravo". Perhaps we need a fileset version in the database ? Or some options are minor, and other major ? Isn't there a way to trick bareos with the content of fileset table ? like saving the date of the previous hash for a given ressource, make the new one and bring back the old data ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot openSUSE Tumbleweed Linux 4.8.3-1-default x86_64 GNU/Linux, nvidia: 367.57 Qt: 5.7.0, KDE Frameworks: 5.26.0, Plasma: 5.8.2, kmail2 5.3.0 (QtWebEngine) -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Re: FileSet changes with out a new full backup
On 10/26/16 12:08, Bruno Friedmann wrote: > On mercredi, 26 octobre 2016 09.41:25 h CEST Douglas K, Rand wrote: >> On 10/26/16 6:03 AM, Jörg Steffens wrote: >>> Besides this, we had also some internal discussion about this. >>> While upgrade to Full is a useful feature, it is normally not required >>> if you use Accurate. Also besides update to Full, an upgrade to Accurate >>> might also be an option. >> Jorg, you are right about Accurate mode, which is enabled on our File >> Set. It seems that the rule "any change to a fileset" is a bit heavy >> handed with Accurate. >> >> For now I've reverted my File Set to avoid the problem and pushed the >> exclude off the the clients via Puppet. I was lucky enough to have file >> = "\\> leveraged that instead of changing the File Set.) >> >> I'll noodle about the co-funding. > > While the full needs after changes can be a burden, I'm not 100% sure to > subscribe to not "forcing it" in a way or another. > > Every admin will have one day or another a change to setup in its filesets. > Accurate will pick that ok, but then the time to restore will come, > and I beat on the fact that there will be a lot of complains about why "my > files are not there" expectation. > The reason will be because at that time, the fileset didn't know about them, > and nobody will remember at that time, a change occurs in the fileset, and no > full were made again. > > I'm sorry if I'm not clear enough yet, I would like to see all the real > scenario before jumping saying "bravo". > Perhaps we need a fileset version in the database ? > > Or some options are minor, and other major ? > > Isn't there a way to trick bareos with the content of fileset table ? > like saving the date of the previous hash for a given ressource, make the new > one and bring back the old data ? It does seem that the change the fileset and get a new full backup rule is safest. And probably a good default. I was noodling about a "I'm smarter than Bareos" option that would allow me to change a fileset and take responsibility for not requiring the next backup be a full backup. In my particular case the change is fairly innocent: The fileset starts at / and backups up all local filesystems other than some directories that are excluded. And my work around was to not add "File = /project/tmp" to the Excludes stanza in the fileset, but instead add a line to the excludes file on the client. Adding the line to the excludes file on the client doesn't force a new backup and yet has exactly the same result as adding it to the fileset. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
