Re: Changing tape block size
"John R. Jackson" wrote: > > >... If I > >could increase the buffer size to 1199840 then I could achive about 15 > >megabytes a second. As it is now I am wasting space and time writing 32K > >blocks. > > 1199840 is a strange number (as in, not a power of 2). Could you live > with a blocksize of 1199104 (1171 KBytes)? That would waste 736 bytes > on each track (less than 1%). It might be interesting to try some dd > tests with 32 KBytes and 1171 KBytes to see how it does. 1171 KBytes would be fine. The Ampex engineer recommended that if the memory used is page aligned use 1168. That is the largest multiple of 8K memory pages (the page size on a SGI.) > Is 1199840 usable data, or does it include stuff the drive adds? The ECC is stored on a seperate track. All of the 1199840 bytes are usable. > In any case, I can give you a larger blocksize right now, with some > caveats. Go to the FAQ and look for the couple of articles on how to > build Amanda from the CVS sources. You want branch amanda-242-tapeio. > Then just set blocksize in your tapetype as needed (see the amanda(8) > man page). I'll try it. Thank you for the help. -- Robert MinskCentropolis Effects, LLC. [EMAIL PROTECTED]10950 Washington Blvd., Studio B Culver City, Ca. 90232-4025
Re: Changing tape block size
>... If I >could increase the buffer size to 1199840 then I could achive about 15 >megabytes a second. As it is now I am wasting space and time writing 32K >blocks. 1199840 is a strange number (as in, not a power of 2). Could you live with a blocksize of 1199104 (1171 KBytes)? That would waste 736 bytes on each track (less than 1%). It might be interesting to try some dd tests with 32 KBytes and 1171 KBytes to see how it does. Is 1199840 usable data, or does it include stuff the drive adds? In any case, I can give you a larger blocksize right now, with some caveats. Go to the FAQ and look for the couple of articles on how to build Amanda from the CVS sources. You want branch amanda-242-tapeio. Then just set blocksize in your tapetype as needed (see the amanda(8) man page). Note that this code is brand new. I *think* it's right, but other than the testing I did, it is not in production anyplace. >In the current version of amanda is there any way to pipe the output thru >"dd" to change the block size? It would be pretty hard. Taper is a complicated I/O processor built for speed and it also needs to be able to deal with error handling. It's not a simple Unix process in a pipeline you can tack something on the end of. Such is the price of progress :-). You might be able to increase TAPE_BLOCK_SIZE in amanda.h (my concern before was when you wanted to decrease it). I think one or two other people have done this, but I don't know what else they had to change to get it to work. >Robert Minsk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Parallel estimates
>I have noticed that amanda does not do it estimates in parallel. >Is this something I can configure? All clients are processed in parallel, i.e. estimate requests are sent to all the clients at the same time. To increase the number of requests processed in parallel on a given client, raise "maxdumps" in amanda.conf (see amanda(8) for more info). Note that this is the same knob used for running the real dumps, i.e. increasing it will allow multiple dumps to run on that client, not just estimates. >Robert Minsk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Changing tape block size
"John R. Jackson" wrote: > > >With the variable block size device the drive makes no assumptions about the > >data coming down the pipe and does not buffer. This means every write request > >goes stright to the tape. > > Ah, I see. None of the device I'm familiar with do that (that I know of). > I just got off the phone with the programmer who supports the drivers on the SGI. Because of how they do there ECC checks each write to the variable block size device writes a track. A track is exactly 1199840 bytes. If I could increase the buffer size to 1199840 then I could achive about 15 megabytes a second. As it is now I am wasting space and time writing 32K blocks. As a side the way the non variable block size device works is it buffers 146 8K blocks (the biggest multiple of 8K < 1199840) and sends that to the drive. Because of buffering and a wasted 3K of space the drive speed is about 10 megs a second. In the current version of amanda is there any way to pipe the output thru "dd" to change the block size? > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Robert MinskCentropolis Effects, LLC. [EMAIL PROTECTED]10950 Washington Blvd., Studio B Culver City, Ca. 90232-4025
Re: RESULTS MISSING
>FAILURE AND STRANGE DUMP SUMMARY: > localhost /etc RESULTS MISSING What version of Amanda? First, don't use "localhost" in your disklist. It will bite you eventually. Use the fully qualified host name. Next, look at /tmp/amanda/sendsize*debug. That's likely where the problem will show up. >Elisa Dalla John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Changing tape block size
>With the variable block size device the drive makes no assumptions about the >data coming down the pipe and does not buffer. This means every write request >goes stright to the tape. Ah, I see. None of the device I'm familiar with do that (that I know of). >Would anything break if I set the TAPE_BLOCK_SIZE to 8 in common-src/amanda.h? I wouldn't do it. While making the user defined blocksize change I found quite a few places things were mixed up w.r.t. tape blocks, disk blocks, and even network buffering, and I think there were even some hard coded values floating around (sigh). Let me think on this a bit. >Robert Minsk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Changing tape block size
"John R. Jackson" wrote: > > Is the 8K value a hardware blocking factor? Can you set the device to > variable blocking? > On the SGI the non variable block size device is fixed at 8K. I can actually change the tape drive block size to anything I want but the SGI limits you to 8K. With the variable block size device the drive makes no assumptions about the data coming down the pipe and does not buffer. This means every write request goes stright to the tape. The DST has a maximum speed of about 15 megabytes per second. We have achived close to 10 megabytes on the non variable (8K) device and only and 400 kilobytes on the variable block size device. > I was considering adding code to deal with folks who write with variable > and then the device gets set to a fixed size, and that might be at least > part of the fix for you. The rest would probably be some minor tweaking > in taper. If you really need to go that route, let me know. I would need blocksizes at least down to 8K. Would anything break if I set the TAPE_BLOCK_SIZE to 8 in common-src/amanda.h? > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Robert MinskCentropolis Effects, LLC. [EMAIL PROTECTED]10950 Washington Blvd., Studio B Culver City, Ca. 90232-4025
Re: Changing tape block size
>We are using a Ampex DST for our backups. It performs best when using an >8k block size. Currently amanda uses at 32k block size which ends up being >about a factor of 10 slower than using an 8k block size. How do I configure >amanda to use an 8k block size? You don't. I'll be applying a change (hopefully in a few minutes) that will let you change the tape block size, but the minimum is 32 KBytes. Most people have whined about 32 KBytes being too small, so it's unusual to hear of someone wanting to go your direction. Is the 8K value a hardware blocking factor? Can you set the device to variable blocking? I was considering adding code to deal with folks who write with variable and then the device gets set to a fixed size, and that might be at least part of the fix for you. The rest would probably be some minor tweaking in taper. If you really need to go that route, let me know. >Robert Minsk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: restore=ufsrestore?
>> If I do a >> 'file DUMPFILENAME', it shows it as a "USTAR Tar file', and if I do a >> 'tar tvf DUMPFILENAME' I can view all the contents correctly. > > Then you're all set. Use GNU tar to extract whatever you want. You're right! In amanda.conf was set to use gnutar instead of dump, the problem is that I was using solaris tar instead of gnutar. I installed gnutar and everything works and life is good! This is not the first problem I have with solaris tar, it seems to have many issues also with long pathnames, but that's other story. Thanks again for your help! Ignacio Tripodi
Parallel estimates
I have noticed that amanda does not do it estimates in parallel. Is this something I can configure? -- Robert MinskCentropolis Effects, LLC. [EMAIL PROTECTED]10950 Washington Blvd., Studio B Culver City, Ca. 90232-4025
Re: amanda + tape changer + solaris 8
Hi, On Tue, Jul 31, 2001 at 11:13:15AM +0200, thomas graichen wrote: [...] > use inside of amanda ... any help would be appreciated First which version of amanda ?. Lets assume 2.4.2p2 from cvs, if not please get the cvs version. Next try the following (From the 2.5.0 docs, i must update the 2.4.2 docs :-)) Solaris with sst kernel module, which is not any longer needed in solaris 2.8. See in the contrib/sst directory The configuration on solaris 2.8 with the sgen driver is done by creating the file /kernel/drv/sgen.conf This file should contain at the beginning the following device-type-config-list="changer","sequential" This will force the driver to attach only to the devices with type either changer (the robot) and sequential (the tape). Next you must tell the driver on which id it should check for devices (in this example tape on id 5, robot on id 6), name="sgen" class="scsi" target=5 lun=0; name="sgen" class="scsi" target=6 lun=0; This will create the 2 device files /dev/scsi/sequential/c0t5d0 (scsitapedev option in chg-scsi.conf) /dev/scsi/changer/c0t6d0(changer option in chg-scsi.conf) So the complete sgen.conf looks like: device-type-config-list="changer","sequential name="sgen" class="scsi" target=5 lun=0; name="sgen" class="scsi" target=6 lun=0; Now you must create the chg-scsi.conf file, take a look in the examples directory for an starting point. To enable chg-scsi you need the following in amanda.conf tpchanger "chg-scsi"# the tape-changer glue script tapedev "0" changerfile "path_to_your_config/chg-scsi.conf" Now change to your config directory (where amanda.conf is in) and try to call there chg-scsi path_to_chg-scsi/chg-scsi -info If you get an result you can try path_to_chg-scsi/chg-scsi -reset and see if the first tape is loaded. Try this an report back success/failures :-) Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
Changing tape block size
We are using a Ampex DST for our backups. It performs best when using an 8k block size. Currently amanda uses at 32k block size which ends up being about a factor of 10 slower than using an 8k block size. How do I configure amanda to use an 8k block size? -- Robert MinskCentropolis Effects, LLC. [EMAIL PROTECTED]10950 Washington Blvd., Studio B Culver City, Ca. 90232-4025
Re: limiting amanda's network usage
On Tue, 31 Jul 2001, John R. Jackson wrote:
> >Does "netusage" actually do anything with regard to the amount of
> >bandwidth amanda uses? ...
>
> No. From the amanda(8) man page ("INTERFACE SECTION"):
Right, I saw that. But "netusage" is not in that section, it's under the
global "CONFIG FILE PARAMETERS" section. I assumed that the note that you
quote applied only to "use" directives in interface {} blocks.
Thanks though. I will give traffic-shaping at the router a shot.
Dan Debertin
--
++ Desist from enumerating your fowl
++ prior to their emergence
++ from the oblong embryo container
++ Dan Debertin
++ Senior Systems Administrator
++ Bitstream Underground, LLC
++ [EMAIL PROTECTED]
++ (612)321-9290 x108
++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387
Re: limiting amanda's network usage
>Right, I saw that. ...
What??? You read the man page??? :-)
>But "netusage" is not in that section, it's under the
>global "CONFIG FILE PARAMETERS" section. ...
But it refers you to the interface section.
Netusage was the original limit in Amanda. Then someone wanted finer
grained control and added multiple limits (interfaces). But because we
never, ever :-), take something *out* of amanda.conf, netusage is still
there as sort of a global/default value.
>I assumed that the note that you
>quote applied only to "use" directives in interface {} blocks.
It also applies to netusage.
>Dan Debertin
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
UNSUBSCRIBE
UNSUBSCRIBE
not an amanda tape???
Hello there,
I figure my last mail was less than informative - usually not my
style and I apologize.
Anyway, one problem seems to persist and I'm clueless as to what
may cause it.
So, my amanda server is a FreeBSD 4.3 STABLE machine with a
Tandberg MLR1.
amanda is version 2.4.1p1, installed from the ports.
Now, what I do is the following: I try and label a tape and
amlabel appears to do it without any complaints:
$ amlabel Hundert6 Hundert601
rewinding, reading label, not an amanda tape
rewinding, writing label Hundert601, done.
... however, each and every time I try it, amlabel keeps telling
me the tape is not an amanda tape.
Consequently amcheck reports the following:
ERROR: /dev/sa0: not
an amanda tape.
(expecting a new tape)
NOTE: skipping tape-writable test.
Any hint what could be causing this? I wrote the tapetype
description for the MLR1 myself, but in an earlier post someone
said it couldn't be the reason.
Tape label description should match the regexp I used
("^Hundert6[0-9][0-9]*$") - but even if it didn't it should
recognize the tape as an amanda tape, or not?
Any hints?
Bye, Jan
--
Radio HUNDERT,6 Medien GmbH Berlin
- EDV -
[EMAIL PROTECTED]
RESULTS MISSING
Hi, we're trying to start our first amanda bkup session without any success Facts: amcheck and amverify succeded: -- Tape DailySet1-01 label ok NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run Server check took 0.117 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.063 seconds, 0 problems found but amdump fails: *** THE DUMPS DID NOT FINISH PROPERLY! The next tape Amanda expects to use is: DailySet1-01. FAILURE AND STRANGE DUMP SUMMARY: localhost /etc RESULTS MISSING -- Everything seems OK. Any idea about that? Thanks in advance! -- - Elisa Dalla - Dip. Scienze dell'Ambiente e del Territorio Universita' di Milano-Bicocca P.za della Scienza 1 - Milano 20126 - Italy tel: 02-64482824
Re: barcodes question
I was using chg-zd-mtx, but seems to work now. Thanks! On Saturday, July 28, 2001, at 03:15 , Thomas Hepper wrote: > Hi, > On Fri, Jul 27, 2001 at 02:15:26PM -0500, Ignacio Tripodi wrote: >> Hi! >> I'm running amanda v2.4.2p2 on Solaris 8 server, attached to a Sun >> STORedge L9 that supports barcodes, and I'd like to know if someone can >> help me on how to create the barcodes database. There's a file in >> amanda >> configs directory called changer-barcodes that is supposed to have all >> the tape labels with each respective barcode, but I don't know where to >> get this info from or how to build this file automatically. >> Thanks! > > Which changer software do you use, and does this software support > the reading and reporting of barcode labels ? > > > Thomas > > -- > --- > | Thomas Hepper[EMAIL PROTECTED] | > | ( If the above address fail try ) | > | ( [EMAIL PROTECTED])| > --- > Ignacio Tripodi Worldwide Information Technologies, Inc. 214.678.1050 x350 http://www.wit-usa.com
Re: not an amanda tape???
[EMAIL PROTECTED] writes:
> Hello there,
>
> I figure my last mail was less than informative - usually not my
> style and I apologize.
>
> Anyway, one problem seems to persist and I'm clueless as to what
> may cause it.
> So, my amanda server is a FreeBSD 4.3 STABLE machine with a
> Tandberg MLR1.
> amanda is version 2.4.1p1, installed from the ports.
>
> Now, what I do is the following: I try and label a tape and
> amlabel appears to do it without any complaints:
>
> $ amlabel Hundert6 Hundert601
> rewinding, reading label, not an amanda tape
> rewinding, writing label Hundert601, done.
>
> ... however, each and every time I try it, amlabel keeps telling
> me the tape is not an amanda tape.
>
> Consequently amcheck reports the following:
>
> ERROR: /dev/sa0: not
> an amanda tape.
>(expecting a new tape)
> NOTE: skipping tape-writable test.
>
> Any hint what could be causing this? I wrote the tapetype
> description for the MLR1 myself, but in an earlier post someone
> said it couldn't be the reason.
>
> Tape label description should match the regexp I used
> ("^Hundert6[0-9][0-9]*$") - but even if it didn't it should
> recognize the tape as an amanda tape, or not?
>
> Any hints?
Jan,
I'd recommend to test writing and reading directly to tape first:
mt rewind
cp somebigfile /dev/nst0
mt rewind
cp /dev/nst0 /tmp/somebigfile
diff somebigfile /tmp/bigfile
This is for a Linux box, so you'll need to adjust the mt
command. /dev/nst0 is the nonrewinding device for the first SCSI
streamer. Naming will be different for BSD.
HTH,
Johannes Nieß
Re: latest 2.5.0 build fails
Ben, Thanks for you quick and detailed answer. >1. Are you sure you really want to build the 2.5 sources? Unless you are >just trying to get chg-scsi working on FreeBSD, it's probably a bad idea. >(Kind of like running FreeBSD-current! :). I do run FreeBSD-current, thought on a 2nd system ;-) > Even then, the 2.5 version >of chg-scsi has been merged back into the 242-branch and chg-scsi builds >on FreeBSD 4.3 with only minor pain. yes that's the one (chg-scsi) that I am looking after. I have been reading the archive and was following a detailed procedure found in a mail (july 6th). what are the minor pains ? Thanks for the other explanations, I'll do that (build the 242-branch) rigth after a good coffee ;-) -philippe
Re: problem with changer
>> I guess I should have a >> list of all my labels and a barcode code for each label, but I don't >> know how to generate that or if I have to do it manually. > > First, zap that file to zero length (cp /dev/null ...). Then, I > **think** > you should be able to do "amtape update" (as the Amanda user) > to build the file. > > This obviously needs much better documentation. Sorry. It's working now! Thanks a lot! I appreciate your effort. Ignacio
restore=ufsrestore?
I'm running amanda v2.4.2p2 on Solaris 8 server with a Sun STORedge attached to it. I could get the backups up and running succesfully, but I'm having a problem when doing a restore. I can run amrestore and get the dump file I want, but I didn't find out how to uncompress that file. If I do a 'file DUMPFILENAME', it shows it as a "USTAR Tar file', and if I do a 'tar tvf DUMPFILENAME' I can view all the contents correctly. All the docs I saw refer to the 'restore' utility, that looks much the same as 'ufsrestore' in solaris. I tried using ufsrestore, but I get the following error: 'Volume is not in dump format', either with the parameters recommended for 'restore' utility or trying with other options. I even tried to do a 'tar xvf DUMPFILENAME', but of course doesn't recognize it as a tar file also. Does somebody know which could be the problem? If restore is not the same as ufsrestore, does somebody know where can I get the file for Solaris 8? (I'm not using compression to do the backups) Thanks!! Ignacio Tripodi
Re: not an amanda tape???
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> (Tue, Jul 31, 2001 at 03:09:24PM +0200) > Hello there, > I figure my last mail was less than informative - usually not my > style and I apologize. > ERROR: /dev/sa0: not > an amanda tape. >(expecting a new tape) I might be wrong here, but isn't /dev/sa0 the rewind device ? Try /dev/nsa0 (or whatever is the NON-rewind device in *BSD). Currently listening to: The Pleasure Elite-Aunt Flow Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O Some say the end is near. =`\<, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
unsubscribe
unsubscribe
Re: latest 2.5.0 build fails
Philippe, > > Even then, the 2.5 version > >of chg-scsi has been merged back into the 242-branch and chg-scsi builds > >on FreeBSD 4.3 with only minor pain. > > yes that's the one (chg-scsi) that I am looking after. I have been reading > the archive and was following a detailed procedure found in a mail (july > 6th). what are the minor pains ? If you get fresh amanda-242-branch sources from today, you may need to patch configure.in to make config/config.h eventually (after autogen and configure) have all the right defines on FreeBSD. The patch is attached to this message. I'm not sure whether a "gmake all" (FreeBSD make has a bug, you'll need GNU make) in the top level will build chg-scsi automatically after the patch has been applied. If not, you should be able to run "cd changer-src; gmake chg-scsi" to build it. I hope this helps! -Ben Index: configure.in === RCS file: /cvsroot/amanda/amanda/configure.in,v retrieving revision 1.188.2.49 diff -u -r1.188.2.49 configure.in --- configure.in2001/07/30 22:38:57 1.188.2.49 +++ configure.in2001/07/31 01:44:49 @@ -1535,6 +1535,8 @@ AC_CHECK_HEADERS(\ arpa/inet.h \ camlib.h \ + cam/cam.h \ + cam/scsi/scsi_message.h \ chio.h \ db.h \ dbm.h \ Benjamin LewisThank goodness modern convenience is a Database Analyst/Programmer thing of the remote future. Purdue University Computing Center -- Pogo, by Walt Kelly [EMAIL PROTECTED]
Re: not an amanda tape???
Check tape device as well as the labelstr values. Here are mine:
tapedev "/dev/nrsa0" # the no-rewind tape device to be used
tapetype DLT1 # what kind of tape it is
labelstr "^Taeglich-[0-9][0-9]*$" # label constraint regexp: all tapes
must match
HTH
-Christoph Sold
[EMAIL PROTECTED] wrote:
>
> Hello there,
>
> I figure my last mail was less than informative - usually not my
> style and I apologize.
>
> Anyway, one problem seems to persist and I'm clueless as to what
> may cause it.
> So, my amanda server is a FreeBSD 4.3 STABLE machine with a
> Tandberg MLR1.
> amanda is version 2.4.1p1, installed from the ports.
>
> Now, what I do is the following: I try and label a tape and
> amlabel appears to do it without any complaints:
>
> $ amlabel Hundert6 Hundert601
> rewinding, reading label, not an amanda tape
> rewinding, writing label Hundert601, done.
>
> ... however, each and every time I try it, amlabel keeps telling
> me the tape is not an amanda tape.
>
> Consequently amcheck reports the following:
>
> ERROR: /dev/sa0: not
> an amanda tape.
>(expecting a new tape)
> NOTE: skipping tape-writable test.
>
> Any hint what could be causing this? I wrote the tapetype
> description for the MLR1 myself, but in an earlier post someone
> said it couldn't be the reason.
>
> Tape label description should match the regexp I used
> ("^Hundert6[0-9][0-9]*$") - but even if it didn't it should
> recognize the tape as an amanda tape, or not?
>
> Any hints?
>
> Bye, Jan
>
> --
> Radio HUNDERT,6 Medien GmbH Berlin
> - EDV -
> [EMAIL PROTECTED]
--
Freundliche Grüße aus Waiblingen
Christoph Sold
--
Systemadministrator, i-clue GmbH, Endersbacher Str. 57, 71334 Waiblingen
Fon: (0 71 51) 9 59 01-12, Fax: (0 71 51) 9 59 01-55, Mail: [EMAIL PROTECTED]
Re: not an amanda tape???
[EMAIL PROTECTED] wrote: > > Hello there, > > I figure my last mail was less than informative - usually not my > style and I apologize. > > [snip] > > $ amlabel Hundert6 Hundert601 > rewinding, reading label, not an amanda tape > rewinding, writing label Hundert601, done. > > ... however, each and every time I try it, amlabel keeps telling > me the tape is not an amanda tape. > > Consequently amcheck reports the following: > > ERROR: /dev/sa0: not That's the rewinbding device. Use /dev/nrsa0 instead. > an amanda tape. >(expecting a new tape) > NOTE: skipping tape-writable test. HTH -Christoph Sold
Re: not an amanda tape???
Hi, > I might be wrong here, > but isn't /dev/sa0 the rewind device ? You are of course absolutely right. I guess I need a new pair of glasses. The fact that this was the problem all the time makes me want to smash my head against my monitor :-% Thanks, however. > Try /dev/nsa0 (or whatever is the NON-rewind device in *BSD). Works just fine... Cheers, Jan -- Radio HUNDERT,6 Medien GmbH Berlin - EDV - [EMAIL PROTECTED]
Re: Tape drive recommendation
>the thing is that it's a taperobot/tapechanger, and I remember reading >discussions that getting that to work is not always a trivial issue. That's going to be true no matter what. Any time software comes in contact with reality (hardware), bad things happen :-). >What kind of tapedrives do you use ? DLT7000 and I use hardware compression. >> ... I have a minor patch to let >> more than one amandad run at a time so you can have multiple tape >> servers working at the same time. > >Do you need a patch for that ? Yes. If two Amanda servers try to contact a single client at the same time, only one will make it in and the other will fail. My patch allows you to have multiple amandad inetd/xinetd entries on a client and tell the server which one to talk to (basically a run time change to the hard coded default 10080 port number). >Im running 3 amandads on the same machine every night >(all 3 to different tapedrives ), ... I think you mean you're running three amdump's (not amandad's) on that machine. >and each client is running multiple >clients (or at least can run ) at the same time. But each client is only in one disklist, right? The change I'm talking about allows a client to be in multiple disklists at the same time. > Gerhard John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Failure & strange dump
>I'm using amanda with the same configuration for 10 days without having >big issue. >but after the other administrator touchs the disklist ... >all my dumps fails with the same error message I assume you're never going to let the other administrator near Amanda again, right? :-) :-) >/-- dejanire /export/diskC1 lev 2 FAILED [errfile open >"/tmp/amanda/dejanire._export_diskC1.2.errout": No such file or >directory] That message comes from the "dumper" program which runs on the server, not the client. My guess is that /tmp/amanda has been removed (although Amanda should have recreated it), or that it has incorrect ownership or modes. Probably the easiest thing to do is just remove it and let Amanda recreate it. A couple of possibilities here are that someone ran an Amanda program (e.g. amadmin) as root instead of the Amanda user. Another is that you have some kind of /tmp cleanup process that removed the area while Amanda was running. >Briner John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: limiting amanda's network usage
>Does "netusage" actually do anything with regard to the amount of
>bandwidth amanda uses? ...
No. From the amanda(8) man page ("INTERFACE SECTION"):
Note that these sections define network interface charac-
teristics, not the actual interface that will be used. Nor
do they impose limits on the bandwidth that will actually be
taken up by Amanda. Amanda computes the estimated bandwidth
each file system backup will take based on the estimated
size and time, then compares that plus any other running
backups with the limit as another of the criteria when
deciding whether to start the backup. Once a backup starts,
Amanda will use as much of the network as it can leaving
throttling up to the operating system and network hardware.
>Dan Debertin
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amrecover error
Hi, I am using amanda2.4.2p1 version on a linux machine.. when I tried to recover one users home directory it's giving one error.. Can someone help out ...to figure out the pblm..? The index server is also a Linux machine.. I have checked all the config parameters in /etc/inetd.conf and /etc/services .. they seems to be ok for me.. do I need to start some other services in the target machine..? please help me out. some sample outputs : target machine [root@alpine src]# pwd /home/jjeffers/sdk/performance_tests/src [root@alpine src]# amrecover -C Daily -s blue -t blue AMRECOVER Version 2.4.1p1. Contacting server on blue ... amrecover: Error connecting to server: Invalid argument [root@alpine src]# uname -a Linux alpine 2.2.14-VA.2.1smp #1 SMP Mon Jul 31 21:53:20 PDT 2000 i686 unknown [root@alpine src]# index server Linux blue.netoctave.com 2.2.17-21mdk #1 Thu Oct 5 13:16:08 CEST 2000 i686 unknown the device file for tape = /dev/nst0 Thanks Rajesh
limiting amanda's network usage
Does "netusage" actually do anything with regard to the amount of bandwidth amanda uses? I have mine set way down at 50 Kbps, and I'm seeing it pull up to 6 Mbps at a time, regardless of what I set it to. Does amanda actually shape its bandwidth usage, or is 'netusage' just for estimates? Dan Debertin -- ++ Desist from enumerating your fowl ++ prior to their emergence ++ from the oblong embryo container ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ [EMAIL PROTECTED] ++ (612)321-9290 x108 ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387
Failure & strange dump
Hi, I'm using amanda with the same configuration for 10 days without having big issue. but after the other administrator touchs the disklist by suppressing one record and do change other stuff on the host that that have the tape server... all my dumps fails with the same error message /-- dejanire /export/diskC1 lev 2 FAILED [errfile open "/tmp/amanda/dejanire._export_diskC1.2.errout": No such file or directory] \ After reading this I thought that the problem was on the backup client host side. But it seems not so "normal" that all of them have the same problem.. Could someone help me thks in advance Briner
Re: Tape drive recommendation
* John R. Jackson <[EMAIL PROTECTED]> (Mon, Jul 30, 2001 at 05:04:47PM -0500) > >Does anyone know if that puppy is supported by amanda ? > If it's SCSI, Amanda can do it (or it should be able to so we'll make it). It is, the thing is that it's a taperobot/tapechanger, and I remember reading discussions that getting that to work is not always a trivial issue. And Ill likely only have a week to set it all up (and do a whole lot more) so I'd prefer not to have to spent too much time tinkering with the scsi changer configs ;) >>Does anyone have any recommendations for backing up this amound of data ? > Just a couple of general theories: > * Make sure no one "disk" (disklist entry) gets out of line. > Ignoring the tape overflow issue, it would still be a bad thing > to have 1.9 TBytes of your 2.0 TBytes in one file system. The day > Amanda decides to do that full dump during the dumpcycle is going > to be bad every time it rolls around (we have one config like that > here and it's a nuisance). Hence gnutar and calcsize ;) seriously, it's gonna be a bunch of linux boxes each with 100 - 150G of diskspace (2 IDE drives of 50 - 75G) > * Extend your dumpcycle so Amanda can spread the full dumps out. > Yes, that means more tapes. > * Run in parallel (yes, more drives and more tapes). We backup up > well over 2 TBytes and this (plus a 28 day dumpcycle) is how we > survive. What kind of tapedrives do you use ? > If you don't have enough clients (i.e. they are silly enough to put > the whole 2 TBytes on a single server), I have a minor patch to let > more than one amandad run at a time so you can have multiple tape > servers working at the same time. Do you need a patch for that ? Im running 3 amandads on the same machine every night (all 3 to different tapedrives ), and each client is running multiple clients (or at least can run ) at the same time. > * Do the math :-). You're familiar with Amanda and know how it behaves. > Write up some scenarios for splitting up the data and do rough > estimates of the timing. Then play with the variables (dumpcycle, > holding disk space, number of configs, drive speed, etc). Yes, I'll have to do that anyway Ill need to make a cost/benefit analysis of the various scenarios . Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\<, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
latest 2.5.0 build fails
Hi, On a system running FreeBSD-4.3 Release, I have retrieved the latest amanda src from cvs. Ran autoconf on configure.in then configure and it fails. Unfortunately I known nothing about autoconf, so any enlightment of my ignorance is welcomed ;-) --->- [perfzilla - root] /tmp/amanda # cd amanda [perfzilla - root] /tmp/amanda/amanda # autoconf configure.in:1718: warning: AC_TRY_RUN called without default to allow cross compiling [perfzilla - root] /tmp/amanda/amanda # ./configure creating cache ./config.cache checking host system type... i386-unknown-freebsd4.3 checking target system type... i386-unknown-freebsd4.3 checking build system type... i386-unknown-freebsd4.3 checking cached system tuple... ok ./configure: 770: Syntax error: word unexpected (expecting ")") [perfzilla - root] /tmp/amanda/amanda # > The line that seems to pose a trouble (770) are : --- AM_INIT_AUTOMAKE(amanda, 2.5.0) AM_CONFIG_HEADER(config/config.h) --- -philippe
