new with amanda
Good day everyone, I have just installed amanda and I have configured it. I want to backup my machine where I installed amanda. No clients yet. I have this error: # su amanda -c /usr/local/amanda/sbin/amcheck Daily Amanda Tape Server Host Check - ERROR: program /usr/local/libexec/planner: not executable ERROR: holding disk /usr/amanda: statfs: No such file or directory amcheck-server: could not get changer info: cannot create /usr/adm/amanda/changer-status-clean: directory nonexistent Amanda Backup Client Hosts Check ERROR: localhost: [host localhost.restricted.dyndns.org: port 1097 not secure] Client check: 1 host checked in 0.121 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) Here is my amanda.conf in /usr/local/etc/amanda/Daily http://restricted.dyndns.org/amanda.conf And here is my disklist in /usr/local/etc/amanda/Daily http://restricted.dyndns.org/disklist Right now, I only have 1 tape. Using dump utility is ok. I can dump my /usr and other fs on my FreeBSD 4.6-STABLE. Now, I would like to learn amanda. It think, my amanda.conf is not being read. I am sure that amandad is running using netstat -na. Here is the output of netstat: Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 0 0 *.10083*.*LISTEN tcp4 0 0 *.10082*.*LISTEN udp4 0 0 *.10080*.* So what mistake did I do or what step in the procedure did I miss? And also, can someone please fix my amanda.conf. I wanted in such a way that it will do full-backup every Saturday only. Again, I have only 1 tape for now. This is just for learning and eventually, implement it in production. Please help. Neil
fullbackup question
Hi, I'd like to set up a second set of tapes for making a full backup each sunday. My daily set with a set of 24 tapes is running from monday to saturday (dumpcycle 6 and tapecycle 24). For the weekly full backuo I have a set of 20 tapes. Amanda should write a full backup to each tape, so I have weekly full backups for the last 20 weeks. Is this the right configuration to force amanda to make a fullback each time: dumpcycle 0 tapecycle 20 maxcycle 0 Contab entry would be 0 8 * * 7 backup /usr/sbin/amdump DudeWeeklySet Thanks Marcus -- Marcus Schopen(0 P.O. Box 10 25 25 //\ Deutsche Zope User Group D-33525 Bielefeld V_/_www.dzug.org
Disk offline
I have just installed 2.4.2p2 on a few redhat 7.0 servers. All work great except 1. I get the following report after backup. FAILURE AND STRANGE DUMP SUMMARY: gator20.tr /home lev 0 FAILED [disk /var offline on gator20.triparish.net?] I get this on all directories on this server. The other servers backup fine. I have reinstalled both the backup server and all clients. I went over all the permissions and they are identical on all the client machines. Amcheck reports no errors and is happy. I upgraded tar to 1.13.25-1. I am at a total loss any help greatly appreciated. Thank you, Lewey Taylor Computer Sales Services, Inc. (985) 879-3219
amanda/iptables problem
I sometimes get sendsize packets being dropped by iptables, presumably because the iptables connection tracking decided the UDP connection was closed. This causes the estimates to take much longer because the first sendsize process gives up. Has anyone found a solution to this? Thanks, John Dalbec
Help with HP Ultrium 1/20 tapedev
Hi,
We just recently switched from older hp surestore DLT 3000 library to
one of the newer SureStore 1/20's with a Ultrium drive. I had amanda
working under the old setup just fine, on this new setup I can't seem
to get everthing up and running. I can run the test chg-zd-mtx from
the tpchanger and get no errors, plus I can load unload tapes using
mtx but the moment I try to run amtape DailySet1 command it just
hangs. Any ideas from anyone? (I've checked permissions ran
everything as root just to be sure, so it's not a permission issue).
Thanks for any help.
# cut from amanda.conf
tpchanger chg-zd-mtx
changerfile /etc/amanda/config/changer
tapedev /dev/nst0
changerdev /dev/sg16
tapetype Ultrium# what kind of tape it is (see
tapetypes below)
labelstr ^.*$ # label constraint regex: all tapes must match
# Actually tape label string is AA1234L1, AA1235L1, etc...
# Cut from changerfirstslot=1
lastslot=19
cleanslot=20
autoclean=0
autocleancount=999
havereader=1
offlinestatus=0
offline_before_unload=0
# Ultrium tape from amanda.conf
define tapetype Ultrium {
comment just produced by tapetype program
length 103998 mbytes
filemark 533 kbytes
speed 1912 kps
}
Re: Help with HP Ultrium 1/20 tapedev
On Tuesday 17 September 2002 11:12, Eiseg Feuer wrote:
Hi,
We just recently switched from older hp surestore DLT 3000 library
to one of the newer SureStore 1/20's with a Ultrium drive. I had
amanda working under the old setup just fine, on this new setup I
can't seem to get everthing up and running. I can run the test
chg-zd-mtx from the tpchanger and get no errors, plus I can load
unload tapes using mtx but the moment I try to run amtape
DailySet1 command it just hangs. Any ideas from anyone? (I've
checked permissions ran everything as root just to be sure, so
it's not a permission issue).
Thanks for any help.
# cut from amanda.conf
tpchanger chg-zd-mtx
changerfile /etc/amanda/config/changer
tapedev /dev/nst0
changerdev /dev/sg16
tapetype Ultrium# what kind of tape it is (see
tapetypes below)
labelstr ^.*$ # label constraint regex: all tapes must match
# Actually tape label string is AA1234L1, AA1235L1, etc...
# Cut from changerfirstslot=1
lastslot=19
cleanslot=20
autoclean=0
autocleancount=999
havereader=1
offlinestatus=0
offline_before_unload=0
# Ultrium tape from amanda.conf
define tapetype Ultrium {
comment just produced by tapetype program
length 103998 mbytes
filemark 533 kbytes
speed 1912 kps
}
Its possible that the new drive uses a diferent scenario for
accessing the drive vs the changer. Some use LUN 0 for the drive
and LUN 1 for the changer, and some will use a different scsi bus
address for the changer.
/var/log/dmesg might contain some clues about this, and you may
even have to rebuild amanda from the newest snapshot as the devices
used are compiled in.
Oh, and much of amanda will not allow itself to be run by root,
security measures and all that.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.15% setiathome rank, not too shabby for a WV hillbilly
Re: make w/ amanda ignoring DESTDIR
Hi Brandon, It works on IRIX with GNU make It doesn't works on IRIX with /sbin/make /sbin/make will works if you remove all the DESTDIR = line from the Makefile. The Makefile.in in amanda are build with automake-1.4, you could try with a more recent release off automake. The package you successfully build use which release of automake? Jean-Louis On Tue, Sep 17, 2002 at 12:47:19PM -0500, Brandon D. Valentine wrote: On Mon, 16 Sep 2002, Jean-Louis Martineau wrote: It works for me. Which release of make are you using, it must be gnu make? I'm using the SysV/POSIX make that comes with IRIX in /sbin/make. It works just fine to compile most GNU packages that use automake, including amanda. Everything works smoothly right up until I try to install to a temproot. It only wants to install in /usr/local irregardless of what I set DESTDIR to in the environment or on the make command line. Are you saying this works for you in general or specifically on an SGI? grep DESTDIR Makefile common-src/Makefile [snip] I have the same reference to DESTDIR in the Makefile.in Do you get them? I have an identical set of occurences of DESTDIR throughout Makefile and Makefile.in, yes. It's a pristine amanda source directory. From what I see in the amanda-hackers archives it looks like there were problems with amanda being DESTDIR clean in the past but that the patches which correct the problem were committed prior to 2.4.2p2, the version I am using. Thanks, -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED] -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: make w/ amanda ignoring DESTDIR
On Tue, 17 Sep 2002, Jean-Louis Martineau wrote: It works on IRIX with GNU make It doesn't works on IRIX with /sbin/make /sbin/make will works if you remove all the DESTDIR = line from the Makefile. Thanks, Jean. Your suggestion made me do some further digging. IRIX's make is among a handful of variants which do not allow command-line variable definitions to override those that preexist in the Makefiles. It seems like the solution to this that the GNU people took was to remove all instances of DESTDIR = from their Makefile.in's. Maybe I'll submit some patches to amanda-hackers to fix it. It's a niggling little bug but if a one-line patch to each of the Makefile.in's will fix it then it's worth people not running into the problem in the future. An explanation of the problem is here: http://sources.redhat.com/ml/bug-automake/1999/msg00267.html -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED]
Re: win32
--- In [EMAIL PROTECTED], JC Simonetti [EMAIL PROTECTED] wrote:
snip
Well... You're right, I got the actual state of the Sourceforge
project and did not touch to anything to the sources. Everything goes
well.
For your bugs :
1. selfcheck bug is not a bug, it's just that selfcheck is not
provided in the Win32 version. If you are suck with the amcheck
errors, do the same thing as me : selfcheck.c : int main() {return
0;}, and if you are lazy compiling such a thing, I've attached it
here.
2. sendsize crash ? Well... Er... Er... Er... Where ??? I've had
some problems with sendsize, but it corrected itself with the
-udp=10080 -no-exit parameters to the amandad.exe program. I did not
examine precisely the source code but the -no-exit seems to be very
important...
What I've done with this project? Well... Just got it from
Sourceforge and installed it on W2K boxes: what I've done is installed
it as a WinNT service. I am running it with an Amanda 2.4.3b2 server
on a Linux box, and no errors reported yet (1,5 Go backed up every
night). Not checked with omre recent versions.
--
Jean-Christian SIMONETTI email: [EMAIL PROTECTED]
SysAdmin Wanadoo Portails phone: (+33)493004911
Sophia Antipolis, France
--
Are you SURE there are no errors? I tested this yesterday. It
appears that sendbackup only logs the errors tothe debug file in
/tmp/amanda. Also, each sendbackup process overwrites this file.
It also appears that this doesn`t support excludes. Amandad reports
the standard exclude list path, but I couldn,t get it to work.
You previously mentioned that amanda maps the archive bit to the UNIX
execute bit. It is actually the win32 tar that does this. I believe
Samba also doed this to help preserve the Windows permissions.
This appears to be early alpha quality software, not ready for
production. Unfortunately, it also appears to be abandoned :-(
Bruce Osborne
mail2web - Check your email from the web at
http://mail2web.com/ .
Re: make w/ amanda ignoring DESTDIR
On Tue, Sep 17, 2002 at 02:14:43PM -0500, Brandon D. Valentine wrote: On Tue, 17 Sep 2002, Jean-Louis Martineau wrote: It works on IRIX with GNU make It doesn't works on IRIX with /sbin/make /sbin/make will works if you remove all the DESTDIR = line from the Makefile. Thanks, Jean. Your suggestion made me do some further digging. IRIX's make is among a handful of variants which do not allow command-line variable definitions to override those that preexist in the Makefiles. It seems like the solution to this that the GNU people took was to remove all instances of DESTDIR = from their Makefile.in's. Maybe I'll submit some patches to amanda-hackers to fix it. It's a niggling little bug but if a one-line patch to each of the Makefile.in's will fix it then it's worth people not running into the problem in the future. The patch is not useful, the Makefile.in are automaticaly generated from the Makefile.am by automake. I have build a new snapshot of amanda-2.4.3b4 with automake-1.5, this fixe the problem with IRIX make. The snapshot is at http://www.iro.umontreal.ca/~martinea/amanda/amanda-2.4.3b4-20020917-with-automake-1.5.tar.gz I would appreciate if many people try it, if it break nothing, I will use automake-1.5 to build the stable 2.4.3 Jean-Louis An explanation of the problem is here: http://sources.redhat.com/ml/bug-automake/1999/msg00267.html -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED] -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: amdump only to holding disk - how to do
On Tuesday 17 September 2002 12:20, Edwin Hakkennes wrote: Jon LaBadie wrote: On Fri, Sep 06, 2002 at 11:44:35AM +0200, Walter Willmertinger wrote: Is there any option to switch amdump only to dump to the (large enough) holding disk? We have the problem that our tape drive (Onstream ADR-50) has a I think everyone who has an Onstream does. frimware problem, as recognized by some people in this group, so that the normal way which amdump uses to write to teh tape, produces hardware errors, when reading the tape. The firmware has problems with the large breaks between writing different tape blocks, which is an usual feature of amanda. So I thought of 1. using amdump to produce the holding disk 2. after amdump has completely finished writing to the holding disk, to use amflush to save the whole thing on tape. This should work, because in this case the tape is written in one large amount without any break. Just leave the tape out, it will automatically collect on the holding disk. This assumes you have the reserve parameter (reserve for incrementals) set to a sufficiently low percentage. The default is 100 I think, meaning reserve the entire holding disk for incrementals. Hi Jon, You forgot to mention to run amflush config in the morning after sticking the tape in. This setup has been running succesfull here for 2 months now. And I also run amverify after each tape is written. Just to make sure In the meantine, I received an OnStream ADR^2 120 SCSI drive for testing purposes. This one works like a charm with Amanda. I use the ADR 50 for the daily backups and the ADR^2 120 for the weekly firebackup (offsite storage) Watch those OnStream ADR's carefully, the ADR-30 in particular has been discussed at length in somewhat less than glowing terms on this list previously. Jon, can you elaborate? My mind, whats left of it, just triggers on the name without any huge data recall. Seems like it was restore problems or some such... -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: make w/ amanda ignoring DESTDIR
On Tue, 17 Sep 2002, Jean-Louis Martineau wrote: I would appreciate if many people try it, if it break nothing, I will use automake-1.5 to build the stable 2.4.3 Thanks, Jean. I'll test the builds here on my IRIX and Linux machines and report back. I'll just hand edit the Makefiles to remove 'DESTDIR =' so I can get on with building my 2.4.2p2 packages since I'm waiting on the 2.4.3 stable release to move over to it in any more than a developmental environment. -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED]
Re: make w/ amanda ignoring DESTDIR
On Tue, 17 Sep 2002, Jean-Louis Martineau wrote: The patch is not useful, the Makefile.in are automaticaly generated from the Makefile.am by automake. I made one anyway in case I ever need to build 2.4.2p2 packages again on IRIX. It's only 8k so I've attached it for the archives in case anyone else finds it useful. -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED] diff -ru amanda-2.4.2p2.orig/Makefile.in amanda-2.4.2p2/Makefile.in --- amanda-2.4.2p2.orig/Makefile.in Tue Apr 3 14:55:47 2001 +++ amanda-2.4.2p2/Makefile.in Tue Sep 17 17:58:18 2002 @@ -32,8 +32,6 @@ includedir = @includedir@ oldincludedir = /usr/include -DESTDIR = - pkgdatadir = $(datadir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ Only in amanda-2.4.2p2/amplot: Makefile diff -ru amanda-2.4.2p2.orig/amplot/Makefile.in amanda-2.4.2p2/amplot/Makefile.in --- amanda-2.4.2p2.orig/amplot/Makefile.in Tue Apr 3 14:55:43 2001 +++ amanda-2.4.2p2/amplot/Makefile.in Tue Sep 17 18:01:55 2002 @@ -34,8 +34,6 @@ includedir = @includedir@ oldincludedir = /usr/include -DESTDIR = - pkgdatadir = $(datadir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ Only in amanda-2.4.2p2/amplot: amcat.awk Only in amanda-2.4.2p2/amplot: amplot.sh Only in amanda-2.4.2p2/changer-src: Makefile diff -ru amanda-2.4.2p2.orig/changer-src/Makefile.in amanda-2.4.2p2/changer-src/Makefile.in --- amanda-2.4.2p2.orig/changer-src/Makefile.in Tue Apr 3 14:55:43 2001 +++ amanda-2.4.2p2/changer-src/Makefile.in Tue Sep 17 18:02:06 2002 @@ -34,8 +34,6 @@ includedir = @includedir@ oldincludedir = /usr/include -DESTDIR = - pkgdatadir = $(datadir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ Only in amanda-2.4.2p2/changer-src: chg-chio.pl Only in amanda-2.4.2p2/changer-src: chg-chs.sh Only in amanda-2.4.2p2/changer-src: chg-manual.sh Only in amanda-2.4.2p2/changer-src: chg-mtx.sh Only in amanda-2.4.2p2/changer-src: chg-multi.sh Only in amanda-2.4.2p2/changer-src: chg-rth.pl Only in amanda-2.4.2p2/changer-src: chg-zd-mtx.sh diff -ru amanda-2.4.2p2.orig/client-src/Makefile.in amanda-2.4.2p2/client-src/Makefile.in --- amanda-2.4.2p2.orig/client-src/Makefile.in Tue Apr 3 14:55:44 2001 +++ amanda-2.4.2p2/client-src/Makefile.in Tue Sep 17 17:58:52 2002 @@ -34,8 +34,6 @@ includedir = @includedir@ oldincludedir = /usr/include -DESTDIR = - pkgdatadir = $(datadir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ Only in amanda-2.4.2p2/client-src: patch-system diff -ru amanda-2.4.2p2.orig/common-src/Makefile.in amanda-2.4.2p2/common-src/Makefile.in --- amanda-2.4.2p2.orig/common-src/Makefile.in Tue Apr 3 14:55:44 2001 +++ amanda-2.4.2p2/common-src/Makefile.in Tue Sep 17 17:59:03 2002 @@ -34,8 +34,6 @@ includedir = @includedir@ oldincludedir = /usr/include -DESTDIR = - pkgdatadir = $(datadir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ Only in amanda-2.4.2p2/common-src: genversion Only in amanda-2.4.2p2/common-src: genversion.h Only in amanda-2.4.2p2.orig/common-src: version.c Only in amanda-2.4.2p2.orig/common-src: versuff.c diff -ru amanda-2.4.2p2.orig/config/Makefile.in amanda-2.4.2p2/config/Makefile.in --- amanda-2.4.2p2.orig/config/Makefile.in Tue Apr 3 14:55:47 2001 +++ amanda-2.4.2p2/config/Makefile.in Tue Sep 17 18:02:16 2002 @@ -32,8 +32,6 @@ includedir = @includedir@ oldincludedir = /usr/include -DESTDIR = - pkgdatadir = $(datadir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ diff -ru amanda-2.4.2p2.orig/docs/Makefile.in amanda-2.4.2p2/docs/Makefile.in --- amanda-2.4.2p2.orig/docs/Makefile.inTue Apr 3 14:55:45 2001 +++ amanda-2.4.2p2/docs/Makefile.in Tue Sep 17 17:59:34 2002 @@ -32,8 +32,6 @@ includedir = @includedir@ oldincludedir = /usr/include -DESTDIR = - pkgdatadir = $(datadir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ diff -ru amanda-2.4.2p2.orig/example/Makefile.in amanda-2.4.2p2/example/Makefile.in --- amanda-2.4.2p2.orig/example/Makefile.in Tue Apr 3 14:55:45 2001 +++ amanda-2.4.2p2/example/Makefile.in Tue Sep 17 17:59:49 2002 @@ -34,8 +34,6 @@ includedir = @includedir@ oldincludedir = /usr/include -DESTDIR = - pkgdatadir = $(datadir)/@PACKAGE@ pkglibdir = $(libdir)/@PACKAGE@ pkgincludedir = $(includedir)/@PACKAGE@ diff -ru amanda-2.4.2p2.orig/man/Makefile.in amanda-2.4.2p2/man/Makefile.in --- amanda-2.4.2p2.orig/man/Makefile.in Tue Apr 3 14:55:45 2001 +++ amanda-2.4.2p2/man/Makefile.in Tue Sep 17 17:59:17 2002 @@ -34,8 +34,6 @@ includedir =
Re: amdump only to holding disk - how to do
On Tue, Sep 17, 2002 at 04:08:51PM -0400, Gene Heskett wrote: Watch those OnStream ADR's carefully, the ADR-30 in particular has been discussed at length in somewhat less than glowing terms on this list previously. Jon, can you elaborate? My mind, whats left of it, just triggers on the name without any huge data recall. Seems like it was restore problems or some such... No, did not follow the thread, sorry. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Amanda and ADIC tape library
Is anyone currently running amanda on solaris with an ADIC Tape library ? We have an ADIC Scalar 1000 here that I'd like to get working, any help appreciated. My big problems right now are with the output from mtx not being understood by amtape/amlabel etc... Also, does anyone have a good tapetype definition for Sony SDX-500C AIT2 tape drives ? Cheers, Al -- Alan C. Horn Inktomi - Unix Architect. +1-650-653-5436 [[EMAIL PROTECTED]]
Re: amanda/iptables problem
John Dalbec wrote: I sometimes get sendsize packets being dropped by iptables, presumably because the iptables connection tracking decided the UDP connection was closed. This causes the estimates to take much longer because the first sendsize process gives up. Has anyone found a solution to this? Thanks, John Dalbec I am currently running amanda through an iptables based firewall with no issues. I'm using Slack 8.1. Are you able to log the drops? =G=
Re: Amanda and ADIC tape library
On Tue, 17 Sep 2002, Alan Horn wrote: Is anyone currently running amanda on solaris with an ADIC Tape library ? Sorry, can't help you with the details. We have an ADIC Scalar 1000 here that I'd like to get working, any help appreciated. My big problems right now are with the output from mtx not being understood by amtape/amlabel etc... Are you using chg-zd-mtx or chg-mtx? Read TAPE.CHANGERS and make sure you've got the right mtx script for your version of mtx. If you're sure you're using the right mtx changer script then can you provide more details such as copy-and-pasted error messages from amtape/amlabel etc? Also, does anyone have a good tapetype definition for Sony SDX-500C AIT2 tape drives ? There is one in the FAQ-O-Matic at amanda.org IIRC. -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED]
Re: Amanda and ADIC tape library
On Tue, 17 Sep 2002, Brandon D. Valentine wrote: Date: Tue, 17 Sep 2002 20:18:54 -0500 From: Brandon D. Valentine [EMAIL PROTECTED] To: Alan Horn [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Amanda and ADIC tape library On Tue, 17 Sep 2002, Alan Horn wrote: We have an ADIC Scalar 1000 here that I'd like to get working, any help appreciated. My big problems right now are with the output from mtx not being understood by amtape/amlabel etc... Are you using chg-zd-mtx or chg-mtx? Read TAPE.CHANGERS and make sure you've got the right mtx script for your version of mtx. chg-zd-mtx. If you're sure you're using the right mtx changer script then can you provide more details such as copy-and-pasted error messages from amtape/amlabel etc? Sure : $ amtape test show amtape: could not get changer info: badly formed result from changer: 0 # 15 $ id uid=500(amanda) gid=3(sys) $ $ amlabel test testlabel001 slot 1 amlabel: could not load slot 1: illegal request I've also attached my amanda.conf and changer.conf for 'test' Cheers, Al -- Alan C. Horn Inktomi - Unix Architect. +1-650-653-5436 [[EMAIL PROTECTED]] ### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ### ### ### ### This file is not meant to be installed as is, and in fact, it ### ### WILL NOT WORK! You must go through it and make changes appropriate ### ### to your own situation. See the documentation in this file, in the ### ### man amanda man page, in the docs directory and at the Amanda### ### web page (www.amanda.org). ### ### ### ### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ### # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. # # If your configuration is called, say, csd, then this file normally goes # in /etc/amanda/csd/amanda.conf. # org test # your organization name for reports mailto [EMAIL PROTECTED] # space separated list of operators at your site dumpuser amanda # the user to run dumps under inparallel 4# maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h netusage 1000 mbps # maximum net bandwidth for Amanda, in MB per sec dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 25 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle ### ### ### # WARNING: don't use `inf' for tapecycle, it's broken! ### ### ### bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300# number of seconds per filesystem for estimates. #etimeout -600 # total number of seconds for estimates. # a positive number will be multiplied by the number of filesystems on # each host; a negative number will be taken as an absolute total time-out. # The default is 5 minutes per filesystem. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 20 # A positive integer telling taper how many 32k buffers to allocate. # WARNING! If this is set too high, taper will not be able to allocate # the memory and will die. The default is 20 (640k). # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. # Some tape changers require tapedev to be defined; others will use # their own tape device selection mechanism. Some use a separate tape # changer device (changerdev), others will simply ignore this # parameter. Some rely on a configuration file (changerfile) to # obtain more information about tape devices, number of slots, etc; # others just need to store some data in files, whose names will start # with changerfile. For
Re: Amanda and ADIC tape library
Alan Horn wrote: On Tue, 17 Sep 2002, Galen Johnson wrote: [cropping out a LOT of stuff :)...] what do you get when you run the mtx commands by hand? =G= I get expected output, I can move tapes around, load and unload, inventory.. etc... -- Alan C. Horn Inktomi - Unix Architect. +1-650-653-5436 [[EMAIL PROTECTED]] You may want to try the other chg-mtx script. and see if it tells you anything. Also, make sure you check your chg-mtx debug files that should give you some other clues... (=G=)
