In the message dated: Wed, 11 Apr 2018 06:25:43 -0700,
The pithy ruminations from Stephen Thompson on
[Re: [Bacula-users] can file retention be job rather than client based?] were:
=>
=> Thanks Kern.
=>
=> I think given the limited nature of his need, I may use a postrun script
+1 for this
On 2018-04-11 03:52, Radosław Korzeniewski wrote:
I'm very surprised that your build is not working and you have to
disable libtool. Unfortunate I never tried Solaris Compiler Suite with
Bacula.
I haven't used solaris in forever but back when, libtool did not work
with Sun's CC. Linker
On 2018-04-11 01:59, Kern Sibbald wrote:
I have never used two Client definitions to backup the same machine, but
in principle it would work fine.
The closest I have is a "cluster ip" floating between two machines, with
3 client/job definitions: one for each physical machine (backing up /etc
Thanks Kern.
I think given the limited nature of his need, I may use a postrun script
to simply wipe database records out of band.
Also if I did use multi-client definitions, I would need to use the same
pool as they all go to the same monthly tapes.
Stephen
On 4/10/18 11:59 PM, Kern
Hello,
I'm building Bacula 9.0.6 on Solaris 11 using gcc (I'm not sure if I used
gcc provided by Oracle or installed externally) and the following configure
(which forces 64bit compilation and debugging symbols):
CXXFLAGS="-m64 -g" CFLAGS="-m64 -g" LDFLAGS="-m64 -g" ./configure
Hello,
2018-04-10 13:13 GMT+02:00 Johannsen, Thorsten :
> Hello list,
>
> in my mail
>
>
> [Bacula-users] scheduled job different that manually initiated job? --WAS:
> Re: Backup problem with 1 of 2 Raspberry PI using Raspbian (Debian)
>
> one of the problems I was
Hello Stephen,
What you are asking for, as you suspect, does not exist and implementing
it would be a bit problematic because every Job would need to keep it's
own retention period. For one client, there can be any number of Jobs
-- typically thousands. Thus the catalog would grow faster