RESULT! - (was Newbie help please with amdump error message)
Hi - especially Chris Marble and John Jackson... What a wonderful thing sleep is... Based on various suggestions, I forced amanda to use GNUTAR. Running amcheck again, it complained about a non-existant directory (gnutar-lists) which I created amdump worked! Thanks Chris / John for responding so quickly and so many times. Dirk
Re: amrestore problem
Hi! > > > root@fileserver:/usr/local/sbin > ./amrestore /dev/sg5 king > > /dev/sg5 is a changer. The tape device is /dev/nst0, and that's what > > amrestore wants. OK, i tested it with this commands: amanda@fileserver:~ > cd /usr/local/sbin/ amanda@fileserver:/usr/local/sbin > ./amrestore /dev/nst0 king amrestore: missing file header block amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of tape: date amanda@fileserver:/usr/local/sbin > HmWhat´s wrong? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amreport Problem
Am Dienstag, 20. Februar 2001 00:22 schrieben Sie: Hi! > If ./configure cannot find the right program (it looks for "Mail", > "mailx" and "mail"), you can set the "MAILER" environment variable to > a full path to a mail program that understands "-s user". > When you're done, run "amadmin xx version | grep MAIL" and see what > that says. It should point to the path Amanda will use. Hmafter typing this i see MAILER="/usr/sbin/sendmail" OK, can i change this without new compiling amanda? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: tweaking the schedule
> "John" == John R Jackson <[EMAIL PROTECTED]> writes: John> In effect, yes (surprised you, didn't I? :-). It takes the average rate Yes. :-) John> You can see those rates with "amadmin info " As I expected, I am averaging around 2KB/sec. Ben
Re: tapes used with chg-manual
>would it be possible to implement a configparameter saying: >no matter how many tapes have been used by the backup, mark all 4 >tapes in the drives as used, and search for the next backup after >the next 4 tapes? You can do this right now. All you have to do is write some code (I'd use Perl) to process the tapelist file. Just make sure all four tapes have the same timestamp (count how many have the most recent timestamp, then change entries with the oldest until you have four with the new). Test it with "amadmin tape". >Christoph John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: tweaking the schedule
>Wouldn't it be easer to (try and) change the code to use this priority >field also for normal operation ? Possibly. I've wondered why the value is not used for this as well. It would be disgustingly easy (which may or may not be a good thing :-) -- we just need to change the sort routine used when the list is read in driver, and adding priority as the primary key will only need a few lines of code. In other words, priority is tested first. Among entries with the same priority, it will do what it does now (fastest estimate first). BTW, did you know that in addition to low (0), medium (1) and high (2) as priority keywords, you can enter a number of your own? Just another bit of worthless trivia :-). >1) it would change existing functionality, and so people might need to > readjust there tapetypes/disklists It probably would not change things very much. I doubt many people use priority, so they most likely default to the same value and thus the sort would not be affected. Which is a good thing. >2) Someone needs to implement it ;) As I said, it will be very easy to do. However, it may not already be this way for a reason, so I'd like to hear other thoughts on it before going ahead. >Gerhard den Hollander Phone +31-10.280.1515 John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: HP C1553A and chio/pickers
>I notice: > > > chio params > /dev/ch0: 6 slots, 1 drive, 0 picker > /dev/ch0: current picker: 0 > >that it says it has no picker when I suspect it should say it has 1 picker. > >In the past I've worked around this by hacking libexec/chg-chio to ignore >this "situation". ... >Where is the "right" place to fix this? Ummm, since it's chio that's "broken", maybe that's the place to fix the problem? Or are you asking about how to make an "official workaround" :-) to Amanda? If so, just make your changes as clean as possible (i.e. so they don't break for someone else that does not have this problem) and post a context or unified diff, along with a ChangeLog entry and what version of Amanda you worked against. >H John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Newbie help please with amdump error message
Hi I've just installed amanda for the first time. A test amdump gives me the following report... FAILURE AND STRANGE DUMP SUMMARY: localhost/etc lev 0 FAILED [disk /etc offline on localhost?] Any light-shining would be appreciated thanks Dirk
Re: Newbie help please with amdump error message
>I've just installed amanda for the first time. A test amdump gives me the foll >owing report... > >FAILURE AND STRANGE DUMP SUMMARY: > localhost/etc lev 0 FAILED [disk /etc offline on localhost?] First, I suggest using the real host name rather than "localhost". You'll be much happier keeping things apart later. Did you run amcheck? Did it have anything to say? Are you using dump or GNU tar? Many versions of dump will not deal with subdirectories of a file system. If that's what you want to do, you may have to use GNU tar. >Dirk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problem with a Seagate tape drive
>ERROR taper no-tape [rewinding tape: Input/output error] >FAIL driver fserver /home/accounting 0 [can't switch to incremental dump] > >I'm not sure what this means ... Did you have any trouble when you ran amlabel on these tapes? Basically, Amanda is just reporting to you what the OS told it. You'll have to look at the system error logs and do other tests with the drive to find out why it (the OS kernel) is reporting an error. >The second problem and i'm not sure if this is related to the first ... It's not related. >FAIL planner fserver /home/fserver/contacts 0 [ disk /home/fserver/contacts of >fline on fserver? ] Does amcheck report any problems? What's in /tmp/amanda/sendsize*debug on fserver? >Trevor Linton John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Amtape not reqinding after a label lookup
>I checked the amidxtaped.debug, and I've figured out what the problem is. >After amtape is called with either the 'label ' or 'current' or any >other where it returns the amlabel of the tape, amtape does not rewind the >tape when it's finished reading the amlabel. >... Is there a way to have >amtape automatically do the rewind after an amlabel check? ... That's probably a reasonable idea. Give the following (2.4.2p1) patch a try and let me know if it works. It does a rewind for the "slot" and "label" commands in amtape, but none of the others. The patch is untested (other than getting a clean compile). > Jason Hollinden John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] (Run "e mhn" at "What now?", then $}base64 -d as needed and remove the Content-Transfer-Encoding line (leave it blank) and these lines.) amtape.diff
Re: tweaking the schedule
> "John" == John R Jackson <[EMAIL PROTECTED]> writes: John> Planner generates the list of what to do based on size, requests for John> special service (forced full dumps, etc) and so on. That's a text "file" John> with one line per disk piped into driver. Does the planner consider the bandwidth that the tape server has to each client? If the estimation says "50 MB" and the link is 14 kbps, then it should be started first. :-) Ben
Re: Tapetypes for Wangdat 3900 (Tecmar)
>These are tapetypes obtained with old 90-meter tapes and a new >125-meter tape purchased from Tecmar. Thanks. Would you mind adding those to the FAQ at www.amanda.org? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: slow backups
>I've been wrestling with some fairly slow backups for a while now. I >have amanda 2.4.2 server, running a dual 733 dell rack server, (256mb >ram, UW scsi disk) with a 3com 100mb switch stack. ... The first thing that always pops to mind when 100Mbit is involved is a duplex mismatch. If one side is full and the other half (where "side" may be a switch, not a host), really bad things occur. What happens if you do an ftp put of several MBytes from the client to /dev/null on the server? Are you seeing lots of errors with netstat? >the only thing I can >think of that is slowing the backup down is GNUtar on the SGI's >... >I also noticed a bug in the SGI sendsize, it's counting the number of >blocks, which are 512 bytes, not 1024, but reporting them as Kbytes. Huh? If you're using GNU tar, then the output is OS independent. We'd be seeing this on every system. What led you to believe there is a problem? If you run the command listed in /tmp/amanda/sendsize*debug, what does the output look like? What did sendsize return? >Ben Kochie John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Amrecover Problem in 2.4.2pl1
>i still have a prob with amrecover in 2.4.2pl1 >i never have this prob in previous version > >i run amanda server on a Sun sol 2.6 >... >but when i try amrecover on the server , to restore a file or dir >i always have : >... >error reading tape: Connection reset by peer Is there anything of interest in /tmp/amanda/amidxtaped*debug on the tape machine? What about in wherever inetd.conf logs things? You might check out this thread, especially if your machines have multiple network interfaces: http://groups.yahoo.com/group/amanda-users/message/27372 >patrick John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: file locking, 2.4.1 vs. 2.4.2
>It would probably be sufficient to add > >AC_CHECK_TYPE (ssize_t, int) > >in configure.in, right after we check for size_t. You would think so. But the code was actually wrong (not terribly, but the references I changed were unsigned so size_t would be fine), and sending a patch out for ./configure is, shall we say, problematic :-). Also, someone has added this test to the main branch, but it's very odd: pushdef([AC_DEFINE_SAVED],defn([AC_DEFINE])) pushdef([AC_DEFINE],[AC_DEFINE_SAVED([$1],[$2],[Define to $2 if $1 is not defined])]) AC_CHECK_TYPE(ssize_t, int) popdef([AC_DEFINE]) popdef([AC_DEFINE_SAVED]) Why is all that pushdef/popdef stuff in there? >Alexandre Oliva John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: questions on DLT7?
>Does anyone know if there is a problem using the DLT7 with amanda or >solaris 2.6 or if there are drivers for solaris 8? I don't know what a "DLT7" is, but on the assumption it's a DLT7000, they work fine at 2.6. I've got almost a dozen. Why? Are you having trouble? >Denyce John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Failure and strange dump summary
>when i run the "new" amcheck utility "/usr/local/sbin/amcheck " i got >the error: > >/usr/local/etc/amanda//amanda.conf", line 85: configuration keyword >expected >"/usr/local/etc/amanda//amanda.conf", line 85: end of line expected >"/usr/local/etc/amanda//amanda.conf", line 88: configuration keyword >expected >"/usr/local/etc/amanda//amanda.conf", line 88: end of line expected So what's on lines 85 and 88? >has the amanda.conf file syntax changed from previous versions of amanda ?? I don't think so. You need to look at the lines it doesn't like and compare them to amanda(8) and/or post them here. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Newbie help please with amdump error message
>The 'program' listed was DUMP so I added > >program 'GNUTAR' to my disklist ... >amadmin now says GNUTAR but the same error comes up in the report. Huh? Amdump still complains about /etc? Is amcheck still happy? What's in /tmp/amanda/sendsize*debug on the client? What version of GNU tar do you have? If it's 1.12, you need to apply the Amanda patches from the web page. If it's 1.13, you should be at 1.13.19 -- almost anything earlier has problems. >Dirk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: message: ...missing estimate on Red Hat Linux client from Iri x 6. 5 host
>nature of the problem is that sendsize failed because the linux client wants >to write in a file /etc/amandates, which was a directory on our system. The >error message never made it to amdump.1 log. I have an action item to make amcheck test for this. It keeps happening to people (for reasons I've never understood). >The fault was detected by running sendsize manually Or you could have looked at /tmp/amanda/sendsize*debug on the client. I should have thought to tell you to look there yesterday. >Gerrit Hommersom John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: tweaking the schedule
>Does the planner consider the bandwidth that the tape server has to >each client? ... In effect, yes (surprised you, didn't I? :-). It takes the average rate of the last three full or incrementals runs and computes the estimated time based on the estimated size. You can see those rates with "amadmin info " >If the estimation says "50 MB" and the link is 14 kbps, >then it should be started first. :-) FYI, it appears planner can't comprehend any client being that slow :-) and forces the average to be at least 30 KBytes/s (DEFAULT_DUMPRATE). Next we need to examine the driver algorithm in more detail. Some of the base information is in the usenix paper on the ftp.amanda.org site. There are two categories of dumpers, "little" and "big". The first three (LITTLE_DUMPERS in driver.c) dumpers from "inparallel" are assigned to "little" duty, everyone else is "big". Little dumpers pick entries from the head (shortest estimated time) of the queue. Big dumpers take entries from the end (longest estimated time) of the queue. You can see inparallel and how many big dumpers there are in the "driver: start time" line in amdump.. If inparallel is set to three (or less), you don't have any "big" dumpers and all the processing will happen from the front of the list. If inparallel is set to four, three dumpers will be picking off the little entries at the head of the list and one dumper will start at the end of the list and work its way backward. If inparallel is five, two dumpers will work from the end, and so on. Next (regardless of big or little) come a series of constraints that may cause a dumper to skip an entry and move on to the next (and possibly give up/go idle if nothing can be run): * The start time for the host or disk may not yet have been reached. (IDLE_START_WAIT) * The "interface" associated with the disk may be exhausted if this dump is started. (IDLE_NO_BANDWIDTH) * There may not be enough holding disk space. (IDLE_NO_DISKSPACE) * The disk may be marked to go direct to tape. (IDLE_NO_HOLD) * The client may already have maxdumps dumps running or there may already be a dump running on that spindle (as defined in disklist). (IDLE_CLIENT_CONSTRAINED) All of this is documented in excruciating detail in amdump.. Look for the "driver: state" lines that appear each time it runs through the list and see the driver-idle: string. So, you need to look at the list from planner and see where your problem clients show up based on the estimated time. Assuming they have high values and would be at the end of the list, look at inparallel and make sure you have some "big" dumpers. Then look through an amdump. file and see why driver is going idle and not running those dumps. >Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Newbie help please with amdump error message
Following another suggestion I had a few minutes ago, I ran
amadmin Daily disklist
The 'program' listed was DUMP so I added
program 'GNUTAR' to my disklist to give
xxx/etc{
nocomp-user
program "GNUTAR"
}
amadmin now says GNUTAR but the same error comes up in the report.
> My error, that doesn't tell you. I think Amanda defaults to dump if it can
> find it. On many systems dump can only work on filesystems but that's not
> true with the linux dump. What version of dump are you running?
> /sbin/dump --version
> will give an error message and the dump version. 0.4b21 is the latest and
> best. If you're running an older one I suggest getting the latest from
> www.sourceforge.net.
>
0.4b19 so I'll get the latest version
> Try specifying a partition to back up in your disklist file. /tmp should be quick
> if it exists.
back to work...
thanks
Dirk
Re: Newbie help please with amdump error message
Sorry about the etiquette.. I was expecting to converse via the mailing list but got a number of direct responses. nocomp-user program is set to DUMP Dirk - Original Message - From: "John R. Jackson" > In the future, you might want to respond to the whole list. They're used > to it :-). If I (or anyone else who tries to help) gets busy, it may > take longer to get a response. It also lets everyone know how resolution > of the problem is progressing. > > >> First, I suggest using the real host name rather than "localhost". > >> You'll be much happier keeping things apart later. > > > >I've tried that as well, got the same report. > > I didn't mean to imply this would fix the problem. It was a general > Amanda usage suggestion. > > >> Are you using dump or GNU tar? ... > > > >Not sure... I built amanda with all the defaults (RH7 and amanda 2.4.2p1). > >Is there an easy way to tell? > > What dumptype did you use in your disklist? > > If you run "amadmin disklist ", what is "program" > set to? > > >Dirk > > JJ >
Re: Amanda & MACs
Ben Kochie wrote: > > yes.. my fault.. i forgot all about dave.. I wish there were other > options for SMB on mac's, from what I've heard.. dave isn't the greatest > thing in the world. > > Yura Pismerov wrote: > > > > Ben Kochie wrote: > > > > > > macintosh clients have been discussed before, but as far as what I've > > > seen, the best way to keep mac files on an amanda backup schedual is to > > > keep the mac files on a unix based (linux+netatalk) fileserver > > > > BTW, there is SMB network implementation for Mac. > > As far as I remembere it is called Dave. > > I guess it would be possible to utilize smbclient to backup Macs. > > Not sure if Dave can create SMB shares though. > > You're going to lose a lot of filesystem information if you back up a Mac using Dave and SMB (the filetype/creator codes, custom icons, etc.). There is no very convenient way to use AMANDA with "classic" MacOS. It may be useful with OS X. If you're serious about backing up the Macs, I would recommend using Dantz Software's Retrospect (1). It's quite different from Amanda in it's approach to backup, but quite suitable for Macs. One strategy you could use to collect the Mac backup along with AMANDA would be to use Retrospect's "backup to an FTP server" feature, then back up the FTP server folder with AMANDA. Disclaimer: I don't work for Dantz, I'm just a satisfied customer (who uses AMANDA to back up all our linux and *nix boxes and Retrospect to back up the Macs) steven 1. http://www.dantz.com/
Re: Amanda & MACs
yes.. my fault.. i forgot all about dave.. I wish there were other options for SMB on mac's, from what I've heard.. dave isn't the greatest thing in the world. Yura Pismerov wrote: > > Ben Kochie wrote: > > > > macintosh clients have been discussed before, but as far as what I've > > seen, the best way to keep mac files on an amanda backup schedual is to > > keep the mac files on a unix based (linux+netatalk) fileserver > > BTW, there is SMB network implementation for Mac. > As far as I remembere it is called Dave. > I guess it would be possible to utilize smbclient to backup Macs. > Not sure if Dave can create SMB shares though. > > > > > > "F.M. Taylor" wrote: > > > > > > I know not of MAC, but have been asked "Can this new backup system backup > > > a MAC". Well, does anyone know the answer?? And if the answer is yes, by > > > what method can this be accomplished. > > > > > > --- > > > Mike Taylor > > > Coordinator of Systems Administration and Network Security > > > Indiana State University. Rankin Hall Rm 039 > > > 210 N 7th St. Terre Haute, IN. > > > Voice: 812-237-8843 47809 > > > --- > > > "You have zero privacy anyway. Get over it." > > >--Scott McNealy, Sun MicroSystems. > > > > -- > > Ben Kochie | [EMAIL PROTECTED] > > IMA Systems Office | 400 Lind Hall, 207 Church St. SE > > http://www.ima.umn.edu | Minneapolis, MN 55455-0463 > > -- > > Yuri Pismerov, TUCOWS.COM INC. (416) 535-0123 ext. 1352 -- Ben Kochie | [EMAIL PROTECTED] IMA Systems Office | 400 Lind Hall, 207 Church St. SE http://www.ima.umn.edu | Minneapolis, MN 55455-0463
Tapetypes for Wangdat 3900 (Tecmar)
These are tapetypes obtained with old 90-meter tapes and a new
125-meter tape purchased from Tecmar.
Cheers,
--
---
" Plus you have the wonderful narrative of how [Dubya] got where
he now is. It took his brother, his father, his father's
friends, the Florida secretary of state, and the Supreme Court
to pull it off. His entire life gives fresh meaning to the
phrase 'assisted living.'"
-- Gary Trudeau quoted in The New Yorker, Jan. 8, 2001
---
Victor R. Cain [EMAIL PROTECTED](865)482-2597
define tapetype WangDAT-3900A {
comment "produced by tapetype program - 90m tapes"
length 1900 mbytes
filemark 106 kbytes
speed 372 kbytes
}
define tapetype WangDAT-3900B {
comment "produced by tapetype program - 125m Tecmar tapes"
length 11650 mbytes
filemark 388 kbytes
speed 1138 kbytes
}
Re: Amanda & MACs
Ben Kochie wrote: > > macintosh clients have been discussed before, but as far as what I've > seen, the best way to keep mac files on an amanda backup schedual is to > keep the mac files on a unix based (linux+netatalk) fileserver BTW, there is SMB network implementation for Mac. As far as I remembere it is called Dave. I guess it would be possible to utilize smbclient to backup Macs. Not sure if Dave can create SMB shares though. > > "F.M. Taylor" wrote: > > > > I know not of MAC, but have been asked "Can this new backup system backup > > a MAC". Well, does anyone know the answer?? And if the answer is yes, by > > what method can this be accomplished. > > > > --- > > Mike Taylor > > Coordinator of Systems Administration and Network Security > > Indiana State University. Rankin Hall Rm 039 > > 210 N 7th St. Terre Haute, IN. > > Voice: 812-237-8843 47809 > > --- > > "You have zero privacy anyway. Get over it." > >--Scott McNealy, Sun MicroSystems. > > -- > Ben Kochie | [EMAIL PROTECTED] > IMA Systems Office | 400 Lind Hall, 207 Church St. SE > http://www.ima.umn.edu | Minneapolis, MN 55455-0463 -- Yuri Pismerov, TUCOWS.COM INC. (416) 535-0123 ext. 1352 S/MIME Cryptographic Signature
Intersting XFS bug.
This is for the archive, as well as anyone who cares, but I recently ran into an interesting XFS bug. xfs_db -r /dev/root xfs_db: sb 1 xfs_db: print uuid uuid = 9d44dc2e-9363-1024-8e23-080069124456 xfs_db: What you see above is a normal filesystem output. What I was seeing was amanda reporting xfsdump exiting on signal 1 for that filesystem. A support call to SGI and they pointed out my problem. There's a bug that SGI hasn't managed to reliably reproduce (and thusly squash) which causes uuid to be set to null on very rare occasion (this is the first time I've seen it in 5+ years dealing with XFS). You can run xfsdump with the -J flag and dump the filesystem, but the only real fix is the dump the filesystem, mkfs it, and restore the data. Running xfsdump on the command line returned no value at all that was reported. It just exited to the command line after it estimated the dumpsize for the filesystem in question. Using -J worked fine. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen <[EMAIL PROTECTED]>
Re: amrecover question
> I'm using amanda 2.4.2p1 on linux redhat7. So, I have a lot of > clients and when I try restore some "disk" I must to locate the tape > (using mt -f /dev/st0 fsf N) before use the amrecover . .that's correct > ? is there another way to do that ? First of all, you won't have much luck positioning the rewinding tape drive... ;-) Always use the non-rewinding device. (here it's /dev/nst0) You don't have to mt fsf to the file. It just saves you some time if you have lots of files on the tape.
Re: Amanda & MACs
Well, MacOS-X is UNIX (FreeBSD), so should probably wait for the upgrade :-) On Tue, 20 Feb 2001, Ben Kochie wrote: >macintosh clients have been discussed before, but as far as what I've >seen, the best way to keep mac files on an amanda backup schedual is to >keep the mac files on a unix based (linux+netatalk) fileserver > >"F.M. Taylor" wrote: >> >> I know not of MAC, but have been asked "Can this new backup system backup >> a MAC". Well, does anyone know the answer?? And if the answer is yes, by >> what method can this be accomplished. >> >> --- >> Mike Taylor >> Coordinator of Systems Administration and Network Security >> Indiana State University. Rankin Hall Rm 039 >> 210 N 7th St. Terre Haute, IN. >> Voice: 812-237-8843 47809 >> --- >> "You have zero privacy anyway. Get over it." >>--Scott McNealy, Sun MicroSystems. > >-- >Ben Kochie | [EMAIL PROTECTED] >IMA Systems Office | 400 Lind Hall, 207 Church St. SE >http://www.ima.umn.edu | Minneapolis, MN 55455-0463 >
unsubscribe
unsubscribe -- Tal Ovadia Jalan Network Services Inc. Phone: (818)-262-3895 --- Why Oh Why didn't I take the Blue Pill...
questions on DLT7?
Hi, Does anyone know if there is a problem using the DLT7 with amanda or solaris 2.6 or if there are drivers for solaris 8? Denyce
Problem with a Seagate tape drive
I have a SEAGATE DAT (DDS-3) tape backup drive, it holds around 1 gig of info, i'm having some errors with the amanda amdump First off, which I think is the largest error is in the /var/log/amanda/DailySet1/log.20010220.0, in which it gives this error message: ERROR taper no-tape [rewinding tape: Input/output error] FAIL driver fserver /home/accounting 0 [can't switch to incremental dump] I'm not sure what this means, the scsi device is terminated correctly, it's on id 4 with one other device on this (hard drive) on id 1, and id 4 does have a terminator on it. The type drive is being recognized by the SCSI driver, in /proc/scsi/scsi it's listed as Host: SCSI1 Channel: 00 Id: 04 Lun: 00 Vendor: ARCHIVE Model: Python 04106-XXX Rev: 7270 Type: Sequential-Access ANSI SCSI revision:02. Any Ideas? The second problem and i'm not sure if this is related to the first or not but in the same log file i have this error which is odd: FAIL planner fserver /home/fserver/contacts 0 [ disk /home/fserver/contacts offline on fserver? ] I have around 5 directories I need to backup, (no disks) in my disklist I have the following setup: fserver /home/fserver/accounting comp-high fserver /home/fserver/JobLog comp-high fserver /home/fserver/contacts comp-high fserver /home/fserver/WEBDEV comp-high fserver /home/accounting comp-high It has an error message in the log file for every one of those except for /home/accounting. I should note, that the user that's running amdump does have access to /dev/nst0. /dev/nst0 is a valid device and i've checked my configuration and if needed can post it here for overview. I'm not subscribed to this list so if you could please respond to my message by directly emailing me I would greatly appreciate it. -- Thanks Trevor Linton Applications Developer/System Administrator Vérité Multimedia Inc. http://www.verite.com DVD * CD * Web * Print * Film * Sound 801.553.1101 x 116 Fax: 801.553.1215 [EMAIL PROTECTED]
Amrecover Problem in 2.4.2pl1
Hi, i still have a prob with amrecover in 2.4.2pl1 i never have this prob in previous version i run amanda server on a Sun sol 2.6 with a exabyte Ez-17 all the backup works fine the restore with amrestore work too but when i try amrecover on the server , to restore a file or dir i always have : on the amrecover.debug log file == Started amidxtaped with arguments "6 -h -p /dev/rmt/1mn spoon ^c1t5d1s0$ 20010214" error reading tape: Connection reset by peer amrecover: pid 3439 finish time Tue Feb 20 12:53:32 2001 thanks a lot patrick --
Re: Failure and strange dump summary
Yop again!
i sucessfully upgraded to amanda 2.4.2
but my original path to the am* binaries changed from /usr/sbin to
/usr/local/sbin
so i copied my /etc/amanda/ files to /usr/local/etc/amanda/
when i run the "new" amcheck utility "/usr/local/sbin/amcheck " i got
the error:
/usr/local/etc/amanda//amanda.conf", line 85: configuration keyword
expected
"/usr/local/etc/amanda//amanda.conf", line 85: end of line expected
"/usr/local/etc/amanda//amanda.conf", line 88: configuration keyword
expected
"/usr/local/etc/amanda//amanda.conf", line 88: end of line expected
my question is :
has the amanda.conf file syntax changed from previous versions of amanda ??
my previus version was 2.4.2-19991216-beta1
- Original Message -
From: "Alexandre Oliva" <[EMAIL PROTECTED]>
To: "FFx" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 12:51 PM
Subject: Re: Failure and strange dump summary
> On Feb 20, 2001, "FFx" <[EMAIL PROTECTED]> wrote:
>
> > my exact version is : amanda 2.4.2-19991216-beta1
>
> Then yours pre-dates the patch. Time to upgrade :-)
>
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist*Please* write to mailing lists, not to me
>
Amtape not reqinding after a label lookup
I've found a message in teh archives (# 25664) that describes my problem, but it doesn't seem to be answered there. When doing an amrecover, I load a tape using 'amtape label ' which loads the tape fine, then this happens: Load tape SMGDR1-06 now Continue? [Y/n]: Y EOF, check amidxtaped.debug file on . amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 I checked the amidxtaped.debug, and I've figured out what the problem is. After amtape is called with either the 'label ' or 'current' or any other where it returns the amlabel of the tape, amtape does not rewind the tape when it's finished reading the amlabel. 'mt -f /dev/nst1 status' shows the tape like this for me: SCSI 2 tape drive: File number=0, block number=1, partition=0. Tape block size 0 bytes. Density code 0x41 (unknown to this mt). Soft error count since last status=0 General status bits on (101): ONLINE IM_REP_EN Which means that it's forwarded in to where the amlabel was read. If I do an 'mt -f /dev/nst0 rewind', the status will then look like this for me: SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 0 bytes. Density code 0x41 (unknown to this mt). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN If I do a manual rewind like that after amtape is finished doing it's business loading the appropriate tape, then amrecover works fine. Is there a way to have amtape automatically do the rewind after an amlabel check? If it's a matter of modifying amtape, I can give it a try, but I'm not great at C code. Thanks... -- Jason Hollinden SMG Systems Admin
slow backups
I've been wrestling with some fairly slow backups for a while now. I
have amanda 2.4.2 server, running a dual 733 dell rack server, (256mb
ram, UW scsi disk) with a 3com 100mb switch stack. the network is far
from saturated.
the only thing that gets me are the clients.. I have 3 SGI's, a
challange-S, an O-200, and an O2. I also have a PII-450 netBSD
machine. all run extremely slow.
as far as I can tell from my MRTG graphs.. no single backup process will
exceed 100KB/sec, most run around 50KB/sec
here are some of my config lines...
amanda.conf
inparallel 12
maxdumps 5
netusage 100 Mbps
define dumptype ima-ss-comp-high-tar {
high-tar
compress server fast
exclude list "/usr/local/amanda/etc/amanda/Test/excludes"
}
define interface eth0 {
comment "100 Mbps ethernet"
use 100 Mbps
}
define interface local {
comment "a local disk"
use 50 mbps
}
-- disklist ---
fs0 /home ima-ss-comp-user-tar1
eth0
fs0 /varsityima-ss-comp-user-tar2
eth0
fs0 /share ima-ss-comp-user-tar3
eth0
fs0 /sgiexport ima-ss-comp-user-tar4
eth0
fs0 /user01 ima-ss-comp-high-tar7
eth0
fs0 /user06 ima-ss-comp-high-tar7
eth0
fs0 /user03 ima-ss-comp-high-tar7
eth0
fs0 /user02 ima-ss-comp-high-tar8
eth0
there are aprox 30 filesystems in the list. and the only thing I can
think of that is slowing the backup down is GNUtar on the SGI's but it
affects the netBSD system as well.
I also noticed a bug in the SGI sendsize, it's counting the number of
blocks, which are 512 bytes, not 1024, but reporting them as Kbytes.
here's an amstatus durring one of the slow backups
Using /var/log/amanda/Test/amdump from Tue Feb 20 01:35:01 CST 2001
fs0:/home1 32k finished (2:27:04)
fs0:/linuxexport 2 224k finished (2:28:52)
fs0:/math1 0 1581856k finished (9:04:42)
fs0:/math2 1 32k finished (2:27:17)
fs0:/sgiexport 0 886048k finished (6:53:37)
fs0:/share 1 320k finished (2:32:22)
fs0:/software11088k finished (2:42:03)
fs0:/user01 0 913064k dumping 332096k (
36.37%) (8:32:10)
fs0:/user02 1 12096k finished (9:10:24)
fs0:/user03 23904k finished (8:35:41)
fs0:/user06 0 1631872k finished (8:35:36)
fs0:/user07 0 1451136k finished (9:10:17)
fs0:/user08 15248k finished (9:17:34)
fs0:/user10 11216k finished (2:46:54)
fs0:/varsity 2 64k finished (2:27:39)
gold:/user20 1 [/usr/local/bin/gtar returned
2] (2:37:31)
gold:/user35 0 [/usr/local/bin/gtar got
signal 13] (2:33:53)
i5:/TeX 1 224k finished (2:28:04)
i5:/syscom 1 224k finished (2:29:27)
mail:/export 0 no estimate
www:/dev/wd0e1 84768k finished (5:32:29)
www:/usr 1 10560k finished (5:41:42)
www:/web 0 4086656k finished (5:23:39)
SUMMARY part real estimated
size size
partition : 23
estimated : 22 14888599k
failed : 34262655k ( 28.63%)
wait for dumping: 0 0k ( 0.00%)
dumping to tape : 0 0k ( 0.00%)
dumping : 1 332096k 913064k ( 36.37%) ( 2.23%)
dumped : 19 9757568k 9712880k (100.46%) ( 65.54%)
wait for writing: 00k0k ( 0.00%) ( 0.00%)
writing to tape : 00k0k ( 0.00%) ( 0.00%)
failed to tape : 00k0k ( 0.00%) ( 0.00%)
taped : 19 9757568k 9712880k (100.46%) ( 65.54%)
11 dumpers idle : not-idle
taper idle
network free kps: 255922
holding space : 29273332k ( 96.97%)
dumper0 busy : 5:10:54 ( 75.72%)
dumper1 busy : 0:50:01 ( 12.18%)
dumper2 busy : 0:10:33 ( 2.57%)
dumper3 busy : 2:41:15 ( 39.27%)
dumper4 busy : 0:06:41 ( 1.63%)
dumper5 busy : 6:01:59 ( 88.16%)
dumper6 busy : 6:35:23 ( 96.29%)
dumper7 busy : 6:30:20 ( 95.07%)
dumper8 busy : 0:18:09 ( 4.42%)
taper busy : 0:37:35 ( 9.16%)
0 dumpers busy : 0:00:00 ( 0.00%)
1 dumper busy : 0:00:03 ( 0.01%)not-idle: 0:00:03
(100.00%)
2 dum
Re: Amanda & MACs
macintosh clients have been discussed before, but as far as what I've seen, the best way to keep mac files on an amanda backup schedual is to keep the mac files on a unix based (linux+netatalk) fileserver "F.M. Taylor" wrote: > > I know not of MAC, but have been asked "Can this new backup system backup > a MAC". Well, does anyone know the answer?? And if the answer is yes, by > what method can this be accomplished. > > --- > Mike Taylor > Coordinator of Systems Administration and Network Security > Indiana State University. Rankin Hall Rm 039 > 210 N 7th St. Terre Haute, IN. > Voice: 812-237-8843 47809 > --- > "You have zero privacy anyway. Get over it." >--Scott McNealy, Sun MicroSystems. -- Ben Kochie | [EMAIL PROTECTED] IMA Systems Office | 400 Lind Hall, 207 Church St. SE http://www.ima.umn.edu | Minneapolis, MN 55455-0463
Amanda & MACs
I know not of MAC, but have been asked "Can this new backup system backup a MAC". Well, does anyone know the answer?? And if the answer is yes, by what method can this be accomplished. --- Mike Taylor Coordinator of Systems Administration and Network Security Indiana State University. Rankin Hall Rm 039 210 N 7th St. Terre Haute, IN. Voice: 812-237-8843 47809 --- "You have zero privacy anyway. Get over it." --Scott McNealy, Sun MicroSystems.
amrecover question
Hi, I'm using amanda 2.4.2p1 on linux redhat7. So, I have a lot of clients and when I try restore some "disk" I must to locate the tape (using mt -f /dev/st0 fsf N) before use the amrecover . .that's correct ? is there another way to do that ? Sergio
Re: Problems with amanda 2.4.2p1
On Feb 20, 2001, Patrick LIN <[EMAIL PROTECTED]> wrote:
> can i know where i can find gnu tar 1.3.19
See docs/INSTALL in 2.4.2p1
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: cruft directory
* Alexandre Oliva <[EMAIL PROTECTED]> (Tue, Feb 20, 2001 at 10:47:26AM -0300) > On Feb 20, 2001, Erik van der Meulen <[EMAIL PROTECTED]> wrote: > >> lost+found: skipping cruft directory, perhaps you should delete it. >> Not sure what to do with thing (English not being my first language...) >> Any suggestions? > Either learn to ignore this message or create a directory in /dump and > use it as the holding disk. If I understand it correctly, amflush looks in /dump for amanda dump directories, and finds one that is not an amanda dir (lost+found) and tells you this. cruft is amflush's name for unknown dirs. As Alexandre suggests, make a subdir under /dump (/dump/amanda or /dump/amanda/YOURCONFIGNAME) that way you won;t get that message. Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O All things (e.g. a camel's journey through =`\<, A needle's eye) are possible, it's true. (=)/(=) But picture how the camel feels, squeezed out In one long bloody thread, from tail to snout.
AW: SCSI-Error with Onstream ADR50i while amdump
> > The AHA2940U2W is connected via the LVD/SE adaptor to the ADR50i. > > At the end of the cable sits a LVD-Terminator. Before this > > terminator there is the Tape-Device. > > > > I just changed the automatic termination from the AHA2940U2W-BIOS to > > enabled and doing some "stress-test". > > Ok, now what are the tech-specs of that ADR50i drive ? > Is it known to be a LVD/SE device ? If not, you should > connect it to the Fast/Ultra bus.. > -- >Rémy Chibois > ADR50i supports LVD/SE. With this combinations it only supports 40MB/s and not 80MB/s. -- Christian Weiss
Re: Problems with amanda 2.4.2p1
Alexandre Oliva a écrit : > > On Feb 17, 2001, Mike Hendrix <[EMAIL PROTECTED]> wrote: > > > I recently upgraded a system and also upgraded amanda also. On the old > > system using amanda 2.4.1p1 I had added the -DIGNORE_TAR_ERRORS so that > > amanda would not toss a good backup just because of a missing file > > Instead of ignoring all tar errors altogether, I'd recommend using GNU > tar 1.13.19, that fixes the bug that would cause certain unimportant > errors to result in a non-zero exit status. > hi, JUst one question can i know where i can find gnu tar 1.3.19 i cannot find it anywhere thanks patrick
Re: SCSI-Error with Onstream ADR50i while amdump
> The AHA2940U2W is connected via the LVD/SE adaptor to the ADR50i. > At the end of the cable sits a LVD-Terminator. Before this > terminator there is the Tape-Device. > > I just changed the automatic termination from the AHA2940U2W-BIOS to > enabled and doing some "stress-test". Ok, now what are the tech-specs of that ADR50i drive ? Is it known to be a LVD/SE device ? If not, you should connect it to the Fast/Ultra bus.. -- Rémy Chibois
Re: cruft directory
On Feb 20, 2001, Erik van der Meulen <[EMAIL PROTECTED]> wrote:
> lost+found: skipping cruft directory, perhaps you should delete it.
> Not sure what to do with thing (English not being my first language...)
> Any suggestions?
Either learn to ignore this message or create a directory in /dump and
use it as the holding disk.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
cruft directory
Hi, I have just upgraded from amanda 2.4.1 to 2.4.2. After an amflush I received the following warning: Scanning /dump... lost+found: skipping cruft directory, perhaps you should delete it. Could not find any Amanda directories to flush. Not sure what to do with thing (English not being my first language...) Any suggestions? -- Erik van der Meulen <[EMAIL PROTECTED]>
Re: SCSI-Error with Onstream ADR50i while amdump
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> (Tue, Feb 20, 2001 at 01:27:25PM +0100) >>> Adapter is an AHA2940U2W, only internaly connected to the ADR50i. >>> So cable length ca. 30cm. - SCSI cabling and terminator are OK. >> Ok, now if I remember, this adapter has 2 buses (1 Fast/Ultra >> and 1 LVD/SE) and >> 4 connectors, 3 internal et 1 external. How is the ADR50i >> connected to the board. >> Sorry to ask those "stupid" questions, but cabling IS really >> important. >> Are there any other SCSI devices on any of the buses ? > The AHA2940U2W is connected via the LVD/SE adaptor to the ADR50i. > At the end of the cable sits a LVD-Terminator. Before this > terminator there is the Tape-Device. Is the tapedrive auto-terminating ? Is the tapedrive indeed detected as doing LVD Xfer rates, iso doing UW ? Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O Some say the end is near. =`\<, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
AW: SCSI-Error with Onstream ADR50i while amdump
> > Adapter is an AHA2940U2W, only internaly connected to the ADR50i. > > So cable length ca. 30cm. - SCSI cabling and terminator are OK. > > > Ok, now if I remember, this adapter has 2 buses (1 Fast/Ultra > and 1 LVD/SE) and > 4 connectors, 3 internal et 1 external. How is the ADR50i > connected to the board. > > Sorry to ask those "stupid" questions, but cabling IS really > important. > Are there any other SCSI devices on any of the buses ? > -- >Rémy Chibois > The AHA2940U2W is connected via the LVD/SE adaptor to the ADR50i. At the end of the cable sits a LVD-Terminator. Before this terminator there is the Tape-Device. I just changed the automatic termination from the AHA2940U2W-BIOS to enabled and doing some "stress-test". I'm sorry for not delivering all the facts! I'm more a software-developer then a hardware-professional. ;) -- Christian Weiss
Re: SCSI-Error with Onstream ADR50i while amdump
> Adapter is an AHA2940U2W, only internaly connected to the ADR50i. > So cable length ca. 30cm. - SCSI cabling and terminator are OK. > Ok, now if I remember, this adapter has 2 buses (1 Fast/Ultra and 1 LVD/SE) and 4 connectors, 3 internal et 1 external. How is the ADR50i connected to the board. Sorry to ask those "stupid" questions, but cabling IS really important. Are there any other SCSI devices on any of the buses ? -- Rémy Chibois
AW: SCSI-Error with Onstream ADR50i while amdump
> > ---/var/log/messages---
> > Feb 20 04:19:39 fordprefect kernel: scsi : aborting command
> due to timeout :
> > pid 1653712, scsi0, channel 0, id 2, lun 0 Write (6) 01 00 00 40 00
> > Feb 20 04:19:41 fordprefect kernel: SCSI host 0 abort (pid
> 1653712) timed
> > out - resetting
> > Feb 20 04:19:41 fordprefect kernel: SCSI bus is being reset
> for host 0
> > channel 0.
> > Feb 20 04:19:44 fordprefect kernel: (scsi0:0:2:0)
> Synchronous at 40.0
> > Mbyte/sec, offset 8.
> > Feb 20 04:19:44 fordprefect kernel: st0: Error with sense
> data: [valid=0]
> > Info fld=0x0, Current st09:00: sense key Unit Attention
> > Feb 20 04:19:44 fordprefect kernel: Additional sense
> indicates Power on,
> > reset, or bus device reset occurred
> > ---/var/log/messages---
> >
> > Does someone know, how to fix?
>
> You should check SCSI cabling and terminators..
> Can you describe your SCSI setup (cable length, adapters,
> internal/external
> devices, ...) ?
> --
>Rémy Chibois
>
Adapter is an AHA2940U2W, only internaly connected to the ADR50i.
So cable length ca. 30cm. - SCSI cabling and terminator are OK.
---mt status---
drive type = Generic SCSI-2 tape
drive status = 512
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 512 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
---mt status---
The ADR50-Device is configured as follows:
---amanda.conf---
define tapetype ADR50 {
comment "ADR50 tape drives"
length 5 mbytes# 50 Gig tapes
filemark 2000 kbytes # I don't know what this means
speed 14336 kbytes # 14 MB/s
}
---amanda.conf---
Re: Failure and strange dump summary
On Feb 20, 2001, "FFx" <[EMAIL PROTECTED]> wrote:
> my exact version is : amanda 2.4.2-19991216-beta1
Then yours pre-dates the patch. Time to upgrade :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Failure and strange dump summary
my exact version is : amanda 2.4.2-19991216-beta1
- Original Message -
From: "Alexandre Oliva" <[EMAIL PROTECTED]>
To: "FFx" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 11:23 AM
Subject: Re: Failure and strange dump summary
> On Feb 20, 2001, "FFx" <[EMAIL PROTECTED]> wrote:
>
> > ? gtar: ./dev/log: socket ignored
>
> Are you sure the client is running Amanda 2.4.2? The patch that
> ignored this message went in on May 28 last year.
>
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist*Please* write to mailing lists, not to me
>
RE: message: ...missing estimate on Red Hat Linux client from Iri x 6. 5 host
nature of the problem is that sendsize failed because the linux client wants to write in a file /etc/amandates, which was a directory on our system. The error message never made it to amdump.1 log. The fault was detected by running sendsize manually Gerrit Hommersom > >>>When introducing the Linux system in the scheme, the backup >fails in the >>>planning stage with the following message. >> >>What does "amcheck -cl " have to say? >> >amcheck -cl does not reveal anomalies as the following log shows: the >missing curinfo and index files are because this machine was >never backed up >under amanda. > >../prog/amanda> amcheck -cl Tape-2 >Amanda Tape Server Host Check >- >Holding disk /disk5/amanda: 9947964 KB disk space available, >that's plenty >NOTE: skipping tape checks >NOTE: info dir amanda/Tape-2/curinfo/linux1.aaa.aaa.aaa: >does not exist >NOTE: index dir amanda/Tape-2/index/linux1.aaa.aaa.aaa: >does not exist >Server check took 0.009 seconds > >Amanda Backup Client Hosts Check > >Client check: 2 hosts checked in 0.090 seconds, 0 problems found > >(brought to you by Amanda 2.4.2) >Gerrit Hommersom >> >>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >> >
Re: Failure and strange dump summary
On Feb 20, 2001, "FFx" <[EMAIL PROTECTED]> wrote:
> ? gtar: ./dev/log: socket ignored
Are you sure the client is running Amanda 2.4.2? The patch that
ignored this message went in on May 28 last year.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: file locking, 2.4.1 vs. 2.4.2
On Feb 20, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
> This appears to be caused by someone getting a little too enthusiastic
> with ssize_t (signed size type), which apparently your OS does not
> provide, at least in the normal include files.
It would probably be sufficient to add
AC_CHECK_TYPE (ssize_t, int)
in configure.in, right after we check for size_t.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
tapes used with chg-manual
Hi, I'm thinking if i'm the only one who has met the following situation: a customer of us has a server with amanda and 4 DDS-2 drives. They have a bit an unusual backupprocedure for amanda: every friday they do a fullbackup to 120meter (2GB native) tapes, rotating through 4 sets of 4 tapes for every week of a month, over the week only incrementals to 90meter (1GB native)tapes are done, one tape used per day. for archiv use over the year they do every last friday of the month a fullbackup to 4 tapes, storing them for ever ( a few years at least ). at the moment they fulls for the weekly backups only take about 2 and a half tape, but du to the expected growth of the data-volume to backup and the lazines of the operators, they want to stick in 4 tapes every friday, without having to search for the needed tapes. Now my question: would it be possible to implement a configparameter saying: no matter how many tapes have been used by the backup, mark all 4 tapes in the drives as used, and search for the next backup after the next 4 tapes? if this could be done, how much work would it be? Christoph
Re: SCSI-Error with Onstream ADR50i while amdump
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> (Tue, Feb 20, 2001 at 09:28:20AM +0100) > I'm using Amanda-2.4.1p1 with SuSE Linux 7.0 (Kernel 2.2.16) and a Onstream > ADR50i SCSI Device (latest Firmware 2.33). > Following error occured while amdump, showing by amcheck Daily: > > /var/log/messages says: > ---/var/log/messages--- > Feb 20 04:19:39 fordprefect kernel: scsi : aborting command due to timeout : > pid 1653712, scsi0, channel 0, id 2, lun 0 Write (6) 01 00 00 40 00 > Feb 20 04:19:41 fordprefect kernel: SCSI host 0 abort (pid 1653712) timed > out - resetting > Feb 20 04:19:41 fordprefect kernel: SCSI bus is being reset for host 0 > channel 0. > Feb 20 04:19:44 fordprefect kernel: (scsi0:0:2:0) Synchronous at 40.0 > Mbyte/sec, offset 8. > Feb 20 04:19:44 fordprefect kernel: st0: Error with sense data: [valid=0] > Info fld=0x0, Current st09:00: sense key Unit Attention > Feb 20 04:19:44 fordprefect kernel: Additional sense indicates Power on, > reset, or bus device reset occurred > ---/var/log/messages--- > Does someone know, how to fix? SCSI - errors: 1) check termination. 2) check cables. 3) recheck termination. 4) check cable length. 5) check drivers. 6) check termination. 7) check hardware (disk/tape) 8) check if all hardware on the chain is indeed reporting correct Xfer speeds. [1] [1] If you have a chain where a wide scsi device is connected to a wide scsi capable PC card, through a narrow scsi cable make sure it expects narrow scsi Xfer rates (some devices negotiate wide scsi in this situation, because they don;t see there's only a narrow cable in between. Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\<, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: tweaking the schedule
* John R. Jackson <[EMAIL PROTECTED]> (Mon, Feb 19, 2001 at 07:39:49PM -0500)
>>I have a couple of machines that are slow and poorly connected to my
>>tape server. In every instance, I happen to *know* that if these
>>machines were to appear first in the backup schedule, the backup would
>>finish more quickly.
>>Is there a way I can push them to the front?
> That's harder than you might think.
When I asked the same question, people suggested to stick a starttime entry
in the dumptypes for the backups I wanted to run later.
e.g. you're using comp-user-tar
and you have your backup starting at 20:00 (and you know you're estimate
phase doesn't take longer than 45 minutes)
make a new tapetype
define comp-user-tar-delayed {
comp-user-tar
starttime 2100
}
and change disklist accordingly
myhost disk1 comp-user-tar-delayed
myhost disk2 comp-user-tar-delayed
myslowhow disk1 comp-user-tar
> fortress.cc.purdue.edu / 1 \
> 0 1970:1:1:0:0:0 597618 182 \
> 1 2001:2:12:4:43:9 24681 35
> The first three fields say this is a dump of "/" on fortress.cc and
> if we have to drop into degraded mode, the priority should be "1".
> Note that "priority" is only used in degraded mode -- don't get your
> hopes up for an easy fix :-).
Wouldn't it be easer to (try and) change the code to use this priority
field also for normal operation ?
There are of course 2 problems with that:
1) it would change existing functionality, and so people might need to
readjust there tapetypes/disklists
2) Someone needs to implement it ;)
Kind regards,
--
Gerhard den Hollander Phone +31-10.280.1515
Technical Support Jason Geosystems BV Fax +31-10.280.1511
(When calling please note: we are in GMT+1)
[EMAIL PROTECTED] POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam
JASON...#1 in Reservoir CharacterizationThe Netherlands
This e-mail and any attachment is/are intended solely for the named
addressee(s) and may contain information that is confidential and privileged.
If you are not the intended recipient, we request that you do not
disseminate, forward, distribute or copy this e-mail message.
If you have received this e-mail message in error, please notify us
immediately by telephone and destroy the original message.
Re: SCSI-Error with Onstream ADR50i while amdump
> ---/var/log/messages--- > Feb 20 04:19:39 fordprefect kernel: scsi : aborting command due to timeout : > pid 1653712, scsi0, channel 0, id 2, lun 0 Write (6) 01 00 00 40 00 > Feb 20 04:19:41 fordprefect kernel: SCSI host 0 abort (pid 1653712) timed > out - resetting > Feb 20 04:19:41 fordprefect kernel: SCSI bus is being reset for host 0 > channel 0. > Feb 20 04:19:44 fordprefect kernel: (scsi0:0:2:0) Synchronous at 40.0 > Mbyte/sec, offset 8. > Feb 20 04:19:44 fordprefect kernel: st0: Error with sense data: [valid=0] > Info fld=0x0, Current st09:00: sense key Unit Attention > Feb 20 04:19:44 fordprefect kernel: Additional sense indicates Power on, > reset, or bus device reset occurred > ---/var/log/messages--- > > Does someone know, how to fix? You should check SCSI cabling and terminators.. Can you describe your SCSI setup (cable length, adapters, internal/external devices, ...) ? -- Rémy Chibois
SCSI-Error with Onstream ADR50i while amdump
Hi, I'm using Amanda-2.4.1p1 with SuSE Linux 7.0 (Kernel 2.2.16) and a Onstream ADR50i SCSI Device (latest Firmware 2.33). Following error occured while amdump, showing by amcheck Daily: ---amcheck Daily--- *** A TAPE ERROR OCCURRED: [[writing file: Input/output error]]. *** PERFORMED ALL DUMPS TO HOLDING DISK. THESE DUMPS WERE TO DISK. Flush them onto tape DailySet102 or a new tape. Tonight's dumps should go onto 1 tape: DailySet103. FAILURE AND STRANGE DUMP SUMMARY: pindar /opt4/iplanet4.1 lev 0 FAILED [data timeout] pindar /opt/app/oracle lev 0 FAILED [out of tape] taper: FATAL syncpipe_get: w: unexpected EOF /-- pindar /opt4/iplanet4.1 lev 0 FAILED [data timeout] sendbackup: start [pindar:/opt4/iplanet4.1 level 0] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/local/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? ? gzip: stdout: Broken pipe ? sendbackup: index tee cannot write [Broken pipe] sendbackup: error [/usr/local/bin/tar got signal 13, index returned 1, compress returned 1] ---amcheck Daily--- /var/log/messages says: ---/var/log/messages--- Feb 20 04:19:39 fordprefect kernel: scsi : aborting command due to timeout : pid 1653712, scsi0, channel 0, id 2, lun 0 Write (6) 01 00 00 40 00 Feb 20 04:19:41 fordprefect kernel: SCSI host 0 abort (pid 1653712) timed out - resetting Feb 20 04:19:41 fordprefect kernel: SCSI bus is being reset for host 0 channel 0. Feb 20 04:19:44 fordprefect kernel: (scsi0:0:2:0) Synchronous at 40.0 Mbyte/sec, offset 8. Feb 20 04:19:44 fordprefect kernel: st0: Error with sense data: [valid=0] Info fld=0x0, Current st09:00: sense key Unit Attention Feb 20 04:19:44 fordprefect kernel: Additional sense indicates Power on, reset, or bus device reset occurred ---/var/log/messages--- Does someone know, how to fix? Christian Weiss Mobile Applications Central Services Business Unit Communications MATERNA Information & Communications Voßkuhle 37, 44141 Dortmund, Germany www.materna.de - www.annyway.com Phone: +49 (0) 231 / 5599-8341 PC-Fax: +49 (0) 231 / 5599-678341 eMail: [EMAIL PROTECTED]
