Thanks Kern! I'll bring in a DBA on our side to have a look.
Would you have any thoughts on this question posed earlier?
3. Why is Bacula spinning off a new job right away after it detects the
deadlock for each affected job instead of waiting until the rescheduled job
runs? I verified that ther
Hello Ana..
For now, I split the file to make the backups...
And it's works...
Later, I will see the results and ask for same others instrutions...
Thanks
2015-08-06 17:26 GMT-03:00 Ana Emília M. Arruda :
> Hélio Gilberto,
>
> Yes. You can have full, differentiall and incremental backups in the
Hélio Gilberto,
Yes. You can have full, differentiall and incremental backups in the same
volume/pool. Bacula will mark your volume full of it reaches the maximum
volume bytes for this volume. Have you had configured maximum volume bytes
for the volume being marked full?
Could you send the result
On 06.08.2015 21:44, Craig Shiroma
wrote:
Hi Kern,
Thank you for the info! We're using MySQL 5.6 Percona
Server, Release 68.0, Revision 656.
Would this setting cause the problem?
innodb_lock_wait
On 06.08.2015 21:36, Craig Shiroma
wrote:
Hi Bryn,
Thank you for the translation! :-) Much appreciated.
I'll ask our DBA to take a look at the DB (mysql). Maybe it
needs some tuning for Accurate. Do you know of any
Hi Kern,
Thank you for the info! We're using MySQL 5.6 Percona Server, Release
68.0, Revision 656.
Would this setting cause the problem?
innodb_lock_wait_timeout = 100
Is it too high or too low or has no bearing on the problem?
Thanks again,
-craig
On Thu, Aug 6, 2015 at 9:26 AM, Kern Sibbal
Hi Bryn,
Thank you for the translation! :-) Much appreciated. I'll ask our DBA to
take a look at the DB (mysql). Maybe it needs some tuning for Accurate.
Do you know of any documentation for this? I only saw a couple of small
sections for Accurate in the manual, mainly how to turn it on and t
On 06.08.2015 18:46, Bryn Hughes wrote:
I think what Kern is getting at is
that your database is what threw the error, not Bacula.
Whatever DB you are using is what is having the issue.
Yes. That is exactly what I was implying
I think what Kern is getting at is that your database is what threw the
error, not Bacula. Whatever DB you are using is what is having the issue.
Bryn
On 2015-08-06 09:11 AM, Craig Shiroma wrote:
Hi Kern,
Thank you very much for the reply! Would you have any suggestions on
what may be caus
Hi Kern,
Thank you very much for the reply! Would you have any suggestions on what
may be causing this problem or how I can debug it? Obviously, I'm
encountering deadlocks when accurate backup runs on some of our hosts and
we want to use accurate backup on all of our hosts if possible.
Warmest
Hi folks...
That's my first post in this mailing list and I think I have a very unrare
problem...
I have this in bacula-sd.conf
Device {
Name = bacula
Archive Device = /media/2c0bc75b-f54e-4f31-8d8c-5568edc0e765/bacula
Media Type = File
LabelMedia = yes
Random Access = yes
AutomaticM
On 8/6/2015 5:09 AM, Raimund Sacherer wrote:
> Hello Josh, Bacula-users,
>
>
>> I have seen this before as well, although not with FreeBSD. Bacula-dir
>> expects the TCP connection with the client to remain up throughout the
>> entire job. In my case I concluded that it was aggressive Windows pow
You could find out with which version of mysql client has been compiled
your bacula with the following command
# ldd /usr/sbin/bacula-dir | grep mysql
libmysqlclient.so.18 => /lib64/libmysqlclient.so.18
(0x7f07abe3d000)
# rpm -qf /lib64/libmysqlclient.so.18
Percona-Server-shared-55-5
> Hey Heitor,
> Actually to 1, no they are not. I have mariadb-5.5.41 on the bacula server
> (client side) and mariadb 10 on the db server. I might try upgrading the
> client
> on the bacula server tomorrow. I don't have SELinux enabled anywhere
> currently.
> I probably will enable that tho onc
On 06.08.2015 10:15, Craig Shiroma
wrote:
Hello again,
I just thought I'd update this post with more information
in hopes of getting some explanation for the deadlocks.
I ran with Accurate backup on our
On 04.08.2015 18:41, Michael Schwager
wrote:
Actually,
the restore jobs were in the 900-range. 687 was indeed the
backup job, as I can see that the numbers before and closely
following it were all backup jobs in the same data r
Hello Josh, Bacula-users,
> I have seen this before as well, although not with FreeBSD. Bacula-dir
> expects the TCP connection with the client to remain up throughout the
> entire job. In my case I concluded that it was aggressive Windows power
> management shutting down the Ethernet interface
One thing I missed mentioning was on the second night accurate backup was
used, the director died about 45 minutes into the backup with the following
error. This did not happen on the first run with accurate enabled.
Aug 4 19:02:27 bacula-dir: Bacula interrupted by signal 11:
Segmentation viola
Hello again,
I just thought I'd update this post with more information in hopes of
getting some explanation for the deadlocks.
I ran with Accurate backup on our test VMs (RHEL) for a couple of days and
got the same errors on some VMs that were running accurate and some that
were not. These hosts
19 matches
Mail list logo
