It works for me, too, but I get this error.
> On 5. Sep 2022, at 20:14, Martin Simmons wrote:
>
> A copy job works for me in Bacula 13.0.0 without this problem (even if the
> bacula-fd isn't running).
>
> __Martin
>
>
>> On Mon, 5 Sep 2022 19:09:18 +0200, Justin Case said:
>>
>> Yes, it
A copy job works for me in Bacula 13.0.0 without this problem (even if the
bacula-fd isn't running).
__Martin
> On Mon, 5 Sep 2022 19:09:18 +0200, Justin Case said:
>
> Yes, it does match. I then replaced the dummy password with the actual FD
> password, and the error did not occur any
Hello
Volume retention is 90 days
File retention is 40 days in client setup
The issue (if it's a real issue) is happening within both timeframes
thanks
Ant
Il 05/09/2022 18:42, Matlink ha scritto:
Which retention are you talking about? Volume retention is not
guaranteed. You should not rely
As you suspect, adding the extra run for level=Data will not work. I just
have separate schedules without any level specified for verify jobs.
__Martin
> On Mon, 5 Sep 2022 19:06:05 +0200, Justin Case said:
>
> Martin, excellent advice. it says at the job info:
>
> level=Data
>
> then
Yes, it does match. I then replaced the dummy password with the actual FD
password, and the error did not occur any more when starting copy jobs. This
behaves differently than documented, that’s why I am asking.
> On 5. Sep 2022, at 17:56, Martin Simmons wrote:
>
> That looks strange to me.
Martin, excellent advice. it says at the job info:
level=Data
then under the schedule info:
Run Level=Full
..
Run Level=Incremental
..
Run Level=Incremental
according to the schedule it is Incremental
The precedence of which level is used cannot be derived from the "show job"
alone.
I was
Which retention are you talking about? Volume retention is not guaranteed. You
should not rely on it for restoring.
Le 5 septembre 2022 12:49:56 GMT+02:00, Antonino Balsamo
a écrit :
>Hello,
>
>my scenario is a one job per volume with no recycle and 90 days retention
>period, usual
On 2022-09-05 11:14 AM, Martin Simmons wrote:
...
I think you need convert_from(), not encode(). Something like
select convert_from(VolumeName::bytea, 'SQL_ASCII') from media;
Right, I saw the starting '\x' and looked no further. OP will have to
figure out what encoding that POS is
Yes, that seems possible. Bacula will find no jobs associated with the volume
so it will look like a pruned volume.
__Martin
> On Mon, 5 Sep 2022 10:49:56 +, Antonino Balsamo said:
>
> Hello,
>
> my scenario is a one job per volume with no recycle and 90 days
> retention period,
On 2022-09-05 4:21 AM, Uwe Schuerkamp wrote:
bacula=# select encode(VolumeName, 'hex') from media;
encode
7a69662d66756c6c2d30303031
7a69662d696e63722d30303032
7a69662d696e63722d30303033
...
Is the "\xss850938sdkl" you posted before an actual
> On Mon, 5 Sep 2022 11:21:52 +0200, Uwe Schuerkamp said:
>
> I've tried casting "blob" and "tinyblob" (the mariadb column types for
> VolumeName, for example) to "text", but pgloader just hangs when
> including those cast statements.
What exact cast statement did you use?
>
> Also, Dima
That looks strange to me. The "JobId 0" maybe means that it was caused by
something else. Does the time "04-Sep 14:19" match the sequence of times in
the other messages about the copy job?
__Martin
> On Sun, 4 Sep 2022 14:33:03 +0200, Justin Case said:
>
> Hi there,
>
> I took this
Maybe the output of
show job=job1-verify
will show where the level is being set to Incremental? It might be the
Schedule resource for example.
__Martin
> On Sat, 3 Sep 2022 22:13:16 +0200, Justin Case said:
>
> Hi
>
> I am confused why I am getting this error:
>
>
> 03-Sep 22:00
Hello Uwe
Could you send me the dumps of MySQL that script had generated?
Best regards
*Wanderlei Hüttel*
Em seg., 5 de set. de 2022 às 06:21, Uwe Schuerkamp <
uwe.schuerk...@nionex.net> escreveu:
> Hi folks,
>
> I've now tried to migrate my mariadb bacula db to postgres using
> Wanderlei's
Hello,
my scenario is a one job per volume with no recycle and 90 days
retention period, usual full/diff/incr pools.
It happens that from time to time (if there are no files in the job due
to no filesystem change) that Bacula purge a volume within the retention
period.
Is that possible
Hi folks,
I've now tried to migrate my mariadb bacula db to postgres using
Wanderlei's scripts linked below. Sadly I end up with the same "hex
value" volume names in the media table. :.( It looks like newer
mariadb / mysql catalogs might require some extra steps to enable a
successful migration
Hello Justin,
It seems that the Copy Pool directive has not been fully implemented. It
was added in 2007 but nothing else happened with it.
Here you can read feature request for the Copy Pool:
17 matches
Mail list logo
