Re: amverify failing alot.
On Thu, Dec 06, 2001 at 10:34:47AM +1100, Jason Thomas wrote:
> On Wed, Dec 05, 2001 at 12:03:41PM +0100, Moritz Both wrote:
> >
> > > Hi after 2 years of struggling with this crap and getting no where, can
> > > anyone help me figure out what is causing these errors.
> >
> > > it seems to be random doesn't matter which tape or drive I use they all
> > > do it. even changing machine and scsi controllers doesn't fix the
> > > problem.
> >
> > > is it something I'm doing wrong.
> >
> > Which operating system do you use? Which version/s? Which tape devices
> > have you tried? Which SCSI controllers? Did the other tape backup
> > product work?
>
> oh yeah sorry, its running on Debian Linux (sid) using amanda 2.4.2p2
> the tape drives are a Sony DDS3 SDT9000 and a HP DDS4 Autoloader.
> the scsi controllers tried are a adaptec aha1510 and an adaptec 2940.
> the other tape backup product was NovaNet8 and it worked.
>
> > To me this looks like the tape device can't read the files on tape
> > ("I/O error") and tar complains as a result of that ("Unexpected
> > EOF"). afaik amverify tends to mix up error message order in its
> > reports.
>
> I really don't know where to go from here, I've tried brand new tapes as
> well.
>
> since I sent the message I've moved the HP tape drive to another machine
> which has a symbios logic scsi controller and different scsi cable. and
> get the same problems. its even on a seperate channel on the scsi
> controller.
Maybe I missed your earlier post.
What error messages are you seeing?
What happens if you try just "dd"ing a big file to a tape
then reading it back in the same way, and checking
its integrity?
--
Dan Wilder
Re: [Amanda-users] Tried this before....
On Thu, 6 Dec 2001, Jason Thomas wrote: >far enough, its just that usually when people send unsubscribes to the >actual list they are idiot. I now see this is not the case. so now you >should send an email to: It's worth commenting that several months ago I had the same issue unsubscribing an adress from amanda-users. While I did not inquire to the list about it, I did send mail to the list admin who was very responsive in getting the situation taken care of. I am not sure why amanda's majordomo configuration has trouble with unsubscribes. I got my email through to the list admin via [EMAIL PROTECTED], a guess at a pretty standard majordomo alias which forwards to a list admin. Brandon D. Valentine -- "Iam mens praetrepidans avet vagari." - G. Valerius Catullus, Carmina, XLVI
RE: tapetype recommendations
On Wed, 5 Dec 2001, Anthony Valentine wrote: >Your tapes hold 35GB native. Correct. >You are backing up: 76399.8 MB (76GB) > >Compressed, that is: 46003.2 MB (46GB) > >Because you use software compression, you have to go by the native capacity >of your tapes. So even compressed, you data won't fit on one tape. My quarrel seems to be with the fact that amanda is attempting to backup more data than will fit on a single tape. This might not be a tapetype problem, but it seems the logical place to start twiddling. It may be that planner is unable to get good estimates for some of this data so what it thought would compress to 35GB only became 46GB post dump. >The only options that I can see are to try to get better compression by >using 'gzip --best' (if Amanda can support adding switches to gzip) or >getting larger tapes. This is unacceptable as I have found that "gzip --best", which amanda does support, causes a nearly exponential increase in the time it takes amdump to run. A considerable fraction of my clients are r5k/r10k/r12k MIPS machines and none of them are terribly fast at gzip as it is. Few of the GNU tools are particularly well optimized for the SGI MIPS platform. Larger tapes are also not available for AIT-1. >Setting the length option in the tapetype clause to more than your tape can >hold probably won't help you any. Correct me if I'm wrong but what I have set the length option to is well _below_ what the tape will hold. With 35GB capacity tapes I have 35000mb or 35840mb depending upon whether Sony uses powers of 2 (the computer science definition) or powers of 10 (the marketing definition) when defining their tape size. I'll go with the former to be safe. I've set length in tapetype to 33000mb, a good 2GB below what the tape will theoretically hold. Worst case scenario is that Amanda uses powers of 2 to define tape size and Sony uses powers of 10. If this is the case then 33000*1024*1024/1000/1000 = 34603 so I should still be safe. Brandon D. Valentine -- "Iam mens praetrepidans avet vagari." - G. Valerius Catullus, Carmina, XLVI
RE: tapetype recommendations
Brandon,
Maybe I'm reading this wrong, but here's what I see:
Your tapes hold 35GB native.
You are backing up: 76399.8 MB (76GB)
Compressed, that is: 46003.2 MB (46GB)
Because you use software compression, you have to go by the native capacity
of your tapes. So even compressed, you data won't fit on one tape.
The only options that I can see are to try to get better compression by
using 'gzip --best' (if Amanda can support adding switches to gzip) or
getting larger tapes.
Setting the length option in the tapetype clause to more than your tape can
hold probably won't help you any.
Sorry.
Anthony Valentine
-Original Message-
From: Brandon D. Valentine [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 05, 2001 1:11 PM
To: [EMAIL PROTECTED]
Subject: tapetype recommendations
Well, today for the first time I hit EOT. I'm using a Sony SDX-300C
AIT-1 drive. Here's the tapetype I've been using and the error messages
as produced by amreport:
define tapetype AIT1-35 {
comment "AIT-1 with 230m tapes (35/70 GB)"
length 33000 mbytes
filemark 500 kbytes
speed 3000 mbytes
}
--- amreport email ---
These dumps were to tape Daily06.
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: Daily07.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:03
Run Time (hrs:min) 4:16
Dump Time (hrs:min)7:05 5:13 1:52
Output Size (meg) 46003.234804.911198.2
Original Size (meg) 76399.859044.717355.1
Avg Compressed Size (%)60.2 58.9 64.5 (level:#disks
...)
Filesystems Dumped 44 15 29 (1:28 4:1)
Avg Dump Rate (k/s) 1846.3 1896.9 1705.0
Tape Time (hrs:min)3:00 2:55 0:05
Tape Size (meg) 28873.028244.6 628.5
Tape Used (%) 87.6 85.61.9 (level:#disks
...)
Filesystems Taped41 14 27 (1:27)
Avg Tp Write Rate (k/s) 2739.3 2751.7 2278.3
taper: tape Daily06 kb 34136032 fm 42 writing file: No space left on
device
driver: going into degraded mode because of tape error.
--- end amreport email ---
Any recommendations on how to change my tapetype definition to avoid
this problem? And yes, I've got hardware compression disabled.
Brandon D. Valentine
--
"Iam mens praetrepidans avet vagari."
- G. Valerius Catullus, Carmina, XLVI
Re: Excludes not working
Putting a dot (.) in front of the directory names did the trick. Thanks to everyone who answered. On Tue, 4 Dec 2001, Stephen Carville wrote: -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: amverify failing alot.
On Wed, Dec 05, 2001 at 12:03:41PM +0100, Moritz Both wrote:
>
> > Hi after 2 years of struggling with this crap and getting no where, can
> > anyone help me figure out what is causing these errors.
>
> > it seems to be random doesn't matter which tape or drive I use they all
> > do it. even changing machine and scsi controllers doesn't fix the
> > problem.
>
> > is it something I'm doing wrong.
>
> Which operating system do you use? Which version/s? Which tape devices
> have you tried? Which SCSI controllers? Did the other tape backup
> product work?
oh yeah sorry, its running on Debian Linux (sid) using amanda 2.4.2p2
the tape drives are a Sony DDS3 SDT9000 and a HP DDS4 Autoloader.
the scsi controllers tried are a adaptec aha1510 and an adaptec 2940.
the other tape backup product was NovaNet8 and it worked.
> To me this looks like the tape device can't read the files on tape
> ("I/O error") and tar complains as a result of that ("Unexpected
> EOF"). afaik amverify tends to mix up error message order in its
> reports.
I really don't know where to go from here, I've tried brand new tapes as
well.
since I sent the message I've moved the HP tape drive to another machine
which has a symbios logic scsi controller and different scsi cable. and
get the same problems. its even on a seperate channel on the scsi
controller.
msg08721/pgp0.pgp
Description: PGP signature
Re: [Amanda-users] Tried this before....
far enough, its just that usually when people send unsubscribes to the actual list they are idiot. I now see this is not the case. so now you should send an email to: [EMAIL PROTECTED] - problems with mailing lists also from the website. or have you done this already? On Wed, Dec 05, 2001 at 08:04:03AM -0500, Ken Clark wrote: > Jason Thomas wrote: > > > > http://www.amanda.org/ > > > > WHERE TO GET MORE INFORMATION ABOUT AMANDA > > Unneeded > > > Amanda is completely unsupported and made available as-is. Unfortunately, we > > don't usually have the time to answer all user > > questions and help all new sites get started. However, we do maintain > > several mailing lists for those interested in Amanda. > > > > Please note: To subscribe or unsubscribe to a mailing list, DO NOT, EVER, > > send mail to that list. > > I know this. I did the right thing and am still receiving messages. > If only the major-domo was as industrious about removing me from the > list as you lot are about jumping on this, :-) I'd be happy. This > was a "last resort". > > > Send mail to > > [EMAIL PROTECTED] > > with the following line in the body of the message: > > subscribe > > and when you want to unsubscribe, use the following line in the body: > > unsubscribe > > > > where is one of the following: > > > > amanda-announce > > amanda-users > > amanda-hackers > > Swell, and when this doesn't work? I did this. I'm not an idiot, > all evidence and opinions to the contrary. msg08720/pgp0.pgp Description: PGP signature
client error
I am trying to add a new client to my amanda backups. I keep getting this error: song6 c0t0d0s6 lev 0 FAILED [song6 NAK: service sendsize unavailable] song6 c0t0d0s0 lev 0 FAILED [song6 NAK: service sendsize unavailable] I installed amanda-2.4.2p2 on an ultrasparc 10 running solaris 8 client. Any ideas why the backup is failing? Soo
tapetype recommendations
Well, today for the first time I hit EOT. I'm using a Sony SDX-300C
AIT-1 drive. Here's the tapetype I've been using and the error messages
as produced by amreport:
define tapetype AIT1-35 {
comment "AIT-1 with 230m tapes (35/70 GB)"
length 33000 mbytes
filemark 500 kbytes
speed 3000 mbytes
}
--- amreport email ---
These dumps were to tape Daily06.
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: Daily07.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:03
Run Time (hrs:min) 4:16
Dump Time (hrs:min)7:05 5:13 1:52
Output Size (meg) 46003.234804.911198.2
Original Size (meg) 76399.859044.717355.1
Avg Compressed Size (%)60.2 58.9 64.5 (level:#disks
...)
Filesystems Dumped 44 15 29 (1:28 4:1)
Avg Dump Rate (k/s) 1846.3 1896.9 1705.0
Tape Time (hrs:min)3:00 2:55 0:05
Tape Size (meg) 28873.028244.6 628.5
Tape Used (%) 87.6 85.61.9 (level:#disks
...)
Filesystems Taped41 14 27 (1:27)
Avg Tp Write Rate (k/s) 2739.3 2751.7 2278.3
taper: tape Daily06 kb 34136032 fm 42 writing file: No space left on
device
driver: going into degraded mode because of tape error.
--- end amreport email ---
Any recommendations on how to change my tapetype definition to avoid
this problem? And yes, I've got hardware compression disabled.
Brandon D. Valentine
--
"Iam mens praetrepidans avet vagari."
- G. Valerius Catullus, Carmina, XLVI
Re: 2 questions : 1) Replace a tape in a set 2) Specify port range
On Wed, 5 Dec 2001 at 7:39pm, David Galveias wrote > 1 ) Replace a tape in a set: > I have a set of 5 tapes, 24 Gb each. At least that was what i thought i had. > The last backup i made, i noticed that one of the tapes is just a 8 Gb tape. > My question is : > Can i just (force) label a new 24 Gb tape to replace this tape and start > using this new tape? What is the impact in amanda's backups "database"? amrmtape the small one, then amlabel a new one. amanda will do the right thing in terms of making sure that whatever was on the tape you removed gets put on tape ASAP. > 2) Port range: > My network has traffic control (firewall) and i'd like to delimit a port > range for amanda. > In most of my machines i've installed amanda's RPMs (binaries) and > therefor the "compile with --port-range=?,?" option is out of question. > In the "examples" directory i saw a "config.site" file and read it. I > understood that this file has two purposes. 1) To define compile options > and 2) To configure a system (i think... :)). > I've tried to put config.site file (suiting my needs) in various > directories (/usr/local/etc, /usr/local/share , etc,etc) but i doesn't > make any effect. What am i doing wrong? Or the config.site file is only > for compiling amanda? If so, is there some other way to define a port range? In general, installing pre-compiled binaries of amanda is frowned upon for exactly this reason -- many settings are specified at compile time. Your only option (AFAIK) is to compile amanda with the portrange settings. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: schedual line 10: syntax error - HELP
Help! Short of strace'ing the entire amdump *shudder*, I can't grep what the hell is causing this error. Any GUESSES even would be more than welcome. -dan > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Garthwaite > Sent: Tuesday, December 04, 2001 10:46 AM > To: [EMAIL PROTECTED] > Subject: schedual line 10: syntax error > > > A moment of introduction: > I'm the UNIX administrator for a branch of Science Applications > International Corporation. I've been using amanda quite > happily now for ~6 > months to feed an HP SureStore Ultrium 1/20 ( that's 2TB > native ) backing up > a data center of RH7.1 and HPUX 10.20 boxen. > > The problem: > Extending this system now to back up ~100 windows lusers. > Half of these > are mobile laptops. To compensate for the on again, of again > nature of all > the laptops, I've written an nice awk/bash script to autogenerate > /etc/amandapass and append the lusers to > /etc/amanda/Daily/disklist on the > fly, just before amcheck and amdump run. > > I'm pretty sure the scripts run flawlessly. One of the > features of the > scripts is to append a cylinder label ( 100, 101, 102... ), > the same to each > windows host. ( to keep the 16 dumpers from hitting the same > poor laptop ) > This also seems to work well during test runs. > > The problem, adding the whole list of 60 or so clients, the > whole dump run > aborts. The logs in /tmp/amanda/*$(date +%Y%m%d).debug all > check out, look > fine, with no errors. The logs in /var/lib/Daily are another matter: > > [amanda@amanda Daily]$ tail amdump.1 > process6.mtg.saic.com / 0 1 2001:11:20:22:15:7 271 18 > process6.mtg.saic.com /stand 0 1 2001:11:20:22:58:8 20 0 > morpheus.mtg.saic.com /stand 0 1 2001:11:20:22:15:37 14 0 > > driver: schedule line 10: syntax error > driver: adding holding disk 0 dir /var/lib/amanda/dumps size 97819744 > reserving 97819744 out of 97819744 for degraded-mode dumps > taper: DONE [idle wait: 629.108 secs] > taper: writing end marker. [AL5853 OK kb 0 fm 0] > amdump: end at Mon Dec 3 17:15:42 EST 2001 > > and > [amanda@amanda Daily]$ tail log.20011203.0 > FAIL planner amanda.mtg.saic.com //wiggin_jo/C$ 0 [dumps too big, but > cannot incremental dump new disk] > FAIL planner amanda.mtg.saic.com //win2klinux/C$ 0 [dumps > too big, but > cannot incremental dump new disk] > FAIL planner amanda.mtg.saic.com //jagoe_d/C$ 0 [dumps too > big, but cannot > incremental dump new disk] > FAIL planner amanda.mtg.saic.com //saic37/C$ 0 [dumps too > big, but cannot > incremental dump new disk] > FAIL planner amanda.mtg.saic.com //dan_ny3/G$ 0 [dumps too > big, but cannot > incremental dump new disk] > FAIL planner amanda.mtg.saic.com //esri-1/D$ 0 [dumps too > big, but cannot > incremental dump new disk] > FAIL planner amanda.mtg.saic.com //perkins_d/D$ 0 [dumps too big, but > cannot incremental dump new disk] > FINISH planner date 20011203 > FATAL driver schedule line 10: syntax error > INFO taper tape AL5853 kb 0 fm 0 [OK] > > Where can I debug the 'schedual line 10: syntax error' in > both of these > files? > > -Dan Garthwaite > >
2 questions : 1) Replace a tape in a set 2) Specify port range
Hi there. I have 2 questions. 1 ) Replace a tape in a set: I have a set of 5 tapes, 24 Gb each. At least that was what i thought i had. The last backup i made, i noticed that one of the tapes is just a 8 Gb tape. My question is : Can i just (force) label a new 24 Gb tape to replace this tape and start using this new tape? What is the impact in amanda's backups "database"? 2) Port range: My network has traffic control (firewall) and i'd like to delimit a port range for amanda. In most of my machines i've installed amanda's RPMs (binaries) and therefor the "compile with --port-range=?,?" option is out of question. In the "examples" directory i saw a "config.site" file and read it. I understood that this file has two purposes. 1) To define compile options and 2) To configure a system (i think... :)). I've tried to put config.site file (suiting my needs) in various directories (/usr/local/etc, /usr/local/share , etc,etc) but i doesn't make any effect. What am i doing wrong? Or the config.site file is only for compiling amanda? If so, is there some other way to define a port range? Thanks for your attention
Re: [Amanda-users] amanda 2.4.3b1
Jean, I am using Amanda 2.4.2p2, where can I find the new features in Amanda 2.4.3b1 ? Thank you, SHu Liu On Tue, 4 Dec 2001, Jean-Louis Martineau wrote: > On Sat, Dec 01, 2001 at 02:46:42PM +1100, Jason Thomas wrote: > > On Fri, Nov 30, 2001 at 04:51:20PM -0500, Jean-Louis Martineau wrote: > > > * tapeio. > > > > could someone provide a summary of what tapeio is/provides/fixes? > > Look at the "OUTPUT DRIVERS" section of the amanda man page. > > Jean-Louis > -- > 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: xinetd: amanda service was deactivated because of looping
On Wed, 5 Dec 2001, Ron Stanonik wrote: > I upgraded my amanda server from redhat 6.2 to redhat 7.1 and upgraded > amanda from 2.4.1p1 to 2.4.2p2. > > I upgraded an amanda client to redhat 7.2 and replaced its copy of > the amanda programs (/usr/local/libexec and /usr/local/sbin) with > copies from the server. > > Afterward I got the infamous "xinetd: amanda service was deactivated ..." > on the client during amcheck. > ... > But why would amandad fail to read the packet? So, I did ldd on amandad > > ldd /usr/local/libexec/amandad > libm.so.6 => /lib/i686/libm.so.6 (0x40027000) > libreadline.so.4.1 => not found > libtermcap.so.2 => /lib/libtermcap.so.2 (0x4004a000) > libnsl.so.1 => /lib/libnsl.so.1 (0x4004e000) > libc.so.6 => /lib/i686/libc.so.6 (0x40064000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) > > Ah, libreadline is missing! No, it's there, but it is > /usr/lib/libreadline.so.4.2. > > The question is why does amandad depend upon libreadline.so.4.1 > and not merely libreadline.so.4? Is this just some compiletime > mistake. The other libraries are only specified to their major number. The problem appears to be that, when libreadline was created, the shared object name (soname) was specified as 4.1, not just 4. gcc -shared -Wl,-soname,libreadline.so.4.1 ... So, any application compiled to use libreadline looks for 4.1, not just 4. Redhat 7.2 includes an rpm readline41-4.1-10.i386.rpm which provides libreadline.so.4.1, and readline 4.2 uses the correct soname, 4. From the readline 4.2 Changes file q. Changed the shared library creation procedure on Linux and BSD/OS 4.x so that the `soname' contains only the major version number rather than the major and minor numbers. Ron [EMAIL PROTECTED]
Re: newbie: gnutar problem?
Use tar not restore.
amrestore -p /dev/nrst0 fije /u3/mgmt | tar xfp -
Andrew
On Wed, 5 Dec 2001, Hussain Ali wrote:
>
> Hello,
>
> I have been using amanda without any problems for a while. I used to use
> dump but have switched to gnutar for dumps that are larger then the tape
> (ie using a more granular technique of direcotory partitioning )
>
> Now, it dumps fine, but i cannot recover the data that was archived via
> dump or gtar . I get the following error (for both gtarred and sumped
> disks):
>
> [root@fiji /tmp/tar 899]$ amrestore -p /dev/nrst0 fiji /u3/mgmt | restore
> ivbf 32 -
> amrestore: short file header block: 2048 bytes
> amrestore: WARNING: not at start of tape, file numbers will be offset
> amrestore: 0: reached end of tape: date Q
> Verify tape and initialize maps
> End-of-tape encountered
> Tape is not a dump tape
>
> note the tape is rewinded and "dd if=/dev/nst0 bs=32k count=1"
>
> AMANDA: TAPESTART DATE 20011130 TAPE normal-012
>
> the tape is good, ie it worked before i started using tar. from what i
> gather from the archives alot there are those who encountered these errors
> with gtar, but the seemed solved... now how do i go about it?
>
> thanks, in advance for any help...
>
> -Hussain
>
>
> * my environment:
>
> netbsd1.5
> gtar 1.12
> amanda2.4.2.p2
>
> * relevent amanda.conf:
>
> define dumptype mydir-nocompress {
> comment "Mydir compress dump type"
> compress none
> program "GNUTAR"
> index yes
> }
>
> relevant inetd.conf
>
> amanda dgram udp waitbackup /usr/pkg/libexec/amandad amandad
> amandaidx stream tcp nowait backup /usr/pkg/libexec/amindexd amindexd
> amidxtape stream tcp nowait backup /usr/pkg/libexec/amidxtaped
>amidxtaped
>
> * screen shot (trying to to recover file that was "dump"ed not
> * "tar"ed)
> amrecover> add dmesg.boot
> Added /var/run/dmesg.boot
> amrecover> extract
>
> Extracting files using tape drive /dev/st0 on host fiji.agiservices.com.
> The following tapes are needed: normal-012
>
> Restoring files into directory /tmp/tar
> Continue? [Y/n]: y
>
> Load tape normal-012 now
> Continue? [Y/n]: y
> Dec 3 11:19:47 fiji inetd[14799]: connection from fiji.agiservices.com,
> service amidxtape (tcp)
> Dec 3 11:19:48 fiji /netbsd: isp0: Bus 1 Target 3 at 10MHz Max Offset 8
> EOF, check amidxtaped.debug file on fiji.agiservices.com.
> amrecover: short block 0 bytes
> UNKNOWN file
> amrecover: Can't read file header
> extract_list - child returned non-zero status: 1
> Continue? [Y/n]: n
> amrecover> quit
>
> ** /tmp/amanda/amidxtaped
> amidxtaped: debug 1 pid 14799 ruid 32770 euid 32770 start time Mon Dec 3
> 11:19:47 2001
> amidxtaped: version 2.4.2.p2
> > SECURITY USER root
> bsd security: remote host fiji.agiservices.com user root local user backup
> amandahosts security check passed
> > 6
> amrestore_nargs=6
> > -h
> > -p
> > /dev/st0
> > fiji
> > ^wd0a$
> > 20011130
> Ready to execv amrestore with:
> path = /usr/pkg/sbin/amrestore
> argv[0] = "amrestore"
> argv[1] = "-h"
> argv[2] = "-p"
> argv[3] = "/dev/st0"
> argv[4] = "fiji"
> argv[5] = "^wd0a$"
> argv[6] = "20011130"
> amrestore: 0: skipping start of tape: date 20011130 label normal-012
> amrestore: missing file header block
> amrestore: 1: reached end of tape: date 20011130
> amidxtaped: amrestore terminated normally with status: 1
> Rewinding tape: done
> amidxtaped: pid 14799 finish time Mon Dec 3 11:19:53 2001
>
>
>
>
>
>
>
>
>
>
>
>
Re: Excludes not working
Joshua Baker-LePain wrote: > > On Tue, 4 Dec 2001 at 10:10am, Stephen Carville wrote > > > I have an exclude list that looks like: > > > > /proc > > /devices > > /tmp > > /temp > > /var/lock > > /var/spool/postfix/private > > /spool/postfix/private > > /var/tmp > > /lost+found > > *..LCK > > > > But amrecover tells me that amanda is still backing up these > > > Indicates that /tmp being excluded up but amanda _is_ backing it up. > > > > So how the frell do I get these directories excluded for real? > > Just a shot in the dark -- try "./tmp". With GNU tar, exclude paths are relative to the current filesystem (as defined in the disklist). On my system I exclude both /tmp and /var/tmp with the one exclude line "./tmp". If you want to exclude one but not the other you need to give / and /var different dumptypes and define different exclusion lists for those dumptypes. John
Re: Shit
On Wed, Dec 05, 2001 at 05:22:11PM +0100, Roy Andrè Tollefsen wrote: > Hello amanda-users, > > Can someone please tell how we can unsubscribe from this list? > > For the last time ... I call this spam there are instructions for this at http://www.amanda.org/ right there on the main page, where it talks about the mailing lists. > -- > geworth cheers, chris -- Christopher Linn, <[EMAIL PROTECTED]>| By no means shall either the CEC Staff System Administrator| or MTU be held in any way liable Center for Experimental Computation | for any opinions or conjecture I Michigan Technological University | hold to or imply to hold herein.
Re: newbie: gnutar problem?
On Wed, 5 Dec 2001 at 10:22am, Hussain Ali wrote > [root@fiji /tmp/tar 899]$ amrestore -p /dev/nrst0 fiji /u3/mgmt | restore > ivbf 32 - > amrestore: short file header block: 2048 bytes > amrestore: WARNING: not at start of tape, file numbers will be offset > amrestore: 0: reached end of tape: date Q > Verify tape and initialize maps > End-of-tape encountered > Tape is not a dump tape > > note the tape is rewinded and "dd if=/dev/nst0 bs=32k count=1" > > AMANDA: TAPESTART DATE 20011130 TAPE normal-012 If you're going to use amrestore, then don't dd the tape past the header! amrestore uses the header to identify the dump file. You only need to use dd to get past the header if you intend on using restore or 'tar x' directly. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Tape Usage
Why doesn't amanda use as much tape as I am giving it? I have amanda
configured to use two tape drives ( AIT SDX1-25C tapes ). My tapetype
states that the tapes are 24192 Mb in size. It filled the first tape
and used only used 8+ Gb of the second. Does amanda ever promote dump
levels or only demote them to reduce the dump size?
Total Full Daily
Estimate Time (hrs:min)0:15
Run Time (hrs:min)11:49
Dump Time (hrs:min) 46:18 40:06 6:12
Output Size (meg) 25957.024438.1 1519.0
Original Size (meg) 59025.654314.0 4711.5
Avg Compressed Size (%)44.0 45.0 32.2 (level:#disks ...)
Filesystems Dumped 181 16165 (1:145 2:20)
Avg Dump Rate (k/s) 159.5 173.3 69.7
Tape Time (hrs:min)2:06 1:51 0:16
Tape Size (meg) 25962.724438.6 1524.1
Tape Used (%) 107.3 101.06.3 (level:#disks ...)
Filesystems Taped 181 16165 (1:145 2:20)
Avg Tp Write Rate (k/s) 3511.1 3773.5 1660.1
NOTES:
planner: Incremental of coyote:hda3 bumped to level 2.
taper: tape 0029 kb 24751776 fm 179 writing file: No space left on device
taper: retrying emeraldfs1:sdb1.0 on new tape: [writing file: No space left on
device]
taper: tape 0030 kb 8929152 fm 3 [OK]
Re: AMRECOVER help!!
On Mon, 3 Dec 2001, Joseph Myers wrote:
- I have successfully completed a backup but am now trying to figure out the
- recover portion of the AMANDA program. Afterall, what good is a backup if
- you can't recover it. Here is my dilemna. I have two computers on a
- network.. Alpha1 and Intelraid1. Intelraid1 is the server and Alpha1 is
- the client so I'm trying to run amrecover on Alpha1 obviously. Here is the
- command I'm running followed by the output
-
- root@alpha1 /]# amrecover -C alpha1 -s intelraid1 -t intelraid1 -d
- /RAID/alpha1
- AMRECOVER Version 2.4.2p2. Contacting server on intelraid1 ...
- 220 intelraid1 AMANDA index server (2.4.2p2) ready.
- 200 Access OK
- Setting restore date to today (2001-12-03)
- 200 Working date set to 2001-12-03.
- 200 Config set to alpha1.
- 200 Dump host set to alpha1.xxx.xxx
- Can't determine disk and mount point from $CWD
- amrecover> setdisk /dev/sda3
- Scanning /RAID/alpha1...
- 20011121: found Amanda directory.
- 200 Disk set to /dev/sda3.
- No index records for disk for specified date
- If date correct, notify system administrator
- amrecover> setdisk /dev/sda3
- Scanning /RAID/alpha1...
- 20011121: found Amanda directory.
- 200 Disk set to /dev/sda3.
- No index records for disk for specified date
- If date correct, notify system administrator
-
- Ok.. here is the directory listing of /RAID/alpha1 on intelraid1:
-
- drwx--2 amanda amanda 4096 Dec 3 10:58 20011121
-
- And inside 20011121/ :
- -rw---1 amanda amanda 3925999616 Nov 21 11:12
- 192.168.1.3._dev_sda3.0
-
- obviously, I just did a dump onto the holding disk here because we have 100
- GB of RAID space to utilize so a tape drive just seems pointless. I'm
- pretty sure indexing is off, I don't know how to turn it on at least. My
- indexdir in my amanda.conf file is set to /usr/local/etc/amanda/alpha1.
- Can someone just tell me either (1) how to get this to work like it should
- or (2) how to use amrestore properly to get this to work? It's not
- imperative that I use this backup archive. The computer still works great
- and everything. I just need to make sure I can recover the files properly
- so if I have to turn on indexing or create another dump.. it's not a
- problem at all. Thanks for any help.
What I so is add indexing to my global dumptype and reference that in
sucessive dumptypes:
define dumptype global {
comment "Global definitions"
index yes
}
define dumptype user-tar {
global
program "GNUTAR"
compress none
priority medium
}
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
[EMAIL PROTECTED]
Re: slocate.cron
There was a version that I had this problem with. Installing the newest version of slocate should take care of the problem. Brian W Thomas Beer <[EMAIL PROTECTED]> said: > Hi, > > after installing amanda on two linux hosts, > I get on one the following error: > > /etc/cron.daily/slocate.cron: line 2: 5380 Segmentation fault > /usr/bin/updatedb -f "nfs,smbfs,ncpfs,proc,devpts" -e > "/tmp,/var/tmp,/usr/tmp,/afs,/net" > > I searched the archives and google, but had no luck. > > Any suggestions why? > > Thanks Tom > --
xinetd: amanda service was deactivated because of looping
I upgraded my amanda server from redhat 6.2 to redhat 7.1 and upgraded amanda from 2.4.1p1 to 2.4.2p2. I upgraded an amanda client to redhat 7.2 and replaced its copy of the amanda programs (/usr/local/libexec and /usr/local/sbin) with copies from the server. Afterward I got the infamous "xinetd: amanda service was deactivated ..." on the client during amcheck. I used tcpdump and saw only three udp packets from the server to the client, but watching xinetd I saw ten invocations of amandad on the client. So I did an strace of xinetd on the client and saw recvfrom(3, "A", 1, MSG_PEEK Since xinetd only peeks at the packet, what if amandad was failing to read the packet, then when it returned the packet would still be there, xinetd would invoke amandad again, voila looping. But why would amandad fail to read the packet? So, I did ldd on amandad ldd /usr/local/libexec/amandad libm.so.6 => /lib/i686/libm.so.6 (0x40027000) libreadline.so.4.1 => not found libtermcap.so.2 => /lib/libtermcap.so.2 (0x4004a000) libnsl.so.1 => /lib/libnsl.so.1 (0x4004e000) libc.so.6 => /lib/i686/libc.so.6 (0x40064000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) Ah, libreadline is missing! No, it's there, but it is /usr/lib/libreadline.so.4.2. The question is why does amandad depend upon libreadline.so.4.1 and not merely libreadline.so.4? Is this just some compiletime mistake. The other libraries are only specified to their major number. I guess I'm lazy, I'd rather not have to recompile amanda everytime libreadline is upgraded. :-) Thanks, Ron [EMAIL PROTECTED]
Shit
Hello amanda-users, Can someone please tell how we can unsubscribe from this list? For the last time ... I call this spam -- geworth
newbie: gnutar problem?
Hello,
I have been using amanda without any problems for a while. I used to use
dump but have switched to gnutar for dumps that are larger then the tape
(ie using a more granular technique of direcotory partitioning )
Now, it dumps fine, but i cannot recover the data that was archived via
dump or gtar . I get the following error (for both gtarred and sumped
disks):
[root@fiji /tmp/tar 899]$ amrestore -p /dev/nrst0 fiji /u3/mgmt | restore
ivbf 32 -
amrestore: short file header block: 2048 bytes
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of tape: date Q
Verify tape and initialize maps
End-of-tape encountered
Tape is not a dump tape
note the tape is rewinded and "dd if=/dev/nst0 bs=32k count=1"
AMANDA: TAPESTART DATE 20011130 TAPE normal-012
the tape is good, ie it worked before i started using tar. from what i
gather from the archives alot there are those who encountered these errors
with gtar, but the seemed solved... now how do i go about it?
thanks, in advance for any help...
-Hussain
* my environment:
netbsd 1.5
gtar1.12
amanda 2.4.2.p2
* relevent amanda.conf:
define dumptype mydir-nocompress {
comment "Mydir compress dump type"
compress none
program "GNUTAR"
index yes
}
relevant inetd.conf
amanda dgram udp waitbackup /usr/pkg/libexec/amandad amandad
amandaidx stream tcp nowait backup /usr/pkg/libexec/amindexd amindexd
amidxtape stream tcp nowait backup /usr/pkg/libexec/amidxtaped amidxtaped
* screen shot (trying to to recover file that was "dump"ed not
* "tar"ed)
amrecover> add dmesg.boot
Added /var/run/dmesg.boot
amrecover> extract
Extracting files using tape drive /dev/st0 on host fiji.agiservices.com.
The following tapes are needed: normal-012
Restoring files into directory /tmp/tar
Continue? [Y/n]: y
Load tape normal-012 now
Continue? [Y/n]: y
Dec 3 11:19:47 fiji inetd[14799]: connection from fiji.agiservices.com,
service amidxtape (tcp)
Dec 3 11:19:48 fiji /netbsd: isp0: Bus 1 Target 3 at 10MHz Max Offset 8
EOF, check amidxtaped.debug file on fiji.agiservices.com.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue? [Y/n]: n
amrecover> quit
** /tmp/amanda/amidxtaped
amidxtaped: debug 1 pid 14799 ruid 32770 euid 32770 start time Mon Dec 3
11:19:47 2001
amidxtaped: version 2.4.2.p2
> SECURITY USER root
bsd security: remote host fiji.agiservices.com user root local user backup
amandahosts security check passed
> 6
amrestore_nargs=6
> -h
> -p
> /dev/st0
> fiji
> ^wd0a$
> 20011130
Ready to execv amrestore with:
path = /usr/pkg/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "/dev/st0"
argv[4] = "fiji"
argv[5] = "^wd0a$"
argv[6] = "20011130"
amrestore: 0: skipping start of tape: date 20011130 label normal-012
amrestore: missing file header block
amrestore: 1: reached end of tape: date 20011130
amidxtaped: amrestore terminated normally with status: 1
Rewinding tape: done
amidxtaped: pid 14799 finish time Mon Dec 3 11:19:53 2001
newbie: gnutar problem?
Hello,
I have been using amanda without any problems for a while. I used to use
dump but have switched to gnutar for dumps that are larger then the tape
(ie using a more granular technique of direcotory partitioning )
Now, it dumps fine, but i cannot recover the data that was archived via
dump or gtar . I get the following error (for both gtarred and sumped
disks):
[root@fiji /tmp/tar 899]$ amrestore -p /dev/nrst0 fiji /u3/mgmt | restore
ivbf 32 -
amrestore: short file header block: 2048 bytes
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of tape: date Q
Verify tape and initialize maps
End-of-tape encountered
Tape is not a dump tape
note the tape is rewinded and "dd if=/dev/nst0 bs=32k count=1"
AMANDA: TAPESTART DATE 20011130 TAPE normal-012
the tape is good, ie it worked before i started using tar. from what i
gather from the archives alot there are those who encountered these errors
with gtar, but the seemed solved... now how do i go about it?
thanks, in advance for any help...
-Hussain
* my environment:
netbsd 1.5
gtar1.12
amanda 2.4.2.p2
* relevent amanda.conf:
define dumptype mydir-nocompress {
comment "Mydir compress dump type"
compress none
program "GNUTAR"
index yes
}
relevant inetd.conf
amanda dgram udp waitbackup /usr/pkg/libexec/amandad amandad
amandaidx stream tcp nowait backup /usr/pkg/libexec/amindexd amindexd
amidxtape stream tcp nowait backup /usr/pkg/libexec/amidxtaped amidxtaped
* screen shot (trying to to recover file that was "dump"ed not
* "tar"ed)
amrecover> add dmesg.boot
Added /var/run/dmesg.boot
amrecover> extract
Extracting files using tape drive /dev/st0 on host fiji.agiservices.com.
The following tapes are needed: normal-012
Restoring files into directory /tmp/tar
Continue? [Y/n]: y
Load tape normal-012 now
Continue? [Y/n]: y
Dec 3 11:19:47 fiji inetd[14799]: connection from fiji.agiservices.com,
service amidxtape (tcp)
Dec 3 11:19:48 fiji /netbsd: isp0: Bus 1 Target 3 at 10MHz Max Offset 8
EOF, check amidxtaped.debug file on fiji.agiservices.com.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue? [Y/n]: n
amrecover> quit
** /tmp/amanda/amidxtaped
amidxtaped: debug 1 pid 14799 ruid 32770 euid 32770 start time Mon Dec 3
11:19:47 2001
amidxtaped: version 2.4.2.p2
> SECURITY USER root
bsd security: remote host fiji.agiservices.com user root local user backup
amandahosts security check passed
> 6
amrestore_nargs=6
> -h
> -p
> /dev/st0
> fiji
> ^wd0a$
> 20011130
Ready to execv amrestore with:
path = /usr/pkg/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "/dev/st0"
argv[4] = "fiji"
argv[5] = "^wd0a$"
argv[6] = "20011130"
amrestore: 0: skipping start of tape: date 20011130 label normal-012
amrestore: missing file header block
amrestore: 1: reached end of tape: date 20011130
amidxtaped: amrestore terminated normally with status: 1
Rewinding tape: done
amidxtaped: pid 14799 finish time Mon Dec 3 11:19:53 2001
Re: Full dump not running in dumpcycle days
The only message in the FAILED AND STRANGE is that a file changed while reading it. amadmin CONFIG due tells me that each is overdue. I am going to do a little more looking into it today and will report my results tomorrow. Andrew On Tue, 4 Dec 2001, Joshua Baker-LePain wrote: > On Tue, 4 Dec 2001 at 2:42pm, [EMAIL PROTECTED] wrote > > > I do not have anything defined for "runspercycle". What messages are > > your refering to? I have the mails for each day. > > OK, runspercycle defaults to be the same as dumpcycle. Are you running > amdump every night? > > Are there any messages in the FAILED AND STRANGE DUMP SUMMARY or under > NOTES? > > What does 'amadmin CONFIG due' say? > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > >
Re: Why amverify complains about missing gtar?
On Tue, 4 Dec 2001 at 10:26pm, José Vicente Núñez Zuleta wrote > Do i need to recompile amanda in order to be able to > check the backups made using TAR on the tape (Solaris) > server? > Yes. Amanda determines and stores the locations of such things at compile time. If GNUtar wasn't there when you compiled amanda, then you need to recompile amanda for it to find gtar. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: replacing a tape
On Wed, 5 Dec 2001 at 12:08am, Gregory LeBaron wrote > Recently, my drive ate daily32. I continued to run without > problems until today when I did what I thought would be the > Right Thing: > $ amrmtape daily daily32 > And then with a new tape: > $ amlabel daily daily32 > > Now I'm getting: > $ amadmin daily tape > The next Amanda run should go onto a new tape. > > And: > [amanda@msr01 amanda]$ amflush daily > Expecting a new tape. (The last dumps were to tape daily28) > > The tapelist file no longer contains an entry for the tape daily32 > I'd thought that the amlabel would add that but I guess not... Whenever you have less active tapes than 'tapecycle', amanda expects a new tape on the next run. I *believe* that a tape isn't marked active until it's used -- IOW, just amlabeling one isn't going to do it. You could just feed amanda daily32 on the next run, but then your tapes will be "out of order" (note: only to you, not to amanda). Or you could try adding it to the tapelist by hand until after daily31 is used, then removing it and *then* using daily32 as your "new" tape. Personally, I'd go with the former -- it's annoying, but there's less chance of screwing things up. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrestore: error reading file header: Input/output error
On Tue, 4 Dec 2001 at 1:21pm, Benjamin Gross wrote > mt -f /dev/nst0 rewind > /usr/local/sbin/amrestore /dev/nst0 lopt > > I get: > > amrestore: 0: skipping start of tape: date 20011204 label Eatoni-01 > amrestore: error reading file header: Input/output error > > I'm running Amanda on a linux box, 2.4 kernel, which has a pair of > Onstream ADR.50 tape drives via scsi. Amanda is setup to backup restore > via dump/restore, not gnu tar. I'm new to using Amanda, so I'm not sure > what other information could be helpful. Any assistance would be > greatly appreciated. Can you dump/restore by hand to those tapes? Amrecover is just telling you what the OS told it. Look for errors in /var/log/messages, and try manually using the tapes. IIRC, there have always been issues with the Onstream drives and Linux. You can also try pulling the dump images off the tapes with dd. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: slocate.cron
On Mon, 3 Dec 2001 at 11:15am, Thomas Beer wrote > after installing amanda on two linux hosts, > I get on one the following error: > > /etc/cron.daily/slocate.cron: line 2: 5380 Segmentation fault > /usr/bin/updatedb -f "nfs,smbfs,ncpfs,proc,devpts" -e > "/tmp,/var/tmp,/usr/tmp,/afs,/net" I don't see at *all* how installing amanda would cause that. Random processes seg-faulting often means hardware trouble, oftentimes bad memory or too much heat. Try some other somewhat intensive programs (e.g. build a kernel with 'make -j4') and see if those complete successfully. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Complaining of user amanda even under root
...but "root" is not allowed to rsh to localhost as user "amanda"... I don't like "rsh" as a security mechanism, amandad should be tcpwrappered in inetd.conf or the equivalent for xinetd instead. Try recompiling / reinstalling amanda with the "--without-bsd-security" option. - Michael Hogsett > Hi there, > > I've tried to find another one like this in th archive without any luck. > Hopefully someone knows the answer. > > As I'm running SuSE 7.3 I have amanda automatically installed. I can run the > amcheck just fine. Also did backup fine by backing up locahost. I then tried > to read the tape with tar but got an error 'tar: /dev/st0 Cannot read Cannot > allocate memory'. Odd as I have 128MB and 66M free. > > So I looked up and discovered the backup log and so on. It all looks fine. So > > I thought I'd try the amrestore. Doing that results in error message: > > '500 Access not allowed: [access as amanda not allowed from root@localhost] > amandahostsauth failed'. > > The funny part is that I'm running as root, not amanda. > -- > > Steve Szmidt > V.P. Information > Video Group Distributors, Inc.
Re: [Amanda-users] amanda 2.4.3b1
On Sat, Dec 01, 2001 at 02:46:42PM +1100, Jason Thomas wrote:
> On Fri, Nov 30, 2001 at 04:51:20PM -0500, Jean-Louis Martineau wrote:
> > * tapeio.
>
> could someone provide a summary of what tapeio is/provides/fixes?
Look at the "OUTPUT DRIVERS" section of the amanda man page.
Jean-Louis
--
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
OUTPUT DRIVERS
The normal value for the tapedev parameter, or for what a
tape changer returns, is a full path name to a non-rewind
ing tape device, such as /dev/nst0 or /dev/rmt/0mn or
/dev/nst0.1 or whatever conventions the operating system
uses.Amanda provides additional application level
drivers that support non-tradition tape simulatation or
features. To access a specific output driver, set tapedev
(or configure your changer to return) a string of the form
driver:driver-info where driver is one of the supported
drivers and driver-info is optional additional information
needed by the driver.
The supported drivers are:
tape This is the default driver. The driver-info is
the tape device name. Entering /dev/rmt/0mn is
really a short hand for tape:/dev/rmt/0mn.
null This driver throws away anything written to it
and returns EOF for any reads except a special
case is made for reading a label, in which case
a "fake" value is returned that Amanda checks
for and allows through regardless of what you
have set in labelstr. The driver-info field is
not used and may be left blank:
tapedev "null:"
The length value from the associated tapetype is
used to limit the amount of data written. When
the limit is reached, the driver will simulate
end of tape.
NOTE: this driver should only be used for debug
ging and testing, and probably only with the
record option set to no.
rait Redundant Array of Inexpensive (?)Tapes.
Reads and writes tapes mounted on multiple
drives by spreading the data across N-1 drives
and using the last drive for a checksum. See
docs/RAIT for more information.
The driver-info field describes the devices to
use. Curly braces indicate multiple replace
ments in the string. For instance:
tapedev "rait:/dev/rmt/tps0d{4,5,6}n"
would use the following devices:
/dev/rmt/tps0d4n
/dev/rmt/tps0d5n
/dev/rmt/tps0d6n
file This driver emulates a tape device with a set of
files in a directory. The driver-info field
must be the name of an existing directory. The
driver will test for a subdirectory of that
named data and return offline until it is pre
sent. When present, the driver uses two files
in the data subdirectory for each tape file.
One contains the actual data. The other con
tains record length information.
The driver uses a file named status in the file
device directory to hold driver status informa
tion, such as tape position. If not present,
the driver will create it as though the device
is rewound.
The length value from the associated tapetype is
used to limit the amount of data written. When
the limit is reached, the driver will simulate
end of tape.
One way to use this driver with a real device
such as a CD is to create a directory for the
file device and one or more other directories
for the actual data. Create a symlink named
data in the file directory to one of the data
directories. Set the tapetype length to what
ever the medium will hold.
When Amanda fills the file device, remove the
symlink and (optionally) create a new symlink to
another data area. Use a CD writer software
package to burn the image from the first data
area.
To read the CD, mount it and create the data
symlink
Why amverify is not checking the tar backups?
Greetings, Our previous sysadmin installed amanda on our main Solaris server but didn't installed GNU tar on it; Now i'm doing some tar backups on our Linux clients but amverify refuses to check them becuase complains that "Gtar is not installed" (but now is it, at /usr/local/bin/tar and a simbolick link to /bin/gtar): Using device /dev/rmt/1bn Volume NEWBREAK_01, Date 20011203 Checked lenbkx0005._export_db__dump1.20011203.0 Checked lenbkx0001._export_data03.20011203.0 Skipped lnxsrv0001._boot.20011203.0 (** Cannot do /bin/gtar dumps) Checked lenbkx0005._export_apps.20011203.1 Checked lenbkx0001._export_data05.20011203.1 Checked lenbkx0005._.20011203.1 Checked lenbkx0001._export_data04.20011203.1 Checked lenbkx0005._export_home.20011203.1 Skipped lnxsrv0001._var.20011203.0 (** Cannot do /bin/gtar dumps) Checked lenbkx0005._usr.20011203.1 Checked lenbkx0001._export_data02.20011203.1 Checked lenbkx0001._export_data01.20011203.0 Checked lenbkx0001._usr.20011203.2 Checked lenbkx0001._apps.20011203.2 Checked lenbkx0001._.20011203.1 Checked lenbkx0001._export_data06.20011203.1 Checked lenbkx0001._export_home.20011203.2 Checked lenbkx0001._var.20011203.1 Checked lenbkx0001._export_data07.20011203.2 Do i need to recompile amanda in order to be able to check the backups made using TAR? Thanks in advance. 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
Static Compile
Alright. I'm currently going through a bit of fun trying to get a new version of the Linux amanda client compiled. I need to get it compiled statically since my clients are running various versions of the Linux system libraries. I was able to compile a static GNUtar just by setting the CFLAGS to "-O -pipe -static" before running configure and make. However, when I run amanda's configure and make with these options set I still get a dynamic binary like so: [bandix@scylla amanda-2.4.2p2]% ldd client-src/amandad libm.so.6 => /lib/i686/libm.so.6 (0x4002b000) libreadline.so.4 => /usr/lib/libreadline.so.4 (0x4004e000) libtermcap.so.2 => /lib/libtermcap.so.2 (0x40074000) libnsl.so.1 => /lib/libnsl.so.1 (0x40078000) libc.so.6 => /lib/i686/libc.so.6 (0x4008e000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) The only substantial difference between GNUtar and amanda's build processes I can discern is that amanda is using libtool. Any recommendations on how to get amanda convinced to compile everything statically? Brandon D. Valentine -- "Iam mens praetrepidans avet vagari." - G. Valerius Catullus, Carmina, XLVI
amrestore: error reading file header: Input/output error
Hello, I've recently installed Amanda 2.4.2p2. I've been able to successfully backup client machines many times, but I have yet to successfully restore from tape. I type the following when I try to restore: mt -f /dev/nst0 rewind /usr/local/sbin/amrestore /dev/nst0 lopt I get: amrestore: 0: skipping start of tape: date 20011204 label Eatoni-01 amrestore: error reading file header: Input/output error I'm running Amanda on a linux box, 2.4 kernel, which has a pair of Onstream ADR.50 tape drives via scsi. Amanda is setup to backup restore via dump/restore, not gnu tar. I'm new to using Amanda, so I'm not sure what other information could be helpful. Any assistance would be greatly appreciated. Thanks, Ben
Re: Problems dumping a big partition with Solaris and Linux
Hello --- Joshua Baker-LePain <[EMAIL PROTECTED]> escribió: > On Mon, 3 Dec 2001 at 11:40am, José Vicente Núñez > Zuleta wrote > > > > amstatus NEWBREAK --file > > backup-logs/NEWBREAK/amdump.3 > > Using /home/amanda/backup-logs/NEWBREAK/amdump.3 > from > > Sat Dec 1 02:30:00 EST 2001 > > > *snip* > > > lnxsrv0001:/dev/hdc5 > 012619006k > > dumping to tape (3:18:18) > > > 1 dumper busy : 0:42:57 ( 98.73%) > > When was that amstatus taken? Does it not *ever* > finish? It's going to > take a while to dump 12GB over the network. > Was taken 3 days ago (i got a problem communicating with my data center and they just replaced our tape today). That's why i sent an old dump (the last i tried). > Can you test the network speed from the Linux > client, maybe via ftp or > NFS? > I tested it ans is fine, we have a 100MB.sec connection between this boxes. I check it using Iperf. Here is the bandwidth from the linux box to the solaris box: [root@lnxsrv0001 iperf-1.1.1-redhat]# ./iperf -c 192.168.0.1 Client connecting to 192.168.0.1, TCP port 5001 TCP window size: 64.0 KByte (default) [ 3] local 192.168.0.10 port 1861 connected with 192.168.0.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 97.8 MBytes 78.2 Mbits/sec And here is the bandwidth from the Solaris box to the Linux box: # ./iperf -c lnxsrv0001 Client connecting to lnxsrv0001, TCP port 5001 TCP window size: 8.0 KByte (default) [ 4] local 192.168.0.1 port 51360 connected with 192.168.0.10 port 5001 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 79.4 MBytes 63.5 Mbits/sec > Are you using dump or tar on the Linux client? What > version, and what > distribution of Linux? I've seen dump hang more > than once... I'm using dump, Linux Redhat 6.2. If dump hangs how can i fix it? Thanks in advance. JV. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > = 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
Amanda and Linux client: Linux client never finishes the backup
Greetings, I'm running an Amanda Server under Solaris and one of my clients is a Linux box; That box has a partition filled with +/-28GB. All the backups run fine, but at the end i never manage to backup that huge partition: > amstatus NEWBREAK Using /home/amanda/backup-logs/NEWBREAK/amdump from Sat Dec 1 02:30:00 EST 2001 lenbkx0001:/ 11216k finished (2:37:02) lenbkx0001:/apps 0 2084032k finished (3:18:18) lenbkx0001:/export/data011 416k finished (2:36:36) lenbkx0001:/export/data021 32k finished (2:36:22) lenbkx0001:/export/data031 32k finished (2:35:23) lenbkx0001:/export/data041 32k finished (2:35:14) lenbkx0001:/export/data051 32k finished (2:34:56) lenbkx0001:/export/data061 32k finished (2:36:58) lenbkx0001:/export/data071 32k finished (2:36:38) lenbkx0001:/export/home 0 1306848k finished (2:52:05) lenbkx0001:/usr 1 32k finished (2:36:56) lenbkx0001:/var 13776k finished (2:36:45) lenbkx0005:/ 1 32k finished (2:35:08) lenbkx0005:/export/apps 1 32k finished (2:34:54) lenbkx0005:/export/home 1 64k finished (2:35:28) lnxsrv0001:/dev/hdc1 1 32k finished (2:34:51) lnxsrv0001:/dev/hdc5 012619006k dumping to tape (3:18:18) lnxsrv0001:/dev/hdc6 1 672k finished (2:35:20) SUMMARY part real estimated size size partition : 18 estimated : 18 16110660k failed : 0 0k ( 0.00%) wait for dumping: 0 0k ( 0.00%) dumping to tape : 1 12619006k ( 78.33%) dumping : 00k0k ( 0.00%) ( 0.00%) dumped : 17 3397344k 3491654k ( 97.30%) ( 21.09%) wait for writing: 00k0k ( 0.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 17 3397344k 3491654k ( 97.30%) ( 21.09%) 3 dumpers idle : not-idle taper writing, tapeq: 0 network free kps: 4848 holding space : 2097152k (100.00%) dumper0 busy : 0:42:50 ( 98.48%) dumper1 busy : 0:00:21 ( 0.83%) dumper2 busy : 0:00:03 ( 0.12%) taper busy : 0:42:06 ( 96.80%) 0 dumpers busy : 0:00:22 ( 0.85%) start-wait: 0:00:12 ( 54.57%) no-diskspace: 0:00:10 ( 45.43%) 1 dumper busy : 0:42:57 ( 98.73%) not-idle: 0:41:42 ( 97.12%) no-diskspace: 0:00:34 ( 1.33%) no-bandwidth: 0:00:31 ( 1.21%) start-wait: 0:00:08 ( 0.34%) 2 dumpers busy : 0:00:08 ( 0.33%) start-wait: 0:00:07 ( 84.82%) no-diskspace: 0:00:01 ( 15.18%) 3 dumpers busy : 0:00:02 ( 0.09%) start-wait: 0:00:02 (100.00%) In the server side i observe zombie taper processes: amanda 25673 25665 0 02:30:00 ?0:00 dumper NEWBREAK amanda 25675 25665 0 02:30:00 ?0:00 dumper NEWBREAK amanda 25672 25665 0 02:30:00 ?1:11 dumper NEWBREAK amanda 12107 12097 0 12:15:33 pts/40:00 -tcsh amanda 12125 12107 0 12:23:22 pts/40:00 grep amanda amanda 25660 25657 0 02:30:00 ?0:00 /bin/sh /home/amanda/sbin/amdump NEWBREAK amanda 25657 269 0 02:30:00 ?0:00 sh -c /home/amanda/sbin/amdump NEWBREAK amanda 25674 25665 0 02:30:00 ?0:00 dumper NEWBREAK amanda 25667 25665 0 02:30:00 ?0:34 taper NEWBREAK amanda 25857 25672 0 03:18:19 ? 45:43 /usr/local/bin/gzip --best amanda 25666 25665 0 0:00 amanda 25668 25667 0 02:30:00 ?0:12 taper NEWBREAK amanda 25665 25660 0 02:30:00 ?0:00 /home/amanda/libexec/driver NEWBREAK And on the clienps -[root@lnxsrv0001 /root]# ps -ef|grep amanda amanda2403 1 0 03:18 ?00:00:00 /home/amanda/libexec/sendbackup amanda2404 2403 0 03:18 ?00:00:03 dump 0usf 1048576 - /dev/hdc5 amanda2405 2404 0 03:18 ?00:00:22 dump 0usf 1048576 - /dev/hdc5 amanda2406 2405 0 03:18 ?00:00:59 dump 0usf 1048576 - /dev/hdc5 amanda2407 2405 0 03:18 ?00:00:59 dump 0usf 1048576 - /dev/hdc5 amanda2408 2405 0 03:18 ?00:00:58 dump 0usf 1048576 - /dev/hdc5 root 4116 4093 0 12:24 pts/900:00:00 grep amanda t a lot of idle dump processes: Thankx in advance. JV = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak
RE: Problem with windows 2000 Professional
Christophe, I use the samba package extensively (2.2.1a), though not for backup with amanda (yet) as you are trying. I tried a simple tar test using smbclient and had no problems. I connected to the client (my laptop, Win2k SP2, NTFS) from my amanda server (RH 7.1) as both myself and as my amanda user (member of the local Backup Operators group). Tarred up about 800K worth of files no problem. Then tested a bigger set of files (116 files, 46 directories, 550MB) also with no problems. Suspecting it might be disk space issue, I even tried this last test in a directory with not enough disk space to hold the resulting tar file. It failed as expected, but never froze. Try running your smbclient tests with a debug level of 3 and a log file (smbclient -l log -d 3) and see what the log says if/when the freeze occurs. Increasing the log level (up to 10) will give you incredible amounts of information (every function entry I believe). Also, check the Event Log on the client. Does the freezing only occur with one client or do other 2000 clients behave similarly? If not every client behaves the same, check permissions and/or service packs. I suspect the freeze occurs because the file may be in use. Or, if the tar is running for some time, perhaps a network problem. I searched the samba lists I'm a member of ([EMAIL PROTECTED], [EMAIL PROTECTED]) and didn't see any posts from yourself. You may try posting there also, check samba.org for the appropriate list (samba-users?). HTH, Doug > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Christophe Condomines > Sent: Thursday, November 29, 2001 7:09 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Problem with windows 2000 Professional > > > Hi, > > I am testing Amanda for my backup solution. > I use Amanda 2.2.4p2 on a Linux Red Hat 7.1 and > without any tape for the test. > The backup works fine on linux. > > I use samba 2.2.2 for the windows clients : > that works with NT and 98, but on windows 2000, the > amdump starts and > finally freeze. > I have checked the use of smbclient and a command > like tar c test.tar > produces the same freeze : smbclient starts to > retrieve some files and > finally stop. It's not always on the same file, it's > not always the same size, ... > Any suggestion ? > > I also try the amanda win32 client, failed on win95, > works on win2k > but very slowly. > Any comments ? > > > = > Christophe Condomines > [EMAIL PROTECTED] > > ___ > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! > Yahoo! Courrier : http://courrier.yahoo.fr >
AMRECOVER help!!
I have successfully completed a backup but am now trying to figure out the recover portion of the AMANDA program. Afterall, what good is a backup if you can't recover it. Here is my dilemna. I have two computers on a network.. Alpha1 and Intelraid1. Intelraid1 is the server and Alpha1 is the client so I'm trying to run amrecover on Alpha1 obviously. Here is the command I'm running followed by the output root@alpha1 /]# amrecover -C alpha1 -s intelraid1 -t intelraid1 -d /RAID/alpha1 AMRECOVER Version 2.4.2p2. Contacting server on intelraid1 ... 220 intelraid1 AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2001-12-03) 200 Working date set to 2001-12-03. 200 Config set to alpha1. 200 Dump host set to alpha1.xxx.xxx Can't determine disk and mount point from $CWD amrecover> setdisk /dev/sda3 Scanning /RAID/alpha1... 20011121: found Amanda directory. 200 Disk set to /dev/sda3. No index records for disk for specified date If date correct, notify system administrator amrecover> setdisk /dev/sda3 Scanning /RAID/alpha1... 20011121: found Amanda directory. 200 Disk set to /dev/sda3. No index records for disk for specified date If date correct, notify system administrator Ok.. here is the directory listing of /RAID/alpha1 on intelraid1: drwx--2 amanda amanda 4096 Dec 3 10:58 20011121 And inside 20011121/ : -rw---1 amanda amanda 3925999616 Nov 21 11:12 192.168.1.3._dev_sda3.0 obviously, I just did a dump onto the holding disk here because we have 100 GB of RAID space to utilize so a tape drive just seems pointless. I'm pretty sure indexing is off, I don't know how to turn it on at least. My indexdir in my amanda.conf file is set to /usr/local/etc/amanda/alpha1. Can someone just tell me either (1) how to get this to work like it should or (2) how to use amrestore properly to get this to work? It's not imperative that I use this backup archive. The computer still works great and everything. I just need to make sure I can recover the files properly so if I have to turn on indexing or create another dump.. it's not a problem at all. Thanks for any help. Joseph
Why amverify complains about missing gtar?
Greetings, Our previous sysadmin installed amanda on our main Solaris server but didn't installed GNU tar on it (now is installed at /usr/local/bin/tar and a simbolick link to /bin/gtar) ; I'm doing some tar backups on our Linux clients but amverify refuses to check them because complains that "Gtar is not installed" :( : Using device /dev/rmt/1bn Volume NEWBREAK_01, Date 20011203 Checked lenbkx0005._export_db__dump1.20011203.0 Checked lenbkx0001._export_data03.20011203.0 Skipped lnxsrv0001._boot.20011203.0 (** Cannot do /bin/gtar dumps) Checked lenbkx0005._export_apps.20011203.1 Checked lenbkx0001._export_data05.20011203.1 Checked lenbkx0005._.20011203.1 Checked lenbkx0001._export_data04.20011203.1 Checked lenbkx0005._export_home.20011203.1 Skipped lnxsrv0001._var.20011203.0 (** Cannot do /bin/gtar dumps) Checked lenbkx0005._usr.20011203.1 Checked lenbkx0001._export_data02.20011203.1 Checked lenbkx0001._export_data01.20011203.0 Checked lenbkx0001._usr.20011203.2 Checked lenbkx0001._apps.20011203.2 Checked lenbkx0001._.20011203.1 Checked lenbkx0001._export_data06.20011203.1 Checked lenbkx0001._export_home.20011203.2 Checked lenbkx0001._var.20011203.1 Checked lenbkx0001._export_data07.20011203.2 Do i need to recompile amanda in order to be able to check the backups made using TAR on the tape (Solaris) server? Thanks in advance. 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
Re[2]: Backing up only one host at a time and ...
On Tue, 4 Dec 2001 at 8:54am, Stefan G. Weichinger wrote > JBL> That sounds like a duplex mismatch. Are the 10M boxen on a switch smart > JBL> enough to deal with this? > > Yes there´s a switch inbetween. > Most of those slow boxes are connected via a hub (coax <-> cat5). > I monitored switch activity, the nic of the amanda machine negotiates > Full Duplex with 100M ... so I did not explicitly lock the nic to > 100M. I'm wondering if you're seeing lots of collisions when the 10M clients start dumping. > JBL> What is your runspercycle? Tapecycle *must* be >= (preferebably >) > JBL> runspercycle. Otherwise, you may be overwriting the *only* full dump of a > JBL> filesystem you have on tape. If that happens, you're SOL at restore time. > > I don´t have runspercycle set. > Wrong ? Gonna read about it once more. > > dumpcycle 14 > tapecycle 11 > runtapes 1 I believe (taking into account your next mail) that it's dumpcycle that needs the units. For example, I want a full dump of every filesystem once a week, running only on weeknights. So I have dumpcycle 1 week runspercycle 5 runtapes 1 I also want a 3 month history of dailies, so I have tapecycle 60 I'm guessing that what you want is: dumpcycle 2 weeks runspercycle 14 runtapes 1 As I mentioned, then, you need *at least* 14 tapes. 15 or 16 would be *much* better. > btw, what´s SOL ? The polite version is 'Sorry, Out of Luck'. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Backing up only one host at a time and ...
On Mon, 3 Dec 2001 at 9:56am, Stefan G. Weichinger wrote > 1) Not all hosts to be backed up have 100M-NICs inside, so while > dumping them it slows down the connection to 100M-hosts. > > (Getting about 10kB/s right now on the 100M-host, that´s not much ...) That sounds like a duplex mismatch. Are the 10M boxen on a switch smart enough to deal with this? > 2) I run multiple dumps a day right now because I´m constantly adding > new disks and testing parameters. My tapecycle is 11, my dumpcycle 14, > I have 11 tapes labeled and used them all already, so that they are in > my tapelist. > But amanda is still requesting new tapes. > Is this because I ran multiple dumps per day ? > How I can I tell her to use DAILY01 after DAILY11 explicitly ? What is your runspercycle? Tapecycle *must* be >= (preferebably >) runspercycle. Otherwise, you may be overwriting the *only* full dump of a filesystem you have on tape. If that happens, you're SOL at restore time. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Problems dumping a big partition with Solaris and Linux
On Mon, 3 Dec 2001 at 11:40am, José Vicente Núñez Zuleta wrote > > amstatus NEWBREAK --file > backup-logs/NEWBREAK/amdump.3 > Using /home/amanda/backup-logs/NEWBREAK/amdump.3 from > Sat Dec 1 02:30:00 EST 2001 > *snip* > lnxsrv0001:/dev/hdc5 012619006k > dumping to tape (3:18:18) > 1 dumper busy : 0:42:57 ( 98.73%) When was that amstatus taken? Does it not *ever* finish? It's going to take a while to dump 12GB over the network. Can you test the network speed from the Linux client, maybe via ftp or NFS? Are you using dump or tar on the Linux client? What version, and what distribution of Linux? I've seen dump hang more than once... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Excludes not working
I think you must add a dot before each exclude list entry and you must use shell wildcards: ./proc/* ./devices/* Those are relative to the partition roots, not necessarily to the filesystem root. Moritz Du schriebst am Dienstag, 4. Dezember 2001: > I have an exclude list that looks like: > /proc > /devices
RE: running Amrecover
Actually that's what I did and I still got the same message. Do I need to restart the inetd? for the .amandahosts to take effect? -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 4:13 PM To: Potts, Ross Cc: '[EMAIL PROTECTED]' Subject: Re: running Amrecover On Mon, 3 Dec 2001 at 10:18am, Potts, Ross wrote > I am trying to run Amrecover to recover a mailbox. When I run as Amanda, I am > told that the binary must run as root, when I run as root, I get "access as > Amanda not allowed from root@" You need to allow access to the amanda account on the tape server from root on the backup client. IOW, put '$CLIENTHOSTNAME root' in ~/.amandahosts on the tape server. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
slocate.cron
Hi, after installing amanda on two linux hosts, I get on one the following error: /etc/cron.daily/slocate.cron: line 2: 5380 Segmentation fault /usr/bin/updatedb -f "nfs,smbfs,ncpfs,proc,devpts" -e "/tmp,/var/tmp,/usr/tmp,/afs,/net" I searched the archives and google, but had no luck. Any suggestions why? Thanks Tom
Re: amrecover: No index records for host?
Thanks guys, worked like a charm. I figured that must have been it, didn't see a version of tar later than 1.13 at the mirror I went to initially. I'm using gnu tar 1.13.25 now with no problems (yet!) Thanks again, Rafe On Tue, 4 Dec 2001, Joshua Baker-LePain wrote: > On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote > > > 06573011000/./security/dev/audio > > 06573011000/./security/dev/fd0 > > 06573011000/./security/dev/sr0 > > 06573011000/./security/dev/st0 > > 06573011000/./security/dev/st1 > > > (these are just the contents of /etc on each host). The version of tar on > > the solaris machine is 1.13. I've heard tar can cause some problems. Do > > you think that might be it? > > Those are corrupted index files due to a bad version of tar. You need at > least 1.13.17, or 1.13.19. They're available from alpha.gnu.org. If the > location of GNUtar moves when you reinstall it, make sure to recompile > amanda so that it picks up the correct version. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > >
Re: [Amanda-users] Tried this before....
http://www.amanda.org/ WHERE TO GET MORE INFORMATION ABOUT AMANDA Amanda is completely unsupported and made available as-is. Unfortunately, we don't usually have the time to answer all user questions and help all new sites get started. However, we do maintain several mailing lists for those interested in Amanda. Please note: To subscribe or unsubscribe to a mailing list, DO NOT, EVER, send mail to that list. Send mail to [EMAIL PROTECTED] with the following line in the body of the message: subscribe and when you want to unsubscribe, use the following line in the body: unsubscribe where is one of the following: amanda-announce amanda-users amanda-hackers On Tue, Dec 04, 2001 at 06:47:38PM -0500, Ken Clark wrote: > unsubscribe [EMAIL PROTECTED] msg08679/pgp0.pgp Description: PGP signature
Re: amverify failing alot.
> Hi after 2 years of struggling with this crap and getting no where, can
> anyone help me figure out what is causing these errors.
> it seems to be random doesn't matter which tape or drive I use they all
> do it. even changing machine and scsi controllers doesn't fix the
> problem.
> is it something I'm doing wrong.
Which operating system do you use? Which version/s? Which tape devices
have you tried? Which SCSI controllers? Did the other tape backup
product work?
To me this looks like the tape device can't read the files on tape
("I/O error") and tar complains as a result of that ("Unexpected
EOF"). afaik amverify tends to mix up error message order in its
reports.
Moritz
> [...]
Amanda 2.4.2p2
I'm upgrading from 2.4.1p1 to 2.4.2p2 and I'm using the following line to run configure from the 2.4.2p2 source directory: ./configure --with-user=bin --with-group=bin --with-config=scms --with-gnutar=/usr/bin/tar --with-smbclient=/opt/samba/bin --with- testing --prefix=/opt/amanda2 Our original amanda is still in /opt/amanda so we put the new version in /opt/amanda2 for testing purposes hence --with-testing. The installation seems to go fine. In /opt/amanda2 there are the following directories: lib, libexec, man, sbin, share I created a etc directory and put my configuration files (updated for 2.4.2p2) in there. I made up a simple test configuration that simply backed up 1 directory on the localhost, but when I tried to label the tape by typing: ./amlabel test TEST1 while in the sbin directory. This produces the following error: amlabel: could not open conf file "/usr/local/etc/amanda/test/amanda.conf": No such file or directory It seems to be looking in /usr/local opposed to /opt/amanda2 why? Thanks in advance Dave - David Flood Systems Administrator [EMAIL PROTECTED] Tel: +44 (0)1224 262721 Robert Gordon University School of Computing St. Andrews Street Aberdeen -
amverify failing alot.
Hi after 2 years of struggling with this crap and getting no where, can anyone help me figure out what is causing these errors. it seems to be random doesn't matter which tape or drive I use they all do it. even changing machine and scsi controllers doesn't fix the problem. is it something I'm doing wrong. after playing with another tape backup product I found that it used a block size of 4096 for my tape drive (not 0 like everyone keeps telling me to use), so I changed to this and it seems to have made amverify fail less, but hasn't fixed the problem all together. thanks - Forwarded message from backup <[EMAIL PROTECTED]> - > Date: Wed, 5 Dec 2001 17:35:36 +1100 > From: backup <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: MonthlySet1 AMANDA VERIFY REPORT FOR MonthlySet101 MonthlySet102 > > Tapes: MonthlySet101 MonthlySet102 > Errors found: > MonthlySet102 (apophos.tsa._apophos.20011203.0): > amrestore: WARNING: not at start of tape, file numbers will be offset > amrestore: 0: restoring apophos.tsa._apophos.20011203.0 > /bin/tar: Skipping to next header > /bin/tar: Error exit delayed from previous errors > 64+0 records in > 64+0 records out > MonthlySet102 (hathor.tsa._hathor_projects1.20011203.0): > amrestore: WARNING: not at start of tape, file numbers will be offset > amrestore: 0: restoring hathor.tsa._hathor_projects1.20011203.0 > amrestore: read error: Input/output error > /bin/tar: Unexpected EOF in archive > /bin/tar: Error is not recoverable: exiting now > 64+0 records in > 64+0 records out > MonthlySet102 (): > amrestore: error reading file header: Input/output error > ** No header > 0+0 records in > 0+0 records out > MonthlySet102 (): > amrestore: error reading file header: Input/output error > ** No header > 0+0 records in > 0+0 records out > MonthlySet102 (): > amrestore: error reading file header: Input/output error > ** No header > 0+0 records in > 0+0 records out > MonthlySet102 (): > amrestore: error reading file header: Input/output error > ** No header > 0+0 records in > 0+0 records out > > amverify MonthlySet1 > Wed Dec 5 15:06:40 EST 2001 > > Loading current slot... > Using device /dev/scsi/host1/bus0/target15/lun0/mtn > Volume MonthlySet101, Date 20011205 > Checked set.ext.tsa._etc.20011205.0 > Checked sobek.tsa._etc.20011205.0 > Checked imhotep.ext.tsa._etc.20011205.0 > Checked bart.tsa._home.20011205.0 > Checked sothis.tsa._sothis_projects1.20011205.0 > Checked sothis.tsa._etc.20011205.0 > Checked sobek.tsa._sobek.20011205.0 > Checked sothis.tsa._sothis_projects3.20011205.0 > Checked imhotep.ext.tsa._imhotep.20011205.0 > Checked set.ext.tsa._mnt_hdc1.20011205.0 > End-of-Tape detected. > Loading next slot... > Using device /dev/scsi/host1/bus0/target15/lun0/mtn > Volume MonthlySet102, Date 20011203 > Checked hathor.tsa._hathor_httpd.20011203.0 > ** Error detected (apophos.tsa._apophos.20011203.0) > amrestore: WARNING: not at start of tape, file numbers will be offset > amrestore: 0: restoring apophos.tsa._apophos.20011203.0 > /bin/tar: Skipping to next header > /bin/tar: Error exit delayed from previous errors > 64+0 records in > 64+0 records out > Checked sothis.tsa._sothis_projects1.20011203.0 > Checked hathor.tsa._hathor_projects4.20011203.0 > ** Error detected (hathor.tsa._hathor_projects1.20011203.0) > amrestore: WARNING: not at start of tape, file numbers will be offset > amrestore: 0: restoring hathor.tsa._hathor_projects1.20011203.0 > amrestore: read error: Input/output error > /bin/tar: Unexpected EOF in archive > /bin/tar: Error is not recoverable: exiting now > 64+0 records in > 64+0 records out > ** Error detected () > amrestore: error reading file header: Input/output error > ** No header > 0+0 records in > 0+0 records out > ** Error detected () > amrestore: error reading file header: Input/output error > ** No header > 0+0 records in > 0+0 records out > ** Error detected () > amrestore: error reading file header: Input/output error > ** No header > 0+0 records in > 0+0 records out > ** Error detected () > amrestore: error reading file header: Input/output error > ** No header > 0+0 records in > 0+0 records out > Too many errors. > Loading next slot... > Using device /dev/scsi/host1/bus0/target15/lun0/mtn > Volume MonthlySet103, Date X > Fresh tape. Skipping... > Loading next slot... > Using device /dev/scsi/host1/bus0/target15/lun0/mtn > Volume MonthlySet104, Date X > Fresh tape. Skipping... > Loading next slot... > Using device /dev/scsi/host1/bus0/target15/lun0/mtn > Volume MonthlySet105, Date X > Fresh tape. Skipping... > Advancing past the last tape... - End forwarded message - -- Jason Thomas Phone: +61 2 6257 7111 System Administrator - UID 0 Fax:+61 2 6257 7311 tSA Consulting Group Pty. Ltd. Mobile: 0418 29 66 81 1 Hall Street Lyneham ACT 2602 http://www.topic.com.au/ msg08676/pgp0.pgp Description: PGP signature
