Hi John,
It always works for me.
I found a bug, it randomly (not that random) take the value of the
tapetype length or the device max-volume-usage property.
In my case, it always use the value of the tapetype length, in your case
it always take the value of the device max-volume-usage proper
But that same man page also says, that for the vfs device, "This
device supports the ENFORCE_MAX_VOLUME_USAGE property. Default value is
true."
Furthermore, the man page says that if ENFORCE_MAX_VOLUME_USAGE is
false, the volumes expand "without limit". But that's not what is
happening. Th
man amanda-devices
MAX_VOLUME_USAGE
(read-write) On devices that support it, this property will
limit
the total amount of data written to a volume; attempts to write
beyond this point will cause the device to simulate "out of
space."
Zero m
I'll have to look at the amanda-devices page for the exceptions.
But I can tell you that while amanda is skipping some level 1
dumps on me, because of calculated size, and I am using vtapes.
Amanda is telling me that its filled the tape and then keeping
things in the holding area.
I suspect that
Last week I asked a few questions about virtual tape size. Well, I
wouldn't say I resolved them but I think I have one clue. One of the
things I asked about is the meaning of the "length" parameter for a tape
definition. I had set it to 25G for my virtual tapes but amanda was
writing 38G to e
