On Mon, 06 Jun 2011 18:54 +0200, "Johan De Meersman"
wrote:
> > Excluding 'performance_schema' appears to eliminate the error. And it
> > seems does NOT cause a reliability-of-the-backup problem.
>
> Hah, no, backing that up is utterly pointless.
that's a useful/final confirmation. thx.
> No,
- Original Message -
> From: ag...@airpost.net
>
> Excluding 'performance_schema' appears to eliminate the error. And it
> seems does NOT cause a reliability-of-the-backup problem.
Hah, no, backing that up is utterly pointless. Never noticed it doing that.
It's basically a virtual schem
On Mon, 06 Jun 2011 12:44 +0200, "Johan De Meersman"
wrote:
>
> I haven't bothered to look for the "bug", but it seems to me to be quite
> reasonable default behaviour to lock the whole lot when you're dumping
> transactional tables - it ensures you dump all tables from the same
> consistent vi
I haven't bothered to look for the "bug", but it seems to me to be quite
reasonable default behaviour to lock the whole lot when you're dumping
transactional tables - it ensures you dump all tables from the same consistent
view.
I would rather take this up with the ZRM people - it should "just
Am 05.06.2011 23:55, schrieb ag...@airpost.net:
> i still have no idea why this is necessary.
take it or not
it is a professional solution which works for
databses with 20 GB every day here with rsync
without interrupt/lock mysqld a second
and it is much faster
> there seems to be a but, prob
i still have no idea why this is necessary.
there seems to be a but, problem, misconfiguration, etc.
wouldn't it make some sense to try to FIX it, rather than setting up a
completely different server?
perhaps someone with an idea of the problem and its solution will be
able to chime in.
--
My
Am 05.06.2011 23:49, schrieb ag...@airpost.net:
>
> On Sun, 05 Jun 2011 23:29 +0200, "Reindl Harald"
> wrote:
>> i would use a replication slave and stop him for consistent backups
>> because dumb locks are not really a good solution independent
>> if this works "normally"
>
> unfortunately, i
On Sun, 05 Jun 2011 23:29 +0200, "Reindl Harald"
wrote:
> i would use a replication slave and stop him for consistent backups
> because dumb locks are not really a good solution independent
> if this works "normally"
unfortunately, i have no idea what that means.
something's apparently broken w
On Sun, 05 Jun 2011 23:30 +0200, "Reindl Harald"
wrote:
> BTW
> WHY is everybody ansering to the list AND the author of the last post?
> this reults in get every message twice :-(
Reply -> sends to ONLY the From == h.rei...@thelounge.net
Reply to all sends to BOTH the From == h.rei...@thelounge.n
BTW
WHY is everybody ansering to the list AND the author of the last post?
this reults in get every message twice :-(
Am 05.06.2011 23:26, schrieb ag...@airpost.net:
> fwiw, others are seeing this. e.g., in addition to the two bugs i'd
> already referenced,
>
> http://www.directadmin.com/forum/s
hm - bad
i would use a replication slave and stop him for consistent backups
because dumb locks are not really a good solution independent
if this works "normally"
Am 05.06.2011 23:26, schrieb ag...@airpost.net:
> fwiw, others are seeing this. e.g., in addition to the two bugs i'd
> already refer
fwiw, others are seeing this. e.g., in addition to the two bugs i'd
already referenced,
http://www.directadmin.com/forum/showthread.php?p=202053
and one
http://qa.lampcms.com/q122897/Can-t-backup-mysql-table-with-mysqldump-SELECT-LOCK-TABL-command
claims a solution
"Add --skip-add-locks to
the grant statements does nobody interest
maybe use phpmyadmin for a clearer display
mysql> select * from mysql.user where user='root' limit 1;
+---+--+---+-+-+-+-+-+---+
hi,
On Sun, 05 Jun 2011 22:24 +0200, "Reindl Harald"
wrote:
> have you checked you permissions-table if all privileges are active for root
i've got,
mysql> show grants for 'root'@'localhost';
+--
have you checked you permissions-table if all privileges are active for root
and have you started "ymsql_upgrade" after all updates?
Am 05.06.2011 22:20, schrieb ag...@airpost.net:
> i use ZRM to do backups of my databases.
>
> with v5.1.x, this works fine,
>
> mysql-zrm-scheduler --now --back
i use ZRM to do backups of my databases.
with v5.1.x, this works fine,
mysql-zrm-scheduler --now --backup-set manual --backup-level 0
to execute a manual backup.
i recently upgraded from v5.1.x -> v5.5.12,
mysqladmin -V
mysqladmin Ver 8.42 Distrib 5.5.12, for Linux on i686
now, at exec
16 matches
Mail list logo
