Re: Any way to parallelize or speed up the planner?
On Tuesday 15 July 2003 12:41, David Trusty wrote: >Hi, > >I have a number of disks which are being backed-up from a single > host. The disks have many thousands of files in many directories. > >When I run the backup, the planner seems to sequentially examine > each of the disks for updates. >This planning stage takes many hours. Is there any way to > parallelize it, or otherwise speed it up? > >Thanks in advance! This is what the optional spndle number is supposed to do in your disklist entries. Give each physical disk its own spindle number. Make sure that MAXDUMPERS or whatever its called (in amanda.conf) is sufficient that one can be running against each disk. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: post operative (almost) sanity checks
On Tue, Jul 15, 2003 at 03:22:13PM -0500, Bruntel, Mitchell L, SOLCM wrote: > NOW my only problem IS: tpchanger should call the C program > (chg-scsi) in my case... where does the CONFIG (chg-scsi.conf) get > called from, or it doesnt need to be? I'm not a chg-scsi user, but I believe you just define changerfile in amanda.conf. chg-scsi does a getconf_str() to find that path, then opens the config file to configure itself. docs/TAPE.CHANGERS says the way to use chg-scsi is something like: tpchanger "chg-scsi" tapedev "1" changerfile "/path/to/your/changer_config_file" Once you specify chg-scsi, tapedev switches meaning to "a pointer to a configuration number inside changerfile", NOT the actual tape device (which is, in turn, specified inside changerfile). But I don't use chg-scsi myself, I'm just reading docs/TAPE.CHANGERS to you. :-) -Jay-
Any hints on a drive I have?
Hello! I'm trying to set up an old drive here, and I might as well ask you people if there's someone out there who's tried (and better yet - MANAGED) to set up this type of drive. To business, it's a HP Colorado 20GBe drive, that is Travan TR-5, connected to the parallel port. I think the setup would be something like loading modules; parport, paride, epat and pt and then the drive will show up on /dev/pt0 but I'm not really sure about that. Neither do I know diddely-squat about putting it to work in Amanda, I can't find any clear documentation or how-to on it. So, any ideas and hints are really welcome! Later, Anders Norrbring Norrbring Consulting
post operative (almost) sanity checks
thanks Jay, makes great sense.
so the tpchanger envirornment is attemping to call the C program in the libexec
directory
NOW my only problem IS: tpchanger should call the C program (chg-scsi) in my case...
where does the CONFIG (chg-scsi.conf) get called from, or it doesnt need to be?
so this error(s)
Amanda Tape Server Host Check
-
(1)amcheck-server: could not get changer info: could not read result from
"/usr/local/etc/amanda/DailyBackup/chg-scsi.conf"
or now:
(2)amcheck-server: could not get changer info: check your config and use a config file
for chg-scsi
..amanda.conf snippet:
..snip..
notes: IF THIS line (A) is commented/# out, I get errror 1
(otherwise I get error B
(A) tpchanger "chg-scsi"
# the tape-changer glue script
(B) tpchanger "/usr/local/etc/amanda/DailyBackup/chg-scsi.conf"
tapedev "/dev/rmt/0n" # the no-rewind tape device to be used
changerfile "/usr/local/etc/amanda/DailyBackup/chg-scsi.conf"
changerdev "/dev/scsi/changer/c1t0d0"
-Original Message-
From: Jay Lessert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 3:52 PM
To: Bruntel, Mitchell L, SOLCM
Cc: [EMAIL PROTECTED]
Subject: Re: Pre-emptive sanity check Question
On Tue, Jul 15, 2003 at 01:58:20PM -0500, Bruntel, Mitchell L, SOLCM wrote:
> OK. Jay makes sense here:
> 1) Jay says: I have choices: chg-scsi or chg-zd-mtx.
> but I have a third config file in the distribution called chg-scsi-solaris.conf
The files: example/chg-scsi-{hpux,linux,solaris}.conf are just example
chg-scsi config files with OS-specific "typical" device names inserted;
they do not represent different tpchanger executables. You'll not find
libexec/chg-scsi-solaris, right?
> The X80 has 80 slots for tapes. (elements) Tape Drive 1 is element
> 451, 2 is 452, 3 is 453,
I'm sure there is an excellent and highly amusing reason for that. :-)
and the cleaning cartridge lives in slot 0
> and element 401-405 are the only way to put tapes in/out of unit!
You're apparently intended to initially populate the library through
the little five-tape import/export hole, and then seldom/never touch
the tapes again. Unless you were planning on rotating tapes off-site,
that's actually a perfectly good way to go, I guess.
Amanda won't do anything with the import/export slots, you'll deal with
that outside amanda somewhere.
With mtx, you would fill the import/export slots, then have a script
do something like:
mtx transfer 401 1
mtx transfer 402 2
mtx transfer 403 3
mtx transfer 404 4
mtx transfer 405 5
> so it should be 'startuse 1', 'enduse 80'
If you're planning on using that many tapes, yes. Only specify as many
slots as you're actually intending to use in this amanda config.
> Now can someone explain the following:
> a) what is the relationship of mtx to chg-scsi
None.
chg-scsi: is a C program that controls a SCSI tape library and directly
implements the amanda changer interface described in
docs/TAPE.CHANGERS. Part of the amanda source distribution.
mtx: A C program that controls a SCSI tape library and does NOT
directly implement the amanda changer interface. It is very useful
to use by hand, however ('mtx load 3 452' would load the tape in
slot 3 to tape drive 452), and a wrapper script can convert it to
amanda. Source from http://mtx.badtux.net/.
There is another, older mtx, which I have never seen in the wild.
chg-zd-mtx: A sh script wrapper around mtx which converts it to the
amanda changer interface.
> b) what is the relationship of chg-scsi.conf and the files in the
>/usr/local/libexec directory (/usr/local/libexec/chg-scsi)
libexec/chg-scsi is a C program that expects to find a configuration
file somewhere. chg-scsi.conf might be that file.
--
Jay Lessert [EMAIL PROTECTED]
Accelerant Networks Inc. (voice)1.503.439.3461
Beaverton OR, USA(fax)1.503.466.9472
Amanda + Cygwin
I was trying to install Cygwin on my Windows machine but when I run amcheck on my sevrer. I got such error: Server Response: Amanda Backup Client Hosts Check WARNING: hxtiwkstn01: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.032 seconds, 1 problem found But I am pretty sure that inetd is running on my client because my cygwin client popped up these messages. ADD : amanda proto=udp, wait=1, user=SYS amandad registered /usr/local/libexec/amandad on someone wants amanda + Closing from 19 812 execl /usr/local/libexec/amandad 812 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1840 execl /usr/local/libexec/amandad 1840 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 824 execl /usr/local/libexec/amandad 824 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 340 execl /usr/local/libexec/amandad 340 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 844 execl /usr/local/libexec/amandad 844 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 2288 execl /usr/local/libexec/amandad 2288 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1852 execl /usr/local/libexec/amandad 1852 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 820 execl /usr/local/libexec/amandad 820 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1920 execl /usr/local/libexec/amandad 1920 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 812 execl /usr/local/libexec/amandad 812 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1840 execl /usr/local/libexec/amandad 1840 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 824 execl /usr/local/libexec/amandad 824 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 340 execl /usr/local/libexec/amandad 340 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 844 execl /usr/local/libexec/amandad 844 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 2288 execl /usr/local/libexec/amandad 2288 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1852 execl /usr/local/libexec/amandad 1852 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 820 execl /usr/local/libexec/amandad 820 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1920 execl /usr/local/libexec/amandad 1920 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 812 execl /usr/local/libexec/amandad 812 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1840 execl /usr/local/libexec/amandad 1840 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 824 execl /usr/local/libexec/amandad 824 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 340 execl /usr/local/libexec/amandad 340 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 844 execl /usr/local/libexec/amandad 844 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 2288 execl /usr/local/libexec/amandad 2288 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1852 execl /usr/local/libexec/amandad 1852 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 820 execl /usr/local/libexec/amandad 820 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1920 execl /usr/local/libexec/amandad 1920 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 812 execl /usr/local/libexec/amandad 812 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1840 execl /usr/local/libexec/amandad 1840 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 824 execl /usr/local/libexec/amandad 824 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 340 execl /usr/local/libexec/amandad 340 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 844 execl /usr/local/libexec/amandad 844 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 2288 execl /usr/local/libexec/amandad 2288 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1852 execl /usr/local/libexec/amandad 1852 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 820 execl /usr/local/libexec/amandad 820 reaped, status 0x100 restored amanda, fd 19 someone wants amanda + Closing from 19 1920 execl /usr/local/libexec/amandad 1920 reaped, status 0x100 resto
Re: amanda + gzip errors on debian?
Just a note that I have experienced a similar problem, but with Redhat and Mandrake rather than Debian Linux. The dump format is GNU tar with gzip compressed on the client side, written to a large holding disk then flushed to tape. The archives on holding disk verify OK, but the problem is retrieving them from tape. So I suspect it is a hardware, SCSI cabling or kernel problem when writing to tape. It's mostly dumps > 8-10GBs that have problems, and then only about 1 out of 3 dumps. However, the dumps done without using gzip have had no problems during restores, and I've done a lot more of those than restores of the gzip'd dumps, which I only used on clients with fast CPUs which don't run batch jobs at night. I've turned on hardware compression and turned off client side compression as an acceptable workaround. Still trying to find a way to resurrect corrupt gzip tar archives. Also Sprach Eric Siegerman: > On Tue, Jul 15, 2003 at 12:10:27PM -0400, Kurt Yoder wrote: > > However, I > > was able to duplicate the problem simply by gzipping a big file to > > my ATA/IDE holding disk. So I'm certain it's not a scsi problem. > > Is it repeatable? I.e. if you gzip the *same* file five times, > do you get the same error five times, at the same location? Or > do you get five different errors? Or maybe a mix of errors and > successes? > > The former would point to a bug in gzip; the latter to hardware > problems of some sort (or kernel, but I'd bet on the hardware). > > Try that test on your freshly installed Debian box, that you say > works fine. Then install (but don't use) Amanda and try it > again. > > Divide and conquer :-) > > -- > > | | /\ > |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] > | | / > When I came back around from the dark side, there in front of me would > be the landing area where the crew was, and the Earth, all in the view > of my window. I couldn't help but think that there in front of me was > all of humanity, except me. > - Michael Collins, Apollo 11 Command Module Pilot > C. Chan <[EMAIL PROTECTED] > GPG Public Key registered at pgp.mit.edu
Re: Pre-emptive sanity check Question
On Tue, Jul 15, 2003 at 01:58:20PM -0500, Bruntel, Mitchell L, SOLCM wrote:
> OK. Jay makes sense here:
> 1) Jay says: I have choices: chg-scsi or chg-zd-mtx.
> but I have a third config file in the distribution called chg-scsi-solaris.conf
The files: example/chg-scsi-{hpux,linux,solaris}.conf are just example
chg-scsi config files with OS-specific "typical" device names inserted;
they do not represent different tpchanger executables. You'll not find
libexec/chg-scsi-solaris, right?
> The X80 has 80 slots for tapes. (elements) Tape Drive 1 is element
> 451, 2 is 452, 3 is 453,
I'm sure there is an excellent and highly amusing reason for that. :-)
and the cleaning cartridge lives in slot 0
> and element 401-405 are the only way to put tapes in/out of unit!
You're apparently intended to initially populate the library through
the little five-tape import/export hole, and then seldom/never touch
the tapes again. Unless you were planning on rotating tapes off-site,
that's actually a perfectly good way to go, I guess.
Amanda won't do anything with the import/export slots, you'll deal with
that outside amanda somewhere.
With mtx, you would fill the import/export slots, then have a script
do something like:
mtx transfer 401 1
mtx transfer 402 2
mtx transfer 403 3
mtx transfer 404 4
mtx transfer 405 5
> so it should be 'startuse 1', 'enduse 80'
If you're planning on using that many tapes, yes. Only specify as many
slots as you're actually intending to use in this amanda config.
> Now can someone explain the following:
> a) what is the relationship of mtx to chg-scsi
None.
chg-scsi: is a C program that controls a SCSI tape library and directly
implements the amanda changer interface described in
docs/TAPE.CHANGERS. Part of the amanda source distribution.
mtx: A C program that controls a SCSI tape library and does NOT
directly implement the amanda changer interface. It is very useful
to use by hand, however ('mtx load 3 452' would load the tape in
slot 3 to tape drive 452), and a wrapper script can convert it to
amanda. Source from http://mtx.badtux.net/.
There is another, older mtx, which I have never seen in the wild.
chg-zd-mtx: A sh script wrapper around mtx which converts it to the
amanda changer interface.
> b) what is the relationship of chg-scsi.conf and the files in the
>/usr/local/libexec directory (/usr/local/libexec/chg-scsi)
libexec/chg-scsi is a C program that expects to find a configuration
file somewhere. chg-scsi.conf might be that file.
--
Jay Lessert [EMAIL PROTECTED]
Accelerant Networks Inc. (voice)1.503.439.3461
Beaverton OR, USA(fax)1.503.466.9472
Re: sdlt versus DLT library
On Tue, Jul 15, 2003 at 02:28:42PM -0400, Mitch Collinsworth wrote: > > On Tue, 15 Jul 2003, Kurt Yoder wrote: > > > AFAIK it will hit end of tape and ask for another tape. However, > > there is no way to flush a single dump image to multiple tapes. So > > if you have a 20 GB dump image (even if it's been split up into > > pieces due to the chunksize parameter) and a 10 GB tape, there is no > > way to put the dump image on that tape. > > > Does this strike anyone besides me as dumb? Yes I've known these > details separately for years, but when they are put together in > the same paragraph it jumps out and says "Hey, the dump has already > been split into managable-sized pieces. All we need is to modify > taper to put them on multiple tapes and voila, we can span tapes!" > > Of course then we'd need to do some fiddling with amrestore to be > able to retrieve all the chunks during a restore... On another mailing list I think the acronynm is PCABM * * Patches Cheerfully Accepted By Maintainers -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Pre-emptive sanity check Question
OK. Jay makes sense here: 1) Jay says: I have choices: chg-scsi or chg-zd-mtx. but I have a third config file in the distribution called chg-scsi-solaris.conf The X80 has 80 slots for tapes. (elements) Tape Drive 1 is element 451, 2 is 452, 3 is 453, and the cleaning cartridge lives in slot 0 and element 401-405 are the only way to put tapes in/out of unit! So much for paying attention. In modifying the chg-scsi file, I thought the commands were well defined. so for example startuse: 451 #The slots associated with the drive 1 would also be enduse451 since the drive is ONLY 1 slot. Howerver, looking (thanks for humility check, Jay!) at The "FM". (in) docs/TAPE.Changers correctly shows that startuse/enduse can be used to set # of slots for machine. so it should be startuse1,enduse80 Now can someone explain the following: a) what is the relationship of mtx to chg-scsi b) what is the relationship of chg-scsi.conf and the files in the /usr/local/libexec directory (/usr/local/libexec/chg-scsi) c) How do I get my unit to start READING the barcodes? thanks again
Re: Solved: tapelist is empty
Jon LaBadie wrote: > On Mon, Jul 14, 2003 at 10:37:18PM +0300, Antonios Christofides wrote: > > I looked at the code, and it's not a trivial fix. > > I'm not so sure it is difficult. > > But none of the 3 printf statements are checked for failures. In my opinion, the error does not occur in the printf statements but when the file is closed, because that is when the output buffers are flushed. I've written more on this in amanda-hackers.
Re: sdlt versus DLT library
On Tue, 15 Jul 2003, Kurt Yoder wrote: > AFAIK it will hit end of tape and ask for another tape. However, > there is no way to flush a single dump image to multiple tapes. So > if you have a 20 GB dump image (even if it's been split up into > pieces due to the chunksize parameter) and a 10 GB tape, there is no > way to put the dump image on that tape. Does this strike anyone besides me as dumb? Yes I've known these details separately for years, but when they are put together in the same paragraph it jumps out and says "Hey, the dump has already been split into managable-sized pieces. All we need is to modify taper to put them on multiple tapes and voila, we can span tapes!" Of course then we'd need to do some fiddling with amrestore to be able to retrieve all the chunks during a restore... -Mitch
Re: Solaris9 : netinet/ip.h: present but cannot be compiled
On Tue, Jul 15, 2003 at 09:34:11AM -0400, Bryan Hodgson wrote: > Let it be noted that in order to get the client to compile for > the use of the one Solaris 2.4 machine still running around here, > I had to "--disable-libtool" in the configuration options. > > A side-effect was (evidently) that the new style header checking > was disabled, Or maybe the disagreement simply doesn't occur on that system, giving the header checking nothing to complain about. Did the configure output contain "checking usability" / "checking presence" pairs, as it did on the other boxes? -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: Solaris9 : netinet/ip.h: present but cannot be compiled
> For more explanation, see this fragment of a thread from the > Autoconf mailing-list archives. The first of these links points > to the question, the second to the reply; the rest of the thread > can be safely ignored :-) > http://mail.gnu.org/archive/html/autoconf/2003-03/msg00154.html > http://mail.gnu.org/archive/html/autoconf/2003-03/msg00156.html > > The second of these messages also suggests an approach that the > Amanda folks could use to suppress this scary-sounding warning, > which is why I've CCed this to the amanda-hackers list... Thanks for passing this along. I've applied something resembling the fix at those URLs. (while I was there I dealt with a manifestation of the same problem for NetBSD for sys/mount.h). -Todd
Re: amanda + gzip errors on debian?
On Tue, Jul 15, 2003 at 12:10:27PM -0400, Kurt Yoder wrote: > However, I > was able to duplicate the problem simply by gzipping a big file to > my ATA/IDE holding disk. So I'm certain it's not a scsi problem. Is it repeatable? I.e. if you gzip the *same* file five times, do you get the same error five times, at the same location? Or do you get five different errors? Or maybe a mix of errors and successes? The former would point to a bug in gzip; the latter to hardware problems of some sort (or kernel, but I'd bet on the hardware). Try that test on your freshly installed Debian box, that you say works fine. Then install (but don't use) Amanda and try it again. Divide and conquer :-) -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: Pre-emptive sanity check Question
On Tue, Jul 15, 2003 at 07:20:12AM -0500, Bruntel, Mitchell L, SOLCM wrote: > 1) The Exabyte folks said the X80 likes to work in ASPI mode, and >that there are no drivers needed for this mode supplied by them. You can now safely ignore the "Exabyte folks", since they've proven themselves clueless. :-) ASPI is an old SCSI API, originated by Adaptec 10 years ago or so, I think, and only exists in the DOS and Windows environment. There is no such thing as an "ASPI mode" for your library, its a non-sequitur. It would be like saying a text file is in "emacs mode" or "vim mode" because you used emacs or vim to read/write it. > This leads me to think the best changer I could use is chg-scsi, and > I have the following questions about that file. I would guess that > this is the file that tries to drive the elements in regular aspi mode > too.. Forget ASPI. It has absolutely nothing to do with you, your library, or amanda. You should be able to make either chg-scsi or chg-zd-mtx work, whichever you feel like. Nice to have choices. > Here's a small snippet from my new chg-scsi file. > # the device that is used for the tapedrive 1 > startuse451 > enduse 451 > AND HERE's the question. This # (451) is what Exabyte calls the > ELEMENT index assignment for my 80 cartridge library, and came out of > the users manual I don't know an X80 from a hole in the ground, but there is no way that 'startuse 451'/'enduse 451' can be correct. You're telling amanda the config has one and only one slot, which (even if 451 is a legal slot, which I doubt) is not what you want. What does 'mtx status' say (I say that only because I don't know what the chg-scsi equivalent is)? > number_configs 3 #(because I have 3 drives. BOY am I smart!!!) > # # configs being set to how many tape drives! As long as you're aware that a single amanda config only knows how to use a single tape drive (except for RAIT). -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Any way to parallelize or speed up the planner?
Bruntel, Mitchell L, SOLCM wrote: Let me rephrase the question slightly. When running your normal "amdump" program, is it just the parallelism command that controls this, or do we need to kick off new (additional) crons to do this? No, there can be only one amandad be active on one port (10080). If you compile another version of amanda, to use a different service port (e.g. 10090), only then you can have two running at the same time. (But this is only used when people have two amanda servers, and want to spread the load of the backup over the two servers.) The parallelism is controlled by maxdumps and splindle numbers. (and constraints like holdingdisk space, bandwith, etc.) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Any way to parallelize or speed up the planner?
David Trusty wrote: I have a number of disks which are being backed-up from a single host. The disks have many thousands of files in many directories. When I run the backup, the planner seems to sequentially examine each of the disks for updates. This planning stage takes many hours. Is there any way to parallelize it, or otherwise speed it up? Are you looking for the maxdumps parameter? In combination with the spindle number of a disklist entry, this can start more than one backup (or estimate) on a host. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: which tape is which ???
On Tue, Jul 15, 2003 at 11:31:21AM -0400, Kurt Yoder wrote: > > Michael D. Schleif said: > > That's my problem: if I knew which of these tapes is the ``most > > recently-written one'' [...] > > Ah. Put one in and do "dd if= of=test_header bs=32k". For a list of the tape's contents, use amrestore. Ask it to restore some nonexistent host. It'll fail of course, but as a side effect, it will print a list of all the DLEs it's skipping over in the process. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: chg-multi says no tape online
Kurt Yoder wrote: Yes. Unfortunately I can't find the documentation that said how to do this any more. However, one does it by setting run-tapes to some number and tpchanger to chg-multi. Then in the changerfile one specifies a single slot pointing to the tape drive device, firstslot 1 and lastslot 1. That's indeed about the setup I have. I have two drives configured in chg-multi and I have runtapes set to 3. Two tapes are filled by amanda, and the rest is left in the holdingdisk, which I flush manually on monday morning. My relevant lines in amanda.conf: runtapes 3 # number of tapes to be used in a single run of amdump tpchanger "chg-multi" # the tape-changer glue script #tapedev "/dev/rmt/2ln" # the no-rewind tape device to be used #rawtapedev "/dev/null" # the raw device to be used (ftape only) changerfile "/var/opt/amanda/etc/archive/chg-multi.conf" #changerdev "/dev/null" (Notice that some lines, like changedev are indeed commented out!) And my chg-multi.conf: multieject 0 firstslot 1 lastslot 2 gravity 0 needeject 0 ejectdelay 0 statefile /var/opt/amanda/archive/changer-status slot 1 /dev/nst0 slot 2 /dev/nst1 -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
RE: Any way to parallelize or speed up the planner?
Let me rephrase the question slightly. When running your normal "amdump" program, is it just the parallelism command that controls this, or do we need to kick off new (additional) crons to do this? Mitch: PS: I'm still stumped on the chg-scsi-solaris.conf question, as to why the "changer" program keeps getting no access to directory. -Original Message- From: David Trusty [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 12:41 PM To: [EMAIL PROTECTED] Subject: Any way to parallelize or speed up the planner? Hi, I have a number of disks which are being backed-up from a single host. The disks have many thousands of files in many directories. When I run the backup, the planner seems to sequentially examine each of the disks for updates. This planning stage takes many hours. Is there any way to parallelize it, or otherwise speed it up? Thanks in advance! David _
Any way to parallelize or speed up the planner?
Hi, I have a number of disks which are being backed-up from a single host. The disks have many thousands of files in many directories. When I run the backup, the planner seems to sequentially examine each of the disks for updates. This planning stage takes many hours. Is there any way to parallelize it, or otherwise speed it up? Thanks in advance! David _
Re: sdlt versus DLT library
Jeremy L. Mordkoff wrote: I’m using a DLT IV tape drive now (one tape a night), but it’s not big enough. I have 70GB partitions and when they get full, I’ll have problems. If I switch to a DLT tape library (8x40GB), will that solve my problem? Will Amanda split backup across two tapes? Or should I just get a SDLT tape drive (160GB)? This used to be a weekly question, but now it getting a daily question. :-) See the last entry in the examples for a disklist (in your sourcedir examples/disklist). (Split up the big fs in to smaller pieces, using gnutar and include/exclude lists.) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: sdlt versus DLT library
Steven J. Backus said: > "Kurt Yoder" <[EMAIL PROTECTED]> wrote: > >> No. See FAQ: >> >> http://amanda.sourceforge.net/fom-serve/cache/32.html > > How about an amflush? Say you have more than one tape worth in the holding disk? AFAIK it will hit end of tape and ask for another tape. However, there is no way to flush a single dump image to multiple tapes. So if you have a 20 GB dump image (even if it's been split up into pieces due to the chunksize parameter) and a 10 GB tape, there is no way to put the dump image on that tape. > So what does the runtapes parameter do? See "man amanda", look for "runtapes". Tells you the maximum number of tapes you can write to if you have a tape changer configured. -- Kurt Yoder Sport & Health network administrator -- Kurt Yoder Sport & Health network administrator
Re: sdlt versus DLT library
Steven J. Backus said: > "Kurt Yoder" <[EMAIL PROTECTED]> wrote: > >> No. See FAQ: >> >> http://amanda.sourceforge.net/fom-serve/cache/32.html > > How about an amflush? Say you have more than one tape worth in the > holding disk? AFAIK it will hit end of tape and ask for another tape. However, there is no way to flush a single dump image to multiple tapes. So if you have a 20 GB dump image (even if it's been split up into pieces due to the chunksize parameter) and a 10 GB tape, there is no way to put the dump image on that tape. > So what does the runtapes parameter do? See "man amanda", look for "runtapes". Tells you the maximum number of tapes you can write to if you have a tape changer configured. -- Kurt Yoder Sport & Health network administrator
Re: sdlt versus DLT library
On Tue, Jul 15, 2003 at 10:30:11AM -0600, Steven J. Backus wrote: > "Kurt Yoder" <[EMAIL PROTECTED]> wrote: > > > No. See FAQ: > > > > http://amanda.sourceforge.net/fom-serve/cache/32.html > > How about an amflush? Say you have more than one tape worth in the > holding disk? If that data in the holding disk is from a single DLE, it still will not meet the requirement that no DLE can be bigger than one tape. So the flush will fail. > So what does the runtapes parameter do? Allows you to split a single dump of many DLEs on multiple tapes. But still, no single DLE can be bigger than a tape. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: sdlt versus DLT library
"Kurt Yoder" <[EMAIL PROTECTED]> wrote: > No. See FAQ: > > http://amanda.sourceforge.net/fom-serve/cache/32.html How about an amflush? Say you have more than one tape worth in the holding disk? So what does the runtapes parameter do? Steve
Re: chg-multi says no tape online
(cc'ing list) Paul Bijnens said: > Kurt Yoder wrote: > >> Hello list >> I recently switched amanda servers, and copied a manual chg-multi > > What is a "manual chg-multi"? I use a "chg-multi" in my config, and I have used a "chg-manual" in the past. Can you use chg-multi for manual purposes too? Yes. Unfortunately I can't find the documentation that said how to do this any more. However, one does it by setting run-tapes to some number and tpchanger to chg-multi. Then in the changerfile one specifies a single slot pointing to the tape drive device, firstslot 1 and lastslot 1. So amanda writes everything it can to tape 1. Then if it has more it tries to write to tape 2..n but is forced to leave it on the holding disk instead. Then you can manually put in the next tape and flush. It worked well on this machine, but I reinstalled the machine with a different hard disk and new configuration (see separate thread on this list about gzip errors for the reason). Now it's not working any more. > How does your chg-multi.conf look like? multieject 0 gravity 0 needeject 0 ejectdelay 0 statefile /var/backups/changer-status firstslot 1 lastslot 1 slot 1 /dev/nst0 Looks identical to the previous working config. -- Kurt Yoder Sport & Health network administrator
Re: which tape is which ???
Also sprach Kurt Yoder (Tue 15 Jul 02003 at 11:31:21AM -0400): > > Michael D. Schleif said: > > > > > That's my problem: if I knew which of these tapes is the ``most > > recently-written one'', then I would know which is in the current > > cycle > > ;< > > > > So, how do I determine that? > > Ah. Put one in and do "dd if= of=test_header bs=32k". > This will grab the amanda tape header and put it in the file > test_header. In this file you will then see the date of the dump on > this tape. Perhaps, that should be: dd if=/dev/nst0 of=~/test_hdr bs=32k count=1 Thank you. -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: sdlt versus DLT library
Jeremy L. Mordkoff said: > I'm using a DLT IV tape drive now (one tape a night), but it's not > big > enough. I have 70GB partitions and when they get full, I'll have > problems. If I switch to a DLT tape library (8x40GB), will that > solve my > problem? Will Amanda split backup across two tapes? Or should I just > get > a SDLT tape drive (160GB)? No. See FAQ: http://amanda.sourceforge.net/fom-serve/cache/32.html -- Kurt Yoder Sport & Health network administrator
Re: Determining optimum block size
On Tue, Jul 15, 2003 at 04:04:33PM +0200, Paul Bijnens wrote: > > Try a blocksize of 512 bytes (no K), and you'll notice the difference. > I'm sure. Indeed, without specifying --maxtapeblocksize to configure, 32k is both the min and max blocksize. I found a thread titled 'amanda and blocksize' in the amanda-hackers list (~Jan 02), and concluded from that discussion that altering the blocksize (via --maxtapeblocksize) is probably a poor idea where amanda is concerned, regardless of real or perceived performance. Evidently the parameter evolved to handle certain problematic pieces of hardware. I suspect that the answer to the original question is that thoughput is high enough that the differences produced by simply doubling or tripling the number of filemarks produced are negligible. The -b parameter to amtapetype might not be particularly useful in the average situation. Bryan
Re: amanda + gzip errors on debian?
Niall O Broin said: > What's your backup device ? If it's a SCSI tape then I'd say your > problem is > most likely SCSI cabling termination. I had this a long time ago and > it drove > me nuts. I eventually found that the SCSI chain wasn't terminated > correctly. > Just like you, I would only encounter the problems on big backups > (because it > was only producing occasional errors, and the bigger the file, the > more > likely I was to encounter it. The way to fix the problem is to make > sure that > all SCSI cable connections are well made and that termination is > correct. > Using good quality SCSI cables is a big help too. > > If OTOH you're not using SCSI tape then I'm afraid I'm all out of > clue. I had a similar thought when I first had this problem. However, I was able to duplicate the problem simply by gzipping a big file to my ATA/IDE holding disk. So I'm certain it's not a scsi problem. -- Kurt Yoder Sport & Health network administrator
Re: sdlt versus DLT library
On Tuesday 15 July 2003 17:01, Jeremy L. Mordkoff wrote: > I'm using a DLT IV tape drive now (one tape a night), but it's not big > enough. I have 70GB partitions and when they get full, I'll have > problems. If I switch to a DLT tape library (8x40GB), will that solve my > problem? Will Amanda split backup across two tapes? Or should I just get > a SDLT tape drive (160GB)? This is a VVFAQ. Amanda will NOT split one backup across two tapes. But you can - you simply use multiple DLEs (disk list entries) for your bigger partitions, ensuring that each one is small enough to fit on a tape. Then you can decide what to do based on your backup needs, how long you want between level 0 backups etc. But if for some reason multiple DLEs doesn't suit you, an SDLT tape will help whereas a DLT library will not. Niall
Re: Amanda don't work with Exabyte VXA-2
On Tuesday 15 July 2003 16:22, Jon LaBadie wrote: > > You can fix that by doing this (as root) > > > > cd /dev > > rm null > > ln -s st0 null > > Shulov, just as a check, Niall meant this as sarcasm. Well, my tongue was rather near my cheek, let's say. I guess this WOULD work, but could lead to some 'interesting' side effects. > DO NOT DO IT! Probably best alright. > But do follow the comments in the amanda.conf file and install docs > to set up your configuration. Bottom line - amanda has to know where she is supposed to put the backups. Perhaps you know where your tape drive is, but amanda surely doesn't unless you tell her. Niall
sdlt versus DLT library
I’m using a DLT IV tape drive now (one tape a night), but it’s not big enough. I have 70GB partitions and when they get full, I’ll have problems. If I switch to a DLT tape library (8x40GB), will that solve my problem? Will Amanda split backup across two tapes? Or should I just get a SDLT tape drive (160GB)? JLM Jeremy Mordkoff Tatara Systems 978-206-0808 (direct) 978-206-0888 (fax) injustice anywhere threatens justice everywhere -- Dr. Martin Luther King
Re: amanda + gzip errors on debian?
On Tuesday 15 July 2003 16:07, Kurt Yoder wrote: > they seem to go fine. However, upon verifying the backups, I notice > gzip errors. I get two different kinds of errors: "crc" errors and > "format violated" errors. The errors don't happen on all dump > images, usually just the bigger ones (which means level 0's, which > means I'm screwed for restores!). I've had them crop up from 300 MB > into the image to 10 GB into it, and anywhere in between. At least > one gzipped image fails on every backup. . . . > Anyone else noticed this problem? And fixed it? What's your backup device ? If it's a SCSI tape then I'd say your problem is most likely SCSI cabling termination. I had this a long time ago and it drove me nuts. I eventually found that the SCSI chain wasn't terminated correctly. Just like you, I would only encounter the problems on big backups (because it was only producing occasional errors, and the bigger the file, the more likely I was to encounter it. The way to fix the problem is to make sure that all SCSI cable connections are well made and that termination is correct. Using good quality SCSI cables is a big help too. If OTOH you're not using SCSI tape then I'm afraid I'm all out of clue. Kindest regards, Niall O Broin
Stumped? amcheck server errors
Hi Folks. I'm really sorry this is such a lame question, but I'm stumped. I've been loooking over my configuration all morning, but I Still cant figure out where my changer config (chg-scsi.solaris.conf) is getting referenced and then denying me access: my amcheck.debug shows: amcheck: dgram_bind: socket bound to 0.0.0.0.793 changer: got exit: 1 str: could not read result from "/usr/local/etc/amanda/DailyBackup/chg-scsi-sola ris.conf" amcheck-server: time 0.039: could not get changer info: could not read result from "/usr/local/etc/amanda/Dai lyBackup/chg-scsi-solaris.conf" amcheck-server: time 0.039: pid 1882 finish time Tue Jul 15 10:38:01 2003 amcheck: spawning /usr/ucb/Mail in pipeline amcheck: argument list: /usr/ucb/Mail -s "DailyBackup AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE" mbruntel My amanda file is in: [EMAIL PROTECTED]: /usr/local/etc/amanda/DailyBackup $> ls -la $PWD/am*.conf -rw-r--r-- 1 amanda operator 9 Jul 15 10:24 /usr/local/etc/amanda/DailyBackup/amanda.conf amcheck-server: could not get changer info: could not read result from "/usr/local/etc/amanda/DailyBackup/chg-scsi-solaris.conf" but it exists! -rw-r--r-- 1 amanda operator2017 Jul 15 09:17 /usr/local/etc/amanda/DailyBackup/chg-scsi-solaris.conf Sorry to be so stupidly blind, but I'll be damned if I can figure out where this is being referenced, and why it isn't working.
RE: cleanup holding disk
no, amdanda works ok, i just some backup in the middle and wanted to clean all temporary files. rm works regards, gregor
Re: which tape is which ???
Michael D. Schleif said: > That's my problem: if I knew which of these tapes is the ``most > recently-written one'', then I would know which is in the current > cycle > ;< > > So, how do I determine that? Ah. Put one in and do "dd if= of=test_header bs=32k". This will grab the amanda tape header and put it in the file test_header. In this file you will then see the date of the dump on this tape. -- Kurt Yoder Sport & Health network administrator
Re: cleanup holding disk
On Tue, Jul 15, 2003 at 10:46:31AM +0200, Gregor Ibic wrote: > how can i clean holdingdisk > > i tried with amcleanup but holdingdisk still have files in it > i dont want to flush it to the tape. My holding disks are consistantly empty (except with valid dump files :) I would think that if amflush doesn't want to flush anything and amcleanup doesn't remove them, then /bin/rm is a good choice. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanda don't work with Exabyte VXA-2
On Tue, Jul 15, 2003 at 10:10:17AM +0100, Niall O Broin wrote: > On Tuesday 15 July 2003 09:46, Shulov Leonid wrote: > > > 1. amcheck don't see exabyte VXA-2 tape : > > > > amcheck DailySet1 > > Amanda Tape Server Host Check > > - > > Holding disk /home/amanda/tmp: 163717756 KB disk space available, that's > > plenty > > ERROR: /dev/null: rewinding tape: Inappropriate ioctl for device > >(expecting a new tape) > > You can fix that by doing this (as root) > > cd /dev > rm null > ln -s st0 null Shulov, just as a check, Niall meant this as sarcasm. DO NOT DO IT! > but it MIGHT be better to fix your config file. > > > Help me please. > > Help yourself - RTFM. But do follow the comments in the amanda.conf file and install docs to set up your configuration. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: which tape is which ???
Also sprach Kurt Yoder (Tue 15 Jul 02003 at 11:10:34AM -0400): > I believe both of them will be accepted by amanda when it's looking > for "backup.005". So just pick the most recently-written one to use > as the "real" backup.005. Then erase the other one using mt or dd, > and treat it as a blank tape. > > Michael D. Schleif said: > > I have been using amanda for several weeks. Initially, I tested > > various > > configurations; but, now I am supposed to be ``in production'' ;> > > > > Somehow, I find myself with two (2) identically labeled tapes: > > backup.005 ;< > > > > amcheck finds both to be valid. > > > > tapelist shows one (1) entry for backup.005. > > > > How can I find out which of these is really in the current backup > > cycle? That's my problem: if I knew which of these tapes is the ``most recently-written one'', then I would know which is in the current cycle ;< So, how do I determine that? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: which tape is which ???
I believe both of them will be accepted by amanda when it's looking for "backup.005". So just pick the most recently-written one to use as the "real" backup.005. Then erase the other one using mt or dd, and treat it as a blank tape. Michael D. Schleif said: > I have been using amanda for several weeks. Initially, I tested > various > configurations; but, now I am supposed to be ``in production'' ;> > > Somehow, I find myself with two (2) identically labeled tapes: > backup.005 ;< > > amcheck finds both to be valid. > > tapelist shows one (1) entry for backup.005. > > How can I find out which of these is really in the current backup > cycle? -- Kurt Yoder Sport & Health network administrator
amanda + gzip errors on debian?
Hello list I've been having a problem with amanda and gzip on my debian backup servers for a while now. I do my backups with gzip compression, and they seem to go fine. However, upon verifying the backups, I notice gzip errors. I get two different kinds of errors: "crc" errors and "format violated" errors. The errors don't happen on all dump images, usually just the bigger ones (which means level 0's, which means I'm screwed for restores!). I've had them crop up from 300 MB into the image to 10 GB into it, and anywhere in between. At least one gzipped image fails on every backup. I installed a second Debian backup server, and it had the exact same problem right after installation. I re-did my backup server on a different hard disk, and still had the problem. I had been using a security-updated gzip, so I tried the pre-security gzip, but had the same problem. I tried manually gzipping and unzipping images on the backup server without using amanda at all, and had the same problem. "Aha!" you say, it must not be amanda then. Well... maybe. I tried a fresh debian install with just the base system on it which includes gzip. I created a 20 GB tar file, gzipped and gunzipped it, and had no errors. The only link between all these boxes with gzip problems is that the Debian amanda-server package was installed. Anyone else noticed this problem? And fixed it? -- Kurt Yoder Sport & Health network administrator
which tape is which ???
I have been using amanda for several weeks. Initially, I tested various configurations; but, now I am supposed to be ``in production'' ;> Somehow, I find myself with two (2) identically labeled tapes: backup.005 ;< amcheck finds both to be valid. tapelist shows one (1) entry for backup.005. How can I find out which of these is really in the current backup cycle? What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- pgp0.pgp Description: PGP signature
Re: Determining optimum block size
Bryan Hodgson wrote: I've done a number of amtapetype runs on an LTO2 drive at various blocksizes, and can't detect meaningful differences at 32k / 64k / 128k. One run at 256k was killed for running too long. Indeed, that's exactly why amanda uses 32k. Try a blocksize of 512 bytes (no K), and you'll notice the difference. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Determining optimum block size
Is there an optimal block size for current tape drives? Once upon a time I acquired the notion that larger tape block sizes yielded better throughput to the tape (subject to the ability of the system to feed data fast enough.) I've done a number of amtapetype runs on an LTO2 drive at various blocksizes, and can't detect meaningful differences at 32k / 64k / 128k. One run at 256k was killed for running too long. Opinions welcome. Bryan
Re: Solaris9 : netinet/ip.h: present but cannot be compiled
On Fri, Jul 11, 2003 at 02:01:17PM -0400, Eric Siegerman wrote: > On Fri, Jul 11, 2003 at 12:57:55PM -0400, Bryan Hodgson wrote: > > configure: WARNING: netinet/ip.h: present but cannot be compiled > > configure: WARNING: netinet/ip.h: check for missing prerequisite headers? > > configure: WARNING: netinet/ip.h: proceeding with the preprocessor's result > > configure: WARNING: ## ## > > configure: WARNING: ## Report this to [EMAIL PROTECTED] ## > > configure: WARNING: ## ## > > You should be OK. > > For more explanation, see this fragment of a thread from the > Autoconf mailing-list archives. The first of these links points > to the question, the second to the reply; the rest of the thread > can be safely ignored :-) > http://mail.gnu.org/archive/html/autoconf/2003-03/msg00154.html > http://mail.gnu.org/archive/html/autoconf/2003-03/msg00156.html > Let it be noted that in order to get the client to compile for the use of the one Solaris 2.4 machine still running around here, I had to "--disable-libtool" in the configuration options. A side-effect was (evidently) that the new style header checking was disabled, and the linker (/usr/ccs/bin/ld) pulled everying together without complaint (tho the results aren't tested yet.) Probably not what the developers intended . Bryan
YA Sanity check question
OK. Here's (I think/hope) my LAST sanity question. My drive locks, and has a special "ENTRY/EXIT" port which is the only way to get tapes in and out of system. is there a parameter I can call? Example question. tape 1 is loaded into drive 1 (element 451) tape 2 is loaded into drive 2 (element 452) tape 3 is loaded into drive 3 (element 453) My "ENTRY/Exit slot (a full magazine of 5 slots) are called, 401-405. Say I want to get the tape out of drive 1 how does amanda get tape 1 out of drive 1 (ok it sends a 1, to eject). what do I do to tell amanda to file back in slot # 1, where it came from? Can someone point me to the code I need to look at? I am guess what I am looking for is how amanda uses the robot to move a tape from (slot#XYZ to slot #45X (drive1/2/3) and once I have that, I will also need to know how to move to slot 401 to actually eject the tape! --where does this (slot/tape information) get referenced? do I have a variable somewhere for entry/exit slots? or do I just need to remember them when ejecting? boy this seems complicated!
RE: Pre-emptive sanity check Question
second Follow up santity check. Or would I be better off going with the chg-solaris script, since this beast also DOES have a bar code reader in it? mitch rest deleted
Pre-emptive sanity check Question
OK. So now that I: a) have working tape drives b) a SCSI id for my robot c) software that seems to work d) a good part of my configuruation issues worked out I have a few more questions. 1) The Exabyte folks said the X80 likes to work in ASPI mode, and that there are no drivers needed for this mode supplied by them. This leads me to think the best changer I could use is chg-scsi, and I have the following questions about that file. I would guess that this is the file that tries to drive the elements in regular aspi mode too.. Here's a small snippet from my new chg-scsi file. # the device that is used for the tapedrive 1 startuse451 enduse 451 AND HERE's the question. This # (451) is what Exabyte calls the ELEMENT index assignment for my 80 cartridge library, and came out of the users manual I am presuming that this is INDEED the # that Amanda wants as the slot#. cleancart 0 # the slot where the cleaningcartridge for drive 1 is located ** This is defined as the fixed cartridge slot for the X80 drive, and is element 0. --snippet follows: number_configs 3 #(because I have 3 drives. BOY am I smart!!!) # # configs being set to how many tape drives! eject 1 # Tapedrives need an eject command sleep 5 # Seconds to wait until the tape gets ready cleanmax15 # How many times could a cleaning tape get used changerdev /dev/scsi/changer/c1t0d0 # # Next comes the data for drive 1 # config 1 drivenum1 dev /dev/rmt/0n # the device that is used for the tapedrive 1 startuse451 # The slots associated with the drive 1 (per p180in manual enduse 451 # This per page 180 in X80 manual statfile/usr/local/etc/amanda/DailyBackup/drive1-stat # The file where the actual slot info is stored cleancart 0 # the slot where the cleaningcartridge for drive 1 is located
Re: Amanda don't work with Exabyte VXA-2
On Tuesday 15 July 2003 09:46, Shulov Leonid wrote: > 1. amcheck don't see exabyte VXA-2 tape : > > amcheck DailySet1 > Amanda Tape Server Host Check > - > Holding disk /home/amanda/tmp: 163717756 KB disk space available, that's > plenty > ERROR: /dev/null: rewinding tape: Inappropriate ioctl for device >(expecting a new tape) You can fix that by doing this (as root) cd /dev rm null ln -s st0 null but it MIGHT be better to fix your config file. > Help me please. Help yourself - RTFM. Niall
Re: Amanda don't work with Exabyte VXA-2
Hi
you've not set the tape device correctly in the amanda.conf - still
/dev/null by the looks of it.
on the client what do you see the the /tmp/amanda denug logs? have you
setup inetd.conf (or xinetd.conf) correctly the HUP-ed inetd afterwards?
--
Martin Hepworth
Senior Systems Administrator
Solid State Logic Ltd
+44 (0)1865 842300
Shulov Leonid wrote:
I have RadHat Linux 9 on Tape server with Amanda 2.4.3 and Debian Linux
3.0 on clients
with Amanda 2.4.2p2-4.
Tape drive I define:
define tapetype VXA-2 {
comment "Exabyte VXA-2 drive on asraid01"
length 16 mbytes
filemark 2300 kbytes
speed 12000 kbytes}
Amanda don't work with Exabyte VXA-2
1. amcheck don't see exabyte VXA-2 tape :
amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /home/amanda/tmp: 163717756 KB disk space available, that's
plenty
ERROR: /dev/null: rewinding tape: Inappropriate ioctl for device
(expecting a new tape)
NOTE: skipping tape-writable test
Server check took 30.096 seconds
2.Tape Server don't see Client:
Amanda Backup Client Hosts Check
WARNING: aspc0001: selfcheck request timed out. Host down?
Client check: 1 host checked in 29.994 seconds, 1 problem found
(brought to you by Amanda 2.4.3)
Help me please.
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**
cleanup holding disk
how can i clean holdingdisk i tried with amcleanup but holdingdisk still have files in it i dont want to flush it to the tape. regards, gregor
Amanda don't work with Exabyte VXA-2
I have RadHat Linux 9 on Tape server with Amanda 2.4.3 and Debian Linux
3.0 on clients
with Amanda 2.4.2p2-4.
Tape drive I define:
define tapetype VXA-2 {
comment "Exabyte VXA-2 drive on asraid01"
length 16 mbytes
filemark 2300 kbytes
speed 12000 kbytes}
Amanda don't work with Exabyte VXA-2
1. amcheck don't see exabyte VXA-2 tape :
amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /home/amanda/tmp: 163717756 KB disk space available, that's
plenty
ERROR: /dev/null: rewinding tape: Inappropriate ioctl for device
(expecting a new tape)
NOTE: skipping tape-writable test
Server check took 30.096 seconds
2.Tape Server don't see Client:
Amanda Backup Client Hosts Check
WARNING: aspc0001: selfcheck request timed out. Host down?
Client check: 1 host checked in 29.994 seconds, 1 problem found
(brought to you by Amanda 2.4.3)
Help me please.
Re: Rewinding tapeless "tapes": why? error?
On Mon, Jul 14, 2003 at 08:10:27PM -0700, bao wrote: > > > > > >"1.server._home.1" is equivalent to one file on a tape. > >You don't rewind one "tape file", you rewind the entire tape. > >Your "tapes" are "file1", "file2", ... > > > >However, each should have a directory named "data". > >And the incremental dump file you show above should > >have been created in that "data" directory. > > > > > Hi Jon, > > I thought using those "file*" would help simplify the long and complex > pathnames. It turned out otherwise. > I'm sorry for the misunderstanding. Here are the complete and correct > file names. > > 1. "ammt -f /Backup/DailySet1/data/1.snook._home.1 rewind" gives > this error > > /Backup/DailySet1/data/1.snook._home.1 rewind failed: Inappropriate > ioctl for device > > 2. "ammt -f file:/Backup/DailySet1/data/1.snook._home.1 rewind" gives > > file:/Backup/DailySet1/data/1.snook._home.1 rewind failed: Not a > directory Still confusion, you are not following the primary part of my comment. > >"1.server._home.1" is equivalent to one file on a tape. > >You don't rewind one "tape file", you rewind the entire tape. > >Your "tapes" are "file1", "file2", ... On a real tape drive you specify the tape drive as something like /dev/nst0 or /dev/rmt/0ln You don't say the "fourth file on the tape drive". Your "tape drive" is file:/Backup or file:/Backup/DailySetX. I'm not sure which, but it certainly is NOT file:/Backup/DailySetX/anything $ amtape FT current amtape: scanning current slot in tape-changer rack: slot 3: date 20030624 label FTape-03 $ ls /w2/FileDrive/FTape-03/data 0-FTape-03 0.FTape-03 1-butch.var1.0 1.butch.var1.0 2-TAPEEND 2.TAPEEND $ ammt -f file:/w2/FileDrive/FTape-03/data/1.butch.var1.0 rewind file:/w2/FileDrive/FTape-03/data/1.butch.var1.0 rewind failed: Not a directory $ ammt -f file:/w2/FileDrive/FTape-03 rewind $ ammt -f file:/w2/FileDrive rewind file:/w2/FileDrive rewind failed: I/O error $ ammt -f file:/w2/FileDrive/FTape-03 status file:/w2/FileDrive/FTape-03 status: ONLINE -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
