Hello,
That is good to know.
You probably already know two things, but I mention them for those who
do not know:
1. There is a chapter (or at least a section) in the main manual on how
to create bootstrap files from Job output.
2. Bacula 7.4.4 or any other Bacula is perfectly capable of readi
On Fri, 24 Mar 2017 14:01:39 +0300
Konstantin Khomoutov wrote:
Answering my other question:
> > Thanks for mentioning that VolAddr is undocumented. That was an
> > oversight that I will fix.
> >
> > Please be aware that VolAddr is a relatively new bsr keyword, so it
> > will not work on older
On Thu, 23 Mar 2017 09:58:35 +0100
Kern Sibbald wrote:
> Thanks for mentioning that VolAddr is undocumented. That was an
> oversight that I will fix.
>
> Please be aware that VolAddr is a relatively new bsr keyword, so it
> will not work on older Bacula's such as 5.2.x. I don't remember when
Hello Martin,
Thanks for mentioning that VolAddr is undocumented. That was an
oversight that I will fix.
Please be aware that VolAddr is a relatively new bsr keyword, so it will
not work on older Bacula's such as 5.2.x. I don't remember when it was
implemented.
Note also: VolAddr is formed
> On Wed, 22 Mar 2017 13:52:50 +0300, Konstantin Khomoutov said:
>
> On Wed, 22 Mar 2017 12:07:55 +0300
> Konstantin Khomoutov wrote:
>
> [...]
> > Here, the job starts at 338:1 and ends at 339:10868, how do I write
> > out the bootstrap file's data to cover that whole range in it?
> > From
On Wednesday 2017-03-22 12:07:55 Konstantin Khomoutov wrote:
> For instance, here's a fragment from the real output for one of my
> volumes (elided a bit for terseness):
>
> Begin Job Session Record: File:blk=338:1 SessId=142 \
>SessTime=1427996423 JobId=5007
> Job=call-recs.2015-05-12_14.00
On Wed, 22 Mar 2017 12:07:55 +0300
Konstantin Khomoutov wrote:
[...]
> Due to the uniqueness + tiny size + large quantities property of these
> data, we have decided to keep only the information on the last few
> backup session in the database to keep its size manageable, and resort
> to "painful
On Wed, 22 Mar 2017 10:31:16 +0100
Andreas Nastke wrote:
> how about archiving the 'tiny' items into larger tar- or zip-files
> on a regular basis (say every 15 minutes) and then only backup the
> archives.
The thing is that having "low-level addressing" data in a bootstrap
file allows Bacula to
how about archiving the 'tiny' items into larger tar- or zip-files
on a regular basis (say every 15 minutes) and then only backup the
archives.
Konstantin Khomoutov schrieb:
> Hi!
>
> I have a somewhat unusual Bacula setup as we're backing call records
> produced by a call-center software -- so
Hi!
I have a somewhat unusual Bacula setup as we're backing call records
produced by a call-center software -- so the files are tiny in size,
there is very large number of them produced daily, they are all unique
and we have to keep them for several years as required by the local
law.
Due to the
10 matches
Mail list logo
