>Here is the result from the amdump log:
>driver: result time 559.820 from dumper0: FAILED 00-1 [data read:
>Connection
> reset by peer]
>driver: QUITTING time 559.841 telling children to quit
OK, now that I understand you're not splitting clients among multiple
servers, what time did dumper0
>I am running amanda 2.4.1-p1 on some Compaq tru-64 boxes attached to DLT's.
>The number of systems I have been backing up has grown dramatically
>recently, so I have split the backups up to run to two different Amanda
>servers.
>
>The problem I have is that I can run backups from 2 of my clients
Hi,
I've checked out the archives and found this problem has occurred for
several people for different reasons, unfortunately I can't find an answer
here for my own problem.
I am running amanda 2.4.1-p1 on some Compaq tru-64 boxes attached to DLT's.
The number of systems I have been backing up ha
Hello...
John R. Jackson wrote:
>>
>> backup all the small partitions
>> several local partitions start
>> one of the partitions across the T1 starts
>> the local partitions end at various times
>> ...
>>
>> remote partition ends (about 4 hours later) and writes to tape
>> holding area dumps
>There is no tape activity for any backups started after the remote
>(slow) backup started.
I'd need to see the amdump. file to diagnose this any further.
It doesn't make any sense and I've never seen Amanda defer writing
to tape. When taper gets done with one file driver always gives it
someth
>Mar 13 13:23:55 nuthatch inetd[17275]: execv
>/usr/local/libexec/amindexd: No such file or directory
This seems pretty obvious to me. Do you have this file? Are all the
directories down to it searchable by the Amanda user listed in inetd.conf?
>RLE
John R. Jackson, Technical Software Special
On Mar 13, 2001, "Carey Jung" <[EMAIL PROTECTED]> wrote:
> My recollection is that exclude files are not supported for 'dump'
> and 'smbclient' dumps. Am I right?
Almost. In 2.4.2(p1?), exclude patterns (but not exclude lists, IIRC)
are supported in smbclient too.
--
Alexandre Oliva Enjoy
>i have a huge filesystem (64Gig) that amanda is refusing to back up. ...
Are you using dump or GNU tar?
>... i tried increasing the etimeout to 3000, but no luck (and it's for SU
>RE not waiting an hour!). The sendsize.debug file has an estimate in it for t
>hat filesystem. ...
Why do you t
>... My recollection is that exclude
>files are not supported for 'dump' ...
Correct.
>and 'smbclient' dumps. ...
Not correct. You may use "exclude", but not "exclude list", to get
rid of one file from an smbclient backup. Yes, this is almost useless,
but it's all smbclient gives Amanda to w
>
>backup all the small partitions
>several local partitions start
>one of the partitions across the T1 starts
>the local partitions end at various times
>...
>
>remote partition ends (about 4 hours later) and writes to tape
>holding area dumps start writeing to tape
Are you saying no tape activi
>
> 2.4.2 makes it possible to define dump types directly in the
> disklist. And since dump types can define the filename for an exclude
> file you can have seperate exclude files for each disk entry (of
> course you could also define the dump types in amanda.conf and use
> different dump types fo
>AMRECOVER Version 2.4.2. Contacting server on CNCBACK ...
>amrecover: Error connecting to server: Connection refused
Assuming it's not a TCP wrappers issue or something like that, there is
a problem with the 2.4.2 amrecover and how it connects to the servers
that is fixed in the current source t
i have a huge filesystem (64Gig) that amanda is refusing to back up. it's only 23%
full, but when i try to back it up, i get [no estimate] on the failure message. i
tried increasing the etimeout to 3000, but no luck (and it's for SURE not waiting an
hour!). The sendsize.debug file has an est
>How do I blank a tape? amlabel -f ? ...
It depends on what you mean by "blank". Once you amlabel a tape, you may
continue to use it with Amanda (as long as you don't change labelstr).
You do not need to re-amlabel it every time it comes back around in
the cycle. Why did you want to "blank
On Mar 13, 2001, Yura Pismerov <[EMAIL PROTECTED]> wrote:
> You can't setup a separate exclude list for each entry in disklist file.
Sure you can! Even in 2.4.1. You just need different dumptypes, each
with its own exclude list.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.
> 2.4.2 makes it possible to define dump types directly in the
> disklist. And since dump types can define the filename for an exclude
> file you can have seperate exclude files for each disk entry (of
> course you could also define the dump types in amanda.conf and use
> different dump types for
Yura Pismerov <[EMAIL PROTECTED]> writes:
> You can't setup a separate exclude list for each entry in disklist file.
> In this particular case you just need to put ./home and ./var into
> exclude file and make 3 separate entries for /, /home and /var in the
> disklist. I assume you don't have ./h
Hello...
I have several machines that I back up using amanda. All but one are on
the same network (100Mbit). The other one is across a T1(1.5Mbit) line.
I noticed the following behavour:
OS: linux (redhat 6.x)
amanda: 2.4.2 and 2.4.2p1
DLT changer
lots of room on the holding disk
"Woodcock, Steve" wrote:
>
> My disk is split thusly:
>
> /dev/sda6 on / type ext2 (rw)
> none on /proc type proc (rw)
> /dev/sda1 on /boot type ext2 (rw)
> none on /dev/pts type devpts (rw,gid=5,mode=620)
>
> FilesystemSize Used Avail Use% Mounted on
> /dev/sda6
Hi,
I'm having some unusual problems using amrecover on a Redhat box. The
message I get is :
AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on
backup.poptel.org.uk ...
amrecover: Error connecting to server: Invalid argument
And in the logs :
Mar 13 13:23:55 nuthatch inetd[17275]:
Alexandre Oliva wrote:
> On Mar 12, 2001, Alexander von Homeyer
><[EMAIL PROTECTED]> wrote:
>
> > amcheck-server: could not get changer info: badly formed result from
> > changer: ""amanda.conf", line 32: configuration keyword expected"
>
> Looks like the changer program is from some older relea
>
> > amcheck-server: could not get changer info: badly formed result from
> > changer: ""amanda.conf", line 32: configuration keyword expected"
>
> Looks like the changer program is from some older release of Amanda.
Yep, we still have used the old changer script. With the new one it
works fine
My disk is split thusly:
/dev/sda6 on / type ext2 (rw)
none on /proc type proc (rw)
/dev/sda1 on /boot type ext2 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
FilesystemSize Used Avail Use% Mounted on
/dev/sda6 16G 2.9G 13G 18% /
/dev/sda1
Hi all,
Thanks for helping on 'hostname lookup failure' issue.
But now I have another trouble.
AMRECOVER Version 2.4.2. Contacting server on CNCBACK ...
amrecover: Error connecting to server: Connection refused
and it seems having response from amandaidx via tcpdump,
17:43:21.497311 lo > CN
Hi,
your tape-drive is detected as /dev/hdb during boot, but you should
use /dev/nht0 to acess it, as it is a tape and not a diskdevice...
Christoph
Alain Muls schrieb:
>
> Hello,
>
> I had a look at the amanda readme and help files but I have no idea
> about
>
> 1. how to set up my tape drive
25 matches
Mail list logo