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
... the funny
thing is that one of the 'disks' on the backup server insists
on adding an exclude-list in the REQ packet, even though it is
not configured to do so in the dumptype ...
You're right, that's very odd.
What do you get if you run amadmin config disklist box? That should
dump the
What do you get if you run amadmin config disklist box?
the listing for that disk is identical to the others (so says
'uniq' and me eyeballs). i'll check to see that it isn't some
weird side-effect from just changing the config file (ie, wait
what amandad's debug file says tomorrow morning).
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
ok, so it *is* the case that the UDP packet is hitting the 2.4.1
8k limit, but this seems to be due to amanda sending out two
lines for backups for each disk, one with the UTC origin date
(1970), and the other the apparently valid request. here's a
pair of lines:
GNUTAR //winhost/profiles 0
ok, so it *is* the case that the UDP packet is hitting the 2.4.1
8k limit ...
You can just crank up MAX_DGRAM to 65535 in common-src/dgram.h and rebuild
both your client and server. Or you could upgrade both to 2.4.2p2.
And if you get there, I can (re)send you the patch that works around
this
You can just crank up MAX_DGRAM to 65535 in common-src/dgram.h and rebuild
both your client and server. Or you could upgrade both to 2.4.2p2.
And if you get there, I can (re)send you the patch that works around
this problem completely.
i'm on debian, so i used 'apt-get source --compile amanda'.
this just popped up the other day, and happened again with last
night's run. i don't recall if i changed anything, but i am
assuming that i must have.
here are two error lines typical of the two types (local and
smb) of shares:
thehost //axon/Users lev 0 FAILED [badly formatted response
hello all.
i've searched around and i can't seem to find too much regarding
this subject. the server that runs amandad also backs itself up, and
none of the shares local to the backup server, in addition to the
smbclient windows shares it backs up are not being backed up due to
this type of
Two letters just came in with the same Subject but (somewhat) different
From: values. I'm hoping they are really from the same person.
here are two error lines typical of the two types (local and
smb) of shares:
thehost //axon/Users lev 0 FAILED [badly formatted response from thehost]
Two letters just came in with the same Subject but (somewhat) different
From: values.
i apologize. i was having much trouble with the list and tried
sending through egroups (yahoo).
There are a couple of possibilities. One is that you've added some
disks and the request (or corresponding
11 matches
Mail list logo
