test
test message This e-mail may contain confidential information and/or copyright material and is intended for the use of the addressee only. Disclosure, distribution or copying of this message is strictly prohibited by law. If you have received this communication in error, please notify the sender immediately by telephone on (01273) 234665 and delete the e-mail. The contents of this message may contain personal views that are not the opinions of EHBAS Ltd, unless specifically stated.
Dumper hangs
Hello. Amanda dumper hangs sometimes; and backup fails with data timeout: FAILURE AND STRANGE DUMP SUMMARY: localhost /home lev 0 FAILED [data timeout] The dumper is still there hours later: #ps -fu amanda UID PID PPID C STIME TTY TIME CMDamanda 21555 1 0 00:55 ? 00:00:00 /usr/lib/amanda/sendbackupamanda 21556 21555 0 00:55 ? 00:00:01 dump 0usf 1048576 - /dev/sdb1amanda 21557 21556 0 00:55 ? 00:00:04 dump 0usf 1048576 - /dev/sdb1amanda 21558 21557 0 00:55 ? 00:02:36 dump 0usf 1048576 - /dev/sdb1amanda 21559 21557 0 00:55 ? 00:02:50 dump 0usf 1048576 - /dev/sdb1amanda 21560 21557 0 00:55 ? 00:02:41 dump 0usf 1048576 - /dev/sdb1amanda 21894 21367 0 09:47 tty1 00:00:00 -bashamanda 21920 21894 0 09:48 tty1 00:00:00 ps -fu amanda I set dtimeout to 3600s; it hangs whether I use a holding disk or not. When the dump succeeds, it runs for 46 minutes. My configuration is a RHS 7.1 (amanda 2.4.2p2). Any ideas ? tia Vincent
is this the amanda-users list?
Am I subscribed yet? This e-mail may contain confidential information and/or copyright material and is intended for the use of the addressee only. Disclosure, distribution or copying of this message is strictly prohibited by law. If you have received this communication in error, please notify the sender immediately by telephone on (01273) 234665 and delete the e-mail. The contents of this message may contain personal views that are not the opinions of EHBAS Ltd, unless specifically stated.
client-side cache space
Hi, I've got two clients with reiserfs filesystems connecting to a server with the tape. Everything works well, but due to compression the transfer rates aren't that high they should be in case of the tape streaming. (needs about 5 MB/s) So, is there any possibility to define an cache space on the client side, where the backup is stored and just transferred after compression ? Thanks in advance Michael
Re: Dumper hangs
On Thu, 13 Dec 2001 at 10:33am, Vincent GRENET wrote Amanda dumper hangs sometimes; and backup fails with data timeout: I set dtimeout to 3600s; it hangs whether I use a holding disk or not. When the dump succeeds, it runs for 46 minutes. My configuration is a RHS 7.1 (amanda 2.4.2p2). Many people (myself included) have hit this issue with Linux dump (or perhaps the combo of Linux dump and 2.4 kernels). You have two options. You can upgrade to the latest dump/restore versions from dump.sourceforge.net, and that may or may not fix the problem. It didn't for me. Or you can switch to using GNUtar for your backups. This is what I did, and haven't looked back. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Is this correct?
Hi all: I have 5 tapes for one HP24DAT SCSI unit. I want to use one tape per day, not including saturday/monday. Is this the correct configuration? dumpcycle 7 days runspercycle 5 days tapecycle 5 tapes thanks
Dumper hangs
Hello. Amanda dumper hangs sometimes; and backup fails with data timeout: FAILURE AND STRANGE DUMP SUMMARY: localhost /home lev 0 FAILED [data timeout] The dumper is still there hours later: #ps -fu amanda UIDPID PPID C STIME TTY TIME CMD amanda 21555 1 0 00:55 ?00:00:00 /usr/lib/amanda/sendbackup amanda 21556 21555 0 00:55 ?00:00:01 dump 0usf 1048576 - /dev/sdb1 amanda 21557 21556 0 00:55 ?00:00:04 dump 0usf 1048576 - /dev/sdb1 amanda 21558 21557 0 00:55 ?00:02:36 dump 0usf 1048576 - /dev/sdb1 amanda 21559 21557 0 00:55 ?00:02:50 dump 0usf 1048576 - /dev/sdb1 amanda 21560 21557 0 00:55 ?00:02:41 dump 0usf 1048576 - /dev/sdb1 amanda 21894 21367 0 09:47 tty1 00:00:00 -bash amanda 21920 21894 0 09:48 tty1 00:00:00 ps -fu amanda I set dtimeout to 3600s; it hangs whether I use a holding disk or not. When the dump succeeds, it runs for 46 minutes. My configuration is a RHS 7.1 (amanda 2.4.2p2). Any ideas ? tia Vincent
Re: is this the amanda-users list?
Thomas C. Robinson wrote: Am I subscribed yet? looks like. :-) 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]
Backing up five days for week
Hi all: I've an Linux RH 7.1 system with an HP-24DAT SCSI. I want to have one tape per day, in a week. I don't understand the dumpcycle theorie. Can someone help me? Thanks
Re: Backing up five days for week
On Thu, 13 Dec 2001 at 12:22pm, Adolfo Manuel Pachón Rodríguez wrote I've an Linux RH 7.1 system with an HP-24DAT SCSI. I want to have one tape per day, in a week. I don't understand the dumpcycle theorie. Can someone help me? I don't quite understand what you're asking, but here's a simple explanation of the broad theory. 'dumpcycle' determines the maximum number of days you want between full backups of a particular filesystem. runspercycle is the number of times you will run amdump in one dumpcycle. So, e.g., if you want a full backup of each filesystem at least once a week, and you'll run amdump every weeknight, then you want: dumpcycle 1 week runspercycle 5 tapecycle is the number of tapes you have. It needs to be at least equal to runspercycle. It really should be at least one or two greater, to account for bad runs requiring an amflush. The bigger your tapecycle, the longer your history. In the above example, if you wanted a two week history of backups (with two extra for mishaps), you'd want tapecycle 12 HTH. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
No such file or directory
Hi, if I run /usr/local/sbin/amcheck -m daily from my bash prompt, there are no errors, however if I run it from the crontab I get the following error /bin/bash: /usr/local/sbin/amcheck -m daily: No such file or directory or /bin/bash: /usr/local/sbin/amcheck -m /etc/amanda/daily: No such file or directory Any pointers? Thanks Tom
Adding Second Tape Drive
Adding a second tape drive and using two tapes per run has done wonders for our backups. Amanda is now promoting level 0 dumps from as much as 8 days ahead. Here is what amadmin conf balance is reporting : due-date #fs orig KBout KB balance --- 12/13 Thu0 0 0 --- 12/14 Fri0 0 0 --- 12/15 Sat0 0 0 --- 12/16 Sun0 0 0 --- 12/17 Mon0 0 0 --- 12/18 Tue0 0 0 --- 12/19 Wed 10 14557160 6144000 -85.4% 12/20 Thu 57 95891156 37089920 -11.8% 12/21 Fri 31 84670042 43171936+2.7% 12/22 Sat2 2238963996448 -97.6% 12/23 Sun0 0 0 --- 12/24 Mon 10 67519547 31314592 -25.5% 12/25 Tue 20 112892816 49574464 +17.9% 12/26 Wed 45 94308175 40627072-3.4% 12/27 Thu4 4606106 1366720 -96.8% --- TOTAL 179 476683965 210285152 42057030 (estimated 5 runs per dumpcycle)
I don't understand this
Hi all: I have an HP24DAT SCSI over Linux RH 7.1. I want to backup the weekdays only, using 5+1 tapes. I've this in the amanda.conf: dumpcycle 7 runspercycle 5 tapecycle 6 The tapes are labeled: Daily-000 (monday) Daily-001 (tuesday) Daily-002 (wednesday) Daily-003 (thursday) Daily-004 (friday) Daily-005 (extra) What I want is this: For each day, use the Daily-00X tape. Today, thursday, I use the Daily-003 tape. With amdump Daily, I do the backup. But the report says this: These dumps were to tape Daily-003. The next tape Amanda expects to use is: Daily-006. This is my question. Why Daily-006? Why not the next tape is Daily-004? Thanks
AMANDA on AIX 433
I just wanted to submit a progress report that may help others along the path to AMANDA on the RISC as the information is really scattered all around. I'm running Amanda-2.4.2p2 CC=gcc Running AIX 4.3.3 MR9 on H50 Compiled using directions here: http://www.backupcentral.com/amanda.html At the current I want to run backups on local machine only. An earlier post in this group ( 31015 ) had mentioned that there was trouble with a file during compile time called mntent.h in /usr/include so you should rename it and retry the compile. Compiled fine at that point. After much configuring and testing I ran amcheck and I got a host error and after looking into it a little further I stumbled across an error in the amindexd program. When executed manually I am getting the following error: amindexd: getpeername: Socket operation on non-socket. This error is refered to in several posts and on other sources. For instance in message ( 9315 ) someone had trouble running a recover because of this error. I managed to solve my host error issue and my check completes fine. That seemed to be mostly of my doing... I didn't have my .amandahosts configured properly and my disklist file didn't like the /dev/hdiskX format - so I changed it to /file/system/names. So at this point pretty much everything checks out but I'm wondering if I'll be able to do anything at all because the amindexd isn't running. I'm not a C programmer but if somebody had source I think I'd be able to compile it...to refer back to a previous message ( 3425 ) regarding the getpeername error Alexandre Oliva said: It means that the process' stdin (the current tty) is not a socket, as amandad expects. ...continuing on to ( 3495 ) Mr. Oliva mentions that amcheck might run should you remove the raw device name and add the mount point (which in my case worked). But outside of my check working I don't understand enough about the program to resolve this getpeername error, nor could I find any relevant information on it outside of the fact that it was supposed to be fixed with the next version. Is it going to be an issue? If so how would I go about fixing it? Regards, Tony _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: Is this correct?
On Thursday 13 December 2001 07:40 am, Adolfo Manuel Pachón Rodríguez wrote: Hi all: I have 5 tapes for one HP24DAT SCSI unit. I want to use one tape per day, not including saturday/monday. Is this the correct configuration? dumpcycle 7 days runspercycle 5 days tapecycle 5 tapes thanks Looks good to me. -- Chris Dahn, SERG Code Ninja 3141 Chestnut St. Attn: MCS Department Philadephia, PA 19104 Office: 215.895.0203 Fax: 215.895.1582 -Software Engineering Research Group- Feel the SERG! http://serg.mcs.drexel.edu/ CAT 186, The Microwave http://pgp.mit.edu:11371/pks/lookup?search=Christopher+Dahnop=index
Re: Dumper hangs
On Thursday 13 December 2001 07:30 am, Joshua Baker-LePain wrote: Many people (myself included) have hit this issue with Linux dump (or perhaps the combo of Linux dump and 2.4 kernels). You have two options. You can upgrade to the latest dump/restore versions from dump.sourceforge.net, and that may or may not fix the problem. It didn't for me. Or you can switch to using GNUtar for your backups. This is what I did, and haven't looked back. It seems like this question/problem pops up every few weeks whenever a new person starts using amanda on linux. Perhaps there should be something in the documentation, or even better, a warning when the person runs configure that they may experience this problem if they try to use dump on linux. I attempted to add something to the Faq-O-Matic because I didn't see this on it, but I got an error adding a user login. I sent a seperate email to the list about it. At any rate, do a search through the email archive over the past few months to get more than enough correspondence about this problem. :) -- Chris Dahn, SERG Code Ninja 3141 Chestnut St. Attn: MCS Department Philadephia, PA 19104 Office: 215.895.0203 Fax: 215.895.1582 -Software Engineering Research Group- Feel the SERG! http://serg.mcs.drexel.edu/ CAT 186, The Microwave http://pgp.mit.edu:11371/pks/lookup?search=Christopher+Dahnop=index
Problem with FAQ-O-Matic?
I was writing another email to the list, and was going to suggest someone add something to FAQ-O-Matic. So, I figured I would just go and do it, but when I tried to add a user login, I got the following error: FAQ::OMatic::Auth::readIDfile: Couldn't read /home/groups/a/am/amanda/fom/meta//idfile because Permission denied Has this happened to anyone else? Who should I contact about this potential problem?
Re: Amrecover is not working with Gnu Tar: help needed
Greetins, I finally solved what was wrong using amrecover to restore the files; Was a nasty combination of: - Lack of the index yes parameter in my amanda.conf dump definitions. - Bad names on my .amandahosts file. Check your /etc/hosts for inaccurate entries, even if you're using NFS (can be a problem). - Running amrecover on the server; Run it as root on the client box and make sure i't works (i checked that using Solaris Dump and Linux TAR). Also another of my problems was using Linux dump. Is simply useless with amanda, stick with tar (not very usefull if you have to backup time sensitive files as Rational Clearcase VOB's). Hope this helps someone else with the same type problem i got. JV. --- José Vicente Núñez Zuleta [EMAIL PROTECTED] escribió: Greetings, I'm using Amrecover to try to recover some file; I did a full dump (forced using amadmin) and i here is the output of a failed recover procedure: amrecover setdate ---08 200 Working date set to 2001-12-08. amrecover sethost lnxsrv0001 200 Dump host set to lnxsrv0001. amrecover setdisk / Scanning /export/data06/amanda-hold-disk-temp... Scanning /home/amanda/holding-disk... 200 Disk set to /. amrecover cd /etc /etc amrecover ls 2001-12-08 . 2001-12-08 .pwd.lock 2001-12-08 CORBA/ amrecover add HOSTNAME Added /etc/HOSTNAME amrecover lcd /tmp amrecover extract Extracting files using tape drive /dev/rmt/1bn on host lenbkx0001. The following tapes are needed: NEWBREAK_05 Restoring files into directory /tmp Continue? [Y/n]: y Load tape NEWBREAK_05 now Continue? [Y/n]: y tar: ./etc/HOSTNAME: Not found in archive tar: Error exit delayed from previous errors extract_list - child returned non-zero status: 2 Continue? [Y/n]: n amrecover The file must be there because i did a full dump but amrecover is saying that the file is not in the tape!. The backup runs perfectly (without errors), amverify says that everythinbg is good with the tape. Any helkp with will be really apreciated, JV. = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com
corrupt data problem.
Hi all.
I've been using Amanda for about 4 years now, on a variety of platforms.
I've just found out that the current site I'm at is having corrupt backup
problems. The backups complete without errors, but the data on the tape is
bad.
We're running amanda-2.4.2p2 on a Linux debian stable system, 2 scsi cards
both Adaptec AHA-294X Ultra SCSI, tape is a Sony SDT-9000 DAT on the second
card. Kernel version is 2.2.17
Here's an example from dd
backup@oolon:~$ dd if=/dev/nst0 bs=32k count=1
AMANDA: TAPESTART DATE 20011206 TAPE gcsi02
ìAô ¤¯Ñ
Piyf: !WËåÏìéÔ¿hn]lyf2B0ÅÉÚ=s'
mglÎÉív^é©ðhd¹^@ËÐîdæ~_fûÜÖêg-'4K({ð¡ªäs]ö?×kò^)^n²bÄ·û¸j°;å,?¾Õ÷Ñ
à°¦´Ül2X¡éêgïì°30ô7{;°û.Z ¦LdUÓkºfHDÖhY¥´sC|¾}¯6ø.U
Ù~Ý`ï#ñ(ðøp²I;{Õµ/'ÐX$ëJååC·3K+mJ¶UPD UDÝ%ȵ?69¦WäA@¼öåã #X öX¡ç
\¹Ã-¨÷XÔ2Å ¹K;ÏÉÜ.K èMÉ¡, -CÜUÍä
à9´QäûÄ8uêX¶[g¨6Ù%zÖ«WG!É]Å¥âúå8f¾^8÷ÁÈF¨l±ð-ÁÌäÉ5fi%Móª ËÇåOÎ ²¾]
The tapes all appear to have the same garbage on them (except tape name, of
course) and about 30% of the 30 tapes I'm using are just fine, perfect backup
and restores. It doesn't appear to be a specific tape, I've managed to get
both a good and a bad backup onto/off of the same tape media.
Has anyone seen anything like this? I'm guessing that this is a bad tape
drive??
--
Rick Morris
Network Manager
WeDoHosting.com
101-4226 Commerce Circle
Victoria BC V8Z 6N6
ph: +1 250 479 1595
fax: +1 250 479 1517
[EMAIL PROTECTED]
http://www.wedohosting.com
Re: No such file or directory
On Thu, 13 Dec 2001, Tom Beer wrote: /bin/bash: /usr/local/sbin/amcheck -m daily: No such file or directory Bad command line parsing. It's taking that whole command line as a filename. Is $IFS being changed somewhere from the default? -Mitch
Linux dump
=?iso-8859-1?q?Jos=E9=20Vicente=20N=FA=F1ez=20Zuleta?= wrote: Also another of my problems was using Linux dump. Is simply useless with amanda, stick with tar (not very usefull if you have to backup time sensitive files as Rational Clearcase VOB's). I'm doing my backups with Linux dump, Solaris ufsdump, HP-UX dump and IRIX xfsdump. No problems. I did update the Linux dump to 0.4b23 from sourceforge.net. What problems was Linux dump causing for you? -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
Re: Who has Configset for Autoloader under Linux?
Joerg Klaas wrote: So, does someone have a set of working conf-files for me, to be able to start an backup using: Linux Kernel 2.2x SONY TSL-11000 DAT Tapechanger (8Tapes) I already found 3 devicefiles which seem to be ok, for me side here. They are /dev/sg0 /dev/sg1 /dev/nst0 but I don't know which are the right ones to use /dev/nst0 should be the non-rewinding tape device. I'm using a 4-tape AIT-2 changer on a Linux 2.4.12 system. A few lines from my amanda.conf file: runtapes 2 # number of tapes to be used in a single run of amdump tpchanger chg-multi # the tape-changer glue script tapedev /dev/ntape# the no-rewind tape device to be used rawtapedev /dev/null # the raw device to be used (ftape only) changerfile chg-multi.conf changerdev /dev/ntape chg-multi is in the same directory and I don't think I had to do anything to it. chg-multi.conf contains: multieject 0 gravity 0 needeject 1 ejectdelay 60 statefile changer-status firstslot 1 lastslot 4 slot 1 /dev/nst0 slot 2 /dev/nst0 slot 3 /dev/nst0 slot 4 /dev/nst0 -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
