Hello,

Hate to say but I'm running (probably) one of the odder configurations.

We run two amanda servers concurrently on a single system (Solaris 9,
Amanda 2.4.4). We are able to do this because one of the servers 
backups up only "local" ie UFS partitions and the other only "remote"
clients (clients not of localhost). We are writing to two separate
jukeboxes (each with a single LTO tape drive).

I have started seeing that the remote backups fail, the following
is the typical message

  panther    /data lev 1 FAILED [no more holding disk space]

I take it to mean that the local backups, running much more quickly
(fast processor, no network) than remote backups and _shareing the
same physical /amanda/work partition_ are filling up the amanda/work
area and the remote backups having no place to write are failing.

Is this the case ? Why don't the (remote) dumps simply delay until
spool clears - or perhaps put one or two into degraded mode, allowing
the other amanda server to write its own drive and clear the spool 
and allowing the remote backups to resume use of spool.

I don't really want to limit the amount of spool available to either
server, I suppose I could probably stagger the two servers in cron but
not certain which way to skew them.

Ideal situation, single amanda server - write completed dumps to
alternate jukeboxes, output any of n-dumps to first available or
best fit drive. Sort of a round-robin on the jukeboxes. Doable ?

                                                thanks,

                                                Brian

---
   Brian R Cuttler                 brian.cuttler AT wadsworth DOT org
   Computer Systems Support        (v) 518 486-1697
   Wadsworth Center                (f) 518 473-6384
   NYS Department of Health        Help Desk 518 473-0773