Re: amanda-users list problem
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?
Re: Saeagate IDE Streamer won't work.
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 -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? You can't update the dumpdates file when dumping a subdirectory sendbackup: error [/sbin/dump returned 1] \ Don't use dump if /home is not a filesystem. Use tar instead.
Re: Linux DUMP
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 unusual conditions (and some not so unusual ones) and tested each program by do a backup and restore of that filesystems. The peculiarities included: files with holes, files with holes and a block of nulls, files with funny characters in their names, unreadable and unwriteable files, devices, files that change size during the backup, files that are created/deleted during the backup and more. She presented the results at LISA V in Oct. 1991. This article is archived here: http://berdmann.dyndns.org/doc/dump/zwicky/testdump.doc.html
Re: making 2.4.3p3 on octane running 6.5.12
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.
Re: Deleting a backup from Amanda's database
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 them. Is there any way of doing that ? I know I can remove a tape altogether (and hence all of its backups) with amrmtape, and amadmin delete wil remove all records of a particular disk from the database, but I can't see any way to remove the record of one disk's backup on one day. Is it possible ? Force a full dump using amadmin config force host.
Re: GNU tar's --atime-preserve switch
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 Tar and what consequences, if any, would doing this have on recovery? Using --atime-preserve alters the ctime, which may be not an option for you.
Re: making 2.4.3p3 on octane running 6.5.12
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 \ depfile='.deps/sendbackup-dump.Po' tmpdepfile='.deps/sendbackup- dump.TPo' \ depmode=gcc /sbin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src-g -O2 -c `test -f sendbackup-dump.c || echo './'`sendbackup-dump.c sendbackup-dump.c: In function `start_backup': sendbackup-dump.c:218: `no_record' undeclared (first use in this function) sendbackup-dump.c:218: (Each undeclared identifier is reported only once sendbackup-dump.c:218: for each function it appears in.) gmake[1]: *** [sendbackup-dump.o] Error 1 gmake[1]: Leaving directory `/usr/local/src/amanda-2.4.3b3/client-src' gmake: *** [all-recursive] Error 1 --end snip I get the same error on a SGI Indigo2 running IRIX 6.5.15 and using gcc 3.0.4 and gmake 3.79.1 from freeware.sgi.com: ld32: WARNING 84 : /usr/lib32/libsun.a is not used for resolving any symbol. ld32: WARNING 84 : /usr/lib32/libm.so is not used for resolving any symbol. ld32: WARNING 84 : /usr/lib32/libtermcap.so is not used for resolving any symbol. ld32: WARNING 84 : /usr/lib32/libsocket.so is not used for resolving any symbol.source='sendbackup.c' object='sendbackup.o' libtool=no \ depfile='.deps/sendbackup.Po' tmpdepfile='.deps/sendbackup.TPo' \ depmode=gcc3 /sbin/sh ../config/depcomp \ 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 \ depfile='.deps/sendbackup-dump.Po' tmpdepfile='.deps/sendbackup-dump.TPo' \ depmode=gcc3 /sbin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src-g -O2 -c `test -f sendbackup-dump.c || echo './'`sendbackup-dump.c sendbackup-dump.c: In function `start_backup': sendbackup-dump.c:218: `no_record' undeclared (first use in this function) sendbackup-dump.c:218: (Each undeclared identifier is reported only once sendbackup-dump.c:218: for each function it appears in.) gmake[1]: *** [sendbackup-dump.o] Error 1 gmake[1]: Leaving directory `/.amd/ente/home/be/src/amanda-2.4.3b3/client-src' gmake: *** [all-recursive] Error 1 configure was: ./configure --with-user=amanda --with-group=sys
Re: Amanda dump level policy
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 filesystems and level 1s get large ? What falls off the edge of the world ? It depends on your value of tapesize and the size of your holding disk. If the backup volume is larger than a single tape, but below holding disk size, the rest will stay on disk waiting to be amflushed. If space is really a shortage, Amanda will decide to leave off subsequent full dumps to do some more incrementals. These are prioritized according to your disklist entries and their configured priority.
Re: Following symlinks
reference the files as: /.backup/whatever/. The trailing /. will force the symlink to get dereferenced. Didn't you mean ./backup/whatever/.?
Re: Question in case of disaster
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 another box.
Re: amanda - my way ?
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 /
Re: AIT libraries
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 get funded. Rackmount is a must, though I'm not so concerned with how many RUs it takes up. So far the only products I am really familiar with are the Sony LIB-152 LIB-162 series. I understand that Overland Data and several other companies are also making AIT libraries. I'd be interested to hear about those. Pros/Cons of them versus the Sony ones, etc. Once upon a time I ran an Overland Library with 19 AIT-2 tapes and a Sony SDX-500C internally just fine with Amanda.
Re: SOS HELP
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 tape if the dump is done when I'm not using a holdingdisk? Probably your backup program (dump/tar) got confused by student's filesystem.
Re: Searching for backed up files.
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 being able to get a list of matching files would be useful to enable you to look in the right place with amrecover. Use (z)grep for the index subdirectory.
Re: Small bug in amoverview
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.
./configure error, Amanda 2.4.2p2 CVS of 20011020
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: `{ echo $as_me:5093: WARNING: *** to
disable it, just #undef XFSDUMP in config/config.h
m4_default([AS_MESSAGE_LOG_FD], [AS_MESSAGE_FD])'
Building starts with
+ cd /usr/src/packages/BUILD
+ cd amanda-2.4.2p2-20011020
+ ./autogen
configure.in: 8: required file `config/config.h.in' not found
configure.in:25: warning: AC_ARG_PROGRAM invoked multiple times
configure.in:1544: warning: AC_PROG_LEX invoked multiple times
+ ./configure --prefix=/usr --sysconfdir=/var/lib
--libdir=/usr/lib/amanda --localstatedir=/var/lib
--libexecdir=/usr/libexec/amanda --with-index-server=amandahost
--with-portrange=15000,15029 --with-tape-device=/dev/nst0
--with-user=amanda --with-group=disk --with-dump-honor-nodump
--with-gnu-ld --enable-shared
autoconf (GNU Autoconf) 2.52
automake (GNU automake) 1.4-p5
Re: Where do I get Gnutar 1.13.19
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/
Re: Should I upgrade to 2.4.3b3?
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. ;-)
Re: DLT
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
success: Amanda 2.4.2p2 on HP-UX 9.01
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.)
Re: Tapetype: STD2401LW
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.
Re: Build dies trying to make amoverview
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. Stop *** Error code 1 Use GNU make (gmake)
Re: restore without database files
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*
Re: Hey Everyone.. I got a little problem.
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 data: : Input/output error] Can you use your tape drive with tar/ufsdump? Does it work?
Re: Tape HP Sure Store DLT 80
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
Re: Problem restoring old backups
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 WEEKLY01 written 2001-10-19
Scanning /holding...
date host disk lv tape or file file status
2002-02-22 heerold.raad.tartu.ee / 0 WEEKLY03 5 OK
Are 'log files' something different from index files?
Hm, somehow your logfiles got lost. The index does not contain the tape
label or the file position on tape. This is in the log files. The index
describes the dump side of your backup and the log describes the tape
side of it.
The log directory should look similar to this one (Amanda 2.4.2p2):
[amanda@ente amanda]$ ls be/log
amdump.1 amdump.28 amflush.17 amflush.6 log.20020215.1
amdump.10 amdump.29 amflush.18 amflush.7 log.20020216.0
amdump.11 amdump.3amflush.19 amflush.8 log.20020216.1
amdump.12 amdump.30 amflush.2 amflush.9 log.20020217.0
amdump.13 amdump.31 amflush.20 log.20020208.0 log.20020217.1
amdump.14 amdump.32 amflush.21 log.20020208.1 log.20020218.0
amdump.15 amdump.4amflush.22 log.20020209.0 log.20020218.1
amdump.16 amdump.5amflush.23 log.20020210.0 log.20020219.0
amdump.17 amdump.6amflush.24 log.20020210.1 log.20020220.0
amdump.18 amdump.7amflush.25 log.20020211.0 log.20020221.0
amdump.19 amdump.8amflush.26 log.20020211.1 log.20020222.0
amdump.2 amdump.9amflush.27 log.20020212.0 log.20020223.0
amdump.20 amflush.1 amflush.28 log.20020212.1 log.20020224.0
amdump.21 amflush.10 amflush.29 log.20020212.2 log.20020225.0
amdump.22 amflush.11 amflush.3 log.20020213.0 log.20020225.1
amdump.23 amflush.12 amflush.30 log.20020213.1 log.20020225.2
amdump.24 amflush.13 amflush.31 log.20020213.2 log.20020226.0
amdump.25 amflush.14 amflush.32 log.20020213.3 log.20020226.1
amdump.26 amflush.15 amflush.4 log.20020214.0 log.20020226.2
amdump.27 amflush.16 amflush.5 log.20020215.0 oldlog
[amanda@ente amanda]$ cat be/log/log.20020226.0
START planner date 20020226
START driver date 20020226
ERROR taper no-tape [cannot overwrite active tape BE28]
INFO planner Full dump of james:/ promoted from 6 days ahead.
INFO planner Full dump of ente:/var/spool/exim promoted from 6 days
ahead.
INFO planner Full dump of james:/boot promoted from 6 days ahead.
INFO planner Full dump of ente:/opt promoted from 6 days ahead.
INFO planner Full dump of ente:/ promoted from 7 days ahead.
FINISH planner date 20020226
STATS driver startup time 640.894
SUCCESS dumper apollo /vmware 20020226 1 [sec 0.352 kb 32 kps 90.7
orig-kb 21]
SUCCESS dumper angelique /var 20020226 1 [sec 2.685 kb 3808 kps 1418.2
orig-kb 3795]
SUCCESS dumper james /usr 20020226 1 [sec 24.385 kb 8512 kps 349.1
orig-kb 8490]SUCCESS dumper james /boot 20020226 0 [sec 13.574 kb 5632
kps 414.9 orig-kb 5600]
[...]
[amanda@ente amanda]$ cat be/log/log.20020226.1
START amflush date 20020226
START taper datestamp 20020226 label BE00 tape 0
SUCCESS taper apollo /vmware 20020226 1 [sec 1.953 kb 64 kps 32.8 {wr:
writers 2 rdwait 0.000 wrwait 0.008 filemark 1.944}]
SUCCESS taper angelique /var 20020226 1 [sec 4.686 kb 3840 kps 819.4
{wr: writers 120 rdwait 0.000 wrwait 3.024 filemark 1.639}]
SUCCESS taper james /usr 20020226 1 [sec 12.721 kb 8544 kps 671.6 {wr:
writers 267 rdwait 0.000 wrwait 10.923 filemark 1.721}]
SUCCESS taper james /boot 20020226 0 [sec 11.180 kb 5664 kps 506.6 {wr:
writers 177 rdwait 0.000 wrwait 9.433 filemark 1.686}]
SUCCESS taper ente /export/ftp.redhat.com 20020226 1 [sec 5.482 kb 1760
kps 321.0 {wr: writers 55 rdwait 0.000 wrwait 3.434 filemark 2.046}]
[...]
Re: RESOLVED: Re: Strange failure to connect to client
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 26 00:52:51 2002 Return-Path: cyrus@ente X-Sieve: cmu-sieve 2.0 Return-path: [EMAIL PROTECTED] Envelope-to: [EMAIL PROTECTED] Delivery-date: Sat, 23 Jun 2001 04:57:31 +0200 Received: from ente.berdmann.de ([192.168.1.6] helo=localhost) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Ddc2-0006ur-00 for [EMAIL PROTECTED]; Sat, 23 Jun 2001 04:57:30 +0200 X-Flags: Delivered-To: GMX delivery to [EMAIL PROTECTED] Received: from pop.gmx.net [194.221.183.20] by localhost with POP3 (fetchmail-5.5.0) for [EMAIL PROTECTED] (single-drop); Sat, 23 Jun 2001 04:57:30 +0200 (CEST) Received: (qmail 15453 invoked by uid 0); 23 Jun 2001 02:53:52 - Received: from surly.omniscient.com (64.134.101.69) by mx0.gmx.net (mx13) with SMTP; 23 Jun 2001 02:53:52 - Received: (from root@localhost) by surly.omniscient.com (8.11.1/8.11.1) id f5N0bkX199799 for amanda.org.amanda-hackers-list; Sat, 23 Jun 2001 00:37:46 GMT Received: from gandalf.cc.purdue.edu ([EMAIL PROTECTED] [128.210.135.25]) by surly.omniscient.com (8.11.1/8.11.1) with ESMTP id f5N0bgX207608 for [EMAIL PROTECTED]; Fri, 22 Jun 2001 20:37:42 -0400 (EDT) Received: from gandalf.cc.purdue.edu (jrj@localhost [127.0.0.1]) by gandalf.cc.purdue.edu (8.9.1/8.9.1) with ESMTP id TAA26259 for [EMAIL PROTECTED]; Fri, 22 Jun 2001 19:37:40 -0500 (EST) Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Use of UDP/TCP ports in Amanda document, and amrecover bug Reply-to: [EMAIL PROTECTED] Date: Fri, 22 Jun 2001 19:37:40 -0500 From: John R. Jackson [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Precedence: bulk This is yet another of my really long letters. Sorry. I applied a change to amrecover.c a while back to use stream_client() instead of the by hand socket setup that was there. This stopped binding the socket to a particular interface which was causing trouble on some systems. Unfortunately, I didn't fully comprehend the interaction between a user port range (e.g. --with-portrange), stream_client() and amrecover. Now, if amrecover is built with --with-portrange, which must be non-privileged (= 1024) for other parts of Amanda to work, it will fail because amrecover requires a privileged port (to prove to the other side it is who it says it is). Before going into potential solutions, a little more background. If this bores you silly, skip to Solutions below. I'm only spelling it out in detail because I'll probably put this in the docs directory (once you nice folks edit it :-) since the issue comes up fairly often. The key questions for the amrecover problem are: * When dumper and taper set up their localhost TCP connection for direct to tape, does the port matter? If NAT, for instance, is also on the machine, will it scramble things? * When not being used for security (non-privileged), does the source port of an incoming TCP connection matter? Amanda doesn't care. Would a firewall or NAT in between cause problems? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] = How Amanda uses UDP and TCP ports = Amanda uses both UDP and TCP ports during its operation. The amandad service is listening (via inetd/xinetd) at a well known (fixed) port on each client for UDP connections. The amindexd and amidxtaped services are listening (also via inetd/xinetd) at well known ports on the tape server for TCP connections. When a process on the tape server wants to talk to a client amandad, it creates a UDP socket and binds it to a port on its side, then sends the packet to the well known amandad service port on the client. Because security information is being passed, the port bound on the connecting side must be privileged ( 1024). This proves to amandad whoever is connecting is running as root, and therefor is trustworthy (there are all sorts of issues with this trust that are beyond the scope of this document). A similar sequence of events happens when amrecover on a client wants to contact amindexd or amidxtaped on the tape server. The port that amrecover binds to its TCP socket must be privileged, which is one of the reasons it must be run as root. Amanda also uses TCP connections for transmitting the backup image, messages and (optionally) the index list from a client back to the dumper process on the tape server. A process called sendbackup is started by amandad on the client. It creates two (or three, if indexing is enabled) TCP sockets and sends their port numbers back to dumper in a UDP message. Then dumper creates and binds TCP sockets on its side and connects to
Re: solved: problem restoring old backups
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 are 'old' and moves the logs to oldlog directory (thank god it doesn't delete them!). I'll try using separate log directories for separate configs in the future. Cool! Look for lines beginning with logfile in the two amanda.conf. $ grep infofile\|logdir\|indexdir be/amanda.conf be-full/amanda.conf be/amanda.conf:infofile /var/lib/amanda/be/curinfo# database DIRECTORY be/amanda.conf:logdir /var/lib/amanda/be/log# log directory be/amanda.conf:indexdir /var/lib/amanda/be/index # index directory be-full/amanda.conf:infofile /var/lib/amanda/be-full/curinfo # database DIRECTORY be-full/amanda.conf:logdir /var/lib/amanda/be-full/log # log directory be-full/amanda.conf:indexdir /var/lib/amanda/be-full/index# index directory
Re: Multi-tape question
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.
Re: Multi-tape question
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 planning
stage - just tell her about each tape having a capacity of 70 GB.
Re: amrecover doesn't mount tape
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.
Re: Problem restoring old backups
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.
Re: Incoherente saving when moving a directory
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 do his job... What backup program do you use?
Re: Problem restoring old backups
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 20020201_0.gz -rw--- 1 amanda wheel 25796 Feb 8 22:10 20020208_0.gz -rw--- 1 amanda wheel 25919 Feb 22 22:12 20020222_0.gz What's in these files? Look into them using zless. Check their access time when you use amrecover. Look at the directory when you are in amrecover. One file should be gunzipped lying around.
Re: Problem restoring old backups
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 20020201_0.gz -rw--- 1 amanda wheel 25796 Feb 8 22:10 20020208_0.gz -rw--- 1 amanda wheel 25919 Feb 22 22:12 20020222_0.gz [...] From this it seems that backup history exists at least for 2002-02-01 and 2002-02-08. Why doesn't amrecover see these indexes? amrecover does see every backup. But you'll have to tell it which date you are interested in. You didn't issue a setdate command. So amrecover shows you the state of the last backup (Feb 22th). If you'd like to switch to another backup - issue setdate --01-25 or setdate --01-26 to get a list of the files backed up on Jan 25th.
Re: Problem restoring old backups
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 that all backups were done to the same tape... Did you already use amadmin find? amadmin WEEKLY find heerold.raad.tartu.ee /\$ should list all your weekly backups Amanda thinks of being on tape. $ amadmin be find apollo /\$ Warning: no log files found for tape BE00 written 2002-02-26 Scanning /dumps/amanda... 20020226: found Amanda directory. date host disk lv tape or file file status 2002-02-09 apollo / 1 BE023 OK 2002-02-10 apollo / 1 BE03 28 OK 2002-02-11 apollo / 1 BE057 OK 2002-02-12 apollo / 1 BE07 17 OK 2002-02-13 apollo / 1 BE096 OK 2002-02-14 apollo / 1 BE136 OK 2002-02-15 apollo / 1 BE146 OK 2002-02-16 apollo / 0 BE16 16 OK 2002-02-17 apollo / 1 BE185 OK 2002-02-18 apollo / 1 BE19 26 OK 2002-02-19 apollo / 1 BE21 22 OK 2002-02-20 apollo / 1 BE22 19 OK 2002-02-21 apollo / 0 BE23 31 OK 2002-02-22 apollo / 1 BE249 OK 2002-02-23 apollo / 1 BE256 OK 2002-02-24 apollo / 1 BE266 OK 2002-02-25 apollo / 1 BE275 OK
Re: restore from disk?
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
Re: Use of amplot?
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.
Re: access as amanda not allowed
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 + bckamanda + localhost amanda Change it to contain: bck.mydomain.com amanda
Re: Testing a tape drive?
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.
Re: Amcheck reports no tape online
Amanda user = amanda Amanda group = backup [...] ERROR: /dev/nst0: Permission denied (expecting a new tape) chown amanda:backup /dev/nst0
Re: Merry Christmas and a happy New Year
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 this some sort of new virus? I have got this email about 10 times today... Seems to have been stuck/looped for seven weeks on internal.mail.telinco.net: Received: from [64.134.101.69] (helo=surly.omniscient.com) by mxng04.kundenserver.de with esmtp (Exim 3.22 #2) id 16cmtC-rL-00; Mon, 18 Feb 2002 13:27:26 +0100 Received: from internal.mail.telinco.net (internal.mail.telinco.net [212.1.128.4]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g1IAbNv417253 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 05:37:36 -0500 (EST) Received: from root by internal.mail.telinco.net with local (Exim 3.22 #1) id 16clAh-0003ul-00 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 10:37:23 + Received: from surly.omniscient.com ([64.134.101.69]) by internal.mail.telinco.net with esmtp (Exim 3.22 #1) id 16IZXC-tI-00 for [EMAIL PROTECTED]; Mon, 24 Dec 2001 18:09:10 + Received: from smtp2.doruk.net.tr (smtp2.doruk.net.tr [212.58.5.5]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id fBOGo5N497468 for [EMAIL PROTECTED]; Mon, 24 Dec 2001 11:50:06 -0500 (EST) Received: from AYKUT ([195.174.64.47]) by smtp2.doruk.net.tr with Microsoft SMTPSVC(5.0.2195.2966); Mon, 24 Dec 2001 18:51:30 +0200 Reply-To: [EMAIL PROTECTED] From: AYKUT CAKIL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Merry Christmas and a happy New Year Date: Mon, 24 Dec 2001 18:09:47 +0200 Organization: ACTIVE TOURISM INC.
Re: Merry Christmas and a happy New Year
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 to have been stuck. Today, I got around 90 mails of amanda-users from Dec 24 2001 to Jan 3 2002. They are doubles to mails already received. It's always internal.mail.telinco.net in between. Maybe the box of [EMAIL PROTECTED] looped. Received: from [64.134.101.78] (helo=guiness.omniscient.com) by mxng00.kundenserver.de with esmtp (Exim 3.22 #2) id 16cm6W-0002c8-00 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 12:37:08 +0100 Received: from surly.omniscient.com (surly.omniscient.com [64.134.101.69]) by guiness.omniscient.com (8.12.1/8.12.1) with ESMTP id g1IBVjmW013054; Mon, 18 Feb 2002 06:32:13 -0500 (EST) Received: (from root@localhost) by surly.omniscient.com (8.11.6/8.11.6) id g1IBVtj417539 for amanda.org.amanda-users-list; Mon, 18 Feb 2002 11:31:55 GMT Received: from internal.mail.telinco.net (internal.mail.telinco.net [212.1.128.4]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g1IArWv418616 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 05:53:38 -0500 (EST) Received: from root by internal.mail.telinco.net with local (Exim 3.22 #1) id 16clPr-0007Jk-00 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 10:53:04 + Received: from guiness.omniscient.com ([64.134.101.78]) by internal.mail.telinco.net with esmtp (Exim 3.22 #1) id 16MH6F-0008j6-00 for [EMAIL PROTECTED]; Thu, 03 Jan 2002 23:16:39 + Received: from surly.omniscient.com (surly.omniscient.com [64.134.101.69]) by guiness.omniscient.com (8.12.1/8.12.1) with ESMTP id g03MrMsh011090; Thu, 3 Jan 2002 17:53:59 -0500 (EST) Received: (from root@localhost) by surly.omniscient.com (8.11.6/8.11.6) id g03Mbo5520487 for amanda.org.amanda-users-list; Thu, 3 Jan 2002 22:37:50 GMT Received: from mail.databuilt.com (f12-1-3-00-0899.beready.att.net [63.241.179.71]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g03MblB377090 for [EMAIL PROTECTED]; Thu, 3 Jan 2002 17:37:48 -0500 (EST) Received: from dither.corp.databuilt.com (dyn.pool-1-129.r99.r100.scptvl.infoave.net [64.53.71.129]) by mail.databuilt.com (8.10.2/8.10.2) with ESMTP id g03Mbc203590 for [EMAIL PROTECTED]; Thu, 3 Jan 2002 17:37:38 -0500 Subject: Running programs during client execution? From: Mark Hazen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.0.99+cvs.2001.12.14.08.57 (Preview Release) Date: 03 Jan 2002 17:37:38 -0500 Message-Id: [EMAIL PROTECTED]
Re: [Amanda-users] Re: backups still failing.
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.
Re: [Amanda-users] Re: backups still failing.
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 compared to DDS3 tapes. You might have faulty hardware, there could be anything from SCSI cabling to the drive, the head or the tape.
Re: bad versions of tar, index files and restores
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 incremental index is corrupted but no data.
Re: Using Amanda with Linux/XFS: failed to get (valid) bulkstat information
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 programs and to have the ability to treat them
differently in the future.
In this case, the warnings seem to be quite normal for busy XFS
filesystems. But xfsdump prints a warning and hopefully the xfsdump
developers will have had their reasons for it: why don't recognize it as
a warning but continue as you would do on the command line? (A warning?
I've got the backups - who cares if I can recover? ;-))
Second reason (technical nature): the dmpline_t/regex pairs in the array
re_table (client-src/sendbackup-dump.c, line 44) are matched against
dump's output in order of array index in parse_dumpline().
client-src/sendbackup.c:
729 dmpline_t parse_dumpline(str)
730 char *str;
731 /*
732 * Checks the dump output line in str against the regex table.
733 */
734 {
735 regex_t *rp;
736
737 /* check for error match */
738 for(rp = program-re_table; rp-regex != NULL; rp++) {
739 if(match(rp-regex, str))
740 break;
741 }
The array re_table is initialized with pairs in order of DMP_SIZE,
DMP_STRANGE, DMP_NORMAL and DMP_STRANGE (for all other lines). One of
the regexps of dmpline_t DMP_STRANGE is [Ff]ail.
client-src/sendbackup-dump.c:
100/* strange dump lines */
101{ DMP_STRANGE, should not happen },
102{ DMP_STRANGE, Cannot open },
103{ DMP_STRANGE, [Ee]rror },
104{ DMP_STRANGE, [Ff]ail },
105/* XXX add more ERROR entries here by scanning dump sources?
*/
106
107/* any blank or non-strange DUMP: lines are marked as normal
*/
108{ DMP_NORMAL, ^ *DUMP: },
If you added failed to get bulkstat to DMP_NORMAL, you would never
match DMP_NORMAL because DMP_STRANGE would have been matched first. So I
inserted DMP_WARNING between DMP_SIZE and DMP_STRANGE.
The XFS boys of SGI told me not to bang my head on these warnings.
Bulkstat is a special XFS feature to get lots of inodes in a single
rush. Sometimes an inode cannot be caught by bulkstat due to filesystem
activity; instead, xfsdump will do a single stat call later on it.
Re: amanda in aix
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 make i receive the next error: make[1]: Entering directory `/home/software/amanda-2.4.2p2/client-src' /usr/bin/sh ../libtool --mode=link gcc -g -O2-o amandad amandad.o ../common-src/libamanda.la libamclient.la ../common-src/libamanda.la -lm -lreadline -lcurses -lnsl -lintl gcc -g -O2 -o amandad amandad.o ../common-src/.libs/libamanda.a -lm -lreadline -lcurses -lnsl -lintl .libs/libamclient.a -lm -lreadline -lcurses -lnsl -lintl ../common-src/.libs/libamanda.a -lm -lreadline -lcurses -lnsl -lintl -lm -lreadline -lcurses -lnsl -lintl ld: 0711-317 ERROR: Undefined symbol: .__main ... I just tried this on a 4.3.3 system here using gcc 2.95.3 and it worked OK. What version of gcc are you using (gcc --version)? Didn't we have that mntent.h issue on AIX 4.3.3?
Re: Newbie first questions
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 user back his deleted filesthough how you would use a tar'ed tape to restore an OS is another thing. It's sort of like building a bridge while standing on thin air...maybe Wile Coyote can do it (for a while, until he looks down). How do you do both? AIX and sysback have built-in magic, but. Here's what I do with AIX: do once in a month an mksysb tape and daily Amanda runs. mksysb only backups the rootvg! This is for a bootable tape in case the drives fail. Every filesystem in each VG is backed up by Amanda. No experience yet with sysback.
Re: Newbie first questions
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 a dump of / involved there, too. Basically you restore the / filesystem, do chroot . sbin/lilo in it and you are ready to run.
Using Amanda with Linux/XFS: failed to get (valid) bulkstat information
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 Oct 20 15:59:20
2001
+++ amanda-2.4.2p2-20011020/client-src/sendbackup-dump.cSun Jan 27 11:56:18
+2002
@@ -97,6 +97,10 @@
{ DMP_SIZE, xfsdump: media file size [0-9][0-9]* bytes, 1},
/* Irix 6.2 xfs dump */
+ /* warnings to be ignored */
+ { DMP_WARNING, ^xfsdump: WARNING: failed to get valid bulkstat information for
+inode }, /* Linux xfsdump */
+ { DMP_WARNING, ^xfsdump: WARNING: failed to get bulkstat information for inode },
+/* Linux xfsdump */
+
/* strange dump lines */
{ DMP_STRANGE, should not happen },
{ DMP_STRANGE, Cannot open },
--- amanda-2.4.2p2-20011020.orig/client-src/sendbackup.cSat Oct 20 15:59:20
2001
+++ amanda-2.4.2p2-20011020/client-src/sendbackup.c Sun Jan 27 11:51:50 2002
@@ -755,6 +755,7 @@
switch(typ) {
case DMP_NORMAL:
case DMP_SIZE:
+case DMP_WARNING:
startchr = '|';
break;
default:
--- amanda-2.4.2p2-20011020.orig/client-src/sendbackup.hSat May 27 23:20:32
2000
+++ amanda-2.4.2p2-20011020/client-src/sendbackup.h Sun Jan 27 11:51:50 2002
@@ -53,7 +53,7 @@
*/
typedef enum {
-DMP_NORMAL, DMP_STRANGE, DMP_SIZE, DMP_ERROR
+DMP_NORMAL, DMP_WARNING, DMP_STRANGE, DMP_SIZE, DMP_ERROR
} dmpline_t;
typedef struct regex_s {
Re: re-doing bad tapes
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 am I hosed? You are hosed. Here's what I do with these tapes: mark them with a fat red edding, keep them for the following rotation cycle and then throw them away.
Re: What if ... ( the index under /var/amanda is gone )
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 /var/lib/amanda/conf to another host with amanda installed. This is scheduled with cron. If the original server dies it is possible to do amadmin conf find|info|... on the second host or to use it as an index server for amrecover.
Re: Strange dump error
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 not an fstab entry that there will be problems? No. You just use the block device in Amanda's disklist.
Re: amanda-users list problem
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?
Re: amanda-users list problem
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 avoided it myself. This need to notice/restore before the tape cycle runs out is a recurring theme in amanda usage. [...] Is surly.omniscient.com backed up by Amanda?
Re: tapetype question
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. The tape is an AIT-1 25/50G tape. Is it ok for me to up the
length? Why does tapetype report at least 4 gigs less then the native
capacity of the tape.
I guess you enabled hardware compression.
Re: indexes
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 tapes - if writing to this single tape fails you will be lost with no backup In my opinion amanda should write next backup on tape just after the previous, so on one tape 80 GB there is a lot of place for lets say 4 backups. But when I run amrecover and type setdate ---21 (today is 23 ) amrecover says: 200 Working date set to 2001-10-21. No index records for cwd on new date Setting cwd to mount point But in directory /usr/local/amanda/DailySet1/index/hostname/partition ther is a lot of files like: 20011023_2.gz 20011022_2.gz 20011021_2.gz all in mode 600. So why amrecover says that there is no indexes, and I can't recover from few days earlier? Did you type sethost hostname and setdisk partition in amrecover?
Re: selfcheck request timed out. Host down? error
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 times out on 1. The host is not down as I can ping and rlogin in to it without any problem. It does also have the appropriate entries in the /etc/services and /etc/inetd.conf What's in /tmp/amanda/*debug on this machine?
Re: OK, what stupid mistake am I making?
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 ./home/oracle/9.01/software/app/oracle/oradata/debian/redo02.log ./home/oracle/9.01/software/app/oracle/oradata/debian/control01.ctl ./home/oracle/9.01/software/app/oracle/product/release/oradata/debian/undotbs01.dbf ./tmp/.ICE-unix ./tmp/.X11-unix ./var/run/postgresql/.s\* ./var/run/sendmail/smcontrol ./var/tmp/.oracle/s\* ./tmp/.sawfish-stan ./tmp/orbit-stan ./tmp/ssh\* | gtar: ./var/run/postgresql/.s.PGSQL.5432: socket ignored | gtar: ./var/tmp/.oracle/s#406.1: socket ignored | gtar: ./var/tmp/.oracle/sEXTPROC: socket ignored | Total bytes written: 8280053760 (7.7GB, 379kB/s) leave off the backslashes, just write ./var/tmp/.oracle/s*
Re: AMANDA WEBSITE ???
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... ;-)
Re: OK, what stupid mistake am I making?
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 SUMMARY:
debian hde4 lev 0 STRANGE
FAILED AND STRANGE DUMP DETAILS:
/-- debian hde4 lev 0 STRANGE
sendbackup: start [debian:hde4 level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/local/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./home/oracle/9.01/software/app/oracle/oradata/debian/control03.ctl: file
changed as we read it
| gtar: ./tmp/ssh-XXFiBGDE/agent.9980: socket ignored
? gtar: ./usr/local/amanda/adm/DailyDump/index/cems/_/20011024_1.gz.tmp: Warning:
Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/cogenal/ad0s1f/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
tar is just whining about files changing during the backup including the
amanda index files itself
? gtar: ./usr/local/amanda/adm/DailyDump/index/cogenwp/c0t3d0s7/20011024_0.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/phse1/c0t0d0/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/phse1/c0t1d0/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar:
./usr/local/amanda/adm/DailyDump/index/stripper/_dev_md_dsk_d5/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/stripperal/ad0s1f/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar:
./usr/local/amanda/adm/DailyDump/index/waterap/_dev_md_dsk_d5/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/waterwp/c0t3d0s6/20011024_0.gz.tmp:
Warning: Cannot stat: No such file or directory
| gtar: ./var/run/postgresql/.s.PGSQL.5432: socket ignored
| gtar: ./var/tmp/.oracle/s#406.1: socket ignored
| gtar: ./var/tmp/.oracle/sEXTPROC: socket ignored
| Total bytes written: 8280053760 (7.7GB, 379kB/s)
sendbackup: size 8085990
sendbackup: end
\
From disklist
---
debian hde4 comp-user-tar 1 local
debian hde1 comp-user-tar 1 local
debian hdf1 holding-disk-tar 2 local
debian hdg1 nocomp-user 3 local # Compressing compressed data makes it
# larger
From amanda.conf
--
define dumptype user-tar {
root-tar
comment user partitions dumped with tar
priority medium
}
define dumptype comp-user-tar {
user-tar
exclude list /usr/local/lib/gnutar_exclude_list
compress client fast
}
ls -l of /usr/local/lib/gnutar_exclude_list
-rw-r--r--1 amanda staff 472 Oct 24 07:52
/usr/local/lib/gnutar_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
./home/oracle/9.01/software/app/oracle/oradata/debian/redo02.log
./home/oracle/9.01/software/app/oracle/oradata/debian/control01.ctl
./home/oracle/9.01/software/app/oracle/product/release/oradata/debian/undotbs01.dbf
./tmp/.ICE-unix
./tmp/.X11-unix
./var/run/postgresql/.s\*
./var/run/sendmail/smcontrol
./var/tmp/.oracle/s\*
./tmp/.sawfish-stan
./tmp/orbit-stan
./tmp/ssh\*
Now clearly the files I wan't to exclude, are not being excluded! Also
what's with the Amanda files themselves, that it's complaining about?
The holding disk is /dev/hdf1, so that should not be related to the
problems with this disk.
--
Stan Brown [EMAIL PROTECTED]843-745-3154
Charleston SC.
--
Windows 98: n.
useless extension to a minor patch release for 32-bit extensions and
a graphical shell for a 16-bit patch to an 8-bit operating system
originally coded for a 4-bit microprocessor, written by a 2-bit
company that can't stand for 1 bit of competition.
-
(c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
Re: data timeout
/-- 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 last level 0 dump: the epoch | DUMP: Dumping /dev/sda6 (/) to standard output | DUMP: Label: none | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 108455 tape blocks. | DUMP: Volume 1 started at: Mon Oct 22 23:02:49 2001 | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] \ NOTES: driver: fs.rocnet.de /dev/sda6 0 [dump to tape failed, will try again] I assume this is Linux' dump. What version are you using? Why don't you use a holding disk instead of writing directly to tape?
Re: ERROR amandad busy
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 cannot kill. Anyone have any ideas what could be wrong with dump? rpm -q dump dump-0.4b21-3 I'd recommend dump-0.4b24 (http://dump.sourceforge.net/). If the problem persists, ask on the dump mailing list.
Re: data timeout
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 use a holding disk because i dump all partitions and in any time i will dump the partition with the holding disk. are there any problems to dump the holding disk partition ? yes, there are - you can't dump a filesystem with the holding disk on it to the holding disk. You'd have to use a special parameter in amanda.conf for it. It results in dumping directly to tape. Go get the latest dump 0.4b24.
Re: amflush thinks that amanda directories are actually cruft after upgrading
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 /bkup total 20 drwx-- 2 backup backup 4096 Oct 18 06:30 20011017 drwx-- 2 backup backup 4096 Oct 21 06:31 20011020 drwx-- 2 backup backup 4096 Oct 21 18:30 20011021 drwx-- 2 backup backup 4096 Oct 24 09:36 20011023 drwxr-xr-x 2 backup backup 4096 May 11 12:50 lost+found truk!backup 111# But when I run amflush (as user backup, of course), I get: truk!backup 111# amflush daily Scanning /bkup... : skipping cruft directory, perhaps you should delete it. : skipping cruft directory, perhaps you should delete it. : skipping cruft directory, perhaps you should delete it. : skipping cruft directory, perhaps you should delete it. : skipping cruft directory, perhaps you should delete it. : skipping cruft directory, perhaps you should delete it. : skipping cruft directory, perhaps you should delete it. Could not find any Amanda directories to flush. I think there are some pathnames and maybe even hostnames in the files on the holding disk.
Re: Data Timeout
2) Which timeout value can I adjust in amanda.conf to avoid the data timeout error? amanda.conf, dtimeout
Re: DUMP program not found
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 messages from amcheck. do make distclean or rm config.cache before you rerun configure
Re: Freebsd not starting amandad
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 and client. The amandad service starts up manually (though, of course, it times out) on the FreeBSD machine. When, on the server, I run the configuration that is supposed to back up the FreeBSD machine, it eventually times out. There is no corresponding amcheck, amdebug, or selfcheck file on FreeBSD /tmp/amanda, or anywhere else on the machine for that matter. The inetd service is running. I have configured the inetd.conf like this: amanda stream udp amanda stream udp waitamanda /usr/local/libexec/amandad amidxtape stream tcpnowait amanda /usr/local/libexec/amandad amandaidx stream tcpnowait amanda /usr/local/libexec/amandad What could be keeping the amanda service from starting? You don't need the lines starting with amidxtape and amandaidx on a client, comment them out. You forgot the last argument on the lines - the name of the program (argv[0]). Add it: $ grep amanda /etc/inetd.conf amanda dgram udp waitamanda /usr/libexec/amanda/amandadamandad amandaidx stream tcp nowait amanda /usr/libexec/amanda/amindexd amindexd amidxtape stream tcp nowait amanda /usr/libexec/amanda/amidxtaped amidxtaped Did you kill -1 PID if inetd? Does netstat -an|grep 10080 shows UDP 10080? Does /etc/services contain port numbers for amanda, amidxtape and amandaidx (the latter two for restores from your FreeBSD box).
Re: ERROR amandad busy
[...] 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 without rebooting would be appreciated. [...] I assume the hanging dumps are on the linux box playing amanda server. What version are you using? You should use the lastest greatest. 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.
Re: data timeout
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 used one time 3600 and another time 7200. What program do you use to backup? Did you run it by hand, i.e. in the same way amanda calls it (look at /tmp/amanda/sendbackup*debug)?
Re: how to restore entire filesystems
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 in a single run If I just restore the files to another directory for copying them over later, then how am I supposed to replace the files which are in use by the machine? dump works by filesystems, you'll have to place you files on another partition/block device/hard drive in between Is there a way to restore, for example, the entire /usr partition 'with one go'? you boot off a floppy/cdrom, mkfs your filesystem usually mounted to /usr, mount it, cd to it and restore rf dump file or export TAPE=/dev/nst0; restore r or something like this Am I a fool? by doing backups - real man's stuff is mirrored on ftp servers all over the world ;-)
Re: Amanda 2.4.2p2, Solaris 8, amandad hangup
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 post your inetd.conf lines and the syslog lines?
Re: Amanda 2.4.2p2, Solaris 8, amandad hangup
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, do you think my previously built 2.4.1p1 client will run correctly with my 2.4.2p2 server ? I don't think so. At least in theory it should run flawlessly. I remember some weird problems when I upgraded some servers or clients from 2.4.1p1 to 2.4.2 and clients or servers were left on 2.4.1p1 but I can't you tell any details at the moment. Just try it. To know if it runs or not takes less time than getting gcc for 2.6. If it doesn't run, try something like http://gcc.gnu.org/, then click somewhere on binaries.
Re: xfsdump: WARNING: failed to get valid bulkstat information for inode 758724
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
sendbackup: start [ente:/var level 2]
sendbackup: info BACKUP=/usr/sbin/xfsdump
sendbackup: info RECOVER_CMD=/usr/sbin/xfsrestore -f... -
sendbackup: info end
| xfsdump: version 3.0 - Running single-threaded
| xfsdump: level 2 incremental dump of ente:/var based on level 1 dump
begun Mon Oct 15 01:48:51 2001
| xfsdump: dump date: Thu Oct 18 01:55:31 2001
| xfsdump: session id: 7da36377-00bd-48f4-afd8-76593ef9b467
| xfsdump: session label:
| xfsdump: ino map phase 1: skipping (no subtrees specified)
| xfsdump: ino map phase 2: constructing initial dump list
? xfsdump: WARNING: failed to get valid bulkstat information for inode
758724
| xfsdump: ino map phase 3: pruning unneeded subtrees
? xfsdump: WARNING: failed to get valid bulkstat information for inode
758724
| xfsdump: ino map phase 4: estimating dump size
? xfsdump: WARNING: failed to get valid bulkstat information for inode
758724
| xfsdump: ino map phase 5: skipping (only one dump stream)
| xfsdump: ino map construction complete
| xfsdump: estimated dump size: 76693376 bytes
| xfsdump: creating dump session media file 0 (media 0, file 0)
| xfsdump: dumping ino map
| xfsdump: dumping directories
? xfsdump: WARNING: failed to get valid bulkstat information for inode
758724
| xfsdump: dumping non-directory files
? xfsdump: WARNING: failed to get valid bulkstat information for inode
758724
| xfsdump: ending media file
| xfsdump: media file size 78355232 bytes
| xfsdump: dump size (non-dir files) : 77925384 bytes
| xfsdump: dump complete: 42 seconds elapsed
| xfsdump: Dump Status: SUCCESS
sendbackup: size 76519
sendbackup: end
\
Now I hacked up Amanda's source code to ignore these WARNINGs. The patch
is attached. It's a diff against the current CVS tree of 2.4.2p2 but it
works for plain 2.4.2p2, too.
The patch introduces a new category DMP_WARNING to the array of regex in
client-src/sendbackup-dump.c xfsdump's output is checked against. Adding
the failed to get valid bulkstat line to DMP_NORMAL didn't help
because the regex for DMP_STRANGE containing [Ff]ail are checked first
in client-src/sendbackup.c. So dmpline_t parse_dumpline(str) would
return DMP_STRANGE instead of DMP_NORMAL. Now it returns DMP_WARNING
which is handled by void process_dumpline(str) in the same way as
DMP_NORMAL and DMP_SIZE.
--- amanda-2.4.2p2-20011020.orig/client-src/sendbackup-dump.c Sat Oct 20 15:59:20
2001
+++ amanda-2.4.2p2-20011020/client-src/sendbackup-dump.cSat Oct 20 20:12:35
+2001
@@ -97,6 +97,9 @@
{ DMP_SIZE, xfsdump: media file size [0-9][0-9]* bytes, 1},
/* Irix 6.2 xfs dump */
+ /* warnings to be ignored */
+ { DMP_WARNING, ^xfsdump: WARNING: failed to get valid bulkstat information for
+inode }, /* Linux xfsdump */
+
/* strange dump lines */
{ DMP_STRANGE, should not happen },
{ DMP_STRANGE, Cannot open },
--- amanda-2.4.2p2-20011020.orig/client-src/sendbackup.cSat Oct 20 15:59:20
2001
+++ amanda-2.4.2p2-20011020/client-src/sendbackup.c Sat Oct 20 20:03:05 2001
@@ -755,6 +755,7 @@
switch(typ) {
case DMP_NORMAL:
case DMP_SIZE:
+case DMP_WARNING:
startchr = '|';
break;
default:
--- amanda-2.4.2p2-20011020.orig/client-src/sendbackup.hSat May 27 23:20:32
2000
+++ amanda-2.4.2p2-20011020/client-src/sendbackup.h Sat Oct 20 20:03:05 2001
@@ -53,7 +53,7 @@
*/
typedef enum {
-DMP_NORMAL, DMP_STRANGE, DMP_SIZE, DMP_ERROR
+DMP_NORMAL, DMP_WARNING, DMP_STRANGE, DMP_SIZE, DMP_ERROR
} dmpline_t;
typedef struct regex_s {
[Fwd: TAKE 820267 - enable xfsrestore to run on non-xfs filesystem]
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 seemed to adversely affect amanda users). It also removes the (harmless) space pre-allocation warnings if restore is writing to a non-xfs filesystem. Ivan Date: Wed Oct 17 20:54:34 PDT 2001 Workarea: omen.melbourne.sgi.com:/hosts/snort/diskb/build6/ivanr/isms/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:104985a cmd/xfsdump/restore/namreg.c - 1.2 cmd/xfsdump/restore/dirattr.c - 1.3 - dont issue a warning if space pre-allocation failed for mmap file if the operation is not supported cmd/xfsdump/restore/content.c - 1.16 - dont check whether housekeeping directory is on xfs filesystem
Re: Problems with amrecover
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 tape drive /dev/nst1 on host devel. The following tapes are needed: EOS-011 EOS-012 Restoring files into directory /tmp Continue? [Y/n]: y Load tape EOS-011 now Continue? [Y/n]: y EOF, check amidxtaped.debug file on devel. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue? [Y/n]: The debug file contains: amidxtaped: debug 1 pid 3112 ruid 1028 euid 1028 start time Thu Oct 18 11:17:09 2001 amidxtaped: version 2.4.2 SECURITY USER root bsd security: remote host afs1.eos user root local user amanda amandahosts security check passed 6 amrestore_nargs=6 -h -p /dev/nst1 svabonius.eos.dk ^/etc$ 20011017 Ready to execv amrestore with: path = /afs/eos.dk/sw/pack/amanda-2.4.2/sbin/amrestore argv[0] = amrestore argv[1] = -h argv[2] = -p argv[3] = /dev/nst1 argv[4] = svabonius.eos.dk argv[5] = ^/etc$ argv[6] = 20011017 amrestore: could not open tape /dev/nst1: Permission denied ^ Here's the error. Please look at remote host afs1.eos user root local user amanda. Maybe you start amidxtaped as user amanda instead of root. Check /etc/inetd.conf or /etc/xinetd* amidxtaped: amrestore terminated normally with status: 2 Rewinding tape: no tape online amidxtaped: pid 3112 finish time Thu Oct 18 11:17:09 2001 I've searched the mail-list archives but didn't find anything that applied to my problem (or at least I don't think so :) ). I have no problems with restoring files using mt and dd on the same tape/tape drive, so it is functioning. The server is running RedHat Linux 7.0, and I've tried both amanda 2.4.2 and 2.4.2p2. Same result. So what do I do wrong here? -- Jens Rohde, System Administrator --- Eastfork Object Space (EOS), Margrethepladsen 3, 8000 Aarhus C, Denmark Tel: +45 8732 8787 / Fax: +45 8732 8788
Re: tapecycle off by 1?
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. But here's what the report said: These dumps were to tapes love129, love130, love131. The next 6 tapes Amanda expects to used are: a new tape, love132, love133, love134, love1, love2. My question is how come it's not expecting love135, after all that's what I have specified in amanda.conf. Kinda looks like a x-1 error. But I'm sure I'm just missing something, and hoping the list can help me... Probably you missed (skipped) a tape someday. Check your tapelist if every tape love1-love131 was used.
Re: Amcheck Error?
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 tape-writable test Tape Daily00 label ok Server check took 0.062 seconds Amanda Backup Client Hosts Check ERROR: natashia.lemonasia.com: [access as amanda not allowed from amanda@natashia] amandah ostsauth failed Client check: 1 host checked in 0.061 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) # natashia:~amanda/.amandahosts should contain the line natashiaamanda
Re: Amcheck Error?
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?
Re: failed because no blank tapes
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. Probably your holding disk is too small to keep your not-yet-run filesystems. There's no point in doing incrementals if you don't have a full dump to rely on.
Re: Amrecover - Amandaidx Looping?
[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 2022 finish time Wed Oct 10 12:12:58 2001
And this is what I see in /var/log/messages:
Oct 10 12:01:20 garfield xinetd[1927]: warning: can't get client
address: Transport endpoint is not connected
[...]
Oct 10 12:01:21 garfield xinetd[1936]: warning: can't get client
address: Transport endpoint is not connected
Oct 10 12:01:21 garfield xinetd[1923]: amandaidx service was
deactivated because of looping
[...]
[root@garfield amanda]# cat /etc/xinetd.d/amandaidx
# default: off
#
# description: Part of the Amanda server package
service amandaidx
{
socket_type = stream
protocol= tcp
wait= yes
user= amanda
group = disk
server = /usr/lib/amanda/amindexd
}
[...]
Please check again with wait = no (don't forget to SIGUSR1 xinetd or
to restart it - SIGHUP won't help).
$ grep ^am /etc/inetd.conf
amanda dgram udp waitamanda /usr/libexec/amanda/amandad
amandad
amandaidx stream tcp nowait amanda
/usr/libexec/amanda/amindexd amindexd
amidxtape stream tcp nowait amanda
/usr/libexec/amanda/amidxtaped amidxtaped
Re: How can I verify that Indexing is working?
- 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 containing the filenames in the backup. What's inside these files?
Re: How do i extract from a specific tape?
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 amidxtaped.debug file on amanda amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue? [Y/n] : short block is mostly an indicator for the wrong blocksize but not in your case. You got level 0 back. when i hit y , i was returned to my amrecover prompt. Does this mean the level 1 data on that tape is corrupt? if so, can i move on to the 3rd tape and at least recover that data? Did you run amverify on these two tapes? Do you perform a full restore (i.e. mkfs, restore, restore, restore)? Or just some files spread out over your tapes? In the first case you don't need the first level 1 but only the last level 1.
Re: amdump problem: missing result reported
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 backed up?
Re: Amrecover - Amandaidx Looping?
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 ``nowait'' entry in this space). If a datagram server connects to its peer, freeing the socket so inetd can received further messages on the socket, it is said to be a ``multi-threaded'' server, and should use the ``nowait'' entry. For datagram servers which process all incoming datagrams on a socket and eventually time out, the server is said to be ``single-threaded'' and should use a ``wait'' entry. Com- sat(8) (biff(1)) and talkd(8) are both examples of the latter type of datagram server. Tftpd(8) is an exception; it is a datagram server that establishes pseudo-connections. It must be listed as ``wait'' in order to avoid a race; the server reads the first packet, creates a new socket, and then forks and exits to allow inetd to check for new service requests to spawn new servers. The optional ``max'' suffix (separated from ``wait'' or ``nowait'' by a dot) specifies the maximum number of server instances that may be spawned from inetd within an interval of 60 sec- onds. When omitted, ``max'' defaults to 40.
Re: selfcheck timeout - host down
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
Re: File too large?
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
Re: Amrecover - Amandaidx Looping?
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 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:10083 0.0.0.0:* LISTEN udp0 0 0.0.0.0:10080 0.0.0.0:* $ grep ^am /etc/services amanda 10080/udp # amanda backup services amandaidx 10082/tcp # amanda backup services amidxtape 10083/tcp # amanda backup services
Re: How can I verify that Indexing is working?
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!
Re: partition too large for tape?
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 incorrectly? Did you switch off hardware compression? Don't mix soft and hard.
Re: amandad simply does not like me.
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 hi Amanda 2.4 NAK HANDLE SEQ 0 ERROR expected Amanda, got hi quit Amanda 2.4 NAK HANDLE SEQ 0 ERROR expected Amanda, got quit $ nc -u ente 10080 Amanda Amanda 2.4 NAK HANDLE SEQ 0 ERROR expected digit, got
Re: help :: advfs patch
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 someone perhaps offer some assistance or point me to a website i could read up on the patch binary some more. for example, DEC includes its own version of `patch`. do i have to use gnu patch? can i use the dec patch? Though I've no idea of DEC's version of patch, but I'd recommend GNU patch. Then you do something like: cd /usr/local/src tar xzf /where/ever/you/stored/amanda-2.4.2p2.tar.gz cd amanda-2.4.2p2 patch -p1 /where/ever/you/lost/advfs-patch.diff The -p option specifies the number of subdir levels to strip off in the diff file, i.e. the might be something like: +++ amanda-2.4.2p2/client/sendsize.c ... --- amanda-2.4.2p2-orig/client/sendsize.c ... So -p1 is to strip off the first level of subdir to apply the diff / to patch client/sendsize.c.
Re: Statically linked binaries?
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 --enable-static=yes option I still end up with dynamically linked binaries, as revealed by running ldd after a make install. Setting the CFLAGS environment variable to contain -static doesn't help either. How can I get Amanda to produce statically linked binaries for me? I think you'll have to hack the Makefiles. I once did it for a statically linked amrestore.
Re: Error compiling on AIX 4.3.3.0.09
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) getfsent.c:154: (Each undeclared identifier is reported only once getfsent.c:154: for each function it appears in.) make: 1254-004 The error code from the last command is 1. [...] A temporary solution is to kick away or to rename mntent.h to mntent.h.ibmsucks. Don't forget to make distclean or rm config.cache before another shot of ./configure --with-user=... ---with-group=... --with-blabla=... Nobody has come up with a general solution for AIX 4.3.3, yet. Though is has bitten many Amanda users/admins on AIX 4.3.3. :-(
Re: level 2 and 3
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 required to trigger an automatic bump from one incremental level to the next. If Amanda determines that the next higher backup level will be this much smaller than the current level, it will do the next level. See also the bumpmult option. bumpmult float Default: 1.5. The bump size multiplier. Amanda multiplies bumpsize by this factor for each level. This prevents active filesystems from bumping too much by making it harder to bump to the next level. For example, with the default bumpsize and bumpmult set to 2.0, the bump threshold will be 10 Mbytes for level one, 20 Mbytes for level two, 40 Mbytes for level three, and so on. bumpdays int Default: 2. To insure redundancy in the dumps, Amanda keeps filesystems at the same incremental level for at least bumpdays days, even if the other bump threshold criteria are met.
Re: Which archive utility to use?
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 http://www.backupcentral.com/amanda-24.html
how to unsubscribe
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 visit http://www.amanda.org/ for instructions how to
unsubscribe from [EMAIL PROTECTED];
}
Hopefully people will get to know how to unsubscribe.
Re: amrecover
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?
Re: Waiting for ack
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: Connection refused, retrying followed by one line of amandad: waiting for ack: Connection refused, giving up! Any hints as to what went wrong? What RPMs did you update? Did you setup some firewalling by default?
