I didn't get any responses from my posting last Thursday, so I'm guessing
I'm really up the creek on this one.
If anyone has any suggestions as to how to fix this problem, please let me
know. I've now gone 4 days without a backup, and I'm afraid I'm going to
have to delete everything and
Hi everyone,
I have some directories that contain both files and subdirectories, some of
which are larger than my tape size (DLT8000: 40Gb). For example:
# pwd
/home/bart/projXXX
# ls
total 52k
drwxrwxrwx5 bart users4.0k May 16 15:15 calmm5/
drwxrwxrwx 23 bart users
I use amanda-2.4.2p2 to backup my cluster; the server with lots of disk
space, and the slave nodes (just /etc, /var/log, /root, on these). I use
dumpcycle 2 weeks
runspercycle 10
tapecycle 22 tapes
runtapes 1
with a tapetype that has length 78000 mbytes even though it's a DLT8000,
40 Gb
I've just completed a full cycle (2 weeks) through my 22 DLT8000 (40Gb)
tapes, and most of my disklist entries have never been dumped.
I have one disklist entry that is getting a full dump every day, and I
don't
know why. It's so large that it's preventing most other things from
Hopefully someone can help me solve my problems...
I've now completed yet another tape cycle with many many FAILED disks. I
think some disks never got dumped at all. Every day in the email report I
see pages of lev 0 FAILED [dumps too big, but cannot incremental dump new
disk] and lev 1
I did solve my previous problem where one 16Gb disk was
getting a full dump every singe day, by deleting it from
my disklist. :( I never figured out why it was being dumped
every day.
Do you have record yes set in your dumptype(s)? What are
dumpcycle, tapecycle, runspercycle,
How are you doing the 2 tapes per day?
I lie to amanda, and tell here there's one tape of size
80Gb, and run amflush manually each day when I get into
the office. If I were running 1
*This* is your problem. What is your reserve set to, and how
much holding disk space do you
I'm using chg-manual, after commenting out the function request() and
un-commenting the alternate version that sends email to root once an hour.
I also changed the sleep command from 60 to 300 sec, since it takes a long
time for my DLT8000 to load a tape (back and forth, trying to sense
Can anyone help me?
I'm using the chg-manual on a DLT-8000, with runtapes=2. I've un-commented
the section in the script that sends mail once an hour, asking for the next
Amanda tape.
Right now, I started an amflush after last night's failure to find the right
tape. It rejected the first
I tried to use amrecover, and ran into lots of problems. I fixed some, but
am stuck -- amrecover says
501 No index records for host: foo.bar.com. Invalid?
I searched the email archives and the web, and the end result seems to be
that people never figured this problem out, and resorted to using
Ok, it appears lots of people successfully use amrecover with indexing, so
here's my sob story...
For the first time ever (after testing during setup, that is) I need to
recover a file from my amanda tapes (Amanda version 2.4.2p2). The same
machine holds the disks, is the amanda server, and is
[root]% amrecover
AMRECOVER Version 2.4.2p2. Contacting server on foo.bar.com ...
220 foo AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2003-01-10)
200 Working date set to 2003-01-10.
200 Config set to Daily.
501 No index records for host:
amrecover setdisk /data
501 No index records for disk: /data. Invalid?
Nope, doesn't work.
You disklist entry is exactly /data?
Well, I simplified things a bit, in addition to naming the server foo.
It's actually:
% grep data /usr/local/etc/amanda/Daily/disklist
foo
However, doing a setdisk /data/mm5_uw/calmm5 produces the
same result (appended to the debug file):
DISK /data/mm5_uw/calmm5/
501 No index records for disk: /data/mm5_uw/calmm5/. Invalid?
Bingo (maybe!).
I think you did:
amrecover setdisk /data/mm5_uw/calmm5/
and you
Hi everyone,
I just happened to notice that a selfcheck and an amandad have been running
for a long time (since 14 Mar, today is 1 Apr):
[root ~]% ps aux | grep amanda
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
amanda8858 0.0 0.0 2068 496 ?SMar14
I've been using amanda-2.4.2p2 for a long time now, without problems. In
the last week or so, my Linux (2.4.20) machine has been crashing, apparently
when amanda runs. I see in the various logs in /var/log when amanda (e.g.
xinetd in /var/log/secure with user amanda, from 127.0.0.1) and then
16 matches
Mail list logo