Hi Craig,
Good news!
You're welcome (again) :). And thank you for your feedback. They are always
useful.
Best regards,
Ana
On Mon, Aug 10, 2015 at 3:35 PM, Craig Shiroma
wrote:
> Hi Ana,
>
> >Did you monitor resource usage during the backups? The list of files
> generated for accurate backups
Hi Kelvin,
Thank you for the info and help! Good information to keep in mind.
I think I found the root of the problem thanks to everyone. See my reply
to Ana.
Thanks again for the post. It's much appreciated.
-craig
On Fri, Aug 7, 2015 at 10:46 AM, Kelvin Minter wrote:
> MyISAM is terrib
Hi Josip,
Thank you for the advice and for looking that up in the mysql docs. That
was pretty much the error I was getting.
See my reply to Ana.
Again, thank you for the help. I really appreciate it.
-craig
On Thu, Aug 6, 2015 at 9:26 PM, Josip Deanovic
wrote:
> On Thursday 2015-08-06 09:4
Hi Ana,
>Did you monitor resource usage during the backups? The list of files
generated for accurate backups are
>kept in memory (by both director and client), so this should cause
resource use (CPU, memory, etc.) to increase in both hosts.
I did monitor these items earlier, but did not notice a
Hi Craig,
On Fri, Aug 7, 2015 at 3:49 PM, Craig Shiroma
wrote:
> Hi Ana,
>
> Thank you for the suggestion!
>
You're welcome!
>
> I'll look into adding more CPU and memory to director, although I didn't
> see much of an impact on either between a non-accurate run and an accurate
> run. For
Hi Ana,
Thank you for the suggestion!
I'll look into adding more CPU and memory to director, although I didn't
see much of an impact on either between a non-accurate run and an accurate
run. For example, there was large depletion of available memory, no
swapping, or high load.
I did add more me
MyISAM is terrible for transactions. If the deadlock is happening because
of table locking then switching the engine to InnoDB might help your
problem.
MyISAM locks the entire table while InnoDB only locks the rows it is
updating.
Check out the link below.
http://stackoverflow.com/questions/20148
Hello Craig,
In one of your posts you mentioned Segmentation violation in the director
host. Accurate backups requires more resources than normal ones. Have you
checked if CPU and memory resources are enough in director and the clients
that are configured for using accurate mode?
Best regards,
An
On Thursday 2015-08-06 09:44:06 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_timeout = 100
>
> Is it too high or too low or has no bearing on the probl
On Thursday 2015-08-06 09:44:06 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_timeout = 100
>
> Is it too high or too low or has no bearing on the probl
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
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
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
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
BTW, I suppose there could've been two jobs for the host(s) in scheduling
queue. If this was the case, is there a way to find out after the fact?
If this did actually happen, what could cause duplicate jobs to be
scheduled on the same day at the same time? I know no one manually ran the
jobs in q
Hello,
I had a few backups fail last night with the following error:
2015-08-03 18:02:46bacula-dir JobId 123984: b INTO File (FileIndex, JobId,
PathId, FilenameId, LStat, MD5, DeltaSeq) SELECT batch.FileIndex,
batch.JobId, Path.PathId, Filename.FilenameId,batch.LStat, batch.MD5,
batch.DeltaSeq FR
23 matches
Mail list logo
