That got brought to my attention today, but unfortunately, my tape cycle
is only eight days, so the last good backup of the file was erased
quite some time ago.
What tapes do you use?
On Wed, Nov 21, 2001 at 08:00:17PM -0500, harald wrote:
[...]
FAILED AND STRANGE DUMP DETAILS:
/-- localhost /home lev 0 FAILED [/sbin/dump returned 1]
sendbackup: start [localhost:/home level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore
Which backup program is best? dump, says some people. Elizabeth D. Zwicky
torture tested lots of backup programs. The clear choice for preserving
all your data and all the peculiarities of Unix filesystems is dump, she
stated. Elizabeth created filesystems containing a large variety of
To add a datum to the context, I have no trouble building and installing
amanda on IRIX with the MIPSpro toolchain. I have not ever had
occasion to try the gcc route. If you access to MIPSpro compilers you
might try them.
IRIX' cc wanted to have a licence password. So I installed gcc.
I just had a problem with a backup shown up by amverify - the second last
filesystem wasn't dumped correctly and the last one not at all. I'd like to
make amanda delete the records of those dumps from its database so I won't
be offered them as choices if ever I need to restore a file from
I am needing to make use of last access time for some of the files on
our system. Currently, Amanda/GNU Tar is modifying it. According to
tar's man page, there is a --atime-preserve switch that will stop tar
from modifying the access time.
How would I make Amanda pass this switch to GNU
Chris Stone wrote:
Hi,
I'm having trouble building the amanda client on an sgi.
--snip
gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src-g -O2 -c
`test -f sendbackup.c || echo './'`sendbackup.c
source='sendbackup-dump.c' object='sendbackup-dump.o' libtool=no \
So if I want to persuade amanda to use more tape I should shorten the dump
cycle, correct ? But I have a DDS-3 with native capacity of 12 GB and no
changer. What happens if in a dump cycle there's more to be backed up than
can fit on the tape e.g. if a lot happens to change on a couple of
reference the files as:
/.backup/whatever/.
The trailing /. will force the symlink to get dereferenced.
Didn't you mean ./backup/whatever/.?
I run amanda-2.4.2p1-2. Supose an intruder break somehow the system and
perform a rm -rf /. From this point, after a fresh reinstall of the
system, how I can restore from tape, if no backup database is not
availale anymore?
I use rsync via ssh after the backup jobs to copy Amanda's index to
But it was a hard fight to convince them to do backups parallel
to their raid-5 array.
Their argument: why backup, we have raid
rm -rf /
I am interested in AIT libraries in the 15-16 tape size range. Solid
compatibility with amanda is a must. We are looking to spend obviously
as little as possible to get a quality product, but $10k is a very firm
ceiling and the closer to $5k we can hold the price, the more likely it
is to
What's the story here, how can student be at 0% since 5.43am when it is now
10am? Has this backup failed? Also if I've got 'holdingdisk no' in the dumptype
for every backup I'm doing so why does the report say the dump is done but
waiting to write to tape? How can it be waiting to write to
Many commercial backup programs have the ability to browse the database for
files matching some wildcard spec. and offer a list of files matching the
spec. and then allow you to pick one or more of these files to be restored.
Has anyone hacked together something like that for amanda ? Even
amoverview parses the output of amadmin find and doesn't handle the found
Amanda directory lines. The fix is so trivial that I'm just mentioning it
inline here because that's actually smaller than the patch :-) After
Thanks for the fix.
Hi,
when trying to build Amanda 2.4.2p2 CVS of 20011020 on a Linux box (SuSE
Linux 8.0), configure fails:
checking for xfsdump... /sbin/xfsdump
checking for xfsrestore... /sbin/xfsrestore
./configure: line 5093: syntax error near unexpected token
`m4_default(['
./configure: line 5093: `{
I looked at message 34157 from the archive where John points Someone to
alpha.gnu.org for gnutar 1.13.19 but I can't find alpha.gnu.org or www.alpha.gnu.org
or ftp.alpha.gnu.org. So where can I get this software at this version or later.
ftp://alpha.gnu.org/gnu/tar/
Even when 2.4.3 proper comes out, there's really no compelling reason to
upgrade *unless* you need any of the new features. If it ain't broke...
If it's not broken, it hasn't got enough features yet. ;-)
Sorry if this subject is off topic but can you use a 40/80 DLT tape
in a 35/70 DLT tape drive. Although we'd only be using it as a 35/70
tape.
no problem to write on DLT IV tapes with a DLT 7000 drive
just for the record: Amanda 2.4.2p2 builds and installs happily on HP-UX
9.01 on an HP9000/710 using HP's CC.
(We'll see tonight if it backups, too.)
Just retested last night, thought it might be useful for someone else.
Kind of a bummer, a 20/40GB drive only able to write out 16.2GB... maybe
I have something misconfigured?
You used hardware compression blowing up the random data tapetype
writes.
I am attempting to make amanda 2.4.2p2 on a NetBSD 1.5_ALPHA system
The make dies with the following message:
cat amcheckdb.sh amcheckdb
chmod a+x amcheckdb
cat amcleanup.sh amcleanup
chmod a+x amcleanup
cat amdump.sh amdump
chmod a+x amdump
make: don't know how to make amoverview.
No, if your database is gone, you are completely lost There is no
way to recover any data except using a very special method called
RTFM
*LOL*
cairostel c0t1d0s0 lev 1 FAILED [input: Can't read data: : Input/output error]
error on my night ly backup This left the dump on the drive and when i
try to do Amflush this is what i get in the e-mail;
FAILURE AND STRANGE DUMP SUMMARY:
cairostel c0t1d0s0 lev 1 FAILED [input: Can't read
I need the configuration the Tape HP Sure Store DLT 80 for the file
amandaconf
If somebody has this information, I would be very thankful
length 8 mbytes
filemark 10 kbytes
kuller# amadmin WEEKLY find heerold.raad.tartu.ee /\$
Warning: no log files found for tape WEEKLY02 written 2002-02-15
Warning: no log files found for tape WEEKLY05 written 2002-02-08
Warning: no log files found for tape WEEKLY04 written 2002-02-01
Warning: no log files found for tape
Is there a complete list of the ports that amanda will use during the
data transfer? I though I had them all (the client could talk to the
server) as amcheck didn't report any errors. However, I remove all
packet filtering and things start working smoothly...
see JRJ attached
From - Sat Jan
I tried to find out who or what moves older logfiles from log
directory to oldlog directory, but this far I haven't succeeded. I
suspect that since I have two different backup configurations
running with same log directory, the DAILY backup process decides
that previous weeks' WEEKLY backups
Waitaminit... this I didn't know. Amanda can't run dumps across tapes? Why
is the runtapes entry even used at all?
Amanda 2.4.2p2 can't spread a single dump image over several tapes.
For a whole backup run it can use as many tapes as you like.
define tapetype DLTtapeIV {
comment DLTtape IV - 40 GB
length 33706 mbytes
filemark 43 kbytes
speed 1820 kps
}
That's the typical result writing random data and using hardware
compression on a 40 GB tape.
If you'd like Amanda to keep 70 GB per tape in mind during the
solution to this? I sure hope 'amrecover' doesn't require me to load the
tape manually.
It does. You have to insert the tape as directed.
I can see no problems with DAILY backups, but for some reason
amrecover doesn't see older WEEKLY backups.
Did you enable indexing? Check for dirs/files in ~amanda/WEEKLY/index.
One of my users changed the name of one of his directory one day
,and few days and few backups later, he deleted some files that it
would like to recover.
But amanda didn't save them again... why ???
I still had an older backup where the data are saved, but I'm wondering
why amanda did'nt
I can see no problems with DAILY backups, but for some reason
amrecover doesn't see older WEEKLY backups.
[...]
-rw--- 1 amanda wheel 25574 Jan 18 22:07 20020118_0.gz
-rw--- 1 amanda wheel 25737 Jan 25 22:07 20020125_0.gz
-rw--- 1 amanda wheel 25752 Feb 2 14:07
I can see no problems with DAILY backups, but for some reason
amrecover doesn't see older WEEKLY backups.
[...]
-rw--- 1 amanda wheel 25574 Jan 18 22:07 20020118_0.gz
-rw--- 1 amanda wheel 25737 Jan 25 22:07 20020125_0.gz
-rw--- 1 amanda wheel 25752 Feb 2 14:07
It seems that for some reason amrecover thinks that all these
backups were done to tape WEEKLY03, although they most definitely
were not. Whatever it is, it explains why amrecover doesn't show
older backups. It thinks they have been overwritten.
Now I have to figure out *why* amanda thinks
I am running amanda on solaris 2.6 and the tape drive died. Is there a way to
restore files from the dump disk?
amrecover
Windows, which I don't want to install on this computer. Is there someway
to have amplot create this image without having X Windows installed?
Any device Ghostview runs on is capable of showing amplot's output.
ERROR [access as amanda not allowed from [EMAIL PROTECTED]]
amandahostsauth failed
I've cheched as far as I can but no clues, what's going wrong?
The file /home/amanda/.amandahosts is:
+ bck.mydomain.com amanda
+ bck
Hi! Is there any canonical way to test a tape drive? I just configured a
new system, and want to make sure that the tape drives are being recognized
correctly.
Just dump or tar several GB to it and read in again or compare it.
Amanda user = amanda
Amanda group = backup
[...]
ERROR: /dev/nst0: Permission denied
(expecting a new tape)
chown amanda:backup /dev/nst0
We wish you all a
Merry Christmas
and a happy
New Year
Aykut Çakýl (Incoming Dept. Manager)
ACTIVE TRAVEL AGENCY
Lufthansa City Center
Istanbul - Turkey
Phone: + 90 - 216 - 349 55 90
Fax: + 90 - 216 - 349 55 94
Email: [EMAIL PROTECTED]
Web: www.activeturkey.com
Is
Rebecca Pakish wrote:
I am wondering the same thing...I only received it from the list, but
anything with a Christmas subject in February pricks my sys admin ears. I
can't find anything from my usual virus sources...if anyone knows anything I
would appreciate the info.
A lot of mails seem
John, have I lost your attention with this, are you too busy?
Any point in trying to use 4k (I assume hardware) blocksize? My
experience has shown DDS drives are best driven at hardware blocksize of
0 (variable) and Amanda writing with 32k blocks.
well I had it at 0 initially, and struggled with failures reading back
from the tape constantly. I changed it to 4096 and it seems to be a
little more reliable. BUT, I still get errors. just less. I happy to use
any block size that will work. why would I get more errors with DDS4
tapes
I realize that I wouldn't be able to interactively use amrecover,
but would a manual fsf and tar -x of a level 0 return a full backup
of the directory, or is it all so much wasted tape? In other words,
do corrupted indexes mean corrupted data or just partial incrementals?
Just the
Before I put this in, is there any particular reason you're adding
DMP_WARNING? Why not just add these entries as DMP_NORMAL?
First reason (beauty): I decided to put the warnings into a different
group than the normal output, just to be ready for further additions of
warnings of other dump
John R. Jackson wrote:
I'm trying to compile amanda 2.4.2p2 in a 4.3.3 aix system.
i installed gtar,gawk, gsed, perl and readline.
When you say you installed these packages, did you build them from source
or did you find binaries someplace?
i run the configure script, but when i do
I read Amanda doc and I read about backup but it doesn't fit with my understanding.
I can see dumping (ufsdump on Solaris) a whole filesystem and
restoring itthough how you get an individual file out of it, is another thing.
I can see taring a filesystem so that you can give the idiot
You do get into issues where there is more than the file system involved.
In AIX, that would be the dreaded ODM :-). Even in Solaris, you would
need to run installboot to write the boot sector. I don't know enough
about Linux, but I wouldn't be surprised to find out there's more than
just
Hi,
here's a patch for Amanda 2.4.2p2 to ignore xfsdump's occasionally
output on busy filesystems WARNING: failed to get bulkstat information
for inode ... and WARNING: failed to get valid bulkstat information
for inode
--- amanda-2.4.2p2-20011020.orig/client-src/sendbackup-dump.c Sat
On Friday, amdump wrote my dump images to a tape successfully, but a
subsequent amverify showed that the tape is defective. Now, my dumps have
been removed from the holding disk, but I don't think the images on the
tape are usable.
Is there any way to re-do this backup onto a good tape or
The index is stored under /var/amanda... and the index stores all
places where to find backups on the different tapes - so far am I right?
Now, the server dies and all disks go south, so /var/amanda --- the
index must be gone - so far am I right ?
I use rsync to mirror
Paul Lussier wrote:
In a message dated: Mon, 26 Nov 2001 22:58:35 +0100
Bernhard R. Erdmann said:
Doublecheck /etc/fstab for this entry. Dump gets the corresponding block
device to the filesystem in the disklist by looking at /etc/fstab.
Hmmm, does that mean that if there's
That got brought to my attention today, but unfortunately, my tape cycle
is only eight days, so the last good backup of the file was erased
quite some time ago.
What tapes do you use?
Greg Troxel wrote:
[EMAIL PROTECTED]:
That got brought to my attention today, but unfortunately, my tape cycle
is only eight days, so the last good backup of the file was erased
quite some time ago.
I've seen others near me have this sort of problem, and I've only
narrowly
I have a Sony SDX-500C and tapetype reported the following:
define tapetype SDX-500C {
comment just produced by tapetype program
length 21709 mbytes
filemark 773 kbytes
speed 3660 kbytes
}
From the above output tapetype believes that this tape will only hold 21
Gigs.
I've got amanda serwer 2.4.2p2 on freebsd 4.4rc5 and amanda client
on linux RH7.0 and freebsd 3.4 release.
There isn't a lot of data to backup, only 2 GB from every host.
Backup is done every night, starting from cron.
Streamer is 40/80GB Tandberg DLT1, I've only one tape.
Go buy some more
I am having a problem backing up one of my UNIX boxes with Amanda. When I
run AmCheck I get the error:
WARNING: bill: selfcheck request timed out. Host down?
Client check: 7 hosts checked in 29.678 seconds, 1 problem found.
As you can see the check runs successfully on 6 hosts but
please post your exclude list
/usr/local/lib/gnutar_exclude_list itself
---
./net
./dev/gpmctl
./dev/log
./home/oracle/9.01/software/app/oracle/oradata/debian/control02.ctl
Mitch Collinsworth wrote:
[...]
We don't need to do backups. We have RAID. :-;
Yeah, we've RAID - guess how many people have been bitten by RAID and
having no backup... ;-)
Stan Brown wrote:
I'm in the process of moving my Amanda server from a HP-UX machine to a
Linux one. The new machines name is debian.
I'm having problems with the tar exclude feature on the new tapejost
itself. Heres the info
please post your exclude list
FAILURE AND STRANGE DUMP
/-- fs.rocnet. /dev/sda6 lev 0 FAILED [data timeout]
sendbackup: start [fs.rocnet.de:/dev/sda6 level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 0 dump: Mon Oct 22 23:02:49 2001
| DUMP: Date of
dump is waiting for I/O - in my opinion it's a dump issue, not an amanda
issue. Try to run dump several times by hand, e.g. dump 0af /dev/null
/dev/md2.
The results are:
root 11659 11177 0 16:56 pts/200:00:00 dump 0af /dev/null /dev/md2
So I have yet another hung process I
driver: fs.rocnet.de /dev/sda6 0 [dump to tape failed, will try
again]
BRE I assume this is Linux' dump. What version are you using? Why don't
you
BRE use a holding disk instead of writing directly to tape?
do you think thats why i'm using no holding disk. i will try it. but i
don't
I just moved my tape drive from one machine to another and I upgraded
from 2.4.1p2 to 2.4.2p2 at the same time. I moved my configuration
files over and all of the logs and curinfo files and the indexes
(indices?).
When I look at my holding disk, ./bkup, I see:
truk!backup 110# ls -l
2) Which timeout value can I adjust in amanda.conf to avoid the data
timeout error?
amanda.conf, dtimeout
ERROR: heerold.raad.tartu.ee: [DUMP program not available]
ERROR: heerold.raad.tartu.ee: [RESTORE program not available]
After installing dump and restore (doh), the error messages were
still there. So I repeated the ./configure, make and make install
steps, but I still get the same error
I'm running amanda 2.4.2p2 on a FreeBSD 4.4 machine as a client.
The server is a RH Linux 7.1. I cannot get the server to start the
amandad service on the FreeBSD machine. The FreeBSD machine does not
have a firewall compiled with the kernel. There is no firewall between
the server
[...]
Twice, dump was started, and the amanda processes were left running
on the machine. dump is in an unkillable state:
14280 amanda 9 0 616 616 488 D 0.0 0.0 0:00 dump
12581 amanda 9 0 616 616 488 D 0.0 0.0 0:00 dump
Hints on how I might kill these
i have a lot of problems with data timeout while backing up my local
partitions. the installation is very simple. i only backup my local
machine. there are a few small partitions. sometimes it work, sometimes
not. i use redhat 7.0 and the amanda 2.4.2p2 and checked the dtimeout
parameter. i
I have full backups of a Linux machine on tape done with Amanda
over the network. Now I would like to basically wipe the entire
machine and restore entire system from backups which are on
another machine. Amanda is configured to use 'dump'.
you can't wipe your running system and restore it
Unfortunately I've run into the other problem, inetd reporting
a loop problem when I installed 2.4.2p2 (upgrade from 2.4.1p1)
on a Solaris 2.6 client of the same server. Changing the inetd
-r parameter did not resolve that issue for me so if anyone would
has any ideas...
Could you please
I've run the amandad on the command line and from the errors I'm
seeing believe the current problem stems from running a client
built under 2.8 on a 2.6 system.
I'm no Solaris expert but my feeling is this _will_ cause problems.
[...]
Don't have a functioning gcc under any of my 2.6 system,
Bernhard R. Erdmann wrote:
Hi,
every night Amanda emails me these warnings from xfsdump. This seems to
be perfectly normal for more or less active filesystems.
Where can we tell Amanda to ignore these warnings?
FAILED AND STRANGE DUMP DETAILS:
/-- ente /var lev 2 STRANGE
Original Message
Subject: TAKE 820267 - enable xfsrestore to run on non-xfs filesystem
Date: Thu, 18 Oct 2001 13:59:49 +1000 (EST)
From: Ivan Rayner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
This removes the restriction that xfsrestore -t must be run on an xfs
filesystem (which
On Thu, Oct 18, 2001 at 12:05:46PM +0200, Jens Rohde wrote:
Hi
I'm stuck! - I've tried to get amrecover to work. There's no problem in
selecting host, disk and files to recover, but when I try to do the actual
recover I get the following error:
amrecover extract
Extracting files using
I've been waiting to reach the 135th tape. For weeks and weeks now, I see
The next 6 tapes Amanda expects to used are: a new tape, a new tape, a new
tape, a new tape, a new tape, a new tape. I've been waiting for it to say
it expects tape #1 again.
Today was suppose to be the big day.
Kit wrote:
I got an error on Amanda Backup Client Hosts Check. Where can I find
amandahostsauth?
# su amanda -c amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /dumps/amanda: 875906 KB disk space available, that's
plenty
NOTE: skipping
After I created the .amandahosts under user amanda's home directory as
you mentioned, the problem is persisted.
Is this file accessible for the amanda user? Is it's access time (ls
-lu) updated each time you run amcheck?
When there's no more blank tape available, amanda just quits and reports the
running or not-yet-run file systems as FAILED. Is there a way to have amanda
keep dumping those running or not-yet-run file systems to the holding disk?
That way I won't miss backing up thoese file systems.
[root@garfield amanda]# cat amrecover.20011010121258.debug
amrecover: debug 1 pid 2022 ruid 0 euid 0 start time Wed Oct 10
12:12:58 2001
amrecover: stream_client: connect(10082) failed: Connection
refused
cannot connect to garfield: Connection refused
amrecover: pid
- Did you set index yes in amanda.conf?
Yes. I set it in the global section:
Please browse through the index directories (~amanda/config/index).
There should be directories for each host backed up and thereunder
directories for each filesystem (/ replaced by _) and therein gzipped
files
1) i ran amrecover (as root) from the host where i lost my data
2) amanda ran through 1 of 3 tapes without error (the tape that had the
level 0 from 10/08)
what a bad hit rate...
3) when amanda switched to the first of 2 tapes with level 1's on it, i got
an error:
EOF, check
What has changed now with the patch is the /tmp/amanda/sendsize.debug
output. I'm sure I found the / and home stuff in sendsize.debug before
(even when they were not backed up), but now they are no longer present.
That's really strange: why should Amanda estimate / and /home if they
aren't
Changing wait=no fixed my problem, but I don't understand why. It worked
before with wait=yes until I switched out my name servers. I am happy for
now, but would like to understand...
from man inetd:
The wait/nowait entry is applicable to datagram sockets only (other
sock-
ets should have a
IIRC, a SIGHUP isn't enough to restart xinetd. You actually have to do
'/etc/init.d/xinetd restart'. Yes, it's annoying.
xinetd wants SIGUSR1 to reread the configuration files
I've got my chunksize set to 2Gb as it is, right now. I'm using linux with
a 2.2.14-5 kernel. Would it cause problems if the chunksize was right at 2Gb?
Perhaps I should lower it.
Oh yes, put it something below 2GB-32KB: a good value is 2000 MB
I have read extensively and have failed to find a solution to my
problem. I am hoping someone will know what I have done wrong. I
can't
seem to get amrecover to work for me.
Check using netstat if the following port are bound:
$ netstat -an|grep :1008.
tcp0 0 0.0.0.0:10082
I am trying to get the indexing working with amanda and I cannot
figure out to verify if I have it right yet.
Did you set index yes in amanda.conf?
Any idea what I am doing wrong? Like Preston says in his book, nobody
cares about backups, only restores!
Yeah, restoring rules!
We have a Quantum 4700 with a DLT 4000 in it. We are using DLT IV
tapes (20-40 gb).
The actual partition is not quite 19 gb in size. Software compression
is turned on. I would expect this partition to fit on one tape.
Are my expectations incorrect? Could I have something configured
Do a netstat -an | grep 10080 on the client, this will tell you if inetd
is at least listening on 10080. You cannot telnet to 10080 because the
protocol for amamda is udp, telnet requires tcp, so this is not a valid test
of functionality.
That's what netcat is good for:
$ nc -u ente 10080
i would like to extend my amanda backup capabitities to one of my DEC v5.1
boxes. the problem is it's running advfs. I've downloaded the patch and
tried to install it unsuccessfully for about a week now. however, i've
never used `patch` and i'm running into a wall on this one.
could
I'm running into trouble when trying to get Amanda binaries statically
linked. I'm trying to compile a set of statically linked linux binaries
that I can place on an NFS mount where linux systems will run them
without fighting over libc revisions, etc. When I run ./configure with
the
I am trying to compile Amanda (2.4.2.p2) on an AIX 4.3.3 box to be used as a
client only (I used the --without-server configure option). It dies during
the compile with this message:
[...]
getfsent.c: In function `open_fstab':
getfsent.c:154: `MNTTAB' undeclared (first use in this function)
Can amanda be configured to limit the incremental level?
I almost always have a few level 2's and often a level 3.
I'd like to never see anything higher than level 1. Why?
Restoring is simpler.
man amanda:
bumpsize int
Default: 10 Mbytes. The minimum savings
Being able to restore using 'standard' UNIX utilities is important to
my overall backup strategy so can I use tar to restore from a tape
made with amanda? If not, will dump work better? I'm not prejudiced
either way.
Use dd to grab the images off the tape, see
I just spent the whole day upgrading/hacking Cyrus for inserting proper
Return-Path:-headers just to make Sieve's reject work...
Part of my ~/.sieve now contains
elsif allof (address :contains to
[[EMAIL PROTECTED],[EMAIL PROTECTED]], header :is
subject unsubscribe) {
reject please
I am trying to test amrecover. when I run amrecover daily, I get the
following error.
AMRECOVER Version 2.4.2p2. Contacting server on mail.daml.org ...
amrecover: Unexpected server end of file
Do you really have a config named daily?
I am having difficulties in running amanda. I am unable to get a backup (but
once was) and I think it was after updating some RPM on my system. It takes
30 minutes to fail and the only info I can find in in the amandad.debug file
on the client. I get 4 lines of
amandad: waiting for ack:
1 - 100 of 185 matches
Mail list logo
