In my usual style for archive backups, I go straight to tape by
specifying no holding disk at all. ... I would think the entries without a
starttime would go ahead and write to tape as there is no holding
disk for which to wait. Yet, things still didn't appear to work this
way when I attempted
Hi and thanks for the help.
--From John R. Jackson--
I'm not sure that's what's going on. Note the following:
driver-idle: no-diskspace
As far as I can tell from the code, Amanda will run everything it can
before those with a delay (but see below). The problem is, the best
client
Well, I only ever want to write to tape when running this config and
so have not specified a holding disk at all.
Oh. Well that explains a few things :-).
Given this, how would you think Amanda would then behave?
As I said, I'm just guessing based on a quick read of the code, but I
think if
Hi, I'm trying to do what Mark Chang started a thread concerning March
6th: back up a laptop that's only available during the day with a host of
computers that are preferentially backed up at night. Jan Edler jumped
in on the topic, too. Seems to be somewhat a problem and one that
isn't easily
... Estimates have all arrived but
every disk, including the laptop's disks which have no delay specified,
have status wait for dumping. ...
You need to look at your active amdump file for the driver: state time
... lines, and in particular at the driver-idle value to find out what
the holdup
