FW: Chris, some time ago we requested changes/corrections to two of our screens in the flash display you
Hi Aman - some ads for you to change -Original Message- From: John Baird [mailto:[EMAIL PROTECTED]] Sent: Thursday, 28 June 2001 15:53 To: Stephen Brown; [EMAIL PROTECTED] Subject: Chris, some time ago we requested changes/corrections to two of our screens in the flash display you Chris, some time ago we requested changes/corrections to two of our screens in the flash display you organise here at RNS. The fund-raising ad has a spelling mistake. it should read "gratefully received" Also the breast screen one should read "they're all over 50" could you fix these please and advise when done, thanks john John Baird Instructional Designer Multi-media Producer Head, Medical Illustrations RNS Hospital, St Leonards NSW 2065 Australia vox +61(0)2 9926 7723 fax +61(0)2 9926 6035 [EMAIL PROTECTED] * This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of NSW Health. *
No Subject
unsubscribe [EMAIL PROTECTED]
Re: dds3 or dds4?
Hi Tom, OK I got it now this is a charity. If the backups aren't too big and you have a big enough holding disk, you might consider a strategy where you do some dumps to the holding disk. For example, I have a config where on Wednesdays, I flush the holding disk and then do a dump with the tape in the drive, and the rest of the week I just dump to disk. If you are just backing up one or two servers, you might consider using a tool like rsync to mirror the disks to another server off site that is not web accessible, or ghosting to a removable hard drive. Lastly, you might consider looking for a corporate sponsor who could put the $ for the DDS4. Tom Strickland wrote: > I've just done some sums: > total for HP SureStore DDS3i, SCSI card, 20 tapes, delivery, VAT: 998.52UKP > total for HP SureStore DDS4i etc: 1408.71 UKP > total for HP DLT1, SCSI card, 20 tapes, delivery, VAT: 2441.415 > > Well, unless I'm being wildly ripped off somewhere, it looks as though > DDS is the only affordable solution. Probably DDS3, I'm afraid. I may > be able to work something out, but at the moment I don't have the > funds to be able to chip in myself. > > Anyway, thanks to all for the advice. Very helpful. -- "Jonathan F. Dill" ([EMAIL PROTECTED]) CARB Systems and Network Administrator Home Page: http://www.umbi.umd.edu/~dill
Re: Amanda 2.5.0 compile problems (Was: Amanda on AIX with an IBM 733 7 library)
>gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../client-src >-I../tape-src-g -O2 -c uscan.c >In file included from ../common-src/amanda.h:140, > from uscan.c:85: >/usr/include/sys/ioctl.h:218: warning: `ECHO' redefined >uscan.c:30: warning: this is the location of the previous definition >uscan.c:57: parse error before `Advanced' >uscan.c:81: `$' in identifier >uscan.c:81: numeric constant contains digits beyond the radix >uscan.c:81: `$' in identifier >... This looks like the uscan.c file didn't get built properly. The "ECHO" thing is supposed to be taken care of. And the "Advanced" message implies it tried to compile the Amanda copyright notice. You might remove it and let it get rebuilt from uscan.l (ditto for uparse.c, which will get rebuilt from uparse.y). I'm not sure if you also have to use flex rather than lex (and bison rather than yacc), but it certainly wouldn't hurt. The other thing you could do is skip recover-src since you're only interested in the SCSI changer. Go into the top level Makefile and find this line: RECOVER_SUBDIRS = recover-src Change it to: RECOVER_SUBDIRS = and Amanda should built but without the amrecover stuff. An (untested) alternative would be to add --without-amrecover to your ./configure line (you might also add --without-client). >Anthony > >P.S. Am I annoying you guys with all these requests? ... Not me. Anyone on this list should be used to a few hundred letters a day :-). And anything that makes Amanda better, such as getting the SCSI changer going on AIX, is a good thing (IMO). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: building 2.4.2p2 on SunOS 5.6
>Ran ./configure --with-user=bin --with-group=sys >... >By the way, this exact source compliled cleanly and is running >on the SGI amanda servers, my error is something specific to >my Sun machine or my parameters. That comment about "exact source" is a concern. Are you trying to build the Sun version in the same area you built the SGI version? To do that, you have to either remove config.cache or run "make distclean", then start with the ./configure step again. The ./configure script figures out (and remembers) a lot of very system specific details. It may still think it's set up for SGI. >humm, I suppose I should ask if there is a newer version >I should be building. I replaced 2.2.6 with 2.4.1p1 ... 2.4.1p1 is a few years old. The latest version is 2.4.2p2, and is available from www.amanda.org. >... The newer version ran successfully but apparently >doesn't have the chunksize that allows larger dumps to >go via the spool area and we ended up with several large/slow >direct to tape dumps. The chunksize setting only allows dumps to be split into pieces in the holding disk (it was meant for hosts that have a 2 GByte individual file size limitation). But the whole image still has to fit before it is sent to tape. If you don't have enough holding disk to do that, the image goes direct to tape. Some future work will change that, but that's the way it is for now. > Brian John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problem backing up
> Okay, I did the following command on the cobalt01 machine: > --- > /usr/local/libexec/runtar --create --directory /home --listed-incremental > /tmp/ff --sparse --one-file-system --ignore-failed-read --totals --file - > .>/dev/null > --- > > It gave me this result: > --- > /usr/local/libexec/runtar: ./mysql/mysql.sock: socket ignored > /usr/local/libexec/runtar: ./tmp/.s.PGSQL.5432: socket ignored > Total bytes written: 165928960 (158MB, 79MB/s) > --- Strange, can we see the result of a mount command And a du -s /home And a df Tho my logs tell me the command is: /usr/bin/tar --create --file /dev/null --directory /home --one-file-system --listed-incremental /tmp/ff --sparse --ignore-failed-read --totals . No --file option in it. Olivier
Re: building 2.4.2p2 on SunOS 5.6
> [newton] /tmp/amanda.new 23> make > Making all in config > Making all in common-src > /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../config >-I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE >-D_FILE_OFFSET_BITS=64 -g -O2 -c alloc.c > gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE >-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c alloc.c >-o alloc.o > In file included from /usr/include/sys/stream.h:26, > from /usr/include/netinet/in.h:38, > from /usr/include/netdb.h:96, > from amanda.h:105, > from alloc.c:33: > /usr/include/sys/model.h:35: parse error before `/' What machine are you running? I would say it looks like a faulty implementation of gcc. Gcc needs to reconfigure certain include files and use them in priority (from /usr/local/include). If this was not provided it could generate such message. Else I see no reasons system include files are faulty (or your system is heavily hacked :) Olivier
Re: amrecover problems
John R. Jackson wrote: > You're inetd.conf line is probably wrong. I'm betting you forgot to > put amidxtaped twice, e.g.: You are correct argh! always the small details ;) > amidxtape stream tcp nowait backup /opt/amanda/libexec/amidxtaped amidxtaped > > Without that trailing "amidxtaped", argv[0] is NULL and that's why the > dbprintf failed. Understood. Thanks again for the help on this. \Ben > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Building one one machine; using on another
>My (uneducated) guess is that it's just something that 2.8 has that 2.6 >doesn't... Well do install flex, then process to install amanda on the 2.6 machine, from the very begining, ie ./configure, etc It is very likely it will never work to ./configure on one OS and make on another OS, because libraries have changed. >/confugure purpose is to detect what is available on your system, so it cannot detect for another system obviously :) Olivier
Re: amrecover problems
>#3 0x13b48 in debug_printf (format=0x1bb70 "%s: version %s\n") at debug.c:64 >#4 0x127a0 in main (argc=0, argv=0xffbefd14) at amidxtaped.c:149 Oh, that problem. You're inetd.conf line is probably wrong. I'm betting you forgot to put amidxtaped twice, e.g.: amidxtape stream tcp nowait backup /opt/amanda/libexec/amidxtaped amidxtaped Without that trailing "amidxtaped", argv[0] is NULL and that's why the dbprintf failed. >\Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
How to turn on/off hardware compression
I am using SUN DDS3 tape device and SunOS 5.7. How can I turn on/off the hardware compression in this device? I cannot find any command such as "datcomp" or "comp" in "mt" man page. Thank you, - Sam
Off-site backup by extra tapes
We've been using Amanda here for several years, and it has performed flawlessly. I haven't seen much information about what people are doing for off-site backups, and I've concocted a scheme that I think will work. I'm curious if anyone has feedback on it. We've got a tape changer with 10 slots and the tapes in a removable carrier "rack". We've always had dumpcycle and runspercycle at 4 days, tapecycle set to 10 tapes, and everything runs nicely unattended. My plan is to get a second rack of tapes, and set tapecycle to 20. Then every time Amanda gets through the current rack, I'll swap it with the other one and take it off site. If I forget or am unable to get the off-site rack on time, the worst that happens is a backup or two sit on the holding disk and can be flushed when I'm able to swap racks. Since the dumpcycle is 4 days, either 10-tape rack will always contain a restorable backup set, with the worst-case scenario being that our level 0 is 14 days old. Since we do daily network off-site copies of our most critical files, that's an acceptable time for disaster recovery of everything else. Am I wrong in any of my assumptions, or missing something? -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/
2 problems left to solve - size and corruption issue
Hi listers: I'm desperate and hope someone can help. After several weeks I've almost got Amanda 2.4.2.p2 up and running properly on a FreeBSD 4.3-STABLE box with a HP SureStore 12000E DDS2 changer. I'm able to back up all but one of my boxes without a glitch. Of course the boxes I *can* back up all have small disks/volumes on them. These boxes are several FreeBSD boxes and a few NT and '9x boxes. Problem number one is that I can't seem to backup my one and only Windows 2000 Professional PC with it's shinny new 60GB HD, all on one big NTFS partition. I've removed as many programs and data as I can from this box, but there's still 6.5GB or so to backup. I'm using DDS2 tapes with hardware compression turned on. I don't use software compression because the median speed of most of my PCs is around a Pentium 133 (it's a home LAN)--it took forever to backup all my boxes with software compression. Plus, I have tons of tapes, so number of tapes used is not an issue for me. Backups fail with the message: //boxname/sharename lev 0 FAILED [too many taper retries] It's not because of lack of space on the holding disk. I went a bought a new 80GB drive just for this purpose. I don't think it's chunksize, I have it set to 3GB just to be safe. I can manually look at the holding disk during a backup and see that files around 3GB are being created. But they don't seem to get written. Is this because it's NOT possible with the current version of Amanda to backup a partition/volume/disk that's larger than a single tape media? If so that would really suck. I've thought of a few things to get around this. I could create multiple shares on the box instead of just C$, for example //boxname/winnt and //boxname/games. But the problem with this is getting files in the root directory backed up. The only way I see to do this is via C$ or equivalent. No? The second issue is more insidious and may/may not be related to the first problem. After every single backup attempt to the Windows 2000 box, a dialogue box pops up on the 2000 box warning me of data corruption! There's been different files involved each time. Today's dialogue box message was: The file or directory C:\cygwin\usr\share\terminfo\a\apple2e is corrupt and unreadable. Please run the Chkdsk utility. OUCH! I'll run Chkdsk and it will find index-related errors. It will successfully fix them. But the problem reoccurs as soon as I try to perform another Amanda backup of it. Weird, eh? The version of Samba I'm using is 2.0.9 from the FreeBSD ports collection. Any thoughts? TIA, Sean Noonan
Re: Amanda setup information request
> Anyways, what I am going to ask is this: > If I have a server that will EVENTUALLY need to backup remote boxes (hence the > amanda). However current it ONLY needs to back up itself. What is the > "proper" way I should be setting this up? DO I have to do a regular install > and THEN a client install? Any help would be appreciated. (IMHO) You should do a regular install which includes the server and client side stuff by default. Once you have that then you can just specify what disks/partitions (local OR remote) in the [config]/disklist file. Here's a snippet of what I got working: # We don't run compression on the master host since it is going to be # busy enough running amanda. tester78 / nocomp-root -1 local tester78 /var nocomp-user -1 local # note: -1 is a placeholder for the spindle number # the holding disk can't be dumped to itself, it uses a disktype that # specifies the "no-hold" option (see amanda.conf). tester78 /opt holding-disk -1 local tester78 being the machine with the Exabyte/AMANDA installed on it. In the same file I have: # tatyana (E250) tatyana / comp-root tatyana /var comp-root tatyana /opt comp-root tatyana /export/home comp-root with tatyana being a tape backup client. If amcheck is happy with it, then you're ready to go! HTH, Chris I'm a free-range carnivore.
Re: Building one one machine; using on another
>I think I'm going to ... install lex or flex on the 2.6 box. ... I forgot to mention that pre-built (pkgadd format) versions of most of these tools (but not Amanda itself -- sigh :-) are at: http://sunfreeware.com/ >> >Btw, I *did* manage to get a copy of 'flex' available to the 2.6 box (via >> >NFS) and it wasn't able to build. >> > >> >Are either of you (Olivier/JRJ) interested in the output? >> >> Sure. Maybe it's something minor. Go ahead and post it. > >Ok here we go... It's not too long actually as it got snagged early. > >taipei# make install >Making install in config >make[1]: Entering directory `/usr/share/src/amanda-2.4.2p2/config' Sorry. I thought by "it" you were talking about building flex. You already posted (or I've already seen) the "library -lgen: not found" stuff for Amanda. I looked at this a little more. Both libgen.a and libtermcap.a are in /usr/ccs/lib, so that may be yet another chunk the previous person removed (or never installed). If you get truly tied up in knots trying to make this machine into something that can compile, contact me offline. I run 2.6 and can probably build an Amanda for you. >Chris John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Building one one machine; using on another
Yeah, it should be, but I think that this machine had just the basics installed on it, and then the previous admin went through and got rid of things deemed unworthy. ;( After reading your other reply and JRJ's great reply, I think I'm going to take the situation by the scruff of the neck and install lex or flex on the 2.6 box. It's not what some people want, but it's a hell of a lot simpler than the alternatives... :) Cheers! Chris On Tue, 26 Jun 2001, Olivier Nicole wrote: > >The production tape server machine is running Solaris2.6 and doesn't have > >all of the marbles necessary (well it's missing lex at least) to configure > >the Makefile. At this point, installing lex on the 2.6 box isn't an > >option. > > Have you tried http://www.gnu.org/software/flex/flex.html > > And lex should be a standard tool of Solaris. > > Olivier > I'm a free-range carnivore.
RE Dell Powervault 120T DLT 7000 Autoloader
At 20:50 26/06/2001 +, Matt Fearnow <[EMAIL PROTECTED]> wrote: >I am new to amanda, and have read through all the emails regarding DLT >autoloader support. I have to admit I am totally confused now. I am not >sure if I should use chg-multi, chg-scsi, or even chg-zd-mtx I have seen >all of these referenced concerning DLT autoloaders. > >So after reading through these threads I have tried each of the above and >have not had any success on any of them. I am currently running RH 7.1 >kernel 2.4.2-2smp The advice to use chg-zd-mtx is good as this is a supported part of amanda. However when this question was asked a few months ago, Chris Pascoe posted a changer script called "chg-csee-mtx" which I am using in an almost identical setup to yours (I am using amanda 2.4.2p1 and RH7.1 on a Dell 2450 with a Powervault 120T Autoloader of which I am only using the first 5 slots). I did have to make one minor change to this script -- there was a typo in that a > and become a <, if I remember correctly. If you get nowhere with chg-zd-mtx, come back to me off list. Chris Ritson -- EMAIL: [EMAIL PROTECTED] POST: Chris Ritson, PHONE: +44 191 222 8175Department of Computing Science, FAX : +44 191 222 8232University of Newcastle upon Tyne, ROOM: 618 Claremont Bridge (the Mill) United Kingdom NE1 7RU.
scsi card for dat drive on linux
In my previous post I mentioned that we're looking to get an HP Surestore. The suppliers said that nothing less a rather expensive Adaptec card would do. If we need to buy an expensive Ultra-Wide card, we will. I would have thought that it was overkill for the speed that such a drive can manage? Am I missing something? Are the lower priced cards of such inferior quality that it would be a mistake to buy them? BTW - no SCSI hard drives in use at the moment - cannot afford them. thanks, Tom
Re: scsi card for dat drive on linux
On Wed, 27 Jun 2001, Tom Strickland wrote: >Date: Wed, 27 Jun 2001 11:40:42 + >From: Tom Strickland <[EMAIL PROTECTED]> >To: amanda <[EMAIL PROTECTED]> >Subject: scsi card for dat drive on linux > >In my previous post I mentioned that we're looking to get an HP >Surestore. The suppliers said that nothing less a rather expensive >Adaptec card would do. If we need to buy an expensive Ultra-Wide card, >we will. I would have thought that it was overkill for the speed that >such a drive can manage? Am I missing something? Are the lower priced >cards of such inferior quality that it would be a mistake to buy them? >BTW - no SCSI hard drives in use at the moment - cannot afford them. Well, one thing I learned is if your device is an UltraWide, and your interface card is a slow-narrow, you'll have to buy expensive adapters and cables to connect them together. The costs of these additional items and the instability they can add to your system (ie in time debugging the scsi chain, having the connectors fall off the back of the card due to the extra weight, etc) can drive your costss beyond what the UltraWide card would have cost you in the first place. I had to run a Scsi2 tape from a Scsi1 controller at a previous job, and even that small step was a pain. The on-device terminators didn't work and I had to add a second external terminator. The whole chain tended to hang and I'd have to powercycle the whole box to free it. (Luckily the system itself was IDE-disk based so I could always gracefully unmount everything except the scsi holding disk. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: dds3 or dds4?
On Wed, Jun 27, 2001 at 06:28:24PM +0200, Christoph Sold wrote: > [List reply stripped] > > Tom Strickland schrieb: > > On Wed, Jun 27, 2001 at 03:58:28PM +0200, Christoph Sold wrote: > > > Tom Strickland schrieb: > > > > We're on the verge of ordering a DDS drive (this week). It'll probably > > > > be an HP Surestore - but the question is DDS3 or DDS4? There's the > > > > obvious difference in capacity, but beyond that are there any other > > > > differences? Speed is an obvious one - any others? > > > > > > After some near disasters with DDS tapes, I suggest also considering > > > DLT1 tapes. Those never failed, even after long storage periods. They > > > come even pretty cheap. > > > > If only! If I was admin for a commercial enterprise, I'd go with DLT > > or similar - but as a charity branch we just can't afford it. > > Huh? This single DLT1 drive has cost less than 4000 Marks -- thats less > than $2000. Speaking of cheap, I again suggest looking at DLT1 drives. > Designed to compete with DDS drives. I've just done some sums: total for HP SureStore DDS3i, SCSI card, 20 tapes, delivery, VAT: 998.52UKP total for HP SureStore DDS4i etc: 1408.71 UKP total for HP DLT1, SCSI card, 20 tapes, delivery, VAT: 2441.415 Well, unless I'm being wildly ripped off somewhere, it looks as though DDS is the only affordable solution. Probably DDS3, I'm afraid. I may be able to work something out, but at the moment I don't have the funds to be able to chip in myself. Anyway, thanks to all for the advice. Very helpful. Tom
unsubscribe
unsubscribe
Re: scsi card for dat drive on linux
Also Sprach Joi Ellis: > Well, one thing I learned is if your device is an UltraWide, and your > interface card is a slow-narrow, you'll have to buy expensive adapters > and cables to connect them together. The costs of these additional > items and the instability they can add to your system (ie in time > debugging the scsi chain, having the connectors fall off the back of the > card due to the extra weight, etc) can drive your costss beyond what > the UltraWide card would have cost you in the first place. > Just another data point: Here is one of my backup server's dmesg: Vendor: HPModel: C1537ARev: L706 Type: Sequential-Access ANSI SCSI revision: 02 Vendor: HPModel: C1537ARev: L708 Type: Sequential-Access ANSI SCSI revision: 02 Vendor: HPModel: C1537ARev: L610 Type: Sequential-Access ANSI SCSI revision: 02 Vendor: ECRIX Model: VXA-1 Rev: 2524 Type: Sequential-Access ANSI SCSI revision: 02 Vendor: ECRIX Model: VXA-1 Rev: 2959 Type: Sequential-Access ANSI SCSI revision: 02 The 1537As are narrow, the Ecrix Wide LVD, the controller an Advansys fast narrow. The drives are external, the cabling is kept short: from controller to the first drive 1 meter, the rest 0.5 meter for a total external length of 3 m. The narrow drives are connected first, then a 50 to 68 pin cable with termination of the 18 pins connects the wide drives. A multimode terminator is at the end of the chain. I haven't had any SCSI errors in this configuration. I believe that the configuration does not violate the SCSI cabling and termination standards but I do admit I am surprised that it works w/o incident. I have done backups on one drive and restores from others at the same time w/o hanging the SCSI bus. The difference in cost between narrow and wide controllers is about $20, the same as for a 50 to 68 pin adapter, so I agree that getting a Wide card with a DDS4 drive is a good idea. In fact even if one buys DDS3 drive I'd go with the Wide controller and an adapter since going from Wide to Narrow is less hazardous than Narrow to Wide, and the likelihood is that you'll junk the DDS3 drives in a year for a larger capacity drive, and all those now come in SCSI Wide. -- C. Chan < [EMAIL PROTECTED] > Finger [EMAIL PROTECTED] for PGP public key.
Re: dds3 or dds4?
* Jonathan Dill <[EMAIL PROTECTED]> (Wed, Jun 27, 2001 at 08:43:16AM -0400) >> We're on the verge of ordering a DDS drive (this week). It'll probably >> be an HP Surestore - but the question is DDS3 or DDS4? There's the > where now some people are getting 75 GB and 180 GB disk drives, and with > new instruments the data sets are increasing in size rapidly. Even the > DDS4 isn't big enough anymore, so I'm having to look into getting a > tapedrive with higher capacity (or using GNUTAR to split up dumps, or > partitioning the drives into smaller chunks, both of which are kind of > messy solutions). If things are different in whatever business you are > in, maybe the DDS3 would be adequate, but it's something to think about. GNUTAR works surprisingly well in practice. As for bigger capacity drives, LTO is the wave of the future. Even DLT4 doesn't get beyond 35/70 whereas LTO comes in 100/200 (and it's only step 1 out of 4 on the roadmap. I think LTO4 (or maybe LTO3) is supposed to be able to handle 1T tapes. Currently listening to: Skinny Puppy - Smothered Hope (Demo) (Back And Forth Series Two) Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\<, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: dds3 or dds4?
Thanks...(comments inline) On Wed, Jun 27, 2001 at 08:43:16AM -0400, Jonathan Dill wrote: > Tom Strickland wrote: > > We're on the verge of ordering a DDS drive (this week). It'll probably > > be an HP Surestore - but the question is DDS3 or DDS4? There's the > > obvious difference in capacity, but beyond that are there any other > > differences? Speed is an obvious one - any others? > > Keep in mind that amanda can't "span" individual backups across multiple > tapes and think about your requirements. If you buy a new disk today, > 18 GB is probably the smallest size that you will find easily available, > and that number keeps going up. I work in an academic research lab > where now some people are getting 75 GB and 180 GB disk drives, and with > new instruments the data sets are increasing in size rapidly. Even the > DDS4 isn't big enough anymore, so I'm having to look into getting a > tapedrive with higher capacity (or using GNUTAR to split up dumps, or > partitioning the drives into smaller chunks, both of which are kind of > messy solutions). If things are different in whatever business you are > in, maybe the DDS3 would be adequate, but it's something to think about. The trouble is that the drive is for a charity. They are becoming more and more server-centric so it becomes increasingly important that we get some kind of off-site backup system in. Our problem is money. I suppose that I may be able to sell the difference in price. HOWEVER - my question was: does anyone know any differences between the two drives OTHER THAN size/speed? For instance, I know that some older models (not DDS3 or DDS4) don't perform read-after-write checking. I was wondering if there is any difference other than size/speed that would make me dump DDS3 in favour of DDS4. Thanks, Tom
Re: Building one one machine; using on another
On Tue, 26 Jun 2001, John R. Jackson wrote: > >Sooo, no go on that road. > > Not too surprising. > > >Btw, I *did* manage to get a copy of 'flex' available to the 2.6 box (via > >NFS) and it wasn't able to build. > > > >Are either of you (Olivier/JRJ) interested in the output? > > Sure. Maybe it's something minor. Go ahead and post it. Ok here we go... It's not too long actually as it got snagged early. taipei# make install Making install in config make[1]: Entering directory `/usr/share/src/amanda-2.4.2p2/config' make[2]: Entering directory `/usr/share/src/amanda-2.4.2p2/config' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/usr/share/src/amanda-2.4.2p2/config' make[1]: Leaving directory `/usr/share/src/amanda-2.4.2p2/config' Making install in common-src make[1]: Entering directory `/usr/share/src/amanda-2.4.2p2/common-src' /usr/bin/sh ../libtool --mode=link gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2-o genversion genversion.o versuff.o alloc.odebug.o error.o util.o file.o -lgen -lm -ltermcap -lsocket -lnsl -lintl gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion genversion.o versuff.o alloc.o debug.o error.o util.o file.o -lgen -lm -ltermcap -lsocket -lnsl -lintl ld: fatal: file values-Xa.o: open failed: No such file or directory ld: fatal: library -lgen: not found ld: fatal: library -ltermcap: not found ld: fatal: File processing errors. No output written to genversion collect2: ld returned 1 exit status make[1]: *** [genversion] Error 1 make[1]: Leaving directory `/usr/share/src/amanda-2.4.2p2/common-src' make: *** [install-recursive] Error 1 My (uneducated) guess is that it's just something that 2.8 has that 2.6 doesn't... Cheers, Chris I'm a free-range carnivore.
AW: Help: amrecover: 500 Access not allowed
Hi Christoph, try the following entries in your .amandahosts: --- client.local root client.local operator --- Maybe the parser don't expect more than one user after host. Be sure that the servername is exactly the same string in .amandahosts as amrecover will expect; i.e.: 500 Access not allowed:[acces as root not allowed from amserver.local.domain.com .amandahosts: => amserver.local.domain.com root cheers, Christian > -Ursprüngliche Nachricht- > Von: Christoph Sold [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 27. Juni 2001 16:11 > An: [EMAIL PROTECTED] > Betreff: Help: amrecover: 500 Access not allowed > > > Dear List, > > trying to restore a remote disk, I telneted to the remote > host, launched > amrecover, only to be greeted by the above mentioned access denied > message. What's wrong with my config? > > amserver: tape & index host > client: host to restore partially > > on host client: > > # amrecover > AMRECOVER Version 2.4.2p2. Contacting server on amserver.local ... > 220 amserver AMANDA index server (2.4.2p2) ready. > 500 Access not allowed:[acces as operator not allowed from > client.local] > amandahostsauth failed > # su -m operator > > amrecover > amrecover: amrecover must be run by root > > Ummm... here's .amadahosts from amserver:# > --- > localhost > amserver > amserver.local > client root operator > client.local root operator > --- > > Thanks in advance > -Christoph Sold >
Re: RE Dell Powervault 120T DLT 7000 Autoloader
You need to change your firstslot=0 to firstslot=1. The "Slots" that the changer.conf file is referring to are listed as "Storage Elements" when you do an mtx status. They go from 1 to 8. On Tuesday 26 June 2001 03:29 pm, you wrote: > Well I've made it a little further now. Atleast I can run different > commands and not get immediate errors. When I try to run amtape show I get > errors. Below is a dump of the logs from /tmp. Any thoughts from anyone? > > bash-2.04$ /usr/sbin/amtape DailySet1/ show > amtape: scanning all 7 slots in tape-changer rack: > amtape: could not load slot /usr/lib/amanda/chg-zd-mtx:: [: =: unary > operator expected > > bash-2.04$ less /tmp/amanda/amtape.20010626133019.debug > amtape: debug 1 pid 14016 ruid 33 euid 33 start time Tue Jun 26 13:30:19 > 2001 changer: got exit: 0 str: 0 7 1 > changer: got exit: 2 str: /usr/lib/amanda/chg-zd-mtx: [: =: unary operator > expected > could not load slot /usr/lib/amanda/chg-zd-mtx:: [: =: unary operator > expected amtape: pid 14016 finish time Tue Jun 26 13:30:21 2001 > > bash-2.04$ less /tmp/amanda/changer.debug.drive0 > Tue Jun 26 13:30:20 EDT 2001 Invoked with args '-info' > STATUS -> currently loaded slot = -1 > INFO -> current slot -1, last slot 7, can go backwards 1 > Tue Jun 26 13:30:20 EDT 2001 Invoked with args '-slot current' > STATUS -> currently loaded slot = -1 > LOADSLOT -> load tape from slot current > -> loading tape from slot to /dev/nst0 > -> status 1, result 'mtx: No source specified' > > Also my amanda.conf: > > runtapes 1 # number of tapes to be used in a single run of > amdump tpchanger "chg-zd-mtx" # the tape-changer glue script > tapedev "/dev/nst0" # the no-rewind tape device to be used > rawtapedev "/dev/null" # the raw device to be used (ftape only) > #changerfile "/var/lib/amanda/DailySet1/changer" > #changerfile "/var/lib/amanda/DailySet1/changer-status" > changerfile "/etc/amanda/DailySet1/changer" > changerdev "/dev/sg4" > > And changer.conf > > firstslot=0 1st tape slot > lastslot=7 Last tape slot > cleanslot=7 Slot with cleaner tape > ># Do you want to clean the drive after a certain number of accesses? ># NOTE - This is unreliable, since 'accesses' aren't 'uses', and we >#have no reliable way to count this. A single amcheck could >#generate as many accesses as slots you have, plus 1. ># ALSO NOTE - many modern tape loaders handle this automatically. > > AUTOCLEAN=0 Set to '1' or greater to enable > > autocleancount=99 Number of access before a clean. > > havereader=0 If you have a barcode reader, set to 1. > > offlinestatus=0 Set to 0 if 'mt status' gives an > "offline" when drive is offline. > Set to 1 or greater if 'mt status' > doesn't give and offline, rather an > "ONLINE" when drive is online. > > OFFLINE_BEFORE_UNLOAD=0 Does your tape driver require a > 'mt offline' before mtx unload? > > At Tuesday 6/26/2001 12:31 PM, Aaron Smith wrote: > > It looks good! Though I believe you'll need to drop the > >.conf off the changerfile entry, otherwise Amanda will look for > >/etc/amanda/DailySet1/changer.conf.conf and not find it. As for > >an example config file, there is one in the comments at the top > >of the chg-zd-mtx script itself. -- -- Aaron Smith vox: 616.226.9550 Network Directorfax: 616.349.9076 Nexcerpt, Inc. [EMAIL PROTECTED]
RE: Amanda 2.5.0 compile problems (Was: Amanda on AIX with an IBM 733 7 library)
Hello!
I get a little further each time. . . I added the Tape_Ioctl function to
scsi-aix.c and attempted to recompile. Here is the error that I got this
time:
gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../client-src
-I../tape-src-g -O2 -c uscan.c
In file included from ../common-src/amanda.h:140,
from uscan.c:85:
/usr/include/sys/ioctl.h:218: warning: `ECHO' redefined
uscan.c:30: warning: this is the location of the previous definition
uscan.c:57: parse error before `Advanced'
uscan.c:81: `$' in identifier
uscan.c:81: numeric constant contains digits beyond the radix
uscan.c:81: `$' in identifier
In file included from /usr/include/dirent.h:35,
from ../common-src/amanda.h:64,
from uscan.c:85:
/usr/include/sys/dir.h:84: parse error before `}'
make[1]: *** [uscan.o] Error 1
make[1]: Leaving directory `/home/amv/amanda-2.5.0/recover-src'
make: *** [all-recursive] Error 1
Thanks for your time!
Anthony
P.S. Am I annoying you guys with all these requests? I know that you guys
volunteer to do this, so I don't want to bother anyone too much. . .
> -Original Message-
> From: Thomas Hepper [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 27, 2001 4:34 AM
> To: [EMAIL PROTECTED]
> Cc: Anthony Valentine; '[EMAIL PROTECTED]'
> Subject: Re: Amanda 2.5.0 compile problems (Was: Amanda on AIX with an
> IBM 733 7 library)
>
>
> Hi,
> On Tue, Jun 26, 2001 at 07:06:09PM -0500, John R. Jackson wrote:
> [..]
> > >ld: 0711-317 ERROR: Undefined symbol: .Tape_Ioctl
> >
> > This looks like something Thomas Hepper will have to help you with.
> > It appears to be a general changer interface routine that is not yet
> > supplied for AIX.
>
> Yup thats missing, add the following to scsi-aix.c
>
> int Tape_Ioctl(int DeviceFD, int command)
> {
> return(-1);
> }
>
> Will fix this the next days...
>
> Thomas
> --
> ---
> | Thomas Hepper[EMAIL PROTECTED] |
> | ( If the above address fail try ) |
> | ( [EMAIL PROTECTED])|
> ---
>
building 2.4.2p2 on SunOS 5.6
Hello there, Ran ./configure --with-user=bin --with-group=sys seemingly successfully, then "# make clean" but when I ran "# make" I saw some errors that prevented the build from completing. humm, I suppose I should ask if there is a newer version I should be building. I replaced 2.2.6 with 2.4.1p1 which was built some time ago for a different amanda server on site. The newer version ran successfully but apparently doesn't have the chunksize that allows larger dumps to go via the spool area and we ended up with several large/slow direct to tape dumps. By the way, this exact source compliled cleanly and is running on the SGI amanda servers, my error is something specific to my Sun machine or my parameters. [newton] /tmp/amanda.new 23> make Making all in config Making all in common-src /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c alloc.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c alloc.c -o alloc.o In file included from /usr/include/sys/stream.h:26, from /usr/include/netinet/in.h:38, from /usr/include/netdb.h:96, from amanda.h:105, from alloc.c:33: /usr/include/sys/model.h:35: parse error before `/' In file included from /usr/include/netinet/in.h:38, from /usr/include/netdb.h:96, from amanda.h:105, from alloc.c:33: /usr/include/sys/stream.h:92: parse error before `}' /usr/include/sys/stream.h:92: warning: data definition has no type or storage class /usr/include/sys/stream.h:216: parse error before `queue_t' /usr/include/sys/stream.h:216: warning: no semicolon at end of struct or union /usr/include/sys/stream.h:218: warning: data definition has no type or storage class /usr/include/sys/stream.h:220: parse error before `}' /usr/include/sys/stream.h:274: parse error before `queue_t' /usr/include/sys/stream.h:274: warning: no semicolon at end of struct or union /usr/include/sys/stream.h:275: warning: data definition has no type or storage class /usr/include/sys/stream.h:425: parse error before `mblk_t' /usr/include/sys/stream.h:425: warning: no semicolon at end of struct or union /usr/include/sys/stream.h:427: parse error before `}' /usr/include/sys/stream.h:463: parse error before `mblk_t' /usr/include/sys/stream.h:463: warning: no semicolon at end of struct or union /usr/include/sys/stream.h:466: parse error before `}' /usr/include/sys/stream.h:479: field `copyreq' has incomplete type /usr/include/sys/stream.h:480: field `copyresp' has incomplete type *** Error code 1 make: Fatal error: Command failed for target `alloc.lo' Current working directory /tmp/amanda.new/common-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Any and all advice welcomed. thanks, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: dds3 or dds4?
On Wed, Jun 27, 2001 at 09:32:02AM -0500, C. Chan wrote: > Also Sprach Tom Strickland: > > The trouble is that the drive is for a charity. They are becoming more > > and more server-centric so it becomes increasingly important that we > > get some kind of off-site backup system in. Our problem is money. I > > suppose that I may be able to sell the difference in price. HOWEVER - > > my question was: does anyone know any differences between the two > > drives OTHER THAN size/speed? For instance, I know that some older > > models (not DDS3 or DDS4) don't perform read-after-write checking. I > > was wondering if there is any difference other than size/speed that > > would make me dump DDS3 in favour of DDS4. > > > > Understood. I have done some pro bono work for public schools and > they are often very short of cash. > As far as I know there are no significant differences other than > speed/size/price. > > Regarding DDS media reliability: > > A lot of admins, including myself, have had problems with > old DDS and DDS2 tapes. However, tape formulations for DDS3 > and DDS4 are considerably improved, and I have not had problems > with DDS3 tapes, except a couple from Sony which where DOA out > of the same box, after using them for the last 4 years. Since > DDS3 media is so cheap (less than $12 per cassette) use lots > of tapes in your Amanda configuration so you have at least two > or three full backups per cycle. Aha! Thanks. This is exactly the sort of info that I'm looking for. I think that I've made up my mind to go with DDS4 if it won't give the treasurer a coronary - otherwise DDS3. Thanks all, Tom
RE: scsi card for dat drive on linux
H...worked with DPT, Adaptec, Buslogic/Symbios Logic/NCR/LSI/whatever they are now Had no complaints about the performance of any of them...but advantage of the LSI's is price (or was, prior to U160 standard). Some linux drivers have been flaky over the years...but the hardware has worked well for all as far as my experience extends (but we all know, two environments, dozens of differences in how identical hardware can be used). bryan Bryan S. Sampsel Systems Administrator Ambeo, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony A. D. Talltree Sent: Wednesday, June 27, 2001 8:42 AM To: amanda Subject: Re: scsi card for dat drive on linux >get a cheap Adaptec PCI controller, since Adaptec is the standard in >compatibility. Back when I was forced to attemp to deliver services on x86 hardware, I had various flakiness with 2940's. Less, to be sure, than with the @#$@# Buslogic 946's that I was forced to use before, but still hassles, especially with more than one in a box. When I tried a DPT controller, everything worked perfectly. I wouldn't buy anything else for x86 hardware. As for speed, there's drive throughput, and there's transfer rate. The transfer rate can indeed be an issue -- slow transfers to the tape drive mean more bus occupancy, which means that there's more contention for disk access. This was especially bad eg. on SunOS 3.x, which didn't do SCSI disconnect/reconnect. Writing to a tape on that platform pretty much hung the whole machine if it had a SCSI system disk. So, if a given tape drive does fast and/or wide transfers, having matching support in the controller and cabling can make a difference.
Re: amrecover problems
John R. Jackson wrote: > You need to rebuild everything, not just amidxtaped, because of the > Amanda libraries it brings in. But you only need to install/test the > resulting amidxtaped binary. With --disable-shared involved, it should > be self-contained. did a 'make distclean' export CFLAGS=-g ./configure --disabled-shared make copied amidxtaped to /usr/local/libexec, and gave inetd a SIGHUP. Ran amrecover and tried extracting a file... core dump started gdb... atsun04:/tmp/amanda# gdb /usr/local/libexec/amidxtaped core GNU gdb 5.0 Copyright 2000 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.7"... Core was generated by `'. Program terminated with signal 11, Segmentation Fault. Reading symbols from /usr/lib/libgen.so.1...done. Loaded symbols for /usr/lib/libgen.so.1 Reading symbols from /usr/lib/libm.so.1...done. Loaded symbols for /usr/lib/libm.so.1 Reading symbols from /usr/lib/libcurses.so.1...done. Loaded symbols for /usr/lib/libcurses.so.1 Reading symbols from /usr/lib/libsocket.so.1...done. Loaded symbols for /usr/lib/libsocket.so.1 Reading symbols from /usr/lib/libnsl.so.1...done. Loaded symbols for /usr/lib/libnsl.so.1 Reading symbols from /usr/lib/libintl.so.1... warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 0074 done. Loaded symbols for /usr/lib/libintl.so.1 Reading symbols from /usr/lib/libc.so.1...done. Loaded symbols for /usr/lib/libc.so.1 Reading symbols from /usr/lib/libdl.so.1...done. Loaded symbols for /usr/lib/libdl.so.1 Reading symbols from /usr/lib/libmp.so.2...done. Loaded symbols for /usr/lib/libmp.so.2 Reading symbols from /usr/platform/SUNW,Ultra-4/lib/libc_psr.so.1...done. Loaded symbols for /usr/platform/SUNW,Ultra-4/lib/libc_psr.so.1 #0 0xff136dec in strlen () from /usr/lib/libc.so.1 (gdb) bt #0 0xff136dec in strlen () from /usr/lib/libc.so.1 #1 0xff17fe18 in _doprnt () from /usr/lib/libc.so.1 #2 0xff181c40 in vfprintf () from /usr/lib/libc.so.1 #3 0x13b48 in debug_printf (format=0x1bb70 "%s: version %s\n") at debug.c:64 #4 0x127a0 in main (argc=0, argv=0xffbefd14) at amidxtaped.c:149 (gdb) break main Breakpoint 1 at 0x12678: file amidxtaped.c, line 98. (gdb) run Starting program: /usr/local/libexec/amidxtaped warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 0074 Breakpoint 1, main (argc=1, argv=0xffbefcd4) at amidxtaped.c:98 98 char *buf = NULL; I did some stepping... and line 104 char *tapename = NULL; ?? Just to make sure that I'm not seeing things... I made sure to run amrecover with -d still NULL. Any help is appreciated apologies for the newbieness here on debugging c code, as I don't do this all too often ;) thanks, \Ben > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Building one one machine; using on another
>The production tape server machine is running Solaris2.6 and doesn't have >all of the marbles necessary (well it's missing lex at least) to configure >the Makefile. At this point, installing lex on the 2.6 box isn't an >option. Why? It's not privileged in any way, so you don't have to install it in any official place. Just build flex with prefix set to (e.g.) $HOME/flex, then make sure $HOME/flex/bin is in your PATH when you run the ./configure for Amanda and it will find and use it from there. Are you sure /usr/ccs/bin/lex doesn't exist on the 2.6 system? Sun puts it in a very odd spot, although if you found it on 2.8 you probably already know that. You might even do some serious cheating and drag the 2.8 version of lex over to the 2.6 machine in your PATH, but it might require some other files (I don't remember). As Olivier said, no way would I try to build Amanda on a more recent OS version (of any type) and take it back to a previous version. You are just asking for trouble (shared library versions, in particular). Another possibility is to build Amanda on the 2.8 system, run "make clean" there, then take that source tree over to the 2.6 system (use something like tar so the modification times stay the same) and try the build there. I don't think "make clean" will remove the .c files lex/flex and yacc/bison generate, so they should just be used. It's at least worth a shot. A variant would be to build Amanda on 2.8, then remove all the .o files (find . -name '*.o' -print | xargs rm) and tar that over to 2.6 and do the "make" again. Removing the .o's is more or less like "make clean", but "make clean" might have gotten rid of things you don't want it to. One other thing might bite you with this sequence. Running ./configure looks at your system for various things, such as where ufsdump is, where GNU tar is, how various OS calls work and so on. If the 2.6 system doesn't behave the same (i.e. some paths are different or some system calls are not there), it could lead to trouble. Except for not having the right paths, I don't think this will be too bad for those two versions of Solaris (I go the other direction all the time, i.e. build on 2.6 but run on 2.7 and 2.8), but it's something to keep in mind (and yet another reason to do the whole sequence on the lowest common denominator machine it will end up running on). >My configure line looks like this: > >./configure --with-user=amanda --with-group=backup --with-config=dailies >--host=sparc-sun-solaris2 --prefix=/usr/share/src/amanda-2.4.2p2/taipei >--exec-prefix=/usr/share/src/amanda-2.4.2p2/taipei FYI, you should not specify --host. Let ./configure figure it out. Also, --exec-prefix defaults to the same value as --prefix, so that's redundant. >I used the prefix options to try to corral the files into one place, but >I'm not sure if any files go elsewhere and my brain fries at about that >point. All of the files "make install" deals with will be put under --prefix, although most go in subdirectories (e.g. $prefix/sbin, $prefix/libexec and so on). The Amanda configuration areas can also go under $prefix or can be put elsewhere. For instance, I use this: ./configure --prefix=/opt/amanda-2.4.2p2 --with-configdir=/var/amanda ... >Also, I know I have to 'make' as the amanda user, but I'm supposed to >'make install' as root because of some various files and stuff. If that's >the case shouldn't I be 'make'ing on the 2.6 box (named taipei) instead? I'm sure with enough work and experience you could eventually make it happy :-), but at some point it's not worth the hassle. >Chris :) John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: dds3 or dds4?
The prices are not much different...unless you're talking a multi-tape setup. bryan Bryan S. Sampsel Systems Administrator Ambeo, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Strickland Sent: Wednesday, June 27, 2001 9:01 AM To: amanda Subject: Re: dds3 or dds4? On Wed, Jun 27, 2001 at 03:58:28PM +0200, Christoph Sold wrote: > > > Tom Strickland schrieb: > > > > We're on the verge of ordering a DDS drive (this week). It'll probably > > be an HP Surestore - but the question is DDS3 or DDS4? There's the > > obvious difference in capacity, but beyond that are there any other > > differences? Speed is an obvious one - any others? > > After some near disasters with DDS tapes, I suggest also considering > DLT1 tapes. Those never failed, even after long storage periods. They > come even pretty cheap. If only! If I was admin for a commercial enterprise, I'd go with DLT or similar - but as a charity branch we just can't afford it. Thanks, Tom
Re: Building one one machine; using on another
Well here's the results: I configured/'make'd amanda on a 2.8 box with everything I needed (gcc & the Sun forte cc). I did this as a regular user. I 'tar'd it up and ftp'd it over to the 2.6 box. This is what I got (I was root btw): taipei# make install Making install in config make[1]: Entering directory `/usr/share/src/amanda-2.4.2p2/config' make[2]: Entering directory `/usr/share/src/amanda-2.4.2p2/config' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/usr/share/src/amanda-2.4.2p2/config' make[1]: Leaving directory `/usr/share/src/amanda-2.4.2p2/config' Making install in common-src make[1]: Entering directory `/usr/share/src/amanda-2.4.2p2/common-src' /usr/bin/sh ../libtool --mode=link gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2-o genversion genversion.o versuff.o alloc.o debug.o error.o util.o file.o -lgen -lm -ltermcap -lsocket -lnsl -lintl gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -o genversion genversion.o versuff.o alloc.o debug.o error.o util.o file.o -lgen -lm -ltermcap -lsocket -lnsl -lintl ld: fatal: file values-Xa.o: open failed: No such file or directory ld: fatal: library -lgen: not found ld: fatal: library -ltermcap: not found ld: fatal: File processing errors. No output written to genversion collect2: ld returned 1 exit status make[1]: *** [genversion] Error 1 make[1]: Leaving directory `/usr/share/src/amanda-2.4.2p2/common-src' make: *** [install-recursive] Error 1 Sooo, no go on that road. Btw, I *did* manage to get a copy of 'flex' available to the 2.6 box (via NFS) and it wasn't able to build. Are either of you (Olivier/JRJ) interested in the output? For now I think I'm going to keep the old DDS stuff on that one machine (taipei.. aka 2.6) and just use another box with the Exabyte/AMANDA combo to back everything ELSE up. :) Thanks for all the input! Chris On Wed, 27 Jun 2001, Olivier Nicole wrote: > >Things like that are the reason I'm here, I believe. He's not here > >anymore, but I don't like to just go hog-wild over a system I've > >inherited. I'm unfamiliar with the functionalities of lex/flex so your > >feedback is good for me. :) > > As John said, grab flex, install it (must be as hard as ./configure, > make and maybe make check) in your home directory. > > The trick may be to be sure that this lex/flex is accessible by amanda > building process, so remember to add flex path into your PATH > environment variable. > > Then hopefully it should build. > > Luckily enough, lex is only used at buidling time to generate some .c > files, and then you can even wipe it out. > > Olivier > I'm a free-range carnivore.
Re: RE Dell Powervault 120T DLT 7000 Autoloader
Well, since I was "fingered" below ;) here's what I intended to be a config, in case you don't have it working yet. I am working out of the directory /etc/amanda/SMGDR0, with an ADIC SC100. Comments below... /etc/amanda/SMGDR0/amanda.conf (important stuff): ==8< tpchanger "chg-zd-mtx" tapedev "/dev/nst0" (Or whatever no-rewind device you use) changerfile "/etc/amanda/SMGDR0/ADIC" (I named it ADIC, but can be anything) changerdev "/dev/sg2" (whatever scsi-generic device the changer is) ==8< The changerfile is just a word that is used to name files. Chg-zd-mtx will create files as such (using above ADIC example): ADIC-access ADIC-barcodes ADIC-clean ADIC-slot You will need to create an ADIC.conf (again, ADIC is an example). There is a template located _within_ chg-zd-mtx (I'm not sure if the general Amanda documentation has this added yet?), but it will look like this: /etc/amanda/SMGDR0/ADIC.conf ==8< firstslot=2 1st tape slot lastslot=15 Last tape slot cleanslot=1 Slot with cleaner tape # Do you want to clean the drive after a certain number of accesses? # NOTE - This is unreliable, since 'accesses' aren't 'uses', and we #have no reliable way to count this. A single amcheck could #generate as many accesses as slots you have, plus 1. # ALSO NOTE - many modern tape loaders handle this automatically. AUTOCLEAN=0 Set to '1' or greater to enable autocleancount=99 Number of access before a clean. havereader=1 If you have a barcode reader, set to 1. offlinestatus=1 Set to 0 if 'mt status' gives an "offline" when drive is offline. Set to 1 or greater if 'mt status' doesn't give and offline, rather an "ONLINE" when drive is online. OFFLINE_BEFORE_UNLOAD=0 Does your tape driver require a 'mt offline' before mtx unload? ==8< All the items are needed, cause I'm a sucky programmer. ;) The cleanslot can be anything, and it doesn't have to be outside the firstslot - lastslot range. All that it means is "if a cleaning operation is called, where would the tape be". If you only do the cleaning manually, you can otherwise use that slot for a regular tape, and swap it manually before calling the cleaning job, or whatnot. Mine is set to 1, which is my mailslot, so I can feed it in without disturbing any tapes. Hope this helps... On Tue, 26 Jun 2001, John R. Jackson wrote: > >... When I try to run amtape show I get > >errors. Below is a dump of the logs from /tmp. Any thoughts from anyone? > > The "currently loaded slot = -1" seems to imply no tape is currently > loaded, which "-slot current" does not appear to be handling. In theory, > it should have seen the "-1" and used "firstslot" from your config file. > > The chg-zd-mtx script went through a large revision not long ago, so > it's hard to know exactly what version you have. The debug file you > quoted implies 2.4.2p2, but you said you were using 2.4.2. > > Here are a couple of suggestions: > > * See if you have this line in the comments at the start of the file: > > Modified by Jason Hollinden <[EMAIL PROTECTED]> on 13-Feb-2001 > > That would indicate you have the latest version. If you don't have > this version, get 2.4.2p2 from SourceForge and unpack it, then copy > just the chg-zd-mtx.sh.in file from it into whatever sources you're > working from (you might want to save the original, "just in case" :-). > Then "make" and "make install" to put it in place. > > * Try "amtape DailySet1 reset" and look at the changer debug file. > It should have a message like this: > > RESET -> loading tape from 1st slot ($firstslot) to $tape > > so you'll be able to see what firstslot is set to inside the > script. > > BTW, you probably should *not* put that trailing slash on the config > name. It's not needed, and I've seen cases (can't remember where) > recently where using the trailing slash on a directory name led > to problems. > > * Add these lines at the start of the script: > > exec 2> /tmp/chg-zd-mtx.$$ > set -x > > Find the loadslot() function and add the "set -x" to it as well. > > This will log a trace of all the statements to the file in /tmp and > hopefully we can see which one caused the "unary operator expected" > error, although I suspect it's related to the firstslot problem. > > >And changer.conf > > > >f
Re: RE Dell Powervault 120T DLT 7000 Autoloader
It looks good! Though I believe you'll need to drop the .conf off the changerfile entry, otherwise Amanda will look for /etc/amanda/DailySet1/changer.conf.conf and not find it. As for an example config file, there is one in the comments at the top of the chg-zd-mtx script itself. On Tuesday 26 June 2001 01:10 pm, you wrote: > Thanks for the heads up. I couldn't find a example config file for > chg-zd-mtx, is there one? > > Here is how amanda.conf is set, does this look correct then? > runtapes 1 # number of tapes to be used in a single run of > amdump tpchanger "chg-zd-mtx" # the tape-changer glue script > tapedev "/dev/nst0" # the no-rewind tape device to be used > rawtapedev "/dev/null" # the raw device to be used (ftape only) > #changerfile "/var/lib/amanda/DailySet1/changer" > #changerfile "/var/lib/amanda/DailySet1/changer-status" > changerfile "/etc/amanda/DailySet1/changer.conf" > changerdev "/dev/sg4" > > I have mtx installed. I can issue the following: > # /sbin/mtx -f /dev/sg4 inquiry > Product Type: Medium Changer > Vendor ID: 'ADIC' > Product ID: 'FastStor DLT' > Revision: 'D116' > Attached Changer: No > > # /sbin/mtx -f /dev/sg4 status >Storage Changer /dev/sg4:1 Drives, 7 Slots ( 0 Import/Export ) > Data Transfer Element 0:Empty >Storage Element 1:Full >Storage Element 2:Full >Storage Element 3:Full >Storage Element 4:Full >Storage Element 5:Full >Storage Element 6:Empty >Storage Element 7:Empty -- -- Aaron Smith vox: 616.226.9550 Network Directorfax: 616.349.9076 Nexcerpt, Inc. [EMAIL PROTECTED]
Re: scsi card for dat drive on linux
>get a cheap Adaptec PCI controller, since Adaptec is the standard in >compatibility. Back when I was forced to attemp to deliver services on x86 hardware, I had various flakiness with 2940's. Less, to be sure, than with the @#$@# Buslogic 946's that I was forced to use before, but still hassles, especially with more than one in a box. When I tried a DPT controller, everything worked perfectly. I wouldn't buy anything else for x86 hardware. As for speed, there's drive throughput, and there's transfer rate. The transfer rate can indeed be an issue -- slow transfers to the tape drive mean more bus occupancy, which means that there's more contention for disk access. This was especially bad eg. on SunOS 3.x, which didn't do SCSI disconnect/reconnect. Writing to a tape on that platform pretty much hung the whole machine if it had a SCSI system disk. So, if a given tape drive does fast and/or wide transfers, having matching support in the controller and cabling can make a difference.
Help: amrecover: 500 Access not allowed
Dear List, trying to restore a remote disk, I telneted to the remote host, launched amrecover, only to be greeted by the above mentioned access denied message. What's wrong with my config? amserver: tape & index host client: host to restore partially on host client: # amrecover AMRECOVER Version 2.4.2p2. Contacting server on amserver.local ... 220 amserver AMANDA index server (2.4.2p2) ready. 500 Access not allowed:[acces as operator not allowed from client.local] amandahostsauth failed # su -m operator > amrecover amrecover: amrecover must be run by root Ummm... here's .amadahosts from amserver:# --- localhost amserver amserver.local client root operator client.local root operator --- Thanks in advance -Christoph Sold
Re: dds3 or dds4?
On Wed, Jun 27, 2001 at 03:58:28PM +0200, Christoph Sold wrote: > > > Tom Strickland schrieb: > > > > We're on the verge of ordering a DDS drive (this week). It'll probably > > be an HP Surestore - but the question is DDS3 or DDS4? There's the > > obvious difference in capacity, but beyond that are there any other > > differences? Speed is an obvious one - any others? > > After some near disasters with DDS tapes, I suggest also considering > DLT1 tapes. Those never failed, even after long storage periods. They > come even pretty cheap. If only! If I was admin for a commercial enterprise, I'd go with DLT or similar - but as a charity branch we just can't afford it. Thanks, Tom
Re: dds3 or dds4?
Tom Strickland schrieb: > > We're on the verge of ordering a DDS drive (this week). It'll probably > be an HP Surestore - but the question is DDS3 or DDS4? There's the > obvious difference in capacity, but beyond that are there any other > differences? Speed is an obvious one - any others? After some near disasters with DDS tapes, I suggest also considering DLT1 tapes. Those never failed, even after long storage periods. They come even pretty cheap. Just my EUR.02 -Christoph Sold
Re: amcleanup don't work
On Tue, Jun 26, 2001 at 11:47:53AM -0500, John R. Jackson wrote: > >amcleanup send an email with an empty report and don't remove the > >indication that is still running an amdump or amflush. > > What happens if you run amreport by hand, **as the Amanda user**, with > just the config name as an arg: > > su -c "amreport " > > Does it complain about anything? Yes. It complains -- amreport: could not open template file "/usr/local/share/amanda/EXB-8500.ps":Permission denied Null message body; hope that's ok s85: nothing to print -- I have corrected the permissions of the file EXB-8500.ps and now everything seams to work. > > Ummm, if you're just getting started, you might want to get a new > Amanda release. 2.4.1p1 is years old. 2.4.2p2 is the latest. I think I will follow your sugestion, because with me amreport is very sensitive to the current directory. It works if my CWD is /etc/amanda/DailySet1. Thanks for your help. > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] > Jose Calhariz --
Re: scsi card for dat drive on linux
Also Sprach Tom Strickland: > In my previous post I mentioned that we're looking to get an HP > Surestore. The suppliers said that nothing less a rather expensive > Adaptec card would do. If we need to buy an expensive Ultra-Wide card, > we will. I would have thought that it was overkill for the speed that > such a drive can manage? Am I missing something? Are the lower priced > cards of such inferior quality that it would be a mistake to buy them? > BTW - no SCSI hard drives in use at the moment - cannot afford them. > > thanks, > > Tom > You should get the very biggest tape drive you can afford and even that won't be enough. If backward compatibility with DDS2 isn't an issue Ecrix VXATape is priced about the same as DDS4 and has a 33GB native capacity. For a few hundred dollars more there is Benchmark DLT (40GB), Sony AIT (35GB) and Tandberg SLR (20-50GB), all worthy technologies. As for SCSI controllers: I have used DDS3 (HP 1537A) with Adaptecs from an old 1542A (the one with all the jumpers) to a 2940, an Advansys, an NCR, an Initio, and a Tekram DC-315. All worked OK and are 50 pin SCSI-2. The Adaptec 1542A can be had free from a junk heap and the Tekram is about $25. I have used DDS4 drives (a Sony SDT10K and an HP SureStore) with NCR and Adaptec, and on some of the above mentioned with a 68 to 50 pin cable with proper termination of the 18 pins. I would say that the DDS drives are not terribly fussy with respect to SCSI controllers (note in passing: nor are the Ecrix VXATape drives since I tried them in the same configurations). The DDS3 only has a transfer rates of 1-2MBps on a good day and a DDS4 only 2-3MBps. So I'd say go ahead and try a cheapie controller. If it works buy another one - controllers do fail. If not, return it and get a cheap Adaptec PCI controller, since Adaptec is the standard in compatibility. -- C. Chan < [EMAIL PROTECTED] > Finger [EMAIL PROTECTED] for PGP public key.
Re: scsi card for dat drive on linux
On Wed, 27 Jun 2001 at 11:40am, Tom Strickland wrote > In my previous post I mentioned that we're looking to get an HP > Surestore. The suppliers said that nothing less a rather expensive > Adaptec card would do. If we need to buy an expensive Ultra-Wide card, Did they mention why? Did their testing demonstrate that the drives *won't* work with other cards, or that they *will* work on the Adaptec card? > we will. I would have thought that it was overkill for the speed that > such a drive can manage? Am I missing something? Are the lower priced > cards of such inferior quality that it would be a mistake to buy them? Well, I've got a 560GB IDE-SCSI RAID hanging off of a "cheap" Initio based U2W (LVD) SCSI card (a100u2w driver), and I can get 30+MB/s reading and writing to the RAID 5. I've actually had (knock on wood) more trouble with the Adaptec controllers integrated on the motherboard of the server than with that controller. The RAID supplier actually suggested that card over an Adaptec solution. Unless they can give you real good reasons backed up by testing, I'd be tempted to ignore them OTOH, this *is* a backup solution, and you don't want to tempt the fates too much. Your call, I'm just trying to provide a data point. Good luck. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Mac OS X
Has anyone compiled/run the Amanda client on a Mac OS X workstation? Thanks - Kevin
Re: RE Dell Powervault 120T DLT 7000 Autoloader
Thanks for the heads up. I couldn't find a example config file for chg-zd-mtx, is there one? Here is how amanda.conf is set, does this look correct then? runtapes 1 # number of tapes to be used in a single run of amdump tpchanger "chg-zd-mtx" # the tape-changer glue script tapedev "/dev/nst0" # the no-rewind tape device to be used rawtapedev "/dev/null" # the raw device to be used (ftape only) #changerfile "/var/lib/amanda/DailySet1/changer" #changerfile "/var/lib/amanda/DailySet1/changer-status" changerfile "/etc/amanda/DailySet1/changer.conf" changerdev "/dev/sg4" I have mtx installed. I can issue the following: # /sbin/mtx -f /dev/sg4 inquiry Product Type: Medium Changer Vendor ID: 'ADIC' Product ID: 'FastStor DLT' Revision: 'D116' Attached Changer: No # /sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 7 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Empty Storage Element 7:Empty
Re: Amanda 2.5.0 compile problems (Was: Amanda on AIX with an IBM 733 7 library)
Hi,
On Tue, Jun 26, 2001 at 07:06:09PM -0500, John R. Jackson wrote:
[..]
> >ld: 0711-317 ERROR: Undefined symbol: .Tape_Ioctl
>
> This looks like something Thomas Hepper will have to help you with.
> It appears to be a general changer interface routine that is not yet
> supplied for AIX.
Yup thats missing, add the following to scsi-aix.c
int Tape_Ioctl(int DeviceFD, int command)
{
return(-1);
}
Will fix this the next days...
Thomas
--
---
| Thomas Hepper[EMAIL PROTECTED] |
| ( If the above address fail try ) |
| ( [EMAIL PROTECTED])|
---
Re: dds3 or dds4?
Tom Strickland wrote: > We're on the verge of ordering a DDS drive (this week). It'll probably > be an HP Surestore - but the question is DDS3 or DDS4? There's the > obvious difference in capacity, but beyond that are there any other > differences? Speed is an obvious one - any others? Keep in mind that amanda can't "span" individual backups across multiple tapes and think about your requirements. If you buy a new disk today, 18 GB is probably the smallest size that you will find easily available, and that number keeps going up. I work in an academic research lab where now some people are getting 75 GB and 180 GB disk drives, and with new instruments the data sets are increasing in size rapidly. Even the DDS4 isn't big enough anymore, so I'm having to look into getting a tapedrive with higher capacity (or using GNUTAR to split up dumps, or partitioning the drives into smaller chunks, both of which are kind of messy solutions). If things are different in whatever business you are in, maybe the DDS3 would be adequate, but it's something to think about. -- "Jonathan F. Dill" ([EMAIL PROTECTED])
Re: RE Dell Powervault 120T DLT 7000 Autoloader
I have a similar unit, it identified itself in /proc/scsi/scsi as a Sony TSL 11000. I use the chg-zd-mtx script and it works just fine. Make sure you have the mtx package installed. On Tuesday 26 June 2001 10:00 am, you wrote: > Sorry, but to just follow up. I am trying to use amanda-2.4.2. > > >I am new to amanda, and have read through all the emails regarding DLT > >autoloader support. I have to admit I am totally confused now. I am not > >sure if I should use chg-multi, chg-scsi, or even chg-zd-mtx I have seen > >all of these referenced concerning DLT autoloaders. > > > >So after reading through these threads I have tried each of the above and > >have not had any success on any of them. I am currently running RH 7.1 > >kernel 2.4.2-2smp > > > >Any info would be appreciated. > > > >Matt -- -- Aaron Smith vox: 616.226.9550 Network Directorfax: 616.349.9076 Nexcerpt, Inc. [EMAIL PROTECTED]
Re: Problem backing up
Okay, I did the following command on the cobalt01 machine:
---
/usr/local/libexec/runtar --create --directory /home --listed-incremental
/tmp/ff --sparse --one-file-system --ignore-failed-read --totals --file -
.>/dev/null
---
It gave me this result:
---
/usr/local/libexec/runtar: ./mysql/mysql.sock: socket ignored
/usr/local/libexec/runtar: ./tmp/.s.PGSQL.5432: socket ignored
Total bytes written: 165928960 (158MB, 79MB/s)
---
160 Mb, not that much huh, and it gives me the answer in just 1.5 second or
so..
And I'm not quite sure that the duration of 1.5 second is okay... Is the
command used to make an
inventory of the data to backup?
The result doesn't look fatal, and probably isn't at all.
Would it help if I should exclude these files?
Or can I only exclude directories? Is there an example exclude.gtar file?
I've been unlucky in finding one up to now.
I haven't been able to do an amcheck while the process runs to see if any
data is transmitted at all. This is because the backup runs at night, and I
don't know if I can simulate a backup without using the backup tapes (thus
not increasing the tapenumber and amount of backups made). If I know that,
it would help me, so I can simulate and test...
Thanks again for additional help.
- Original Message -
From: John R. Jackson <[EMAIL PROTECTED]>
To: Robert Hoekstra <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, June 23, 2001 4:09 AM
Subject: Re: Problem backing up
> >FAIL dumper cobalt01.somewhere.nl /home 0 [data timeout]
> >...
> >Could it be because of MySQL (b)locking read-access to the tar process?
>
> As Olivier said, it's unlikely to be a locking problem. Unix does not,
> in general, apply mandatory locks. They are advisory, meaning a process
> (such as a backup program like GNU tar) is free to ignore them.
>
> If you watch the holding disk (or amstatus) while this is going on, how
> big does the image get? I'm interested in whether it's zero length,
> bigger than just the 32 KByte header, or if a lot of stuff got dumped
> and then it stalled.
>
> Here's another test. The /tmp/amanda/sendbackup*debug file on the client
> shows the GNU tar command line used.
>
> If you're doing a full dump (level 0), create a zero length temp
> file someplace ("cp /dev/null /tmp/xxx").
>
> Otherwise, look for the --listed-incremental flag file name. It should
> have a ".new" suffix. A file with that same name but without the ".new"
> should exist on the client. Copy that to the temp file.
>
> Now, run the command sendbackup tried to run but change the file passed
> to --listed-incremental to the temp file you just created. Send stdout
> of GNU tar to /dev/null (with output redirection -- do **not** change
> the --file argument) and see what happens.
>
> You can either run it like this as the Amanda user:
>
> .../runtar --create --file - ... > /dev/null
>
> or run it as root:
>
> gtar --create --file - ... > /dev/null
>
> As an alternative to ignoring the output, pipe the first GNU tar
> into a second that just does a catalogue ("... | gtar tvf -"). If it
> consistently gets to the same place when it hangs, that will tell you
> a lot about where the problem is.
>
> If it works fine and amdump/sendbackup still does not work, it's going
> to take some more head scratching (and probably some patches to try and
> log what's going on -- are you up for that?).
>
> >PS. the message is in plain text. ;-) ...
>
> Thanks! :-)
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
Re: tape record too big for supplied buffer
>... Amcheck says that the tape DAILY03 is active tape, ejects >the tape and sends me mail requesting to load Amanda tape (I use >chg-manual). ... Aha! Look in the chg-manual script for a line like this: $DD if=$tape count=1 >> $logfile 2>&1 Try changing it to this: $DD if=$tape bs=32k count=1 >> $logfile 2>&1 Let me know if that takes care of the problem and I'll make the change "official" (and look for any other similar "mistakes"). Without the "bs=32k", dd defaults to 512 bytes, which would certainly cause the message you're seeing. Thanks for bringing this up and providing just the right information to (hopefully) fix it. >BTW, if anyone on amanda-users list sees this, please drop me a >line off-list. ... My first response was triggered by your E-mail to the list, so it appears to be working. I know the list went through some ISP changes recently, and things have been a bit shaky since then, but I'm pretty sure the administrator is working on it. I'll forward your note just to be sure he's aware. >Toomas John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
dds3 or dds4?
We're on the verge of ordering a DDS drive (this week). It'll probably be an HP Surestore - but the question is DDS3 or DDS4? There's the obvious difference in capacity, but beyond that are there any other differences? Speed is an obvious one - any others? thanks, Tom
Re: Building one one machine; using on another
>Sooo, no go on that road. Not too surprising. >Btw, I *did* manage to get a copy of 'flex' available to the 2.6 box (via >NFS) and it wasn't able to build. > >Are either of you (Olivier/JRJ) interested in the output? Sure. Maybe it's something minor. Go ahead and post it. >Chris John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Building one one machine; using on another
>Things like that are the reason I'm here, I believe. He's not here >anymore, but I don't like to just go hog-wild over a system I've >inherited. I'm unfamiliar with the functionalities of lex/flex so your >feedback is good for me. :) As John said, grab flex, install it (must be as hard as ./configure, make and maybe make check) in your home directory. The trick may be to be sure that this lex/flex is accessible by amanda building process, so remember to add flex path into your PATH environment variable. Then hopefully it should build. Luckily enough, lex is only used at buidling time to generate some .c files, and then you can even wipe it out. Olivier
AW: disk /dev/dsk/c0t3d0s0 offline on arane.webcom.de?
Hello Mr. Jackson, thanks for your help! I solve the Problem. I had to copy 'sendbackup' in the right Direktory and I had to install gtar new Version on the Client. I'm very happy with this nice tool AMANDA :-). nice to meet you, God bless you, ... cu Bernd Zimmermann Betreff: Re: disk /dev/dsk/c0t3d0s0 offline on arane.webcom.de? >I get always the Message: >[disk /dev/dsk/c0t3d0s0 offline on arane.webcom.de?] Did you run amcheck? What did it say? What does /tmp/amanda/sendsize*debug on arane.webcom.de have to say about the "failing" disk? >Bernd Zimmermann John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: disk /dev/dsk/c0t3d0s0 offline on arane.webcom.de?
>I would like to Backup a Disk/Partition on a another Solaris(7)-Box. >I get always the Message: >[disk /dev/dsk/c0t3d0s0 offline on arane.webcom.de?] >What could it mean? What do I wrong? What does amcheck says about it? Olivier
Re: disk /dev/dsk/c0t3d0s0 offline on arane.webcom.de?
>I did'nt find anything about "failing" disk... What I meant was, did it say anything about /dev/dsk/c0t3d0s0? And it does not appear that it did. However, I asked the wrong question (sorry). I should have asked what was in /tmp/amanda/sendbackup*debug for that disk. Is "/" mounted from /dev/dsk/c0t3d0s0? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Building one one machine; using on another
>Btw, I *did* manage to get a copy of 'flex' available to the 2.6 box (via >NFS) and it wasn't able to build. Can't you get it fresh from GNU site? It looks like one can hardly trust things left around by the former guy :) Olivier
Re: amrecover problems
>Does it make the things run slower if a program is ALWAYS compiled with -g? In general, yes. How much is highly dependent on the program. For instance, if it's I/O bound or always doing system calls, then optimization doesn't buy you much. But it can be very noticeable in surprising places (even things that you think are I/O bound may do more CPU work than you expect). I don't know about specific portions of Amanda (just never tried it). But I'm also not entirely sure how you'd go about coercing autoconf, et al, to change from -O to -g. It's also not needed all that often any more. Most Amanda problems can be diagnosed from the logs and don't need a program debugger. Which is OK since most people don't know (and, because of the stability of modern systems, don't need to know) how to run them. >Olivier John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Too many filesystems to AMANDA?
"John R. Jackson" wrote: > > >When i run amdump the result is: > > > >[...] > >FAILED [badly formatted response from brutus] > > What's in the /tmp/amanda/amandad*debug file on brutus that matches > this error? Thanks for your answer. amandad.20010626104712.debug amandad: debug 1 pid 29654 ruid 507 euid 507 start time Tue Jun 26 10:47:12 2001 amandad: version 2.4.2p2 [...] GNUTAR //x.x.es/Cinetsrv 0 1970:1:1:0:0:0 1 [several more] [...] sending ack: Amanda 2.4 ACK HANDLE 000-38920708 SEQ 993545232 bsd security: remote host brutus.xpress.es user amanda local user amanda amandahosts security check passed amandad: running service "/usr/local/libexec/sendsize" amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-38920708 SEQ 993545232 OPTIONS maxdumps=1; FORMAT ERROR IN REQUEST PACKET amandad: got packet: Amanda 2.4 ACK HANDLE 000-38920708 SEQ 993545232 amandad: pid 29654 finish time Tue Jun 26 10:47:12 2001 > What happens if you run amcheck? When I run amcheck: Amanda Tape Server Host Check - Holding disk /var/dumps: 7519832 KB disk space available, that's plenty ERROR: cannot overwrite active tape prueba00 (expecting a new tape) NOTE: skipping tape-writable test [...] * Because I am doing tries, I want reuse the same tape and then I do: amrmtape prueba prueba00 Output: ** amrmtape: preserving original database in curinfo.orig.7722 (exported). Discarding Host: x.s.es, Disk: /usr/local/sbin/, Level: 0 Discarding Host: x.s.es, Disk: /var/lib/mysql/, Level: 0 Discarding Host: x.s.es, Disk: /etc/, Level: 0 Discarding Host: x.s.es, Disk: /opt/, Level: 0 ** amcleanup prueba Then I run again amcheck ... *** Amanda Tape Server Host Check - Holding disk /var/dumps: 7522880 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape prueba00 label ok NOTE: index dir /var/adm/amanda/prueba/index/us/__tr.s.es_Cinetsrv: does not exist NOTE: index dir /var/adm/amanda/prueba/index/us/__px.s.es_Dinetsrv: does not exist NOTE: index dir /var/adm/amanda/prueba/index/us/__px.s.es_Cinetsrv: does not exist NOTE: index dir /var/adm/amanda/prueba/index/us/__as.s.es_Dinetsrv: does not exist NOTE: index dir /var/adm/amanda/prueba/index/us/__as.s.es_Cinetsrv: does not exist NOTE: index dir /var/adm/amanda/prueba/index/us/__ob.s.es_Dinetsrv: does not exist NOTE: index dir /var/adm/amanda/prueba/index/us/_us al_: does not exist NOTE: index dir /var/adm/amanda/prueba/index/us/_v_dir_v_: does not exist Server check took 0.223 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 7.340 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) *** And a new amandad.20010626195211.debug * amandad: debug 1 pid 7985 ruid 507 euid 507 start time Tue Jun 26 19:52:11 2001 amandad: version 2.4.2p2 [...] got packet: Amanda 2.4 REQ HANDLE 000-589D0708 SEQ 993577931 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR //tr.ss.es/Cinetsrv 0 OPTIONS |;bsd-auth;index; [so on, alls the same, Cinetsrv 0 OPTIONS |;bsd-auth;index;] sending ack: Amanda 2.4 ACK HANDLE 000-589D0708 SEQ 993577931 bsd security: remote host brutus.xpress.es user amanda local user amanda amandahosts security check passed amandad: running service "/usr/local/libexec/selfcheck" amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-589D0708 SEQ 993577931 OPTIONS ; OK \\th.ss.es\Cbaloe OK \\pa.ss.es\Dprueba [...] OK /usr/local/libexec/runtar executable OK /bin/gtar executable OK /etc/amandates read/writable OK /usr/local/var/amanda/gnutar-lists/. read/writable OK /usr/bin/smbclient executable OK [/etc/amandapass is readable, but not by all] OK /dev/null read/writable OK /tmp/amanda has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: got packet: Amanda 2.4 ACK HANDLE 000-589D0708 SEQ 993577931 amandad: pid 7985 finish time Tue Jun 26 19:52:18 2001 * And the selfcheck: * [...] selfcheck: checking disk //tr.ss.es/Cinetsrv selfcheck: spawning /usr/bin/smbclient in pipeline selfcheck: argument list: smbclient \\th.ss.es\Camalon -U xxx -E -c quit selfcheck: OK selfcheck: extra info: added interface ip=a.b.c.d bcast=a.b.c.255 nmask=255.255.255.0: session request to TH.SS.ES failed (Called name not present): Domain=[YY] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] [...] * > >I have tried chance MAX_DGRAM (64*1024) to M
