cruft missing files
Hi, last week one of the holding disks of our backup server (running amanda) crashed; unfortunately containing some dumps of file systems. after replacement of the disk (and using some other disks as holding disks) and some more backups made to disk (in degraded mode), an amflush now always reports: NOTES: amflush: /bak/amanda/coco/20020812: could not open working dir: No such file or directory amflush: fav._usr_openwin.1: disk fav:/usr/openwin not in database, skipping it. amflush: fav._.1: disk fav:/ not in database, skipping it. amflush: fav.c1t5d0s5.1: disk fav:c1t5d0s5 not in database, skipping it. amflush: fav._usr.1: disk fav:/usr not in database, skipping it. amflush: fav._var.1: disk fav:/var not in database, skipping it. amflush: fav._opt.1: disk fav:/opt not in database, skipping it. amflush: fav.c1t5d0s6.1: disk fav:c1t5d0s6 not in database, skipping it. amflush: Could not rmdir /big2/amanda/coco/20020812. Check for cruft. amflush: /big1/amanda/coco/20020812: could not open working dir: No such file or directory amflush: /bak/amanda/coco/20020816: could not open working dir: No such file or directory amflush: /big1/amanda/coco/20020816: could not open working dir: No such file or directory amflush: /bak/amanda/coco/20020819: could not open working dir: No such file or directory amflush: sheena.sdb2.0.1: ignoring cruft file. amflush: /big1/amanda/coco/20020819: could not open working dir: No such file or directory amflush: /bak/amanda/coco/20020820: could not open working dir: No such file or directory amflush: sheena.sdc1.0.1: ignoring cruft file. amflush: sheena.sdc1.0.2: ignoring cruft file. amflush: sheena.sdc1.0.3: ignoring cruft file. amflush: info.hdc2.0.1: ignoring cruft file. amflush: info.hdc2.0.2: ignoring cruft file. [...] directories above reported as missing really don't exist. does anybody know how to get rid of these messages ? I already tried to run amcheckdb, but it just reports Ready. tnx in advance.
connection refused on client ?!
Hi, we're using amanda now for several years to back up our servers, but since a few days we have a strange problem with one of our hosts: Amanda Backup Client Hosts Check WARNING: cmso: selfcheck request timed out. Host down? Client check: 14 hosts checked in 30.960 seconds, 1 problem found. the log- and debug files on cmso look like: /var/log/messages: Mar 25 14:18:32 cmso amandad[1275]: error receiving message: Connection refused Mar 25 14:18:32 cmso inetd[402]: /usr/sbin/tcpd (pid 1275): exit status 1 Mar 25 14:18:41 cmso amandad[1282]: error receiving message: Connection refused Mar 25 14:18:41 cmso inetd[402]: /usr/sbin/tcpd (pid 1282): exit status 1 Mar 25 14:18:51 cmso amandad[1288]: error receiving message: Connection refused Mar 25 14:18:51 cmso inetd[402]: /usr/sbin/tcpd (pid 1288): exit status 1 /tmp/amanda/amandad.debug: amandad: debug 1 pid 2073 ruid 202 euid 202 start time Mon Mar 25 14:39:49 2002 amandad: version 2.4.1p1 amandad: build: VERSION=Amanda-2.4.1p1 amandad:BUILT_DATE=Wed Feb 28 18:49:15 CET 2001 amandad:BUILT_MACH=Linux cmso 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown [...] got packet: Amanda 2.4 REQ HANDLE 000-005E0508 SEQ 1017063743 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR md3 0 OPTIONS |;bsd-auth;compress-best;no-record;index;exclude-file=/etc/exclude.gtar; GNUTAR md2 0 OPTIONS |;bsd-auth;compress-best;no-record;index;exclude-file=/etc/exclude.gtar; GNUTAR md1 0 OPTIONS |;bsd-auth;compress-best;no-record;index;exclude-file=/etc/exclude.gtar; GNUTAR md0 0 OPTIONS |;bsd-auth;compress-best;no-record;index;exclude-file=/etc/exclude.gtar; sending ack: Amanda 2.4 ACK HANDLE 000-005E0508 SEQ 1017063743 amandad: running service /usr/local/amanda/libexec/selfcheck amandad: error receiving message: Connection refused strage that the client gets a Connection Refused when receiving a message. During tests earlier this day I also got a message like received malformed ACK in the client's amandad.debug, but I can't reproduce this now. restarting the inetd doesn't help. unfortunately I can't reboot the machine right now. the tape server is located in the internal LAN behind a firewall doing NAT; the server to be backed up is located in the external LAN. this server also runs some rather heavy-weight JAVA application servers; the problem started when we installed another APPserver from HP (HP-AS). the HP-AS is not running now but the problem still persist. I guess that there's something wrong with the local ports, but I can't figure it out right now. OS is RedHat Linux 6.2, there are no local ipchains defined. Any ideas ? tnx in advance.
disk offline - addendum
sorry, I forgot OS is: SunOS fav 5.4 Generic_101945-43 sun4m sparc regards, rainer.
disk offline ?
Hi, After adding a new old server named fav to amanda, I keep getting the following message: FAILURE AND STRANGE DUMP SUMMARY: fav/home2 lev 0 FAILED [disk /home2 offline on fav?] It doesn't matter if the disk is specified by device file or mount directory: favc1t4d0s6tar-srv-low# /home2 fav/home2 tar-srv-low# /home2 backup works with all other disks: fav c1t5d0s5tar-srv-low# /home1 fav c1t2d0s6tar-srv-low# /mnt2 fav / tar-srv-low # / fav /usrtar-srv-low # /usr [...] mount reports: / on /dev/md/dsk/d0 read/write/setuid on Thu Dec 27 14:40:16 2001 /usr on /dev/md/dsk/d6 read/write/setuid on Thu Dec 27 14:40:16 2001 /proc on /proc read/write/setuid on Thu Dec 27 14:40:16 2001 /dev/fd on fd read/write/setuid on Thu Dec 27 14:40:16 2001 /var on /dev/md/dsk/d4 read/write/setuid on Thu Dec 27 14:40:16 2001 /tmp on swap read/write on Thu Dec 27 14:40:21 2001 /opt on /dev/md/dsk/d5 setuid/read/write on Thu Dec 27 14:40:21 2001 /usr/openwin on /dev/md/dsk/d3 setuid/read/write on Thu Dec 27 14:40:21 2001 /mnt1 on /dev/dsk/c1t5d0s6 setuid/read/write on Thu Dec 27 14:40:21 2001 /home2 on /dev/dsk/c1t4d0s6 setuid/read/write on Thu Dec 27 14:40:21 2001 /home1 on /dev/dsk/c1t5d0s5 setuid/read/write on Thu Dec 27 14:40:21 2001 /mnt2 on /dev/dsk/c1t2d0s6 setuid/read/write on Thu Dec 27 14:40:21 2001 I already had a look at the FAQ and I'm sure that: - the disk isn't to large (2 gigs total) - the file system isn't corrupted (fsck reports OK) - tar is used for backup, not dump. so there's the permission problem left, but I'm not really familiar with sun device files. after a quick look I had the impression that permissions are the same for all disk device files. tnx in advance. regards, rainer.
disk offline - addendum
sorry, I forgot OS is: SunOS fav 5.4 Generic_101945-43 sun4m sparc regards, rainer.
sender email address
Hi, is there a possibility to specify a different email address for the sender of amanda mails ? I.e. mails generated by amanda should have the From: address [EMAIL PROTECTED] and not [EMAIL PROTECTED]. tnx in advance.
re-index old tapes ?
Hi, When installing amanda, I set up a tape cycle of about 20 DAT2 tapes named TAPE01 to TAPE20. some months ago, I upgraded the streamer to DAT3, put the old DAT2 tapes away and labelled 20 new DAT3 tapes with the names TAPE01 to TAPE20. from the point of amanda's view, it was a seamless migration to the new dat drive/tapes. the problem is: I urgently need to restore files from the old DAT2 tapes which are, of course, no longer in the current amanda index. Is there a possibility to re-index such tapes, even if they have the same label as a current one ? is it wise to re-label the old tape to a different name or will re-labelling erase them ? tnx in advance.
selfcheck request timed out.
Hi, an internal server is running amanda to back up several external servers on it's DAT drive. between the amanda servers and the external servers is a firewall running linux ipfwadm w/ masquerading. since a reboot of the firewall, amanda reports selfcheck request timed out. for some (up to four) servers. some servers are never reported (they seem to repsond to the selfcheck request), the other servers change (i.e., servers a,b,c,d are reported to time out, 1 hour later servers c,d,e,f are reported to time out). on the timed out servers, /tmp/amandad.debug looks like this: amandad: debug 1 pid 26949 ruid 202 euid 202 start time Mon Jul 9 18:23:59 2001 amandad: version 2.4.1p1 amandad: build: VERSION=Amanda-2.4.1p1 amandad:BUILT_DATE=Sat Jul 15 01:09:15 CEST 2000 amandad:BUILT_MACH=OpenBSD shauna 2.7 GENERIC#25 i386 CC=gcc amandad: paths: bindir=/usr/local/amanda/bin amandad:sbindir=/usr/local/amanda/sbin amandad:libexecdir=/usr/local/amanda/libexec amandad:mandir=/usr/local/amanda/man amandad:CONFIG_DIR=/usr/local/amanda/etc/amanda amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/r amandad:DUMP=/sbin/dump RESTORE=/sbin/restore amandad:COMPRESS_PATH=/usr/bin/gzip amandad:UNCOMPRESS_PATH=/usr/bin/gzip MAILER=/usr/bin/Mail amandad: defs: DEFAULT_SERVER=shauna DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=shauna amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL DEBUG_CODE CLIENT_LOGIN=amanda amandad:FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=.gz amandad:COMPRESS_FAST_OPT=--fast COMPRESS_BEST_OPT=--best amandad:UNCOMPRESS_OPT=-dc got packet: Amanda 2.4 REQ HANDLE 001-606B0508 SEQ 994695840 SECURITY USER amanda SERVICE selfcheck OPTIONS ; DUMP sd1a 0 OPTIONS |;bsd-auth;srvcomp-best;index; DUMP sd0a 0 OPTIONS |;bsd-auth;srvcomp-best;index; sending ack: Amanda 2.4 ACK HANDLE 001-606B0508 SEQ 994695840 amandad: running service /usr/local/amanda/libexec/selfcheck amandad: sending REP packet: Amanda 2.4 REP HANDLE 001-606B0508 SEQ 994695840 OPTIONS ; OK sd1a OK sd0a OK /sbin/dump executable OK /sbin/restore executable OK /etc/dumpdates read/writable OK /dev/null read/writable OK /tmp has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: got ack: Amanda 2.4 REQ HANDLE 001-606B0508 SEQ 994695840 SECURITY USER amanda SERVICE selfcheck OPTIONS ; DUMP sd1a 0 OPTIONS |;bsd-auth;srvcomp-best;index; DUMP sd0a 0 OPTIONS |;bsd-auth;srvcomp-best;index; amandad: weird, it's not a proper ack addr: peer 13AC98C2 dup 13AC98C2, port: peer A4F1 dup A7F1 amandad: sending REP packet: Amanda 2.4 REP HANDLE 001-606B0508 SEQ 994695840 OPTIONS ; OK sd1a OK sd0a OK /sbin/dump executable OK /sbin/restore executable OK /etc/dumpdates read/writable OK /dev/null read/writable OK /tmp has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: waiting for ack: timeout, retrying amandad: got ack: Amanda 2.4 REQ HANDLE 001-606B0508 SEQ 994695840 SECURITY USER amanda SERVICE selfcheck OPTIONS ; DUMP sd1a 0 OPTIONS |;bsd-auth;srvcomp-best;index; DUMP sd0a 0 OPTIONS |;bsd-auth;srvcomp-best;index; amandad: weird, it's not a proper ack addr: peer 13AC98C2 dup 13AC98C2, port: peer A4F1 dup A8F1 amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, giving up! amandad: pid 26949 finish time Mon Jul 9 18:24:59 2001 amcheck needs approx. 1 minute to report these timeouts. any ideas what might be wrong ? I don't understand why the firewall settings which haven't change for some months suddenly don't seem to work any longer. tnx in advance.
dumps larger than tape
Hi, I'm using amanda now for quite a long time to backup 8 unix hosts on a 4 Gig DAT streamer (uncompressed). Over the course of time, data volume grew larger and now amanda permanently refuses to backup volume sdb1 on host sheena: sheena sdb1 lev 0 FAILED [dumps too big, but cannot incremental dump new disk] I submitted a "amadmin config force sheena sdb1" some days ago, but of no use. meanwhile, the last full backup of this volume has been overwritten in the tape rotation. [rfu@sheena rfu]$ df -k Filesystem 1024-blocks Used Available Capacity Mounted on /dev/sdb14307040 3719800 364340 91% /web1 sure this volume is quite close to 4 gigs, but compressed with gzip it has something about 2 gigs which should fit on a tape easily. is there any chance to get amanda to make a level 0 backup of this volume until our new 12 gig streamer gets delivered and installed ? would make me sleep better at night. thanks in advance.
