in my amanda.conf file I have the line:
reserve 10 # percent
which as I read the comments, means that amanda will still do full backups,
if they'll fit in the other 90% of the 80GB disk I'm using as a 'holding'
disk.
however, when the dump runs, I get the ever-popular:
lev 0 FAILED [dumps too
You've got it backwards, the 10% you reserved is used for fulls, the other
90% is used for incrementals.
hmmm, the comments read completely the opposite of that, but I'll give it a
try.
thanks much!
Carl Soderstrom.
--
Systems Administrator
Real-Time Enterprises
www.real-time.com
I don't think Amanda is telling you that the level 0 won't fit on the
holding disk. It is telling you that it won't fit on the tape.
no, in that case it usually gives the 'dumps too big for tape' error
message.
If you want to have Amanda backup more than will fit on the tape and
If you have enough holding disk, don't configure a changer and specify an
absurdly large tapetype.
tried that. 40GB should be enough to hold everything, but I'll turn
it up to 70GB (size of the holding disk).
Then Amanda will do all the backups required and
give you an EOT error in
On Fri, Oct 25, 2002 at 11:42:52AM -0700, Jerry wrote:
There is a firewall between my backup server and one
of the hosts I want backup.
the most expedient method of getting to the host in our experience, is to
set up a VPN connection from the firewall to the machine you want to back
up. that
On Fri, Oct 25, 2002 at 05:33:25PM -0700, Jerry wrote:
Actually I thought I saw a post on here before that
you can, in newer versions, backup to disk. Also, on
sourceforge there is a utility called backuppc
http://sourceforge.net/projects/backuppc/
It looks to be a disk-only solution, it
running an amanda client, v2.4.3 on RedHat 7.3, using xinetd; syslog shows
repeated and rapid segfaults from amandad when I run 'amcheck'. I get the
following entries in the amandad log:
amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket
amandad: error receiving message:
I've got an AIT-2 tape drive, which supposedly will hold 50-100GB.
the tapetype that I found, seems to say that it's 43GB:
define tapetype AIT2 {
comment AIT-2 with 230m tapes
length 43778 mbytes
filemark 3120 kbytes
speed 5371 kps
}
but what happens when the data is compressible? I'm doing
due to permission problems, we've had repeated cases of tar returning error
message '2', even tho amanda uses the --ignore-failed-read option (tar
1.3.25). as I understand it, amanda should still accept the backup data that
tar got, but it doesn't. it simply ignores the backup.
is there an
define tapetype AIT2 {
comment AIT-2 with 230m tapes
length 43778 mbytes
filemark 3120 kbytes
speed 5371 kps
}
That was on somebody's particular hardware. You may want to run tapetype
yourself, or just put length 5 mbytes and see if you hit EOT.
since the box is
Here's what I'm using with my AIT-2 drive:
define tapetype AIT-2 {
comment SDX-500C
length 46700 mbytes # This is a safer uncompressed length
filemark 1541 kbytes
speed 2920 kps# Not used with the current Amanda
lbl-templ /usr/local/pkg/amanda/example/3hole.ps
due to permission problems, we've had repeated cases of tar returning error
message '2', even tho amanda uses the --ignore-failed-read option (tar
1.3.25). as I understand it, amanda should still accept the backup data that
tar got, but it doesn't. it simply ignores the backup.
let me
I found the problem with my localhost timeouts (after setting up a test
server so I could run tests during the day).
turns out that machine is so beaten up by disk I/O that estimates take ages.
(the machine runs at a load of 2-4; estimates on a 3.2GB filesystem takes 15
minutes; and I want to
I'm trying to set up an amanda client on an AIX 4.3.3 machine. amcheck -c
doesn't complain about anything; but when backups are tried, the amanda
result mail complains about the disks possibly being offline.
the runtar debug files in /tmp/amanda have the following:
runtar: debug 1 pid 44618 ruid
Our backup server has spontaneously stopped doing backups of itself, after
working fine for several months. it backs up (most) other clients fine; but
the daily mail message says:
localhost /var/tmp lev 0 FAILED [Request to localhost timed out.]
localhost /var/lib/rpm lev 0 FAILED [Request
On Wed, Feb 13, 2002 at 01:00:33PM -0600, Carl Wilhelm Soderstrom wrote:
Our backup server has spontaneously stopped doing backups of itself, after
working fine for several months.
oh, and in case I didn't imply it; I did try amcheck, and it works fine.
Carl.
--
Network Engineer
Real-Time
Heh, Hi Carl..
Hi Mike. :) didn't know you were on this list. :)
localhost /var/tmp lev 0 FAILED [Request to localhost timed out.]
localhost /var/lib/rpm lev 0 FAILED [Request to localhost timed out.]
localhost /etc lev 0 FAILED [Request to localhost timed out.]
There
17 matches
Mail list logo
