Redo amdump
During this nigth, some machines crashed during the backup and I don't trust the backup that amanda have done. I think it could have taped garbage. How do I redo the amdump of this nigth, as it have never happened? Supose that it was labeled DailySet1-01 In trying to do that, I have amrmtape DailySet1-01. But whenever amdump started to run, it remember the backups it have done this nigth. So I deleted from the logs, the amdump and log files of this nigth. Now it forgets about the the backups of this nigth. I am not shure, but I think it is triyng to do too many level 0 backups. It is possible it is runing the full backups of this nigth and next nigth? I am running version 2.4.2 Jose Calhariz --
Re: [backup@avondel.nl: DailySet1 AMANDA MAIL REPORT FOR July 7, 2001]
On Sat, Jul 07, 2001 at 09:10:10 +0200, Erik van der Meulen wrote: Could someone please help me with a little advice on the interpretation of the attached Amanda log? I have been receiving this error for the second day in a row now. Thanks to those who responded. I decided to replace both tapes (amlabel -f) for new ones. Suppose they were old. I clean my drive regularly, it reports with a flashing light that it wants to be cleaned. Right now my amflush is running on the new tape, things seem to be cool! Thanks again. -- Erik van der Meulen [EMAIL PROTECTED]
Error: can not access sda1: No such file or directory
Hi I wonder if someone might be able to help me - I'm just struggling to install Amanda properly. I get the following strangeness when running amcheck : Amanda Backup Client Hosts Check ERROR: rajiv [can not access sda1 (sda1): No such file or directory] Client check: 1 host checked in 0.286 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) If anyone can help I'd be really grateful :-) Thanks Mike Mount output is: /dev/sda1 on / type ext2 (rw) none on /proc type proc (rw) /dev/sdb1 on /var/spool/mail type ext2 (rw) /dev/sdb2 on /home type ext2 (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) /dev/hda1 on /mnt/old-ide type ext2 (rw) Disklist is: rajiv sda1 always-full rajiv sdb1 always-full rajiv sdb2 always-full
RE: Permission denied Error
let me give this one a shot: first, make sure that the amanda account on the remote system (if that's what you're using) has an .amandahosts file in its home directory with the server host/user in it. second, make sure (on the remote host) that you make the necessary changes to /etc/hosts.allow and/or /etc/hosts.deny to allow access from the amanda server to the client (remote host). -edwin -Original Message- From: Travis Rail [mailto:[EMAIL PROTECTED]] Sent: Saturday, July 07, 2001 3:47 AM To: [EMAIL PROTECTED] Subject: Permission denied Error How do I give amanda access file systems on a remote host? I get this error when I run amcheck. ERROR: HOSTNAME: [can not access /dev/sdd1 (sdd1): Permission denied] Travi sRail
upgrading from DAT to DLT
hello, i'm sorry as this is definitely a newbie question, however, i don't have much experience with backup devices. i was recently appointed as UNIX admin here (no previous admins) and i began using my workstation with a 20/40 GB DAT drive as an amanda server to do simple network backups for a few of the mission-critical boxes (just to get something going). however, now i'd like to get serious and plug in the PowerStor L200 drive (8 DLT Tapes) someone here bought over a year ago that's just been sitting around and start doing some real backup stuff. my question is, however, what would be the device name for the multi-tape changer under linux. will it remain /dev/[n]st0 or will it change to something else? again, sorry this is so basic. does anyone else have an L200 that would possibly be willing to post their chg-multi settings (or not)? thanks in advance for any assistance. Highest Regards, Edwin R. Rivera UNIX Administrator Tel: +1 305 894 4609 Fax: +1 305 894 4799 [EMAIL PROTECTED]
RE: chg-scsi
I would like a copy. Thanks, Rob -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John R. Jackson Sent: Saturday, July 07, 2001 11:50 AM To: Amanda-Users Subject: Re: chg-scsi Does anyone know why the chg-scsi would be missing from the libexec directory? ... Sigh. My guess would be a problem with a GNU tool we use called automake. I'll see if I can track it down, but it's all black art to me. FWIW, I've upgraded my copy of automake (which was a bit of an adventure in itself) and the latest and greatest version fixes the problem that caused chg-scsi to not be installed. If anyone needs an updated Makefile.in, just ask and I'll make it available. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: Upgrade to 2.4.2p2 client generages dumps way too big message
Check your tape definition. I found the HP def to be too small for the DDS3 I was using. Fixed it and all backed up well. bryan Bryan S. Sampsel Systems Administrator Ambeo, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Oscar Ricardo Silva Sent: Sunday, July 01, 2001 12:08 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Upgrade to 2.4.2p2 client generages dumps way too big message I noticed that 2.4.2p1 had a problem on some Linux machines (associating /dev/root with /) and saw that this had been fixed in 2.4.2p2. I upgraded the client portion of Amanda on all my backup targets so as to have on consistent version. Unfortunately, right after I did that, I got the following after one backup run: FAILURE AND STRANGE DUMP SUMMARY: cba-ar.gw. /var lev 0 FAILED [dumps too big, but cannot incremental dump new disk] ser11-ar.g /var lev 0 FAILED [dumps too big, but cannot incremental dump new disk] cba-ar.gw. / lev 0 FAILED [dumps too big, but cannot incremental dump new disk] ser11-ar.g / lev 0 FAILED [dumps too big, but cannot incremental dump new disk] cba-ar.gw. /usr lev 0 FAILED [dumps too big, but cannot incremental dump new disk] emissary.o /boot lev 1 FAILED [dumps way too big, must skip incremental dumps] utar3.gw.u /boot lev 1 FAILED [dumps way too big, must skip incremental dumps] scuff.cc.u /boot lev 1 FAILED [dumps way too big, must skip incremental dumps] utar2.gw.u /boot lev 1 FAILED [dumps way too big, must skip incremental dumps] egi.utsyst /usr/ports lev 1 FAILED [dumps way too big, must skip incremental dumps] agnes.ots. / lev 1 FAILED [dumps way too big, must skip incremental dumps] cybill.gw. /home lev 1 FAILED [dumps way too big, must skip incremental dumps] emissary.o / lev 1 FAILED [dumps way too big, must skip incremental dumps] noc.the.ne / lev 1 FAILED [dumps way too big, must skip incremental dumps] mpd.ots.ut / lev 1 FAILED [dumps way too big, must skip incremental dumps] egi.utsyst / lev 1 FAILED [dumps way too big, must skip incremental dumps] gatekeeper / lev 1 FAILED [dumps way too big, must skip incremental dumps] dnscache1. / lev 1 FAILED [dumps way too big, must skip incremental dumps] and more ... This was not the case for all my clients though, some did get backed up. The clients have file systems with sizes ranging from 4GB to 18GB so none are too big. All my backups had been running fine before the upgrade. Any thoughts as to what could be causing this? This is the second night in a row that these errors have been generated. Any information would be appreciated. Oscar
Change Amanda Client
Hi, I am running amanda-2.3.0.4. Does anyone who knows how to change amanda clients. Such as delete an existing client and add another new client. Backup server is Solaris 2.6 (Ultra 60), the client needs to be removed is Solaris 2.6(Ultra 30) and the client needs to be added is Solaris 2.8(Ultra 80). Thanks
Samba
Hi , I am new to amanda back up , I joined a firm 1 week back, They are running amanda-2.4.2p1 backup s/w on their Linux/solaris/BSD (unix) environment. We have few NT machines which needs to be included with the Amanda backup.. I heard that Loading Samba on win2k unix boxes, and configuring amanda will enable to take backup of both win2k and unix servers.. If someone have done the same thing , can u guide me with the correct procedure..? Thanks Rajesh.
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.
somehow the .rhosts file was deleted
All the more reason to have amanda complain about access problems! Thanks to all of you for your responses. You were right about not trusting their answers. :-) -- Denise E. [EMAIL PROTECTED] Systems Engineer734.822.2037 Download the free WALID WorldConnect software and start using ML.ML domain names today. http://www.walid.com
Re: changer problems
exact same problem: [amanda@bserver fontenot]$ mtx --version mtx version 1.2.13 [amanda@bserver fontenot]$ mtx status Storage Changer /dev/changer:2 Drives, 11 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Data Transfer Element 1:Empty Storage Element 1:Full Storage Element 2:Full :VolumeTag= Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full :VolumeTag= Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full :VolumeTag= Storage Element 11:Full This is an ExaByte EXB-210 library with one 8mm tape drive, no barcode reader. The chg-scsi in 2.4.2p2 and 2.5.0 cvs does not work right with this changer - after loading 10th tape won't do anything else (yes, I have gravity set to 0) - so I switched to mtx which controls the changer great. Unfortunately, of the three(!) chg-mtx type scripts now at my disposal - two come with amanda, one with mtx - NONE of them work right. Between chg-scsi not working and this problem, amanda is taking me a lot longer to get going than it should. I also lost a day because the cvs version of amlabel does not report errors like the 2.4.2p2 version does - it did not give me the sense errors so I had no way of knowing that it was failing due to bad tapes. Once I reverted to 2.4.2p2 that problem became obvious. Dwayne ., John R. Jackson [EMAIL PROTECTED] wrote: Still I have problems with amanda 2.4.2p2 and my changer. I got the error amcheck-server: could not get changer info: badly formed result from changer: /usr/local/libexec/chg-zd-mtx: [: -eq: unary operator expected What version of mtx are you using? What does mtx -f /dev/sga status have to say (in particular, the Data Transfer Element lines)? Sandra John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
