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
> /-- 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: still problem during dump: "missing result" reported
Dear Chris, dear John, > > > What do you have maxduumps set to? Maybe increasing or decreasing it > > > for this one host will help. > > increasing maxdumps did not help. Again I got > > > > adler / lev 0 FAILED [missing result for / in adler response] > > > > this night for the 33rd filesystem on adler. :-( > > No more ideas. It was just a sort of vain hope that changing maxdumps > would help. Maybe the problem is with the size of the packet being > exchanged with the adler host. Can you play with your disklist and > combine any of your filesystems using gnutar) to get you down to 32? I tried to get some hints from amanda by digging through the source code. I found out, that the disklist itself is read in correctly (all entries are present in the program's C structure). Looking a little bit further revealed the problem: The amanda server issues the sendsize command to the clients (asking for sizes for level0 and level1 dumps in this case). This question is passed on via some protocol to the client (in this case adler). On the client side in sendsize program there is a loop reading in from (stdin), the daemon somehow I assume. The last line I get here while reading is truncated (even in case I back up 32 filesystems here; the exclude=file information is truncated which I can also see in the logfile later). The command for getting required sizes simply is too long! This also fits well with the error I get: adler does not compute the dump sizes for those filesystems it does not see. And amanda server is wondering why there are no answers for these filesystems -> "missing result". I saw that this is a known problem when searching through the amanda-hackers archive at egroups. There should be a patch available; in fact John already supplied me with this patch and I tried it, but it did not work. Maybe I got a broken version of the patch?? John, could be please check this again? Kind regards, Urte -- \|/ @ @ ---oOO-(_)-OOo- Urte Fuerst _/_/ _/ _/_/_/ German Aerospace Center DLR _/ _/_/ _/_/ _/ _/ _/ _/_/ Institute of Aeroelasticity _/_/ _/ _/ _/_/ Bunsenstrasse 10 _/_/ _/ _/_/D - 37073 Goettingen _/_/ _/ _/ _/Phone: +49 (0)551 709 2432 _/ _/ _/ _/_/ Fax:+49 (0)551 709 2862 _/_/_/_/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
Re: ERROR amandad busy
> I assume the hanging dumps are on the linux box playing amanda server. > What version are you using? You should use the lastest & greatest. Hm, maybe I wasn't clear. The server is Solaris. I have all other Solaris clients; this is my first Linux client. I am using 2.4.2p2. > 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 RedHat 7.1 install... thanks for any clues. Lynette Bellini Systems Administrator University of Minnesota
Re: Redhat 7.1 troubles
I would like to thank everybody for their replies. Changing my wait =
no to wait = yes in xinetd.d/amanda did the trick.
Jennifer Peterson wrote:
> Hi,
>
> I wonder if anybody can help me out with this problem. I installed
> amanda-client-2.4.2p2-1.i386.rpm on my Redhat 7.1 box, and I have
> amandad running through xinetd like so:
> service amanda
> {
> socket_type= dgram
> protocol= udp
> wait= no
> user= amanda
> group= disk
> server= /usr/lib/amanda/amandad
> disable= no
> groups = yes
> only_from = "backup_computer"
> }
>
> When I restart xinetd, the amanda service starts up just fine, and when
> I amcheck from my backup computer, no errors are reported. However,
> after about 20 minutes or so, I get this in my syslog:
>
> Oct 22 15:24:11 my_computer xinetd[29480]: amanda service was
> deactivated because of looping
> Oct 22 15:24:41 my_computer amandad[30051]: error receiving message:
> timeout
>
> The amandad error log on my_computer reads basically the same thing:
> amandad: dgram_recv: timeout after 30 seconds
> amandad: error receiving message: timeout
>
> At this point amcheck also fails.
>
> If I restart xinetd right before the backup begins, then the backup works.
>
> Any suggestions?
>
> Thanks,
>
> Jenn Peterson
>
>
Re[2]: 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. BRE> What program do you use to backup? Did you run it by hand, i.e. in the BRE> same way amanda calls it (look at /tmp/amanda/sendbackup*debug)? /-- 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]
Re: Freebsd not starting amandad
> I added the last argument, the name of the program, and restarted inetd, but > it still didn't work. It still timed out. The netstat -an | grep 10080 had > this output: > tcp4 0 0 *.10080*.*LISTEN > > The /etc/services had these lines: > amanda 10080/udp #Dump server control > amandaidx 10082/tcp #Amanda indexing > amidxtape 10083/tcp #Amanda tape indexing > > ...Doesn't the amanda service run as udp? Why does the netstat have the > 10080 port as a tcp service? Don't know much about FreeBSD, but amandad should run on UDP 10080. You might check with lsof who is listening on TCP 10080. $ netstat -an | grep 10080 udp0 0 0.0.0.0:10080 0.0.0.0:*
Re: NEWBIE> Configuring Amanda w/ DAT drive
> I would like to start using amanda to handle backups on my lan. > However, I am not sure how to handle it. I have a 4MM Dat drive w/ 4 > tape library (Archive DAT). Can amanda be configured to support each of > the 4 tapes individually or is it limited to only treat it as one 16GB > logical tape? Amanda should use each of the four tapes in a single run. Look at "changer support" and probably mtx for controlling the changer.
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: still problem during dump: "missing result" reported
Urte Fuerst wrote: > > > What do you have maxduumps set to? Maybe increasing or decreasing it > > for this one host will help. > increasing maxdumps did not help. Again I got > > adler / lev 0 FAILED [missing result for / in adler response] > > this night for the 33rd filesystem on adler. :-( No more ideas. It was just a sort of vain hope that changing maxdumps would help. Maybe the problem is with the size of the packet being exchanged with the adler host. Can you play with your disklist and combine any of your filesystems using gnutar) to get you down to 32? -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
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: EZ-17 + M2 + chg-zd-mtx = amcheck problems
Thanks to everybody who helped me.
It turns out I did not label my tapes properly. So now I know how to label
them... It should be great to get faq-o-matic back on-line again !
Claude.
Claude Lefrancois wrote:
[EMAIL PROTECTED]">Hello,
I am new to Amanda. I have an Exabyte EZ17 Autoloader (Mammoth2) with AME225
cartridges. The tape is connected to a Redhat Linux 6.2 system with an Adaptec
7899 U160 on-board SCSI controller. The SCSI driver identifies the tape
and the changer correctly.
I have installed Amanda-2.4.2p2 and mtx-1.2.13. From the command line, I
can control the changer with mtx (unload, load x, status). With mt, I can
control the tape (rewind, fsf, offline, status, etc.). I had successfully
used dump/restore with this tape.
Now, I try to configure Amanda. I have the following output from the amcheck
command:
[root@lmcpc111335 /root]# su amanda -c "amcheck DailySet1"
Amanda Tape Server Host Check
-
Holding disk /var/tmp: 3873928 KB disk space available, using 2849928
KB
amcheck-server: slot 1: not an amanda tape
amcheck-server: slot /usr/lib/amanda/chg-zd-mtx:: no tape online
amcheck-server: slot /usr/lib/amanda/chg-zd-mtx:: no tape online
amcheck-server: slot /usr/lib/amanda/chg-zd-mtx:: no tape online
amcheck-server: slot /usr/lib/amanda/chg-zd-mtx:: no tape online
amcheck-server: slot /usr/lib/amanda/chg-zd-mtx:: no tape online
amcheck-server: slot /usr/lib/amanda/chg-zd-mtx:: no tape online
ERROR: new tape not found in rack
(expecting a new tape)
NOTE: skipping tape-writable test
NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist
NOTE: it will be created on the next run
Server check took 268.382 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.043 seconds, 0 problems found
(brought to you by Amanda 2.4.2p2)
I can ear/see the changer going through each cartridges and say "no tape
online". Any ideas ?
Can somebody tell me why I get "not an amanda tape" and "no tape online"
messages ?
I am using the following tapelist which I have found in the mailing list:
define tapetype M2-AME225 {
comment "Exabyte EZ17 Mammoth2"
length 57487 mbytes
filemark 0 kbytes
speed 11765 kbytes
}
Can somebody confirm me this is OK ? since the faq-o-matic system is down
and I cannot validate this information.
Thanks a lot for your help,
Claude.
--
Claude LeFrançois
Packet Core Network (LMC/XP/DG)
Ericsson Canada Inc.
Tel: +1 (888) 345-7900 x7579
Fax: +1 (514) 345-5837
Mailto:[EMAIL PROTECTED]
Re: every 10 days amanda fails
=?iso-8859-1?Q?gloria_era=F1a?= wrote: > > I've been noticing that our amanda backup fails every 10 days and stop to > backup our main server. Can someone point me why I'm getting this? I'm not > very familiar with amanda and we rely on someone's script for our backup > which makes it more complicated. I would appreciate for any help. Thanks. Is your dumpcycle 10? Does your disklist specify a 10-day cycle for any particular drives (actually a special dumptype specified in amanda.conf)? I expect there's some disk that's getting a full backup every 10 days and there's a problem with it or the connectivity to that computer). -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
NEWBIE> Configuring Amanda w/ DAT drive
Hello, I would like to start using amanda to handle backups on my lan. However, I am not sure how to handle it. I have a 4MM Dat drive w/ 4 tape library (Archive DAT). Can amanda be configured to support each of the 4 tapes individually or is it limited to only treat it as one 16GB logical tape? TIA -- John C. Wingenbach
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 "? 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).
data timeout
Hi, 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. any ideas ? thanks claus
Freebsd not starting amandad
Hi, 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? Thanks, Lalo -- Lalo Castro CNS McHenry Library UC Santa Cruz
indexes
Hi 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. 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? I'va attached amanda.conf file from amanda serwer Thanks fro your help Greetings Marek ### !!! 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 /usr/local/etc/amanda/csd/amanda.conf. # org "DailySet1" # 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 6 Kbps# maximum net bandwidth for Amanda, in KB per sec dumpcycle 2 weeks # the number of days in the normal dump cycle runspercycle 0 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 1 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 more information about individual tape # changers, read docs/TAPE.CHANGERS. # At most one changerfile entry must be defined; select the most # appropriate one for your configuration. If you select man-changer, # keep the first one; if you decide not to use a tape changer, you may # comment them all out. runtapes 1 # number of tapes to be
exclude list question
Hello,
I have a question about exclude lists:
If my dumptype looks like:
define dumptype test {
program "GNUTAR"
comment "test"
priority medium
exclude list "/etc/amanda/ConfDir/exclude"
}
I get the following process on the client:
25496 ?R 0:03 /bin/tar --create --directory /usr
--listed-incremental /var/lib/amanda/gnutar-lists/hostname.sda5_0.new
--sparse --one-file-system --ignore-failed-read --totals --file /dev/null
--exclude-from=/etc/amanda/ConfDir/exclude .
Which is what I expect to see, but if I attempt to use a directory that
begins with a dot "." it does not work:
For example new dump type:
define dumptype test {
program "GNUTAR"
comment "test"
priority medium
exclude list ".amexclude/exclude"
}
Produces the following on the client:
5763 ?R 0:00 /bin/tar --create --directory /usr
--listed-incremental /var/lib/amanda/gnutar-lists/hostname.sda5_0.new
--sparse --one-file-system --ignore-failed-read --totals --file /dev/null
.
Any ideas?
TIA.
Andrew
RE: Question on level 0 dumps
Richard, You are able to set up your disklist in such a way that you can control the size of each filesystem that will be dumped. You do not have to backup by disk or partition. You can backup by individual directories. For example, here is a section of my disklist file: ### AIX on SBS sbs / root-tar sbs /usr root-tar sbs /home root-tar ### Gemini on SBS sbs /gemini/disk1/d0 gemini-full-high sbs /gemini/disk1/d1 gemini-full-high sbs /gemini/disk1/d5 gemini-full-high sbs /gemini/disk1/laisys gemini-inc-low sbs /gemini/disk1/obj gemini-inc-low sbs /gemini/disk1/sys gemini-inc-low sbs /gemini/disk2/d2 gemini-full-high sbs /gemini/disk2/d7 gemini-full-med Now even though our /gemini filesystem is 40GB, I am able to backup fine by specifying subdirectories in my disklist. I hope this helps you out! Anthony Valentine -Original Message- From: Morse, Richard E [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 5:29 AM To: '[EMAIL PROTECTED]' Subject: Question on level 0 dumps Hi! I would like to start using Amanda to back up a small LAN I have, consisting mainly of Solaris 2.6 machines (+ 1 NT box, although that can wait, and 1 RedHat 7 box). The machine that I intend to use as a host is an older SPARCstation 2, which has two tape drives attached -- a DDS3 drive and an older EXAbyte drive. I understand that the tapes that I use, since Amanda can't use both drives, need to be able to handle a level 0 dump from any of the machines. What I'm wondering is, does the level 0 dump have to be unbroken across the entire machine, or does Amanda schedule by partitions? That is, most of the machines use have somewhere between 4 and 8 gigs of data on them, which cannot fit on one of the EXAbyte tapes. However, none of their partitions are larger than about 3 gigs, which would fit on one of the tapes. So what I'm wondering is if Amanda schedules backups on the partition level or on the host level. Just in case you're wondering why I want to use the EXAbyte tapes, it's because I have about 100+ of them, whereas I only have around 20 of the DDS3 tapes, and although I will be buying more, I'm wondering if I can get way with the EXAbyte tapes for a while... Thanks muchly, Ricky Morse - Richard Morse Systems Administrator, MGH Biostatistics Research [EMAIL PROTECTED] <-> 617 724 9830
Re: DUMP program not found
Hi Bernhard! On 23 Oct 01 at 8:22 you wrote: > do "make distclean" or "rm config.cache" before you rerun configure Thanks. I should have figured that one out myself. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * What are you looking down here for? Read the message!
multiboot hosts
Sorry if this was also included in a garbage message. I've got to learn how to use this mail reader :)) I'm just brainstorming at the moment. My laptop is setup to multiboot; three OS's, Win2K, RH 7.1, and Solaris 8. None are being backed up by amanda at the moment. I'm wondering how best to get it (the laptop) and them (the 3 os's) into a backup system that expects a host to be on the network at dump time and have the same os and directory organization each time a dump is done. Any ideas or experiences welcome. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing [EMAIL PROTECTED] 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
ERROR amandad busy
Hi all, In order of what I am hoping to accomplish: 1) get amanda to back up the troubled client again 2) kill the wedged dump processes The nitty gritty: I have approximately 15 solaris clients running amanda. I recently set up a Linux box as an amanda client. It ran correctly for the first two runs, doing a level 0 first, and then a level 1 (as expected). I use a separate FullSet tapeset to capture all fullsets on the weekend, and that failed: tetris /dev/md2 lev 0 FAILED [Request to tetris timed out.] When I resumed the regular DailySet on Monday, I got: tetris /dev/md2 lev 0 FAILED [tetris NAK: amandad busy] There appeared to be amanda processes lurking from the FullSet failure, and I manually killed them. Since then, amanda has failed on every run with the "amandad busy" message. 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. tetris is running kernel: 2.4.3-12smp glibc: glibc-2.2.2-10 tar: tar-1.13.19-4 (Having seen some notes in the archives about potential tar core dumps with the Kernel/glibc combo I have, I verified the version of tar.) Here are my most recent *.debug out of /tmp/amanda on the machine: sendsize: debug 1 pid 12579 ruid 650 euid 650 start time Mon Oct 15 23:59:14 2001 /usr/local/amanda-2.4.2p2/libexec/sendsize: version 2.4.2p2 calculating for amname '/dev/md2', dirname '/home' sendsize: getting size via dump for /dev/md2 level 0 sendsize: running "/sbin/dump 0Ssf 1048576 - /dev/md2" running /usr/local/amanda-2.4.2p2/libexec/killpgrp killpgrp: debug 1 pid 12580 ruid 650 euid 0 start time Mon Oct 15 23:59:14 2001 /usr/local/amanda-2.4.2p2/libexec/killpgrp: version 2.4.2p2 sending SIGTERM to process group 12580 it won't die with SIGTERM, but SIGKILL should do do't expect any further output, this will be suicide amandad: debug 1 pid 12578 ruid 650 euid 650 start time Mon Oct 15 23:59:14 2001 amandad: version 2.4.2p2 amandad: build: VERSION="Amanda-2.4.2p2" amandad:BUILT_DATE="Tue Oct 9 13:59:33 CDT 2001" amandad:BUILT_MACH="Linux tetris.software.umn.edu 2.4.3-12smp #1 SMP Fri Jun 8 14:38:50 EDT 2001 i686 unknown" amandad:CC="gcc" amandad: paths: bindir="/usr/local/amanda-2.4.2p2/bin" amandad:sbindir="/usr/local/amanda-2.4.2p2/sbin" amandad:libexecdir="/usr/local/amanda-2.4.2p2/libexec" amandad:mandir="/usr/local/amanda-2.4.2p2/man" amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" amandad:CONFIG_DIR="/usr/local/amanda-2.4.2p2/etc/amanda" amandad:DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/" DUMP="/sbin/dump" amandad:RESTORE="/sbin/restore" GNUTAR="/bin/gtar" amandad:COMPRESS_PATH="/bin/gzip" UNCOMPRESS_PATH="/bin/gzip" amandad:MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/usr/local/amanda-2.4.2p2/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="moby" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="moby" amandad:DEFAULT_TAPE_DEVICE="/dev/nrst28" HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" got packet: - Amanda 2.4 REQ HANDLE 00D-0008D618 SEQ 1003208113 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=tetris; DUMP /dev/md2 0 1970:1:1:0:0:0 -1 DUMP /dev/md2 1 2001:10:10:3:36:15 -1 DUMP /dev/md2 2 2001:10:12:3:54:24 -1 - sending ack: - Amanda 2.4 ACK HANDLE 00D-0008D618 SEQ 1003208113 - bsd security: remote host moby.jaws.umn.edu user amanda local user amanda amandahosts security check passed amandad: running service "/usr/local/amanda-2.4.2p2/libexec/sendsize" amandad: got packet: - Amanda 2.4 REQ HANDLE 00D-00090DD0 SEQ 1003287366 SECURITY USER root SERVICE selfcheck OPTIONS ; DUMP /dev/md2 0 OPTIONS |;bsd-auth;compress-fast;index; - amandad: received other packet, NAKing it addr: peer 134.84.132.41 dup 134.84.132.41, port: peer 936 dup 782 sending nack: - Amanda 2.4 NAK HANDLE 00D-00090DD0 SEQ 1003287366 ERROR amandad busy - amandad: got packet: - Amanda 2.4 REQ HANDLE 00D-0008BDA8 SEQ 1003287913 SECURITY USER amanda SERVICE sendsize OPTIONS maxdumps=1;hostname=tetris; DUMP /dev/md2 0 1970:1:1:0:0:0 -1 DUMP /dev/md2 1 2001:10:10:3:36:15 -1 DUMP /dev/md2 2 2001:10:12:3:54:24 -1 - amandad: received other packet, NAKing it addr: peer 134.84.132.41 dup 134.84.132.41, port: peer 936 dup 788 sending nack: - Amanda 2.4 NAK HANDLE 00D-0008BDA8 SEQ 1003287913 ERROR amanda
I moved my tape drive and library from one machine to another, andI upgraded, and now I have problems with mtx
Hi. I moved my tape drive from one machine to another, and I upgraded from 2.4.1 to 2.4.2p2 and I have problems with mtx. truk!backup 11# amcheck -s daily Amanda Tape Server Host Check - WARNING: holding disk /bkup: only 46879560 KB free (65536000 KB requested) amcheck-server: slot 6: not an amanda tape amcheck-server: fatal slot 7: Unloading Data Transfer Element into Storage Element 6...mtx: Request S ense: Long Report=yes ERROR: label daily-046 or new tape not found in rack (expecting tape daily-046 or a new tape) NOTE: skipping tape-writable test NOTE: info dir /usr/local/share/amanda/curinfo/umtanum/_: does not exist WARNING: info file /usr/local/share/amanda/curinfo/spinoza/__iona_C/info: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/spinoza/__kauai_C: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__dosbox_C: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__beagle2_C: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__hbfd_D: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__hbfd_C: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__ach_F: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__ach_E: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__ach_D: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__blake-pc_C: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__video-pc_F: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__video-pc_E: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__video-pc_D: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/tropomyosin/__video-pc_C: does not exist NOTE: info dir /usr/local/share/amanda/curinfo/truk/__bikini_C: does not exist WARNING: info file /usr/local/share/amanda/curinfo/truk/__tasmania_D/info: does not exist WARNING: info file /usr/local/share/amanda/curinfo/truk/__tasmania_C/info: does not exist Server check took 8.073 seconds (brought to you by Amanda 2.4.2p2) truk!backup 7# /usr/local/pkgs/amanda-2.4.2p2/libexec/chg-zd-mtx-2.4.2p2 -info /usr/local/pkgs/amanda-2.4.2p2/libexec/chg-zd-mtx-2.4.2p2: [: : integer expression expected /usr/local/pkgs/amanda-2.4.2p2/libexec/chg-zd-mtx-2.4.2p2: [: -lt: unary operator expected 22 1 truk!backup 8# truk!backup 8# mtx -f /dev/tape-changer status Storage Changer /dev/tape-changer:1 Drives, 23 Slots ( 1 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full Storage Element 8:Full Storage Element 9:Full Storage Element 10:Full Storage Element 11:Full Storage Element 12:Full Storage Element 13:Full Storage Element 14:Full Storage Element 15:Full Storage Element 16:Full Storage Element 17:Full Storage Element 18:Full Storage Element 19:Full Storage Element 20:Full Storage Element 21:Full Storage Element 22:Full Storage Element 23 IMPORT/EXPORT:Full truk!backup 9# Any suggestions? My amanda.conf file is: org "RCS Backup System" # your organization name for reports mailto "admin" # space separated list of operators at your site dumpuser "backup" # the user to run dumps under inparallel 4# maximum dumpers that will run in parallel netusage 8000 Kbps # maximum net bandwidth for Amanda, in KB per second # increased from 1800 Kbps 2000-10-29 JHS # increased from 5000 Kbps to 8000 Kbps 2001-06-29 JHS # See http://www.backupcentral.com/amanda-10.html for details. dumpcycle 14 days # the number of days in the normal dump cycle runspercycle 14 # the number of amdump runs in dumpcycle days # (2 weeks * 7 amdump runs per week ) tapecycle 45 tapes # the number of tapes in rotation # Then, I changed it to 50 because that's how many tapes I have. # Keep 22 tapes in the changer, at least 14 of which are recent backups # Not more than 8 of which are old tapes to be backed up # The remaining 28 tapes are off site backup, or 6 weeks of archival storage # 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 10800 # number of seconds per filesystem for estimates. # increased from 2400 seconds 2000-12-22 because spinoza # keeps timi
Re: Amanda 2.4.2p2, Solaris 8, amandad "hangup"
Bernhard, We had successful backup of all systems except the 2.6 box last night, it was a file protection problem on the /usr/local/libexec directory (yassp over-tighened security for us). The 2.6 box no longer mounts the 2.8 system's /usr/local and instead has an installation of the previously built (and fortunately archived) 2.4.1p1 which did return proper results when checked by the 2.8 box's 2.4.2p2 amanda server. Tonight will tell us if dumps will actually run correctly. Thanks for your help, at this point it looks like we're back in business. thanks, Brian > > 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: Redhat 7.1 troubles
On Tue, 23 Oct 2001, Jennifer Peterson wrote: >after about 20 minutes or so, I get this in my syslog: > >Oct 22 15:24:11 my_computer xinetd[29480]: amanda service was >deactivated because of looping >Oct 22 15:24:41 my_computer amandad[30051]: error receiving message: timeout > >The amandad error log on my_computer reads basically the same thing: >amandad: dgram_recv: timeout after 30 seconds >amandad: error receiving message: timeout Have you tried looking at the latest debug output in /tmp/amanda after running amcheck? I ran into the "deactivated because of looping" error on a few clients which were still GLIB2.1 based machines where my NFS automounted amanda binaries were compiled against GLIBC2.2. Find out what errors the amandad binary is spewing into /tmp/amanda/*.debug -- "Never put off until tomorrow what you can do today. There might be a law against it by that time." -- /usr/games/fortune, 07/30/2001 Brandon D. Valentine
Re: Redhat 7.1 troubles
Try setting wait = yes
On Tue, 23 Oct 2001, Jennifer Peterson wrote:
- Hi,
-
- I wonder if anybody can help me out with this problem. I installed
- amanda-client-2.4.2p2-1.i386.rpm on my Redhat 7.1 box, and I have
- amandad running through xinetd like so:
- service amanda
- {
- socket_type = dgram
- protocol= udp
- wait= no
- user= amanda
- group = disk
- server = /usr/lib/amanda/amandad
- disable = no
- groups = yes
- only_from = "backup_computer"
- }
-
- When I restart xinetd, the amanda service starts up just fine, and when
- I amcheck from my backup computer, no errors are reported. However,
- after about 20 minutes or so, I get this in my syslog:
-
- Oct 22 15:24:11 my_computer xinetd[29480]: amanda service was
- deactivated because of looping
- Oct 22 15:24:41 my_computer amandad[30051]: error receiving message: timeout
-
- The amandad error log on my_computer reads basically the same thing:
- amandad: dgram_recv: timeout after 30 seconds
- amandad: error receiving message: timeout
-
- At this point amcheck also fails.
-
- If I restart xinetd right before the backup begins, then the backup works.
-
- Any suggestions?
-
- Thanks,
-
- Jenn Peterson
-
-
--
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
[EMAIL PROTECTED]
HELP: "server fast" compression in a loop?
HELP! I've got a machine that is trying to backup a directory that is about 4GB. I've got the dumptype set with server fast compression. It's been going for at least 8 hours (on this one disklist entry). The machine is very fast, so it's not just lagging. Other disklist entries went fine and quick. the holding area shows: host.disk.0.tmp host.disk.0.1.tmp host.disk.0.2.tmp ... Each of these are 500M (one is constantly growing towards 500. Then, if I look a bit later, they're all gone and it is starting at the beginning. What is wrong? What's the best way to stop it? --Dan
Re: Redhat 7.1 troubles
Jennifer Peterson wrote:
>
> Hi,
>
> I wonder if anybody can help me out with this problem. I installed
> amanda-client-2.4.2p2-1.i386.rpm on my Redhat 7.1 box, and I have
> amandad running through xinetd like so:
> service amanda
> {
> socket_type = dgram
> protocol= udp
> wait= no
> user= amanda
> group = disk
> server = /usr/lib/amanda/amandad
> disable= no
> groups = yes
> only_from = "backup_computer"
> }
>
> When I restart xinetd, the amanda service starts up just fine, and when
> I amcheck from my backup computer, no errors are reported. However,
> after about 20 minutes or so, I get this in my syslog:
>
> Oct 22 15:24:11 my_computer xinetd[29480]: amanda service was
> deactivated because of looping
> Oct 22 15:24:41 my_computer amandad[30051]: error receiving message: timeout
>
> The amandad error log on my_computer reads basically the same thing:
> amandad: dgram_recv: timeout after 30 seconds
> amandad: error receiving message: timeout
>
> At this point amcheck also fails.
>
> If I restart xinetd right before the backup begins, then the backup works.
>
> Any suggestions?
>
> Thanks,
>
> Jenn Peterson
Hello Jennifer,
xinetd usually disables a service if it is called more than 10 times a
second.
However, if you have to dump much disks, this number is to small.
To change this behaviour put the following line in your
/etc/sysconfig/xinetd on the client:
EXTRAOPTIONS="-loop 100"
and restart xinetd.
This will let xinetd start amandad up to 100 times a second.
I hope it works,
Bram.
Re: Question about disklist
On Tue, 23 Oct 2001, Michael Sobik wrote: >All, > >I was wondering if I can do something like this in the disklist: > >client /home/user1 user-tar >client /home/user2 user-tar >... > >instead of backing up the entire partition that has /home on it? I think >this will create separate dump images for each directory and therefore avoid >having a dump image larger than a single tape. amcheck doesn't complain, but >will this work? Anybody try it? Yes, my entire disklist is setup in that fashion. I have an awk script that runs out of cron on my amanda server which parses the auto.home autofs map into a disklist in the exact style you have mentioned above. I also then have an auto.backup autofs map which gets parsed as well where I can keep directories to backup which don't belong under /home. -- "Never put off until tomorrow what you can do today. There might be a law against it by that time." -- /usr/games/fortune, 07/30/2001 Brandon D. Valentine
Re: Redhat 7.1 troubles
On Tue, 23 Oct 2001 at 7:28am, Jennifer Peterson wrote
> I wonder if anybody can help me out with this problem. I installed
> amanda-client-2.4.2p2-1.i386.rpm on my Redhat 7.1 box, and I have
The standard way to install amanda is from source. But...
> amandad running through xinetd like so:
> service amanda
> {
> socket_type = dgram
> protocol= udp
> wait= no
That should be wait=yes.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: Timeout errors
Jeremy Wadsack ([EMAIL PROTECTED]): > I am getting consistent timeout errors on a couple hosts. This doesn't > occur when I run amcheck, just during a dump. I'm using tar on all > hosts, so it's not a Linux dump issue. These two hosts are conspicuous > because they are old (so kernel, libraries and software all could be > out of date). > In both cases, the tail of /tmp/amand/amandad.debug looks like this: > amandad: dgram_recv: recvfrom() failed: Connection refused > amandad: waiting for ack: Connection refused, giving up! > The confusing thing is that it handles the sendsize call just fine > without a failed connection. This looks (but I'm not positive) like > the connection from the client to the server is failing, which I > didn't know it did. > Finally, these systems seem to have tar 1.12 (not patched). I am in > the process of upgrading to the latest version, but the tar issues are > not listed in the documentation as causing a 'timeout' error, so I > don't think that's going to fix it. > Anyway, if anyone has any thoughts or insight, I'd appreciate it. Just to follow up on this. I upgraded the two hosts to the latest tar and still get timeouts. I haven't seen this kind of thing in the archives. Does anyone have a clue what's going on here? TIA, -- Jeremy Wadsack Wadsack-Allen Digital Group
Re: gnutar options (indexs and the dreaded "big numbers")
On Tue, 23 Oct 2001 at 9:56am, Frank Smith wrote >What options does Amanda call tar with? I would like to be able to > verify that a tar build works correctly without waiting to run a backup > (i.e., tar a directory to /dev/null creating the index file and then > examine the index to see if it worked correctly). > The list of options are in /tmp/amanda/sendbackup*debug (if you're currently using tar). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Redhat 7.1 troubles
Hi,
I wonder if anybody can help me out with this problem. I installed
amanda-client-2.4.2p2-1.i386.rpm on my Redhat 7.1 box, and I have
amandad running through xinetd like so:
service amanda
{
socket_type = dgram
protocol= udp
wait= no
user= amanda
group = disk
server = /usr/lib/amanda/amandad
disable= no
groups = yes
only_from = "backup_computer"
}
When I restart xinetd, the amanda service starts up just fine, and when
I amcheck from my backup computer, no errors are reported. However,
after about 20 minutes or so, I get this in my syslog:
Oct 22 15:24:11 my_computer xinetd[29480]: amanda service was
deactivated because of looping
Oct 22 15:24:41 my_computer amandad[30051]: error receiving message: timeout
The amandad error log on my_computer reads basically the same thing:
amandad: dgram_recv: timeout after 30 seconds
amandad: error receiving message: timeout
At this point amcheck also fails.
If I restart xinetd right before the backup begins, then the backup works.
Any suggestions?
Thanks,
Jenn Peterson
Re: Question about disklist
On Tue, 23 Oct 2001 at 7:26am, Michael Sobik wrote > I was wondering if I can do something like this in the disklist: > > client /home/user1 user-tar > client /home/user2 user-tar > ... > > instead of backing up the entire partition that has /home on it? I think > this will create separate dump images for each directory and therefore avoid > having a dump image larger than a single tape. amcheck doesn't complain, but > will this work? Anybody try it? Yes, it will work (as long as you are using GNUtar, which it looks like you are). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: TapeTypes
Hallo Chris,
tapetype generated the following for me.
# Suse Linux 7.0, Kernel 2.4.2, /dev/nst0, Symbios Logic/NCR 53c896
define tapetype DLT1 {
comment "just produced by tapetype program"
length 34608 mbytes
filemark 21 kbytes
speed 1414 kps
}
Regards
Andreas
amrecover is so slow ...
Hello, I recently had to recover some files 'accidentally' deleted by a user. The client is 2.4.2p2 on a RedHat 7.0. The server is also 2.4.2p2 on a Tru64 alpha. The partition is backed up with dump and compressed on the client with gzip. The problem is this : when I ran amrecover as root on the client, at the top of the partition, I was able to cd into the right directory, add the vanished files to the recovery list and then ask to extract. I put the right tape into the drive and launched the recovery. After some times (some hours really), nothing had happened, so I looked on the server, and gzip was running (on the server !) using about 0.5% of the CPU. amidxtaped was running, and the tape drive was occasionally busy. The partition is about 3 GB, so with gzip so timid, I could wait some more days ... Finally, I ran amrestore on the server, piped to restore -i, and the restore took about 5 minutes. I then transferred the files on the client. But isn't there a way to have amrecover perform faster? Is client- side compression the issue? Thanks for any hint Raoul -- Dr Raoul De Guchteneere Département de Physique Université catholique de Louvain
gnutar options (indexs and the dreaded "big numbers")
While experimenting with gnu tar 1.13.25, I got the infamous big numbers in the index file (I was previously using 1.12). The archives suggest 1.13.19 works, but the Amanda web page claims 1.13.18 with a patch (and the link to the patch returns an error). What options does Amanda call tar with? I would like to be able to verify that a tar build works correctly without waiting to run a backup (i.e., tar a directory to /dev/null creating the index file and then examine the index to see if it worked correctly). Thanks, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Question about disklist
All, I was wondering if I can do something like this in the disklist: client /home/user1 user-tar client /home/user2 user-tar ... instead of backing up the entire partition that has /home on it? I think this will create separate dump images for each directory and therefore avoid having a dump image larger than a single tape. amcheck doesn't complain, but will this work? Anybody try it? Thanks, Mike
Append to Tape
Hi Everybody I have a backup server running Amanda, with a 12 Tape Library. I am trying to port this to a backup server which is an AIT 1 model. I would like to know if Amanda has the ability to append to tape i.e Running Full/ Level 0 dumps on one night and there after running incremental backups until tape change it needed. My other question is that I am findind it a problem to get backup software which is compatible with OpenBSD. At present moment, Amanda is the only one that work. Does anyone know of any other software which is available to use with OpenBSD. -- Regards Pyuesh Daya Tel : (011) 719 0384 Fax : (011) 719 0444
Re: Question on level 0 dumps
On Tue, 23 Oct 2001 at 9:28am, Morse, Richard E wrote > What I'm wondering is, does the level 0 dump have to be unbroken across the > entire machine, or does Amanda schedule by partitions? Actually, amanda schedules by disklist entires. If you are using dump as your backup program, then these must be partitions. But, if you are using GNUtar, then these can be subdirectories of partitions. So you should be able to handle it on the Exabyte. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: TapeTypes
I'm using this - tough I can't just now tell you where
I got it from and I can't saw that its really correct.
Normally I defer to the tape-type-list (bottom of the page
link) at www.amanda.org but I see that its not currently
available.
define tapetype DLT8000 {
comment "Differential Digital Linear Tape 8000"
length 82000 mbytes
filemark 8 kbytes
speed 5500 kbytes
}
>
> Anyone have a tapetype for 40/80GB DLT1 Tapes? Tapetype will definitely
> take too long to run on this drive
>
> --Chris
>
TapeTypes
Anyone have a tapetype for 40/80GB DLT1 Tapes? Tapetype will definitely take too long to run on this drive --Chris
Question on level 0 dumps
Hi! I would like to start using Amanda to back up a small LAN I have, consisting mainly of Solaris 2.6 machines (+ 1 NT box, although that can wait, and 1 RedHat 7 box). The machine that I intend to use as a host is an older SPARCstation 2, which has two tape drives attached -- a DDS3 drive and an older EXAbyte drive. I understand that the tapes that I use, since Amanda can't use both drives, need to be able to handle a level 0 dump from any of the machines. What I'm wondering is, does the level 0 dump have to be unbroken across the entire machine, or does Amanda schedule by partitions? That is, most of the machines use have somewhere between 4 and 8 gigs of data on them, which cannot fit on one of the EXAbyte tapes. However, none of their partitions are larger than about 3 gigs, which would fit on one of the tapes. So what I'm wondering is if Amanda schedules backups on the partition level or on the host level. Just in case you're wondering why I want to use the EXAbyte tapes, it's because I have about 100+ of them, whereas I only have around 20 of the DDS3 tapes, and although I will be buying more, I'm wondering if I can get way with the EXAbyte tapes for a while... Thanks muchly, Ricky Morse - Richard Morse Systems Administrator, MGH Biostatistics Research [EMAIL PROTECTED] <-> 617 724 9830
obsul40 /export/diskA1 lev 0 FAILED [obsul40 NAK: amandad busy]
hi, I start having this probleme only in one machine when it used to work for a while without having any problems. I noticed that some deamon was still working on this machine ps -ef | grep am " root 12346 168 0 00:45:00 ?0:00 amandad root 12347 12346 0 00:45:02 ?0:00 /unige/amanda/libexec/sendsize root 12348 12347 0 00:45:02 ?0:00 /unige/amanda/libexec/killpgrp " so I gently kill them and relaunch an backupbut still... the same problem appear again any idea thanks in advance
No Subject
unsubscribe
Need help..
Hello Amanda Users, I describe my problem below and need your suggestions: The environment: I have compiled amanda 2.4.2p2 on a Sun Ultra with RedHat Linux 6.2. This has a Quantum DLT 4000 tape unit attached and is our server. I have installed amanda (version same as on the server) on HP-UX 10.20, Solaris 2.6, and RedHat 7.1 (on x86) platforms. These are intended to be the client systems. On the server, the amanda is compiled with amanda as the userid and disk as the group id. The problem: On x86 based RedHat 7.1 clients, the amanda user is amanda and group is disk. With this, I am able to backup files onto the tape unit. But this needs "chmod o+x" for all files/directories to be backed up. On Solaris, I create a userid amanda and put it into the group 0. I am unable to backup file systems because the user amanda has no access to files owned by other users. On HP-UX, the userid is amanda and the group is sys. Again, I fail to backup full filesystems. The above results are as per the UNIX file ownerships and access rights. The user amanda can only read the files and directories it is permitted to. Nothing new about that. On the other hand I donot want to make root as the amanda user because of security issues. My question is which userid and groupid I should choose so that I can backup files belonging to users ? I have seen postings from other people using Linux, HP, Solaris, and Windows (via SAMBA) as client systems. I would really appreciate if they can share their experiences with me. Please reply to me directly as this may not be of general interest. I will post a summary of answers I get. Thanks for your time. --ajit |-| | Ajit K. Jena Phone : | | Office +91-22-5767751 | | Computer Centre+91-22-5722545 x8750 | | Indian Institute of Technology Home +91-22-5722545 x8068 | | POWAI, Bombay Fax :+91-22-5723894 | | PIN 400076, India Email :[EMAIL PROTECTED] | |-|
Re: EZ-17 + M2 + chg-zd-mtx
Hi,
On Mon, 22 Oct 2001, Claude Lefrancois wrote:
> Hello,
>
> I am new to Amanda. I have an Exabyte EZ17 Autoloader (Mammoth2) with
> AME225 cartridges. The tape is connected to a Redhat Linux 6.2 system
> with an Adaptec 7899 U160 on-board SCSI controller. The SCSI driver
> identifies the tape and the changer correctly.
> > I have installed Amanda-2.4.2p2 and mtx-1.2.13. From the command line, I
> can control the changer with mtx (unload, load x, status). With mt, I
> can control the tape (rewind, fsf, offline, status, etc.). I had
> successfully used dump/restore with this tape.
>
I have an EZ17 with a Mammoth 2 drive, Amanda-2.4.2p2 and mtx-1.2.13 on a
Solaris 7 system. Some months ago this list helped me
fix my chg-zd-mtx script to get rid of amtape 'offline'
errors. Probably amtape commands don't work for you either and if you
get amtape to work then amcheck will also work.
I've attached my chg-zd-mtx script. Note that it contains debugging
commands, so you'll get /tmp/amanda/chg-zd-mtx.* logs that will contain
lots of info.
Also, check that your changer.conf file does not contain comments,
because it does not understand comments. I think one of the
mistakes I made was to have "commented out" lines that were are actually
being processed. If you have comments, you need to remove them.
Here's my changer.conf file:
firstslot=1
lastslot=7
OFFLINE_BEFORE_UNLOAD=1
AUTOCLEAN=0
havereader=0
> Now, I try to configure Amanda. I have the following output from the
> amcheck command:
>
> [root@lmcpc111335 /root]# su amanda -c "amcheck DailySet1"
Maybe try to test the EZ17 with amtape instead of amcheck,
eg: 'amtape DailySet1 current' or 'amtape DailySet1
slot next' or 'amtape DailySet1 show'
Pam
<<<-- chg-zd-mtx -->>>
#!/bin/sh
#
# Exit Status:
# 0 Alles Ok
# 1 Illegal Request
# 2 Fatal Error
#
# Contributed by Eric DOUTRELEAU <[EMAIL PROTECTED]>
# This is supposed to work with Zubkoff/Dandelion version of mtx
#
# Modified by Joe Rhett <[EMAIL PROTECTED]>
# to work with MTX 1.2.9 by Eric Lee Green http://mtx.sourceforge.net
#
# Modified by Jason Hollinden <[EMAIL PROTECTED]> on 13-Feb-2001
# to work with MTX 1.2.10, >9 slots, has barcode support, and works with
# multiple configs at once.
# NOTE: Only tested the 2 additions with an ADIC Scalar 100.
# All my additions have a ' Comment' close by.
# NOTE: all variables are now placed in a 'changerfile'.conf in your
# amanda config directory, where 'changerfile' is what's set in
# amanda.conf. Ex. if amanda.conf has:
# changerfile="/etc/amanda/Dailyset1/CHANGER"
# Then the variables file will be "/etc/amanda/Dailyset1/CHANGER.conf".
#
# Here is a commented out example file, with all the variables needed:
# firstslot=2 1st tape slot
# lastslot=15 Last tape slot
# cleanslot=1 Slot with cleaner tape
#
# # Do you want to clean the drive after a certain number of accesses?
# # NOTE - This is unreliable, since 'accesses' aren't 'uses', and we
# #have no reliable way to count this. A single amcheck could
# #generate as many accesses as slots you have, plus 1.
# # ALSO NOTE - many modern tape loaders handle this automatically.
#
# AUTOCLEAN=0 Set to '1' or greater to enable
#
# autocleancount=99 Number of access before a clean.
#
# havereader=1 If you have a barcode reader, set to 1.
#
# offlinestatus=1 Set to 0 if 'mt status' gives an
# "offline" when drive is offline.
# Set to 1 or greater if 'mt status'
# doesn't give and offline, rather an
# "ONLINE" when drive is online.
#
# OFFLINE_BEFORE_UNLOAD=0 Does your tape driver require a
# 'mt offline' before mtx unload?
# You may need to customize these things
MT=/usr/bin/mt
MTF=-f
MTX=/home/backup/mtx-1.2.13/mtx
Check the 'readyError' section if mt acts differently for you
as stated below.
See the 'readstatus' section below if using a different drive than 0.
# No user-level customized required beyond this point.
# Paths
prefix=/home/backup/amanda
exec_prefix=${prefix}
sbindir=${exec_prefix}/sbin
libexecdir=${exec_prefix}/libexec
# try to hit all the possibilities here
PATH=$sbindir:$libexecdir:/usr/bin:/bin:/usr/sbin:/sbin:/usr/ucb:/usr/local/bin:/home/backup/mtx-1.2.13
export PATH
#what is this test? comment it out for now...
USE_VERSION_SUFFIXES="no"
#if test "$USE_VERSION_SUFFIXES" = "yes"; then
# SUF="-2.4.2p2"
#else
SUF=
#fi
email=`amgetconf$SUF mailto`
mailer=/usr/bin/mailx
myname=$0
tape=`amgetconf$SUF tapedev`
TAPE=`amgetconf$SUF changerdev`; export TAPE # for
obsul40 /export/diskA1 lev 0 FAILED [obsul40 NAK: amandad busy]
hi, I start having this probleme only in one machine when it used to work for a while without having any problems. I noticed that some deamon was still working on this machine ps -ef | grep am " root 12346 168 0 00:45:00 ?0:00 amandad root 12347 12346 0 00:45:02 ?0:00 /unige/amanda/libexec/sendsize root 12348 12347 0 00:45:02 ?0:00 /unige/amanda/libexec/killpgrp " so I gently kill them and relaunch an backupbut still... the same problem appear again any idea
