We are seeing a fairly recent problem with some of our amanda
installation (we have 11 different amanda jobs each night using
from 2.2.6 to 4.2.x).
We have some partitions that amanda is running "direct to tape"
rather than via the spool area even though we have sufficient
spool space.
On Apr 10, 2001, [EMAIL PROTECTED] (Brian Cuttler) wrote:
Wondering if this isn't a "feature" of 2.2.6 and a must upgrade
for performance issue at our site.
The smaller problem partition is only 4 gig, the larger in excess
of 18, both partitions continue to grow.
I'm afraid you'll have to
To: Alexandre Oliva
Cc: Brian Cuttler; [EMAIL PROTECTED]; J Chris Knight
Subject: Re: Amanda 2.2.6, not using spool area
Alex,
Holding disk on "wcnotes" is 36 gig (in a single partition) the
level 1 backup that went direct to tape last night was 11 gig
(5 gig from anoth
Thank you. Paul Bort had the same thought.
I'd thought we'd exceeded the 2 gig barrier long ago - perhaps
that was only on some of the newer version amanda servers.
Thank you both - will schedule an upgrade to both amanda systems.
Oh - which release do you recommend. We don't need the latest
I'm attempting to build Amanda 2.4.2p2 on Solaris 5.6 and finding
the following...
[newton] /local/source/etc/amanda/amanda-2.4.2p2 43 ./configure --with-user=bin
--with-group=sys
which seems to run to completion (we have notes from previous installation
that talk about the --disable-libtool
I'm attempting to build Amanda 2.4.2p2 on Solaris 5.6 and finding
the following...
output ending with...
checking whether lockf locking works... (cached) no
checking whether lnlock locking works... (cached) no
configure: warning: *** No working file locking capability found!
configure: warning:
