Hi, when restoring, listing files, backing up, purging or pruning mysql
process uses 100% CPU and the machine is unusable, and such operations last
to long. Doing some research I found that this can be related to database
indexes, but I didn't understanf well what I need to do .Here is the output
Hi,
On a bacula installation that I originally set up on a machine running
Debian etch, everything was running smoothly.
Since etch has been EOL'ed, it was necessary to upgrade it, and we
recently did do an upgrade to lenny. This also involved an upgrade of
bacula from 1.38 (the version in etch)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Cregan wrote:
Hi We have just started to use bacula as our backup solution and
are suffering some performance problems. The details are
Server: Debian 4.0 running bacula 2.2.4 is multihomed as it backs
up over two networks. Storage is
Hi
We have just started to use bacula as our backup solution and are
suffering some performance problems. The details are
Server:
Debian 4.0 running bacula 2.2.4 is multihomed as it backs up over two
networks.
Storage is Overland Arcvault24 on same host
Database is mysql:
On Mon, 25 Apr 2005, Andreas Kopecki wrote:
More than enough, but you'll ensure postgres is actually using it.
How big is its memory footprint?
postgres 19292 /usr/bin/postmaster -D /var/lib/pgsql/data
postgres 10088 postgres: stats buffer process
postgres 9096 postgres: stats collector