>i'm on debian, so i used 'apt-get source --compile amanda'. i
>am not immediately sure how to integrate user patches into the
>process ...
'fraid I wouldn't know anything about that either. Why not just build
Amanda yourself? It's not hard.
>... is this a patch that segments the request into
>multiple packets (i've heard talk of this), and if so, would
>that break older clients?
I was suggesting you just increase the packet size. In 2.4.1 it's
8 KBytes. In 2.4.2 it's 64 KBytes.
Or if, in the process of building from source, you go with 2.4.2(p2)
you'll get that change anyway.
If 64 KBytes is still a problem (which it probably won't be), then I
also have a patch that splits requests into multiple packets, but it
only applies against 2.4.2p2. And no, it does not break older clients.
>... i also can't understand the two separate
>size requests. why does it ask for a level 0 size *and* a
>level 1 size? ...
Amanda *always* asks for a level 0, the same level as the last run
(which is a level 1 for PC's due to the way they work) and it may
also throw in a request for the next level (probably not for PC's).
That's to gather all the information it needs to pick which levels to
do based on tape capacity, length of time since the last full dump, etc.
For instance, if Amanda gets all the estimates and they would be larger
than a tape, it will demote full dumps back to incrementals until the
total estimated size fits. To do that it needs to know how big those
incrementals are.
Or, if the tape fails during the run, Amanda will drop back to degraded
mode where it (usually) just does incrementals instead of full dumps.
Again, it would need to know the estimated size (for holding disk
allocation).
This may have started happening because something changed in amanda.conf.
For instance, if these backups used to always request a full dump (not
sure about that one) or if the path to the exclude list changed, or if
you used to pass a single exclusion pattern and now you're passing a
file name, etc.
Uh, oh. I just realized something from a previous posting. You said
you saw this:
GNUTAR //winhost/profiles 0 1970:1:1:0:0:0 1 exclude-list=/etc/amanda/exclude.gtar
That's not going to work. You're passing an exclusion **file** to do
a PC (smbclient/smbtar) backup. Samba only supports a single pattern
("exclude", not "exclude list" in amanda.conf). Which is unfortunate,
but you'd have to bug the Samba folks about that. Or some Amanda user
could get ambitious and write up a Samba patch that Amanda could include
ala what we do for GNU tar 1.12.
>-c
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
