Re: Guidelines for using a tape library?
--On Thursday, April 11, 2002 04:21:10 + David Trusty <[EMAIL PROTECTED]> wrote: > I am using the Qualstar under HPUX. Mine's on a Linux box. > I haven't found a way to address the tapes individually. I see > only two SCSI devices, whether I use the "RANDOM" or "SEQUENTIAL" > modes on the Qualstar. Is that how yours works too? > Does Amanda have some way of accessing the individual tapes? I'll verify with my docs at work tomorrow, but I believe that 'random' makes it work like a true changer and 'sequential' behaves more like a stacker. Amanda has changer scripts that can be configured to find and use the correct tape(s) for each run. Mine shows three devices, one is the changer mechanism (the scsi driver sees it as a Qualstar) and the other two are the two tape drives in the unit (the scsi driver shows those two as Sony). Look in your boot messages to see if you have something similar (its been many years since I've touched HPUX, someone else will have to chime in on how to probe scsi devices on HPUX). You may also need the mtx drivers to control the changer (http://mtx.sourceforge.net/) if HPUX doesn't have enough builtin support. Make sure you can load/unload/move tapes from the command line before you even bother with the amanda changer scripts or you will waste a lot of time and get very confused. > Also, if a dump image is bigger than one physical tape, I don't > think amanda would work. I'm just starting on the task now, > so I'm not sure that would be the case. What is your experience > in this area? With the released version that is true, although you can use GNU tar and backup subdirectories that are each smaller than a tape. I believe tape-spanning is in development but I don't know an ETA. I personally prefer tar over dump, but many on this list have the opposite opinion. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Guidelines for using a tape library?
Frank, Thanks! Here is some more info. I am using the Qualstar under HPUX. I haven't found a way to address the tapes individually. I see only two SCSI devices, whether I use the "RANDOM" or "SEQUENTIAL" modes on the Qualstar. Is that how yours works too? Does Amanda have some way of accessing the individual tapes? Also, if a dump image is bigger than one physical tape, I don't think amanda would work. I'm just starting on the task now, so I'm not sure that would be the case. What is your experience in this area? Thanks!! David >From: Frank Smith <[EMAIL PROTECTED]> >To: David Trusty <[EMAIL PROTECTED]>, [EMAIL PROTECTED] >Subject: Re: Guidelines for using a tape library? >Date: Thu, 11 Apr 2002 00:00:35 -0500 > >--On Thursday, April 11, 2002 03:26:08 + David Trusty ><[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I have a Qualstar tape library, which has 20 tapes. > > > > The library can be configured to look like one massive tape drive, > > with the 20 physical tapes hidden from the host application. I can > > cause the unit to eject the current physical tape and load a > > new one by using the "mt offl" command. > > > > My question is this. Does anyone have any tips for using Amanda > > in this type of a configuration? In particular, I am interested > > in any tips regarding labeling of tapes, since when I advance > > the unit to the next physical tape, I cannot guarantee that it > > will still have an old Amanda label. > > > > What do you think? > > > > Thanks in advance! > > > > David > > >Why not just leave it configured in its 'normal' state as a 20 slot >changer? Then you can just tell Amanda what range of slots to use >and amlabel the tapes in those slots. That's how I use our Qualstar >80 slot, and it is working fine like that. I don't think the 'just >one really big tape' idea fits well with how Amanda works, but maybe >someone else on the list can give some advantages to that approach. > >Good luck, >Frank > > >-- >Frank Smith >[EMAIL PROTECTED] >Systems Administrator Voice: >512-374-4673 >Hoover's Online Fax: >512-374-4501 _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com
Re: Guidelines for using a tape library?
--On Thursday, April 11, 2002 03:26:08 + David Trusty <[EMAIL PROTECTED]> wrote: > Hi, > > I have a Qualstar tape library, which has 20 tapes. > > The library can be configured to look like one massive tape drive, > with the 20 physical tapes hidden from the host application. I can > cause the unit to eject the current physical tape and load a > new one by using the "mt offl" command. > > My question is this. Does anyone have any tips for using Amanda > in this type of a configuration? In particular, I am interested > in any tips regarding labeling of tapes, since when I advance > the unit to the next physical tape, I cannot guarantee that it > will still have an old Amanda label. > > What do you think? > > Thanks in advance! > > David > Why not just leave it configured in its 'normal' state as a 20 slot changer? Then you can just tell Amanda what range of slots to use and amlabel the tapes in those slots. That's how I use our Qualstar 80 slot, and it is working fine like that. I don't think the 'just one really big tape' idea fits well with how Amanda works, but maybe someone else on the list can give some advantages to that approach. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda overwrites level0 without warning
--On Thursday, April 11, 2002 03:37:15 +0200 Frederic Saincy <[EMAIL PROTECTED]> wrote: > Hi, > > Frank Smith <[EMAIL PROTECTED]> writes: > >> The planner logic might not be set >> up to handle this extreme case. > > I don't know very well amanda's internal and this is the occasion for > me to look at the sources. If the planner can't, amdump must wonder: > "If i do this, can admin restore the system ?". > > If not, there is 2 solutions in an environment without tape changer: > > 1) do nothing > 2) do a level0. > > I imagine all prefers the second solution. > > I gonna look at this "extreme case" further: i did it as a test, but > imagine, for example, a bad written /etc/cronttab and the > The_Big_Problem (r) once level0 was overwritten. Too bad. > > Bye. Even if it gave the warning it would do no good if it ran enough times before you read the daily reports, as the warnings won't stop it from overwriting the tape. If you aren't using a changer just append an mt offline command to your amdump command in cron and then Amanda can't overwrite a tape without your assistance. Once you get Amanda doing some real work it will probably become impossible to run through your entire set of tapes in a day, since Amanda won't run again if it is still running from the run before, and all the planners and dumpers take some time to complete. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Guidelines for using a tape library?
Hi, I have a Qualstar tape library, which has 20 tapes. The library can be configured to look like one massive tape drive, with the 20 physical tapes hidden from the host application. I can cause the unit to eject the current physical tape and load a new one by using the "mt offl" command. My question is this. Does anyone have any tips for using Amanda in this type of a configuration? In particular, I am interested in any tips regarding labeling of tapes, since when I advance the unit to the next physical tape, I cannot guarantee that it will still have an old Amanda label. What do you think? Thanks in advance! David _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com
Re: amanda overwrites level0 without warning
Hi, Frank Smith <[EMAIL PROTECTED]> writes: > The planner logic might not be set > up to handle this extreme case. I don't know very well amanda's internal and this is the occasion for me to look at the sources. If the planner can't, amdump must wonder: "If i do this, can admin restore the system ?". If not, there is 2 solutions in an environment without tape changer: 1) do nothing 2) do a level0. I imagine all prefers the second solution. I gonna look at this "extreme case" further: i did it as a test, but imagine, for example, a bad written /etc/cronttab and the The_Big_Problem (r) once level0 was overwritten. Too bad. Bye.
Re: multiple amdump per day overwrites level0
>I agree it should warn you about the over-write, but if I remember >your original posting correctly your config had a tapecycle of >about a week and runspercycle was around 6 or so, yet you ran >amdump 8 times in one day. The planner logic might not be set >up to handle this extreme case. I took a quick look and think you're right. If things had been run "normally" (one run per day) I think it would have issued the proper warnings. I've got too many other things going on right now to pursue this, but have written it up in the TODO list. I agree with both of you that it should have warned about this. >Frank John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: advfs dislist entry
>What is the proper way to enter an advfs partition into the disklist?
Regardless of file system or OS type, you should be able to
enter either the mount point (e.g. "/home") or a full device name
("/dev/rdsk/c0t0d0s0") or a device shorthand ("c0t0d0s0").
I don't know how the latter two relate to IRIX, but I always recommend
using the mount point. If you swap hardware around at some point that's
like to stay constant.
I assume you got the advfs.diff patch installed?
There is a test program for all of this:
cd client-src
make getfsent
./getfsent
You can also run it with various names on the command line to have it
do those lookups:
./getfsent /home /opt
>EZ
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: partition has negative byte count
>Ex. Total bytes written: -594548736 > >I'm using gnutar ... What version (gnutar --version)? You **must** use 1.13.19 (or later) or else 1.12 plus the patches at www.amanda.org. >Jenn John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: dump fails for what reason??
>I think it has to do with the amanda demon. I send parts of my amdump.1 >logfile with it. Anybody any Idea Ummm, yes. It's pretty obvious: dumper: stream_client: gethostbyname(localhost) failed Amanda can't do a host name lookup on "localhost". You've got something wrong with the DNS or /etc/hosts or whatever setup. I just took a note to add a test for this to amcheck. >Axel John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: holding disk vs straight to tape
>So I'm thinking about testing the backups on that server without >using the holding disk. How is this done, is there a way of >specifying it in the amanda.conf for all dumptypes as well as >somehow specifying it for individual dumptypes? Put: holdingdisk "no" in whichever dumptypes you want. >David Flood John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: error [/bin/tar got signal 13]
>I am trying to get AMANDA working for the first time and am stuck >getting amdump to complete with all my partitions. I have tracked the >problem down to this error at the end of the sendbackup.debug file on >the client: > >error [/bin/tar got signal 13] Signal 13 is "broken pipe", which is rarely the fault of the program that reports it, but rather the next thing downstream. Is "amcheck" happy? What does your Amanda E-mail report say (all of it, except the detail section at the end). >The error changes slightly if I change the setup. i.e. DUMP doesn't >seem to work at all ... Details, please. What does it say? >Michael "Murph" Robbert John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Newbie question: amncheck - unary operator expected
>The current problem is that I'm getting the WARNING: tapedev is /dev/null, >dumps will be thrown away >but I have no tapedev "/dev/null" in my amanda.conf file. Frank is right. You need to set tapedev to "/dev/nst0". >I'm not sure about my changer config file ... It would help if you posted it. >chg-scsi-linux.conf up just because the tapedrive is connected to the scsi >card and my platform is Linux), replaced its dev entries (/dev/nst0, >/dev/sg1) with /dev/sga and changed the values of startuse, enduse and >cleancart. Huh? Did you look at the comments in the script? There aren't any variables named startuse, enduse or cleancart. >Greg John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: how to set blocksize in amanda?
>Tapetype reported speed at 2811kb/s and the vendor supplied data is 3mb/s)(= >3072 kb/s). Close enough. You never want to believe what vendors tell you. They take the rotational speed of the tape and the density and claim that's how fast it can run, when back here in the real world we all know a lot of other things get in the way. >that's about 5% only.. so I guess you were right? I'm **always** right :-). >1 questions - tapetype reported length at 38794 mbytes, and the vendor >says 40mb, couldn't this shortage in length (so to speak) also be >because it uses 32kb filemarks instead of the recommended 128kbit? I thought you said you were using a DLT-7000? That has a maximum native capacity of 35 GBytes. Don't be confused by the 40/80 stuff on the DLT-IV cartridges. That only applies to a DLT-8000. That same tape in a DLT7000 is 35/70. I'm not sure how you managed to get more than 35 GBytes on your tape. You're right that you will probably not the native (vendor) capacity either. Again, the real world gets in the way. I forget if DLT has inter-record gaps, but that would certain affect things. And there could be some tape damage that required retries, etc. >Well anyways, you are right that this is not that big a performance >issue.. I'll start testing with the current setup, as soon as I find out >what filemark means :-) A file mark is a hardware indication between files on a tape. In the old days :-), it was literally a special recording mark that could be detected during high speed search, so it actually took up physical space. At the other end of the spectrum, some newer drives record it in a special track (or a directory) and it takes up zero space. It's usually not a big deal with high capacity drives unless you back up a bajillion file systems with Amanda. It was a big deal when Amanda was first being written and the silly ExaByte 8200 file mark was measured in MBytes :-). >Klavs Klavsen John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
partition has negative byte count
Hi everyone, I've got three partitions on IRIX 6.5 (efs and xfs) that return total bytes written as a negative number. Ex. Total bytes written: -594548736 I'm using gnutar, and needless to say there's "no size line match in above gnutar output." Any idea what's going on? Thanks, Jenn
Re: SOS! problems with amrecover
>I have a strange problem with amrecover. ... As Alisa said, the most likely cause is that you don't have indexing turned on. A quick way to check this is: amadmin rtec disklist shakira.r-tec.int Look for "index YES". >If I try to set the disk default by using >setdisk /backup/client1 (client1 is the holding disk of a client) That's not what you want to do for "setdisk". You're supposed to enter the disk that was backed up on the client. For example, let's say your disklist entry looks something like this: shakira.r-tec.int /usr/local some-dumptype Then you would want to do this (if amrecover can't figure it out for itself): sethost shakira.r-tec.int setdisk /usr/local >Leonie Nuenighoff John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Should I upgrade to 2.4.3b3?
> Even when 2.4.3 proper comes out, there's really no compelling reason to > upgrade *unless* you need any of the new features. If it ain't broke... If it's not broken, it hasn't got enough features yet. ;-)
Re: Spanning multiple tapes
>We're using the Amanda version 2.3.0.4 on Solaris. Good grief! :-) >We have been having the problem (recenlty) where >the backups have been failing due to reaching the end >of the tape. ... There are two ways you could be hitting end of tape. It might be that the total cumulative size of all the image is bigger than the tape. Or you might have a single image that won't fit on a single tape. Which is it? The former (lots of images, but all smaller than a single tape) can be dealt with using a tape changer. Note that you don't have to have an actual hardware changer. Amanda comes with two "manual" changers (chg-manual and chg-multi) and I have another I'll be glad to help anyone with who wants it. Or you could write your own (they are pretty simple shell/Perl scripts). If the problem is a really big image, then you're right that Amanda does not yet support tape overflow (part of the image on one tape and the remainder on another). Although take a look at the 2.4.3 RAIT code and the discussion of it today in the list. You can use it with multiple tape drives and "cheat". If you do decide to upgrade, just a head's up that 2.4 changed the protocol and breaks backward compatibility with 2.3 (not one of our finer moments -- sigh), so you have to upgrade everything at once. >Gardiner Leverett John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: without tapes
>> Put /dev/null in for your tape device when running the amdumps, then >> set it to a real tape and do an amflush. > >Wasn't there a comment on this list before about using something non- >existent (like /dev/nosuchdevice) instead of /dev/null because amanda >was somehow 'aware' of /dev/null and would perform backups differently? Absolutely correct. Do **not** set tapedev to /dev/null unless you really want Amanda to throw all your data away. That "feature" is meant for debugging, performance test, etc. At 2.4.3 this changes to "null:" and "/dev/null" goes back to an older behavior of throwing an error (since you cannot rewind it :-). But I would still strongly recommend the "/no/such/device" technique -- you know for certain what's going on with that. >Frank John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Two tape drives
>This is the closest method Amanda has to spanning one partition or >filesystem over multiple tapes, correct? ... At the moment, yes. >... If so, how do I configure to toss the parity >away if I only have two tape drives? If it's similar to RAID 3 then >I can just specify the third drive as /dev/null? Close. You would set it to "null:", which is another Amanda output driver that throws data away. I think. I'd certainly want to experiment with this a bit. >C. Chan < [EMAIL PROTECTED] > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: multiple amdump per day overwrites level0 [long]
I agree it should warn you about the over-write, but if I remember your original posting correctly your config had a tapecycle of about a week and runspercycle was around 6 or so, yet you ran amdump 8 times in one day. The planner logic might not be set up to handle this extreme case. Frank --On Thursday, April 11, 2002 00:49:30 +0200 Frederic Saincy <[EMAIL PROTECTED]> wrote: > Hi, > > Stephen Carville <[EMAIL PROTECTED]> writes: > >> So, when you hit the seventh amdump, you should have a >> full of every filesystem on one of tapes 2 thru 6 so tape 1 can hold >> partials. > > I thougth it works like this too. Amanda simply overwrite the only one > level0 in the set of tapes, without warnings. let's reiterate the > manipulation. > >> $ amadmin find > > orion:~$ amadmin DailySet1 find > Scanning /usr/local/amanda/holdingdisk... > > date hostdisk lv tape or file file status > 2002-04-10 orion.progiweb.home / 0 DailySet1-031 OK > 2002-04-10 orion.progiweb.home / 1 DailySet1-042 OK > 2002-04-10 orion.progiweb.home / 1 DailySet1-052 OK > 2002-04-10 orion.progiweb.home / 1 DailySet1-002 OK > 2002-04-10 orion.progiweb.home / 1 DailySet1-012 OK > 2002-04-10 orion.progiweb.home / 1 DailySet1-021 OK > 2002-04-10 orion.progiweb.home / 1 DailySet1-031 OK > 2002-04-10 orion.progiweb.home / 0 DailySet1-041 OK > 2002-04-10 orion.progiweb.home /home 0 DailySet1-032 OK > 2002-04-10 orion.progiweb.home /home 1 DailySet1-041 OK > 2002-04-10 orion.progiweb.home /home 1 DailySet1-051 OK > 2002-04-10 orion.progiweb.home /home 1 DailySet1-001 OK > 2002-04-10 orion.progiweb.home /home 1 DailySet1-011 OK > 2002-04-10 orion.progiweb.home /home 1 DailySet1-022 OK > 2002-04-10 orion.progiweb.home /home 1 DailySet1-032 OK > 2002-04-10 orion.progiweb.home /home 0 DailySet1-042 OK > > >> $ amadmin info > > Current info for orion.progiweb.home /: > Stats: dump rates (kps), Full: 655.0, 642.0, -1.0 > Incremental: 947.0, 944.0, 941.0 > compressed size, Full: 37.0%, 37.0%,-100.0% > Incremental: 6.4%, 6.4%, 6.4% > Dumps: lev datestmp tape file origK compK secs > 0 20020410 DailySet1-041 492800 182109 278 > > Current info for orion.progiweb.home /home: > Stats: dump rates (kps), Full: 1006.0, 1003.0, -1.0 > Incremental: 115.0, -1.0, -1.0 > compressed size, Full: 61.6%, 61.6%,-100.0% > Incremental: 7.9%, 8.0%, 8.0% > Dumps: lev datestmp tape file origK compK secs > 0 20020410 DailySet1-042 778770 479897 477 > > >> $ amoverview > > date 04 > host disk 10 > > orion.pr /01 > orion.pr /home01 > > > *level0 is on DailySet1-04, i have made it yesterday. > > amdump (tape04) l0/l0 (yestday) > amdump (tape05) l1/l1 (today) > amdump (tape00) l2/l1 (today) (btw why level2 ?) > amdump (tape01) l2/l1 (today) > amdump (tape02) l2/l1 (today) > amdump (tape03) l2/l1 (today) > > *Before the overwrite: > >> $ amadmin find > > Scanning /usr/local/amanda/holdingdisk... > > date hostdisk lv tape or file file status > 2002-04-10 orion.progiweb.home / 1 DailySet1-042 OK > 2002-04-10 orion.progiweb.home / 0 DailySet1-041 OK > 2002-04-11 orion.progiweb.home / 1 DailySet1-051 OK > 2002-04-11 orion.progiweb.home / 2 DailySet1-002 OK > 2002-04-11 orion.progiweb.home / 2 DailySet1-012 OK > 2002-04-11 orion.progiweb.home / 2 DailySet1-022 OK > 2002-04-11 orion.progiweb.home / 2 DailySet1-032 OK > 2002-04-10 orion.progiweb.home /home 1 DailySet1-041 OK > 2002-04-10 orion.progiweb.home /home 0 DailySet1-042 OK > 2002-04-11 orion.progiweb.home /home 1 DailySet1-052 OK > 2002-04-11 orion.progiweb.home /home 1 DailySet1-001 OK > 2002-04-11 orion.progiweb.home /home 1 DailySet1-011 OK > 2002-04-11 orion.progiweb.home /home 1 DailySet1-021 OK > 2002-04-11 orion.progiweb.home /home 1 DailySet1-031 OK > > >> $ amadmin info > > Current info for orion.progiweb.home /: > Stats: dump rates (kps), Full: 655.0, 642.0, -1.0 > Incremental: 780.0, 776.0, 774.0 > compressed size, Full: 37.0%, 37.0%,-100.0% > Incremental: 4.6%, 4.6%, 4.6% > Dumps: lev datestmp tape file origK compK secs >
Re: multiple amdump per day overwrites level0 [long]
Hi, Stephen Carville <[EMAIL PROTECTED]> writes: > So, when you hit the seventh amdump, you should have a > full of every filesystem on one of tapes 2 thru 6 so tape 1 can hold > partials. I thougth it works like this too. Amanda simply overwrite the only one level0 in the set of tapes, without warnings. let's reiterate the manipulation. > $ amadmin find orion:~$ amadmin DailySet1 find Scanning /usr/local/amanda/holdingdisk... date hostdisk lv tape or file file status 2002-04-10 orion.progiweb.home / 0 DailySet1-031 OK 2002-04-10 orion.progiweb.home / 1 DailySet1-042 OK 2002-04-10 orion.progiweb.home / 1 DailySet1-052 OK 2002-04-10 orion.progiweb.home / 1 DailySet1-002 OK 2002-04-10 orion.progiweb.home / 1 DailySet1-012 OK 2002-04-10 orion.progiweb.home / 1 DailySet1-021 OK 2002-04-10 orion.progiweb.home / 1 DailySet1-031 OK 2002-04-10 orion.progiweb.home / 0 DailySet1-041 OK 2002-04-10 orion.progiweb.home /home 0 DailySet1-032 OK 2002-04-10 orion.progiweb.home /home 1 DailySet1-041 OK 2002-04-10 orion.progiweb.home /home 1 DailySet1-051 OK 2002-04-10 orion.progiweb.home /home 1 DailySet1-001 OK 2002-04-10 orion.progiweb.home /home 1 DailySet1-011 OK 2002-04-10 orion.progiweb.home /home 1 DailySet1-022 OK 2002-04-10 orion.progiweb.home /home 1 DailySet1-032 OK 2002-04-10 orion.progiweb.home /home 0 DailySet1-042 OK > $ amadmin info Current info for orion.progiweb.home /: Stats: dump rates (kps), Full: 655.0, 642.0, -1.0 Incremental: 947.0, 944.0, 941.0 compressed size, Full: 37.0%, 37.0%,-100.0% Incremental: 6.4%, 6.4%, 6.4% Dumps: lev datestmp tape file origK compK secs 0 20020410 DailySet1-041 492800 182109 278 Current info for orion.progiweb.home /home: Stats: dump rates (kps), Full: 1006.0, 1003.0, -1.0 Incremental: 115.0, -1.0, -1.0 compressed size, Full: 61.6%, 61.6%,-100.0% Incremental: 7.9%, 8.0%, 8.0% Dumps: lev datestmp tape file origK compK secs 0 20020410 DailySet1-042 778770 479897 477 > $ amoverview date 04 host disk 10 orion.pr /01 orion.pr /home01 *level0 is on DailySet1-04, i have made it yesterday. amdump (tape04) l0/l0 (yestday) amdump (tape05) l1/l1 (today) amdump (tape00) l2/l1 (today) (btw why level2 ?) amdump (tape01) l2/l1 (today) amdump (tape02) l2/l1 (today) amdump (tape03) l2/l1 (today) *Before the overwrite: > $ amadmin find Scanning /usr/local/amanda/holdingdisk... date hostdisk lv tape or file file status 2002-04-10 orion.progiweb.home / 1 DailySet1-042 OK 2002-04-10 orion.progiweb.home / 0 DailySet1-041 OK 2002-04-11 orion.progiweb.home / 1 DailySet1-051 OK 2002-04-11 orion.progiweb.home / 2 DailySet1-002 OK 2002-04-11 orion.progiweb.home / 2 DailySet1-012 OK 2002-04-11 orion.progiweb.home / 2 DailySet1-022 OK 2002-04-11 orion.progiweb.home / 2 DailySet1-032 OK 2002-04-10 orion.progiweb.home /home 1 DailySet1-041 OK 2002-04-10 orion.progiweb.home /home 0 DailySet1-042 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-052 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-001 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-011 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-021 OK 2002-04-11 orion.progiweb.home /home 1 DailySet1-031 OK > $ amadmin info Current info for orion.progiweb.home /: Stats: dump rates (kps), Full: 655.0, 642.0, -1.0 Incremental: 780.0, 776.0, 774.0 compressed size, Full: 37.0%, 37.0%,-100.0% Incremental: 4.6%, 4.6%, 4.6% Dumps: lev datestmp tape file origK compK secs 0 20020410 DailySet1-041 492800 182109 278 1 20020411 DailySet1-051 65710 28604 23 2 20020411 DailySet1-032 17070 7801 Current info for orion.progiweb.home /home: Stats: dump rates (kps), Full: 1006.0, 1003.0, -1.0 Incremental: 4315.0, 4315.0, 4314.0 compressed size, Full: 61.6%, 61.6%,-100.0% Incremental: 66.0%, 66.0%, 66.0% Dumps: lev datestmp tape file origK compK secs 0 20020410 DailySet1-042 778770 479897 477 1 20020411 DailySet1-031654043151 > $ amoverview date 04 04 host disk 10 11 orion.pr /10 12 orion.pr /home10 11 *After the overwrite: amdump (tape04) l2/l1 (today) > $ amadmin fin
Single tape?
Hi, I'm new to Amanda and I want to use it because I have multiple platforms (Sun, SGI, Linux and PCs) that I need to back up. Only the server will be backup daily while users data will be backup weekly (or something other than daily). Anyway, my question is, Is there a way to 'force' amanda to use the same tape (2 or 3 days in a raw) for incremental backups? Couldn't find anything on this and yes, I know you are not suppose to use the same tape over but this is not crucial data (not final data) and I have a ton of data to backup and not enough tapes. Thanks David
[amanda@gorn.americom.com: AmeriCom AMANDA MAIL REPORT FOR April 10, 2002]
Sorry I have to keep posting this but I cannot find the problem...
I do not understand what is causing the error "RESULTS MISSING".
Is this an error anyone understands or has experienced?
I implemented a couple of patches a few weeks ago for other problems I
was encountering (based on suggestions from this list) and if my memory
serves me, I was not having this problem prior to this.
Maybe I need to re-install the pre-patch version, but I want to know if
there is a legitimate problem or not before undoing the patches.
Thanks,
Dick
--- Start of forwarded message ---
Date: 10 Apr 2002 12:48:27 -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: AmeriCom AMANDA MAIL REPORT FOR April 10, 2002
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape Daily5.
The next tape Amanda expects to use is: Daily7.
FAILURE AND STRANGE DUMP SUMMARY:
solo.ameri /bigger RESULTS MISSING
solo.ameri /idebigger RESULTS MISSING
maul.ameri / RESULTS MISSING
andorian.a / RESULTS MISSING
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min) 0:40
Dump Time (hrs:min)0:49 0:29 0:20
Output Size (meg)6422.0 5068.7 1353.3
Original Size (meg) 6422.0 5068.7 1353.3
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 20 1 19 (1:17 3:1 4:1)
Avg Dump Rate (k/s) 2243.7 2983.9 1163.1
Tape Time (hrs:min)0:36 0:29 0:07
Tape Size (meg) 6422.6 5068.7 1353.9
Tape Used (%) 18.5 14.54.0 (level:#disks ...)
Filesystems Taped20 1 19 (1:17 3:1 4:1)
Avg Tp Write Rate (k/s) 3010.2 2983.8 3113.3
NOTES:
planner: Last full dump of solo.americom.com:/idebigger on tape overwritten in 1
run.
planner: Last full dump of gorn.americom.com:/ on tape overwritten in 1 run.
planner: Last full dump of vulcan.internal.americom.com:/usr on tape overwritten in
1 run.
planner: Last full dump of maul.americom.com:/ on tape overwritten in 1 run.
planner: Last full dump of andorian.americom.com:/ on tape overwritten in 1 run.
planner: Incremental of solo.americom.com:/idebigger bumped to level 3.
planner: Incremental of solo.americom.com:/bigger bumped to level 2.
planner: Dump too big for tape: full dump of solo.americom.com:/ delayed.
planner: Dump too big for tape: full dump of gorn.americom.com:/ delayed.
taper: tape Daily5 kb 6576736 fm 20 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
- -- -
andorian.ame / MISSING --
binar.americ / 1 416416 --0:07 61.4 0:01 528.2
binar.americ /database 1 32 32 --1:12 0.4 0:07 8.5
binar.americ /home 1 20672 20672 --1:01 340.5 0:054170.4
binar.americ /usr1 224224 --0:22 10.3 0:01 320.0
gorn.americo / 3 223008 223008 --1:422189.1 0:563990.9
gorn.americo //zena/C1 608416 608416 --6:161616.9 3:382789.3
gorn.americo /ideroot1 288288 --6:39 0.7 0:01 402.9
maul.americo / MISSING --
maul.americo /boot 1 32 32 --0:00 103.6 0:01 82.9
solo.americo / 4 414400 414400 --1:483830.0 1:553612.9
solo.americo /bigger MISSING --
solo.americo /boot 1 32 32 --0:00 94.3 0:01 83.2
solo.americo /idebiggerMISSING --
solo.americo /ideboot1 32 32 --0:00 136.9 0:01 87.0
solo.americo /ideroot1 288288 --0:01 247.4 0:01 389.0
vulcan.inter / 1 960960 --0:04 258.9 0:011034.4
vulcan.inter /boot 1 32 32 --0:00 69.1 0:01 78.5
vulcan.inter /home 1 416416 --0:09 48.4 0:01 535.8
vulcan.inter /usr0 51903365190336 -- 28:592983.9 29:002983.8
vulcan.inter /var1 70592 70592 --0:223205.9 0:164280.3
wookie.inter / 1 44224 44224 --0:076727.3 0:133358.0
wookie.inter /boot 1 32 32 --0:00 153.0 0:05 12.2
wookie.inter /usr11664 1664 --0:08.9 0:011615.4
(brought to you by Amanda version 2.4.2p2)
--- End of forwarded message ---
Re: holding disk vs straight to tape
On Wed, Apr 10, 2002 at 02:26:40PM -0500, Marc W. Mengel wrote: > I never used amanda with negative chunksizes, so I can't help you > here. The chunksize doesn't have anything to do with whether something > is put on disk, it just says what the biggest "chunk" of a backup > image will be put in one file in that disk. Not quite true. Prior to 2.4.2, negative chunksize was "magic" to tell amanda to bypass holdingdisk. I used to use that function; in 2.4.2, I've tweaked the number and size (parameter "use") of my holdingdisk entries to achieve roughly the same result for my particular installation. TMTOWTDI. :-) -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
amanda or a commercial solution?
Hi all, i just joined a new startup and am setting up everything. So of course, i'm looking around for a backup software and while there are some good expensive commercial solutions, there's also amanda. In my previous job, we had a very customized amanda setup which worked fine but i was annoyed at some of its features. Right now, what i need to hear and know is that: (1) amanda will be able to backup Network Appliances with no problem. (i'm quite sure this is the case, but i don't know how it's done.) (2) amanda can make use of a barcode reader and is able to load/unload/.. tapes as needed in a tape library. [we had no barcode reader and a painful setup for this.] The last thing i would like to get from you all are recommendations for tape libraries, as well as which driver you use (as these typically don't come with the library). i've used the stc driver on Solaris, but afair, this doesn't support the barcode reader.. Please answer directly to me, i'll post a summary. Thanks!
Re: Newbie question: amncheck - unary operator expected
--On Wednesday, April 10, 2002 14:26:34 -0500 Greg Wardawy <[EMAIL PROTECTED]> wrote: > The current problem is that I'm getting the WARNING: tapedev is /dev/null, > dumps will be thrown away > but I have no tapedev "/dev/null" in my amanda.conf file. > Here goes the beginning part of amanda.conf: > > changerfile "/usr/local/etc/amanda/chg-scsi-linux" > changerdev "/dev/sga" > tpchanger "chg-zd-mtx" > I think you might also need tapedev specified in your amanda.conf, something like: tapedev "/dev/nst0" # the no-rewind tape device to be used Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: vmlinux in boot does not restore
Also Sprach Anthony A. D. Talltree: > > http://lwn.net/2001/0503/a/lt-dump.php3 > >for what Linus has to say about it. > > Which as always is handwaving to cover the fact that he's too lazy to fix it. > I'm still confused about this. Is it because the kernel buffer vs page cache architecture is inherently flawed, implemented poorly, or is ext2/3 dump the problem? Since xfsdump and XFS are not subject to the same caveats, it would seem possible to write a dump util for a filesystem in the 2.4.x kernels which works subject to the usual limitations of dump on a live filesystem. Linus does mention in the above: However, it may be that in the long run it would be advantageous to have a "filesystem maintenance interface" for doing things like backups and defragmentation.. Is such an interface necessary? I doubt FAT16/32 has such an interface, perhaps it is so simple it doesn't require one. Syncsoft's backup util for Windows NT/2000 claims it can backup live filesystems without file corruption - does NTFS have such an API? -- C. Chan < [EMAIL PROTECTED] > PGP Public Key: finger [EMAIL PROTECTED]
Re: SOS! problems with amrecover
Misspelled amanda config? That would keep it from finding the right index directory in that config's amanda.conf... On Wed, 10 Apr 2002, "Nünighoff, Leonie, NUE" wrote: > > Hello mailinglist, > > I have a strange problem with amrecover. > This afternoon I have a presentation about amanda backup service and nothing > works (murphy's task...) > > When I start amrecover as root, the following error occurs: > > shakira:/ # amrecover -C rtec -s shakira.r-tec.int -t shakira.r-tec.int -d > /dev/nst0 > AMRECOVER Version 2.4.2p2. Contacting server on shakira.r-tec.int ... > 220 shakira AMANDA index server (2.4.2p2) ready. > 200 Access OK > Setting restore date to today (2002-04-10) > 200 Working date set to 2002-04-10. > 200 Config set to rtec. > > 501 No index records for host: shakira. Invalid? <- !!! > > > Trying shakira.r-tec.int ... > 200 Dump host set to shakira.r-tec.int. > Can't determine disk and mount point from $CWD > amrecover> > > terrible. > If I try to set the disk default by using > setdisk /backup/client1 (client1 is the holding disk of a client) > In this directory I find the data of the /etc-directory of this client1. > > Have a look what happens: > > amrecover> setdisk /backup/client1 > 501 No index records for disk: /backup/client1. Invalid? > amrecover> > > The same error occurs if I only set the mountpoint /backup as disk, not > /backup/client1 . > It happens with all my holding disks. > > Can you imagine what's my problem? > Please help me...I will really get in trouble if I fail my presentation... > > Thank you so much, > > best regards > > Leonie Nuenighoff > > > > > -- - Marc Mengel <[EMAIL PROTECTED]>
error [/bin/tar got signal 13]
I am trying to get AMANDA working for the first time and am stuck getting amdump to complete with all my partitions. I have tracked the problem down to this error at the end of the sendbackup.debug file on the client: error [/bin/tar got signal 13] The error changes slightly if I change the setup. i.e. DUMP doesn't seem to work at all and if I turn on indexing I get a broken tee error I think. The client is running RH6.2 and AMANDA 2.4.1p1-7 The servier is running RH7.2 and AMANDA 2.4.2p2-4 I believe that both are the most current RH RPMS from RedHat. I'll be happy to supply any config files or more information if anybody thinks that they can crack this problem. Thanks! -- Michael "Murph" Robbert System Administrator for Math/CS Colorado School of Mines, Golden, CO 80401-1887 Office: SH220 Office phone: 303-273-3786 Pager: 303-461-6543 or Text messages: [EMAIL PROTECTED] Email: [EMAIL PROTECTED]
Re: vmlinux in boot does not restore
Also Sprach Marc W. Mengel: > > If you read up on the Linux lists, with Linux 2.4.* kernels, using > "dump" for your backups can get various errors and is not recommended. > See > http://lwn.net/2001/0503/a/lt-dump.php3 > for what Linus has to say about it. > This specifically applies to dump for ext2/ext3 and not xfsdump for XFS, though xfsdump may have other problems under Linux. Of the other filesystems, I don't think ReiserFS or JFS even have a dump util at the moment, though JFS does have one under AIX (called "backup" rather than "dump"). > Especially avoid dump if you're running 2.4.0-2.4.4 SMP kernels. See > http://lwn.net/2001/0503/kernel.php3 > Any idea if this is still an issue on the 2.4.18+ kernels? -- C. Chan < [EMAIL PROTECTED] > PGP Public Key: finger [EMAIL PROTECTED]
Re: Newbie question: amncheck - unary operator expected
> >>> [EMAIL PROTECTED] 04/09/02 12:17PM >>>
> >
> >I got it. Thanks a lot. I'll install it first thing tomorrow morning.
>
> Let me know how it goes. In theory :-), it's perfect. But I don't
> run mtx here so debugging has been a bit of an adventure. It's ever so
> faintly possible there is a minuscule portion of a tiny chance you'll
> find a problem. But if so, send me the output of what you tried, the
> corresponding /tmp/amanda/*debug file, and why you think it's wrong
> (in case it's not obvious).
Thank you for your help, John. I'm trying to use the script I've downloaded
from your ftp site. I removed my old amanda installation (it was installed
from redhat 7.2 rpm) and everything related to it. Then I installed
amanda-2.4.2p2 from the source, placed chg-zd-mtx.sh.in-243 in changer-src
renaming it to chg-zd-mtx.sh.in, run ./configure --with-user=amanda
--with-group=disk and make from the top and then make install from
changer-src.
The current problem is that I'm getting the WARNING: tapedev is /dev/null,
dumps will be thrown away
but I have no tapedev "/dev/null" in my amanda.conf file.
Here goes the beginning part of amanda.conf:
#amanda.conf
org "DailySet"
mailto "amanda wardawyg"
dumpuser "amanda"
inparallel 4
netusage 600 Kbps
dumpcycle 4 weeks
runspercycle 4 weeks
tapecycle 25 tapes
bumpsize 20 Mb
bumpdays 1
bumpmult 4
etimeout 300
runtapes 2
changerfile "/usr/local/etc/amanda/chg-scsi-linux"
changerdev "/dev/sga"
tpchanger "chg-zd-mtx"
tapetype DAT-120m
labelstr "^DailySet1[0-9][0-9]*$"
holdingdisk hd1 {
comment "main holding disk"
directory "/var/tmp"
use 1000 Mb
}
infofile "/usr/adm/amanda/Daily/curinfo"
logdir "/usr/adm/amanda/Daily"
indexdir "/usr/adm/amanda/Daily/index"
define tapetype DAT-120m {
comment "DAT tape (120m tapes)"
length 4000 mbytes
filemark 250 kbytes
speed 512 kbytes
}
###cut##
I'm not sure about my changer config file - I took an example file (I picked
chg-scsi-linux.conf up just because the tapedrive is connected to the scsi
card and my platform is Linux), replaced its dev entries (/dev/nst0,
/dev/sg1) with /dev/sga and changed the values of startuse, enduse and
cleancart.
OK, here goes amcheck output:
[
root@linver sbin]# su amanda -c"/usr/local/sbin/amcheck Daily"
Amanda Tape Server Host Check
-
WARNING: tapedev is /dev/null, dumps will be thrown away
Holding disk /var/tmp: 15421824 KB disk space available, that's plenty
NOTE: skipping tape checks
NOTE: info dir /usr/adm/amanda/Daily/curinfo: does not exist
NOTE: it will be created on the next run
Server check took 0.004 seconds
Amanda Backup Client Hosts Check
WARNING: linver: selfcheck request timed out. Host down? #I'll work on it
later - my comment
Client check: 1 host checked in 30.006 seconds, 1 problem found
(brought to you by Amanda 2.4.2p2)
and the contest of the corresponding debug file:
amcheck: debug 1 pid 21850 ruid 33 euid 0 start time Wed Apr 10 13:34:12 2002
amcheck: dgram_bind: socket bound to 0.0.0.0.766
amcheck: pid 21850 finish time Wed Apr 10 13:34:42 2002
I tried to put tapedev "/dev/sga" in amanda.conf but I've got:
amcheck-server: could not get changer info: cannot determine drive slot from
/dev/sga
and (with runtapes 1 and #tpchanger "chg-zd-mtx"):
ERROR: /dev/sga: rewinding tape: Permission denied
(expecting a new tape)
##
Thank you again
Greg
Re: amrecover - permission denied
Sounds like your /dev/nst0 device is not readable by your amanda user. What does an 'ls -l /dev/nst0' look like? On Wed, 10 Apr 2002 [EMAIL PROTECTED] wrote: > Hi folks, > I'm using amanda-2.4.2p2 on Redhat 7.2 ... all backups seems to be ok > but now I need to recovery some files and when I try to use amrecover > I'm getting the follow error: > > ---xxx--- > amidxtaped: debug 1 pid 28508 ruid 501 euid 501 start time Wed Apr 10 > 12:24:36 2002 > amidxtaped: version 2.4.2p2 > > SECURITY USER root > bsd security: remote host svr-ip02.inetpres.private user root local user > amanda > amandahosts security check passed > > 6 > amrestore_nargs=6 > > -h > > -p > > /dev/nst0 > > mail.inetpres.com > > ^/home/vpopmail$ > > 20020408 > Ready to execv amrestore with: > path = /usr/local/sbin/amrestore > argv[0] = "amrestore" > argv[1] = "-h" > argv[2] = "-p" > argv[3] = "/dev/nst0" > argv[4] = "mail.inetpres.com" > argv[5] = "^/home/vpopmail$" > argv[6] = "20020408" > amrestore: could not open tape /dev/nst0: Permission denied > amidxtaped: amrestore terminated normally with status: 2 > Rewinding tape: no tape online > amidxtaped: pid 28508 finish time Wed Apr 10 12:24:36 2002 > ---xxx--- > as a extra information the amanda user belongs to disk group. > any ideas ?? > > thx > Sergio Pereira > > -- - Marc Mengel <[EMAIL PROTECTED]>
Re: holding disk vs straight to tape
On Wed, 10 Apr 2002, David Flood wrote: > What are the advantages/disadvantages of using the holding disk? > What are the advantages/disadvantages of dumping stuff straight to > tape? Advantages of holding disk: * Better tape throughput, better tape reliability because you can stream your tapedrive. * you can be backing up multiple clients at the same time, each writing to the holding disk, and then spool them out later. * You can keep some dump images on the holding disk and restore from them without fetching a tape. Disadvantages: * You need a big enough holding disk to be useful. > We have a tapeserver which is our fileserver and as such is just > backing itself up. When we upgraded from 2.4.1p1 to 2.4.2p2 the > backups suddenly started taking longer. It's just accured to me one > of the differences I had to make that could be causing this. That is > a negative chunksize was no longer supported in 2.4.2p2. A > negative chunksize meant that all dumps larger than the chunksize > value was dumped straight to disk. I never used amanda with negative chunksizes, so I can't help you here. The chunksize doesn't have anything to do with whether something is put on disk, it just says what the biggest "chunk" of a backup image will be put in one file in that disk. The size of your holding disk, in combination with the "reserve" value, and any "holdingdisk" flag on the particular dumptype is what determines what gets dumped to disk versus directly to tape. > So I'm thinking about testing the backups on that server without > using the holding disk. How is this done, is there a way of > specifying it in the amanda.conf for all dumptypes as well as > somehow specifying it for individual dumptypes? - Marc Mengel <[EMAIL PROTECTED]>
Re: vmlinux in boot does not restore
> http://lwn.net/2001/0503/a/lt-dump.php3 >for what Linus has to say about it. Which as always is handwaving to cover the fact that he's too lazy to fix it.
Re: Two tape drives
Also Sprach Marc W. Mengel: > > On Mon, 1 Apr 2002, C. Chan wrote: > > > > > Is there currently a way to back up to two or more tape drives simultaneously > > > using the same Amanda config? > > > In 2.4.3 (currently in beta) you can stripe a backup accross two tapes > with the RAIT code, but to do so you have to throw the parity stripe away, > so if either tape fails, you lose both. > This is the closest method Amanda has to spanning one partition or filesystem over multiple tapes, correct? If I have two 40GB tape drives and an 80GB partition which I want to backup using dump and not GNU tar, I can use the RAIT code w/o parity to span the partition over the two smaller tapes? If so, how do I configure to toss the parity away if I only have two tape drives? If it's similar to RAID 3 then I can just specify the third drive as /dev/null? > Otherwise you can just run two amdumps, and have each one do roughly > half of your data. > But this won't span a large partition over smaller drives. > - > Marc Mengel <[EMAIL PROTECTED]> > -- C. Chan < [EMAIL PROTECTED] > PGP Public Key: finger [EMAIL PROTECTED]
Re: without tapes
--On Wednesday, April 10, 2002 13:56:02 -0500 "Marc W. Mengel" <[EMAIL PROTECTED]> wrote: > On Wed, 3 Apr 2002, Juanjo wrote: > >> Hi, >> >> Is it possible to run amanda "without-tapes" so it dumps only to holding >> disk? >> But what I mean is not to take off the tapes physically but disabling tape >> writing. I want to accumulate incrementals worth a week and flush them on >> friday to a tape... >> >> How can I do such a thing? > > Put /dev/null in for your tape device when running the amdumps, then > set it to a real tape and do an amflush. > Wasn't there a comment on this list before about using something non- existent (like /dev/nosuchdevice) instead of /dev/null because amanda was somehow 'aware' of /dev/null and would perform backups differently? You could just not have the correct tape in the drive and amanda will keep accumulating the backups in the holding disk. Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: GFS-rotation scheme with amanda
Amanda is not so picky about tape rotations. As long as the scheme you use doesn't try to overwrite any backups which you've said you should still keep of a given partition, and the tape labels match the regexp in your amanda.conf, you can rotate the tapes any way you like. On Mon, 8 Apr 2002, Georg Lutz wrote: > Hello, > > I am about to check if it is possible to implement a GFS-backup scheme we used with >ArcServe: > > There are 4 day-tapes day1-day4 which are used every week from Monday to > Thursday in rotation, so only the tape with the oldest data is overwritten. > > There are 5 week-tapes week1-week5 which are used on the last work-day of > the week (mostly friday) in rotation, so only the tape with the oldest data is >overwritten. > > On the last work-day of the month a archival monthly backup which is never > overwritten. > > Only full backups of the local host should be performed. > > My idea was to create 3 amanda tape sets: > day: dumpcycle 0, runspercycle 1 day ???, tapecycle 4 tapes > week: dumpcycle 0, runspercycle 1 day ???, tapecycle 5 tapes > month: dumpcycle 0,runspercycle 1 day ???, tapecycle 999 tapes > > amdup will be called via wrapper script which determines what tape-set has to > be used. > > > Would this configuration work as I described above? > > Another problems could be public holidays. Would it be save to just not call > amdump at this days? Would amanda be upset and confuse the rotation-cycle(not > overwrite the oldest tape)? > > BTW, is it possible to browse through all index databases on the server with >amrecover or is it mandantory to specify exactly one? > > Please CC, I'm not subscribed. > > Thanks in advance. > > -- - Marc Mengel <[EMAIL PROTECTED]>
Re: without tapes
On Wed, 3 Apr 2002, Juanjo wrote: > Hi, > > Is it possible to run amanda "without-tapes" so it dumps only to holding > disk? > But what I mean is not to take off the tapes physically but disabling tape > writing. I want to accumulate incrementals worth a week and flush them on > friday to a tape... > > How can I do such a thing? Put /dev/null in for your tape device when running the amdumps, then set it to a real tape and do an amflush. - Marc Mengel <[EMAIL PROTECTED]>
Re: disklist and hw compression
When you are using hardware compression on the tape drive, the
backup image cached on disk is of course not yet compressed.
If it thinks the dump won't fit on the tape, did you pick
a different tapetype for the compressed device?
On Tue, 2 Apr 2002, Matthew Boeckman wrote:
> I have two (hopefully) quick questions.
>
> I'm running an ultra5, and trying to level0 a 60+gig filesystem. Using
> software compression took over 22 hours (i killed it at that point) so I
> decided to use hardware, specifying /dev/rmt/0cn as the tape device in
> amanda.conf. When I tried to run amdump, it failed saying that "dumps
> too large for disk", which is true if you don't count the hardware
> compression I was trying to use. The tapes are AIT2 50GB tapes. Is there
> a way to force amanda to do this? I assume perhaps amadmin csd force
> ? I wanted to know for sure before kicking off another
> 20+hour backup cycle. Or is there something that I have to configure in
> amanda to let it know i'm using hardware compression and to ignore tape
> warnings?
>
> The second and sort-of corollary to that is what is the exact syntax of
> exclude files referenced from disklist? I can't seem to find an exact
> answer in the documentation/FAQOMATIC. The examples/disklist file has
> the following:
> slowsrv /usr {
>user-tar
>exclude list ".exclude"
>compress server fast
> } 2 le0 # no line break before spindle and interface
> Does that mean that .exclude is in /usr ? Is it exclude absolute
> pathnames or any pattern match? In other words if I want to exclude
> /usr/bob, and in the exclude I have /bob, will that exclude any match
> for bob, or only subdirs of the mount being backed up? Likewise, what
> are the "compress server fast" lines about?
>
> Thanks!
>
>
--
-
Marc Mengel <[EMAIL PROTECTED]>
Re: files disappearing?
On Tue, 2 Apr 2002, Tom Van de Wiele wrote: > hi > > I was just wondering. We have a big fileserver here, which is backup'ed > every day. On two occassions, 2 dirs have disappeared. > > I'm just making sure, amanda doesn't write to the disk its backup'ing, > right? If it doesn't, then some (l)user here is the cause. Except in the case where the disk is the disk cache, or is where you are writing logfiles, etc. amanda does not write to disks it is backing up. - Marc Mengel <[EMAIL PROTECTED]>
Re: Problem sending mail
Sounds like the configure script couldn't find a mail program and set it to NONE. You should have gotten an error message like: *** WARNING: Amanda cannot send mail reports without these programs. Set MAILER to some program that accepts -s subject user < message_file. when you ran configure. In any case, that's what you need to do, set MAILER in the environment to a program like "mail" or "mailx" that takes a -s subject argument, and redo the configure. On Mon, 1 Apr 2002, John Rosendahl wrote: > I have amanda (2.4.3b2) running for the most part but it will not send > me a report > When I run amreport I get the following message > sh: NONE: command not found > amreport: mail command failed: NONE -s "MEC Denver AMANDA MAIL REPORT > FOR March 28, 2002" [EMAIL PROTECTED] > > I would think that I could find the simple thing I need to change in > order to get sendmail to replace none but I can't find it. any help > would be greatly appricated. > > > > > > -- - Marc Mengel <[EMAIL PROTECTED]>
Re: need help on how to config root partition in disklist
You can certainly put "/" in your disklist as the drive name. Probably /dev/hda6 isn't working because that is not how the drive is mounted in /etc/fstab, rather it is mounted by LABEL=/ or some other such thing. On Mon, 1 Apr 2002 [EMAIL PROTECTED] wrote: > Hi, > > I am a relatively new amanda users. I got a problem where I could not > find answers in the exsiting mail archive. > > The problem is: in my disklist file I listed > > machinename /dev/sda6 root-tar > > /dev/sda6 is my root partition and the mount point is / > > and I always get the error message about disk offline. > > although the following lines work fine. > > machinename /dev/sda1 root-tar > machinename /dev/sdb1 high-tar > > /dev/sda1 is the /boot partition and /dev/sdb1 is the /home partition. > > I checked the sendsize.*.debug file. It looks like that amanda didn't > translate the filesystem names to the right dirname. > > A working case will be like: > calculating for amname '/dev/sda1' dirname '/boot' > > the failed case looks like > calculating for amname '/dev/sda6' dirname '/dev/sda6' > > How could I get around with this? > > Can I put "/" instead of "/dev/sda6" in my disklist file? I am > hesitating to do this because I am not sure if I will include > everything ( for example /home which is a separate partition) by > using just /. What I intended to do is only backuping the root > partition. > > My OS is RedHat 7.2 and amanda verison 2.4.2p2. > > Thanks. zhiwei > > > > > > -- - Marc Mengel <[EMAIL PROTECTED]>
Re: Two tape drives
On Mon, 1 Apr 2002, David Flood wrote: > I want to split my backups over two DLT drives. Is this possible and > if so how is it best done? Can amanda be configured to do this > somehow or do/can I run two instances of amanda at the same > time? Running two amdumps with different configs at the same time is easiest. - Marc Mengel <[EMAIL PROTECTED]>
Re: Two tape drives
On Mon, 1 Apr 2002, Eric Trager wrote: > > On Mon, 1 Apr 2002, C. Chan wrote: > > > Is there currently a way to back up to two or more tape drives simultaneously > > using the same Amanda config? > > Apparently not. In 2.4.3 (currently in beta) you can stripe a backup accross two tapes with the RAIT code, but to do so you have to throw the parity stripe away, so if either tape fails, you lose both. Otherwise you can just run two amdumps, and have each one do roughly half of your data. - Marc Mengel <[EMAIL PROTECTED]>
Re: Not writing tape label...
On Fri, 29 Mar 2002, James Kelty wrote: > When I run the amlabel utility (% amlabel Daily Daily123), I get this error: > > rewinding, reading label, not an amanda tape > rewinding, writing label Daily123, checking label > amlabel: no label found, are you sure /dev/st0 is non-rewinding? It is referring to the devices nodes in /dev; usually there is (at least) /dev/st0 and /dev/nst0 (or /dev/st0n depending on platform) where the former is a rewind-on-close() device, and the latter only does a rewind when specifically asked (via 'mt rewind', etc.) So most likely you need to specify /dev/nst0 rather than /dev/st0. Marc
dump fails for what reason??
Hi Guys, I am trying to find out why my tapebackup will not work. Amcheck reports no problems but every dump attempt fails. I think it has to do with the amanda demon. I send parts of my amdump.1 logfile with it. Anybody any Idea Thanks in advanc. Axel GENERATING SCHEDULE: DUMP node16 sda7 20020410 11775 0 1970:1:1:0:0:0 20375963 679198 1 1970:1:1:0:0:0 20375963 679198 driver: adding holding disk 0 dir /home/amanda size 2097152 reserving 629145 out of 2097152 for degraded-mode dumps driver: start time 110.101 inparallel 1 bandwidth 2600 diskspace 2097152 dir OBSOLETE datestamp 20020410 driver: drain-ends tapeq LFFO big-dumpers sssSS driver: result time 110.101 from taper: TAPER-OK driver: dumping node16:sda7 directly to tape driver: send-cmd time 110.101 to taper: PORT-WRITE 00-1 node16 sda7 0 20020410 taper: try_socksize: receive buffer size is 65536 taper: bind_portrange: port 736: Permission denied taper: stream_server: waiting for connection: 0.0.0.0.2739 driver: result time 110.101 from taper: PORT 2739 driver: send-cmd time 110.101 to dumper0: PORT-DUMP 01-2 2739 node16 sda7 NODEVICE 0 1970:1:1:0:0:0 DUMP |;bsd-auth;compress-fast; driver: state time 110.101 free kps: 2570 space: 2097152 taper: writing idle-dumpers: 0 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 110.101 if : free 570 if ETH0: free 1000 if LOCAL: free 1000 driver: hdisk-state time 110.101 hdisk 0: free 2097152 dumpers 0 dumper: stream_client: gethostbyname(localhost) failed driver: result time 110.142 from dumper0: FAILED 01-2 [taper port open: Resource temporarily unavailable] amdump: end at Wed Apr 10 13:58:55 EDT 2002 (END) signature.asc Description: This is a digitally signed message part
Re: multiple amdump per day overwrites level0
On 10 Apr 2002, Frederic Saincy wrote: - Hi all, - - in my amanda.conf - ### - dumpcycle 1 weeks - runspercycle 5 - tapecycle 6 tapes - ### - - i ran 7 amdumps today (testing). The first amdump does a level0, and - the last overwrite this unique level0 with a level1. - - This is a bug, a feature or did i miss something ? :) - - I can give more information if needed. - - Thank you and Bye. As I undertand the amanda scheduling algorithm, it does a full for everything to get started and then tries to spread the fulls out over the tapecycle. So, when you hit the seventh amdump, you should have a full of every filesystem on one of tapes 2 thru 6 so tape 1 can hold partials. To list what backups are on what tapes, try: $ amadmin find $ amadmin info $ amoverview -- -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt == Government is like burning witches: After years of burning young women failed to solve any of society's problems, the solution was to burn more young women. ==
advfs dislist entry
Should be a simple one... What is the proper way to enter an advfs partition into the disklist? I looked into the /etc/fdmns// directory, saw which partition was involved and put that into the disklist. The report comes back: FAIL planner 0 [disk offline on ?] Thanks, EZ
amrecover - permission denied
Hi folks, I'm using amanda-2.4.2p2 on Redhat 7.2 ... all backups seems to be ok but now I need to recovery some files and when I try to use amrecover I'm getting the follow error: ---xxx--- amidxtaped: debug 1 pid 28508 ruid 501 euid 501 start time Wed Apr 10 12:24:36 2002 amidxtaped: version 2.4.2p2 > SECURITY USER root bsd security: remote host svr-ip02.inetpres.private user root local user amanda amandahosts security check passed > 6 amrestore_nargs=6 > -h > -p > /dev/nst0 > mail.inetpres.com > ^/home/vpopmail$ > 20020408 Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = "amrestore" argv[1] = "-h" argv[2] = "-p" argv[3] = "/dev/nst0" argv[4] = "mail.inetpres.com" argv[5] = "^/home/vpopmail$" argv[6] = "20020408" amrestore: could not open tape /dev/nst0: Permission denied amidxtaped: amrestore terminated normally with status: 2 Rewinding tape: no tape online amidxtaped: pid 28508 finish time Wed Apr 10 12:24:36 2002 ---xxx--- as a extra information the amanda user belongs to disk group. any ideas ?? thx Sergio Pereira
Spanning multiple tapes
I looked around in the archive and didn't find this answered (directly), so here is a similar issue: We're using the Amanda version 2.3.0.4 on Solaris. We have been having the problem (recenlty) where the backups have been failing due to reaching the end of the tape. Problem is, the backups don't span multiple tape. I can't find a config to do this listed in the man pages. The functionality exists on other versions, but I don't know if it will work on our version. Simple question: do I need to just upgrade the server (and client software) and fix it in the new config? -- Gardiner Leverett [EMAIL PROTECTED] Merit Network, Inc. Phone: 734-647-9888 4251 Plymouth Rd., Suite 2000 Ann Arbor, MI 48105-2785 http://www.merit.edu
holding disk vs straight to tape
What are the advantages/disadvantages of using the holding disk? What are the advantages/disadvantages of dumping stuff straight to tape? We have a tapeserver which is our fileserver and as such is just backing itself up. When we upgraded from 2.4.1p1 to 2.4.2p2 the backups suddenly started taking longer. It's just accured to me one of the differences I had to make that could be causing this. That is a negative chunksize was no longer supported in 2.4.2p2. A negative chunksize meant that all dumps larger than the chunksize value was dumped straight to disk. So I'm thinking about testing the backups on that server without using the holding disk. How is this done, is there a way of specifying it in the amanda.conf for all dumptypes as well as somehow specifying it for individual dumptypes? Why was this disabled or has it been replaced by another feature I don't know about. David Flood Systems Administrator
Re: SOS! problems with amrecover
Looks like you didn't specify "index yes" in your dumptype definition (near the end of the amanda.conf file). I ran into this yesterday when I was trying to run amrecover from a client. Maybe you could do what I did-- - redefine the dumptype (add 'index yes') - use amadmin to force a level 0 dump on an example file system - run amdump (an index will be created during this run) Nünighoff, Leonie, NUE wrote: >Hello mailinglist, > >I have a strange problem with amrecover. >This afternoon I have a presentation about amanda backup service and nothing >works (murphy's task...) > >When I start amrecover as root, the following error occurs: > >shakira:/ # amrecover -C rtec -s shakira.r-tec.int -t shakira.r-tec.int -d >/dev/nst0 >AMRECOVER Version 2.4.2p2. Contacting server on shakira.r-tec.int ... >220 shakira AMANDA index server (2.4.2p2) ready. >200 Access OK >Setting restore date to today (2002-04-10) >200 Working date set to 2002-04-10. >200 Config set to rtec. > >501 No index records for host: shakira. Invalid? <- !!! > > >Trying shakira.r-tec.int ... >200 Dump host set to shakira.r-tec.int. >Can't determine disk and mount point from $CWD >amrecover> > >terrible. >If I try to set the disk default by using >setdisk /backup/client1 (client1 is the holding disk of a client) >In this directory I find the data of the /etc-directory of this client1. > >Have a look what happens: > >amrecover> setdisk /backup/client1 >501 No index records for disk: /backup/client1. Invalid? >amrecover> > >The same error occurs if I only set the mountpoint /backup as disk, not >/backup/client1 . >It happens with all my holding disks. > >Can you imagine what's my problem? >Please help me...I will really get in trouble if I fail my presentation... > >Thank you so much, > >best regards > >Leonie Nuenighoff > > > >
Re: Problem with 2.4.3b3 on FreeBSD
Hi, > >If you want to continue using 2.4.3b3, apply the following patch: > > There's one problem with your patch. The fclose() call should either be > protected inside the "if (exclude != NULL)" test, or it should be changed > to afclose(), which will test for NULL. Oops -- right! Seems that Solaris 2.8 checks fclose() for NULL, but not feof(), as it worked fine with that patch. But you're right, of course; the fclose() definitely belongs _inside_ the "if (exclude != NULL)" block. Best regards, Holger -- [EMAIL PROTECTED] ++49 +5246 80 1438
FAQ - wrong data
Hi guys,
I found the DLT I have.. it's a Tandberg DLT1 (that's why it states
40/80gb on tape type IV).
found this under that drive:
>> from FAQ-o-matic
Quantum DLT7000 391B
data from tapetype length 38398 mbytes filemark 40 kbytes speed 1494 kps
On FreeBSD 4.4RC5 PIII 1GH 512MB RAM
data from tapetype: length 38398 mbytes filemark 40 kbytes speed 1494
kps On FreeBSD 4.4RC5 PIII 1GH 512MB RAM on Adaptec 19160B Ultra160 SCSI
<<
As you can see I got twice the kps as they did.. see earlier post:
[root]# tapetype -f /dev/tape -e 35g
wrote 1238544 32Kb blocks in 108 files in 13999 seconds (short write)
wrote 1244278 32Kb blocks in 217 files in 14257 seconds (short write)
define tapetype unknown-tapetype {
comment "just produced by tapetype program"
length 38794 mbytes
filemark 0 kbytes
speed 2811 kps
}
so I wouldn't really like to set the filemark at 40kbytes, if that means
it will run at half speed..
Do any of you have any explanations for this HUGE difference?
--
Regards,
Klavs Klavsen
-| This mail has been sent to you by: |
Klavs Klavsen - OpenSource Consultant
[EMAIL PROTECTED] - http://www.vsen.dk
Get PGP key from www.keyserver.net - Key ID: 0x586D5BCA
Fingerprint = A95E B57B 3CE0 9131 9D15 94DA E1CD 641E 586D 5BCA
[ I believe that... ]---
It is a myth that people resist change. People resist what other
people make them do, not what they themselves choose to do...
That's why companies that innovate successfully year after year
seek their peopl's ideas, let them initiate new projects and
encourage more experiments.-- Rosabeth Moss Kanter
signature.asc
Description: This is a digitally signed message part
Re: how to set blocksize in amanda?
On Tue, 2002-04-09 at 19:38, John R. Jackson wrote: > >I was wondering how I set the blocksize in amanda? > > Version 2.4.3 (now in beta test) has this ability. See amanda(8). Cool :-) > So the point is, do a **lot** of testing first before deciding to > go down this path. The simplest thing is to just look at your daily > Amanda E-mail. It reports the tape write speed. Look at the value for > full dumps (since they are large enough to be statistically useful). > Is it close to the rated drive speed? If so, then messing with the > block size isn't going to make it go any faster. Tapetype reported speed at 2811kb/s and the vendor supplied data is 3mb/s)(3072 kb/s). that's about 5% only.. so I guess you were right? 1 questions - tapetype reported length at 38794 mbytes, and the vendor says 40mb, couldn't this shortage in length (so to speak) also be because it uses 32kb filemarks instead of the recommended 128kbit? Well anyways, you are right that this is not that big a performance issue.. I'll start testing with the current setup, as soon as I find out what filemark means :-) -- Regards, Klavs Klavsen -| This mail has been sent to you by: | Klavs Klavsen - OpenSource Consultant [EMAIL PROTECTED] - http://www.vsen.dk Get PGP key from www.keyserver.net - Key ID: 0x586D5BCA Fingerprint = A95E B57B 3CE0 9131 9D15 94DA E1CD 641E 586D 5BCA [ I believe that... ]--- It is a myth that people resist change. People resist what other people make them do, not what they themselves choose to do... That's why companies that innovate successfully year after year seek their peopl's ideas, let them initiate new projects and encourage more experiments.-- Rosabeth Moss Kanter signature.asc Description: This is a digitally signed message part
Re: [amanda@gorn.americom.com: AmeriCom AMANDA MAIL REPORT FOR April 9, 2002]
i guess your next step would be the more detailed logs. How about reviewing the 'amdump.[0-9]' files in the 'logdir' directory defined in amanda.conf ? [EMAIL PROTECTED] wrote: > > Thanks for your reply... > > However, the Ecrix V17 tapesize is set to 35000 mbytes and... > > Filesystem Size Used Avail Use% Mounted on > solo.americom.com:/ is: /dev/sda3 7.9G 6.9G 632M 92% / > gorn.americom.com:/ is: /dev/sda4 5.1G 4.3G 547M 89% / > > The other MISSING filesystems are also easily under 35G. Is amanda
Re: Problems getting client to work.
+ John R. Jackson <[EMAIL PROTECTED]> [07.04.02 20:24]: > >Of course... I've tried 2.4.2p2 too, with no luck. So I updated to the > >"bleeding-edge" version. > > OK. Just wanted to make sure you understood what you were running. I've downgraded to 2.4.2p2 again, since the beta did not work either. Another thing I did was touching /home/balu/.amanda.exclude, selfcheck ignored it, but the admin told me that it was listed as an ERROR in the amcheck mail... I've also redone the config, checked the amanda-user (who had /bin/false as shell for whatever reason) and all rights (I didn't have to change them though). And now it suddenly works. :-) Thanks for you suggestions Balu
SOS! problems with amrecover
Hello mailinglist, I have a strange problem with amrecover. This afternoon I have a presentation about amanda backup service and nothing works (murphy's task...) When I start amrecover as root, the following error occurs: shakira:/ # amrecover -C rtec -s shakira.r-tec.int -t shakira.r-tec.int -d /dev/nst0 AMRECOVER Version 2.4.2p2. Contacting server on shakira.r-tec.int ... 220 shakira AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-04-10) 200 Working date set to 2002-04-10. 200 Config set to rtec. 501 No index records for host: shakira. Invalid? <- !!! Trying shakira.r-tec.int ... 200 Dump host set to shakira.r-tec.int. Can't determine disk and mount point from $CWD amrecover> terrible. If I try to set the disk default by using setdisk /backup/client1 (client1 is the holding disk of a client) In this directory I find the data of the /etc-directory of this client1. Have a look what happens: amrecover> setdisk /backup/client1 501 No index records for disk: /backup/client1. Invalid? amrecover> The same error occurs if I only set the mountpoint /backup as disk, not /backup/client1 . It happens with all my holding disks. Can you imagine what's my problem? Please help me...I will really get in trouble if I fail my presentation... Thank you so much, best regards Leonie Nuenighoff
tapetype output and blocksize problems
Hi.
Waited till tapetype ran to the end (sorry for the impatience) - and got
the output below.
I have a few questions/problems.
1) it says it writes 32kb blocks - how can I make it write in 128kb
blocks (recommended block size (=filemark?) for Quantum DLT-7000)?
2) it says filemark 0 kbytes - howcome?
3) the speed mentioned here is only approx. 3mb/s - it's suppose to
handle more than that isn't it? - will this value change if I hit the
right filemark value (if filemark=block size that is)?
[root]# tapetype -f /dev/tape -e 35g
wrote 1238544 32Kb blocks in 108 files in 13999 seconds (short write)
wrote 1244278 32Kb blocks in 217 files in 14257 seconds (short write)
define tapetype unknown-tapetype {
comment "just produced by tapetype program"
length 38794 mbytes
filemark 0 kbytes
speed 2811 kps
}
--
Regards,
Klavs Klavsen
-| This mail has been sent to you by: |
Klavs Klavsen - OpenSource Consultant
[EMAIL PROTECTED] - http://www.vsen.dk
Get PGP key from www.keyserver.net - Key ID: 0x586D5BCA
Fingerprint = A95E B57B 3CE0 9131 9D15 94DA E1CD 641E 586D 5BCA
[ I believe that... ]---
It is a myth that people resist change. People resist what other
people make them do, not what they themselves choose to do...
That's why companies that innovate successfully year after year
seek their peopl's ideas, let them initiate new projects and
encourage more experiments.-- Rosabeth Moss Kanter
signature.asc
Description: This is a digitally signed message part
Re: [amanda@gorn.americom.com: AmeriCom AMANDA MAIL REPORT FOR April 9, 2002]
OK, I did: > grep [/_]idebigger amdump.1 setting up estimates for solo.americom.com:/idebigger solo.americom.com:/idebigger overdue 11782 days for level 0 setup_estimate: solo.americom.com:/idebigger: command 0, options: got result for host solo.americom.com disk /idebigger: 0 -> 8004440K, 2 -> 1278246K, 3 -> 223245K pondering solo.americom.com:/idebigger... next_level0 -11782 last_level 2 (due for level 0) (picking inclevel for degraded mode) solo.americom.com /idebigger pri 11783 lev 0 size 8004440 solo.americom.com /idebigger 11783 0 1970:1:1:0:0:0 8004440 1999 3 2002:4:2:13:4:16 223245 63 That's it! Apparently something is missing. What does it mean? > >Can anyone tell me what log/debug files to look in to find out why I > >keep getting the MISSING errors below, and what I should be looking for? > > Start with amdump.1 (the most recent amdump log file). It has a very > detailed log of everything that went on during the run. > > Pick one of your clients and disks to look for (I'd use "idebigger" since > it's unique). For the following I just grep'd amdump.1 for "[/_]data", > which happens to be a unique file system in one of my configs (I also > left out a couple of lines of no interest). In general you should see > a sequence of events something like this (mixed in with all the other > activity): > > # grep '[/_]data' amdump.1 > setting up estimates for fortress.cc.purdue.edu:/data > got result for host fortress.cc.purdue.edu disk /data: 0 -> 3349550K, 5 -> >2722448K, 6 -> 2717312K > fortress.cc.purdue.edu /data 1 5 2002:4:6:7:59:19 2722448 1995 > driver: send-cmd time 1261.520 to dumper4: FILE-DUMP 04-5 >/amanda/RCD/20020409/fortress.cc.purdue.edu._data.5 fortress.cc.purdue.edu /data 5 >2002:4:6:7:59:19 2048000 DUMP 2722560 |;bsd-auth;index; > driver: finished-cmd time 4526.310 dumper4 dumped fortress.cc.purdue.edu:/data > driver: send-cmd time 8077.002 to taper: FILE-WRITE 00-00689 >/amanda/RCD/20020409/fortress.cc.purdue.edu._data.5 fortress.cc.purdue.edu /data 5 >20020409 > driver: finished-cmd time 8953.699 taper wrote fortress.cc.purdue.edu:/data > > The first two lines are planner getting the estimate. The next line is > the schedule for driver. The next two lines are driver telling dumper4 > to do the backup into the holding disk (FILE-DUMP). The last two lines > are taper writing it to tape. > > The sequence is slightly different if the file system goes direct to tape. > > >Dick > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Re: [amanda@gorn.americom.com: AmeriCom AMANDA MAIL REPORT FOR April 9, 2002]
Thanks for your reply... However, the Ecrix V17 tapesize is set to 35000 mbytes and... Filesystem Size Used Avail Use% Mounted on solo.americom.com:/ is: /dev/sda3 7.9G 6.9G 632M 92% / gorn.americom.com:/ is: /dev/sda4 5.1G 4.3G 547M 89% / The other MISSING filesystems are also easily under 35G. Is amanda reporting what filesystems didn't fit for the given run? Thing is, it's the same filesystems missing each day and they don't seem to be getting backed up ever. Please advise further... > i suppose this will do it: > > > planner: Dump too big for tape: full dump of solo.americom.com:/ delayed. > > planner: Dump too big for tape: full dump of gorn.americom.com:/ delayed. > > a single backup point must be able to fit onto one tape. So if your tape > is 4gig, but your partition is 6 gig, then it wont do it. > > [EMAIL PROTECTED] wrote: > > > > Can anyone tell me what log/debug files to look in to find out why I > > keep getting the MISSING errors below, and what I should be looking for? > > > > The same filesystems are MISSING each day. > > > > Thanks, > > Dick > > > > --- Start of forwarded message --- > > Date: 9 Apr 2002 12:52:11 - > > From: [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > > Subject: AmeriCom AMANDA MAIL REPORT FOR April 9, 2002 > > > > *** THE DUMPS DID NOT FINISH PROPERLY! > > > > These dumps were to tape Daily4. > > The next tape Amanda expects to use is: Daily5. > > > > >
