Re: Ran a Tapetype for LTO-3 if anyone is interested
I am unsure why my tape is half the speed but almost 40 gigs more than the
others in the Amanda Wiki. My tapes are Imation Ultrium LTO 3 tapes. Maybe
they are a little longer?
Amtapetype was executred with the device /dev/st0, I do not think this
would make a difference, or can it? Also SCSI generic support was not
available at the time.
Now that I have everything from the barcode reader working to the tapes
labeled, I will run the tapetype again. I also have SCSI generic enabled
and plan to run tapetype with the /dev/nst0 device.
I will cut and paste the complete console message after the job is
complete if it comes out different. I will use the same tape that I used
to run the original tapetype too.
After all, I too am wondering why I got more space but half the speed. I'd
rather have the reverse.
Tano
On Wed, July 12, 2006 12:18 am, Paul Bijnens wrote:
On 2006-07-11 19:46, Tanniel Simonian wrote:
Amanda Group
I ran the amtapetype from Amanda 2.5.0p2 last night, took about 6 hours
to
complete the estimate:
Model: Quantum Superload 3 LTO-3 16 Tape Library.
define tapetype QS3LTO-3 {
comment Quantum Super Loader 3 LTO-3 16 tape library
length 448369 mbytes
filemark 6403 kbytes
speed 37739 kps
}
I ran amtapetype on /dev/st0 on a debian Testing distribution.
SCSI interface VHDI 68 Pin Ultra 160 connector running on a Adaptec
39160
2 channel SCSI 160 PCI-X interface. Server DELL PE 850 Dual Core P4 3.4
GHZ 4 GB RAM
Wow. You got 440 Gbyte on a 400 Gbyte tape???
But your speed is about half what others got...
Compare this to:
http://wiki.zmanda.com/index.php/Tapetype_definitions#LTO_Ultrium_3_with_400.2F800_Gbyte_tapes
I'm curious about the cause these significant differences!
(Not owning an LTO3 -- just curious.)
--
Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Feeling lazy, do I have to upgrade to 2.5.0p2?
Amanda group, I recently purchased the new Quantum LTO-3 library. I also purchased a server that unfortunately works initially with Debian's Testing installation which defaults to 2.5.0p2 of Amanda-server/client. I can communicate with the 20 amanda-clients on 2.4.4 with the amanda-server 2.5.0p2 amcheck, heck I am even able to dump/tar. I've had many successful test backups so far, but don't want to be surprised with a weird problem later on. I quickly glanced at the documentation for incompatibility issues 2.4.4 vs 2.5.0p2, but found none. Thanks!
Ran a Tapetype for LTO-3 if anyone is interested
Amanda Group
I ran the amtapetype from Amanda 2.5.0p2 last night, took about 6 hours to
complete the estimate:
Model: Quantum Superload 3 LTO-3 16 Tape Library.
define tapetype QS3LTO-3 {
comment Quantum Super Loader 3 LTO-3 16 tape library
length 448369 mbytes
filemark 6403 kbytes
speed 37739 kps
}
I ran amtapetype on /dev/st0 on a debian Testing distribution.
SCSI interface VHDI 68 Pin Ultra 160 connector running on a Adaptec 39160
2 channel SCSI 160 PCI-X interface. Server DELL PE 850 Dual Core P4 3.4
GHZ 4 GB RAM
Tanniel
On Tue, May 23, 2006 2:40 pm, Jon LaBadie wrote:
On Tue, May 23, 2006 at 01:22:02PM -0700, Pavel Pragin wrote:
Brian Cuttler wrote:
Does anyone have the tape type for the LTO3 (Quantum) ?
Are there any other parameters I should tweak to get better
performance/utilization ?
This is still a reasonable default ?
tapebufs 20
I am running the StorEdge C2 jukebox with lto3 drive on a SunFire 280R
under Solaris 9 with 4 gig of memory.
Try using this command to determine tapetype:
amtapetype -f /dev/nst0 (/dev/nst0) will be diff for solaris i think
A tapetype run on an lto-3 drive without a good estimate option
might take about 14 days to complete :(
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Any experience with Quantum Superloader 3 LTO-3 16 tape library?
We are looking into purchasing a new tape library. Our current choice is an Overland 11 tape LTO-3 library. However, the Quantum Superloader 3 option recently fell on our laps and we're trying to decide if it is reliable and if it will work with Amanda/Debian. Anyone have any experience with the Quantum Superloader 3 or similar Quantum product and if you could describe your experience with the unit. Our current tape hardware is an Exabyte 1x7 Mammoth 2 (60/150) drives. regards, Tano
Question about Amcheck and it's ability to cross physical networks?
Hi, A few weeks ago I had asked whether Amanda can run primarily on TCP. I am unsure whether I was able to describe my problem in great detail. I'll try again.. To make this short, I am trying to backup a few servers outside my physical network and get an error of Host down when Amcheck is performed. If I put the servers back on my physical network all is well and configured properly. The set up goes like this: The servers are in a Library at a University Campus. I want to backup servers in another department located outside the Library's physical network. There are two routers between the Library (Amanda server site) and the X department (client amanda sites). There are no firewalls in place in between the routers, host firewalls, or ACLs on the routers to prevent communication between the Library and X department. The routers are Cisco series 6500s, the machines are Dells and Custom built servers. The connection between the two departments is at 1 gigabit with very little network utilization ~4 to 5%. The amanda clients are configured properly. The amanda server is configured correctly as well and everything works when the machines are on the same physical network. The problem is when they are are different networks. Is there a problem with Amanda crossing physical networks? I know Amanda uses UDP to create an initial check, but I also know that UDP should cross networks, unless it's being dropped since the packet size is too small or has low priority?? Any comments regarding whether you use amanda across physical networks would be greatly appreciated. Also a sample configuration would be appreciated. Tano
Re: Amrecover: No index records for disk for specified date: Done
Jon LaBadie said: On Wed, Apr 27, 2005 at 11:46:49AM -0700, Tanniel Simonian wrote: Hello Group, I tend to figure things out on my own fairly quickly, however I can't seem to figure this problem out. I have a tape that I archived on February 25th, 2005. My tape cycle is 5 weeks and therefore February 25th has long been gone. A tapecycle has no units. It is a simple integer, number of tapes in rotation. I had stopped backing up this particular host on that date due to stability issues. However, I need to restore a tar'd file from this tape off that host. How do you mean you archived that tape? Is that a different archive config? Or did you just pull it out of rotation? Possibly replacing it with another of the same label so amanda thinks it might have been overwritten? Pulled the tape out of rotation and placed a new tape with the same label. At first I figured that since the tape was old, that the index record has been rotated or removed. I check /var/lib/amanda/xes/index/brimstone/sdb1 and noticed that the index file does index exist for that date. Was that a level 0? I wonder if a level is needed for amrecover to work - I don't know the answer. Yes the tape is a level 0. Does it have a list of files? Or might the dump have failed that day? You mentioned some type of stability problems. The instability did not affect the backups of that particular machine. The instability was due to old hardware and the proactive need to replace it. If it is not possible to use amrecover at this point, someone one to point me on how to restore a file from tape that has a combination of zipped tar's and dumps. Joshua pointed you in the right direction. Yes, thanks for the point. I was able to find the correct tape file and restore all the files from the tape. Then grabbed what I needed and deleted the rest. Not as elegant as the interactive amrestore or amrecover, but it got the job done. Thanks for the responses. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Amrecover: No index records for disk for specified date
Hello Group, I tend to figure things out on my own fairly quickly, however I can't seem to figure this problem out. I have a tape that I archived on February 25th, 2005. My tape cycle is 5 weeks and therefore February 25th has long been gone. I had stopped backing up this particular host on that date due to stability issues. However, I need to restore a tar'd file from this tape off that host. I run amrecover -C xes setdate 2005-02-25 sethost brimstone setdisk sdb1 and this message pops up: No index records for disk for specified date If date correct, notify system administrator At first I figured that since the tape was old, that the index record has been rotated or removed. I check /var/lib/amanda/xes/index/brimstone/sdb1 and noticed that the index file does index exist for that date. My question is this. If the tapecycle (which I tried to change temporarily in the config but no such luck) is less than the date you're trying to restore, will amanda not be able to restore it and automatically fail with the message above? Or am I not doing something wrong? If it is not possible to use amrecover at this point, someone one to point me on how to restore a file from tape that has a combination of zipped tar's and dumps. Thanks for any knowledge.
Re: parse of reply message failed
I know this seems a bit late, I just moved to linux 2.6.9 after reading about ip_conntrack_amanda and config_ip_nf_amanda fixes. However, I am somewhat confused, I encounted the parse of reply message failure error even though 2.6.9 (based on my reading) contained the patch code? Should I have still applied the patch found at the link below? --- I have CONFIG_IP_NF_AMANDA=y and CONFIG_IP_NF_NAT_AMANDA=y I have tried to run a backup with and without IpTables running. I was using 2.4.22 before, and decided it was time to update. Nothing else has been changed other than sysvinit (for kernel support). I will try to turn off these options and not use Iptables, to see if this alleviates the issue. Any additional suggestions would be greatly appreciated. [EMAIL PROTECTED] said: On Fri, Nov 05, 2004 at 10:12:25AM +0100, Paul Bijnens wrote: [EMAIL PROTECTED] wrote: On Thu, Nov 04, 2004 at 04:11:18AM -0500, foo wrote: I was wrong, it turns out to be ip_conntrack_amanda from netfilter that's the culprit. I haven't tested yet, but others have confirmed it. I thought that was fixed in kernel 2.6.6 or did it break again? See: http://www.mail-archive.com/amanda-users@amanda.org/msg26347.html Huh, I didn't know it was broken before (never having used it previously). Yes, this is a new issue. Here's a patch that's supposed to fix it, untested by me: http://marc.theaimsgroup.com/?l=linux-kernelm=109960579302508w=2 -ryan
Tapetype for Onstream SC50
I spent about 10 hours running tapetype for an Onstream SC50, and only to lose the information to a power surge. Can anyone give me the tapetype of an Onstream SC50? If not, then I will run tapetype again, and put down the information for everyone's else benefit. Just wish it didn't take forever.
Results Missing
Okay, I am strictly annoyed. I just added a new host to my backups. Its a debian system running amanda version 2.4.2p2 client. I tried using TAR, and I tried using DUMP. I am not getting TAPE out of space messages or any other error reports on amcheck. Amcheck comes out clean, no hosts problems, no tape problems. I have 17 file systems that I back up and it just keep messing up on this host. I can't put my finger on it, and its driving me nuts. Here is the message I get from Amanda when it emails me. server /dev/hda1 RESULTS MISSING I can't tell what I need to look for in the logs to help me understand my problem. Any help would be greatly appreciated. Thanks.
Amrecover erroring when extracting
Hello, Please let the gods of Amrecover hear my request! Here is the list of events that I do to get to the certain point of error. $ amrecover config AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 yohko AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-05-17) 200 Working date set to 2002-05-17. 200 Config set to exa. 200 Dump host set to yohko. Can't determine disk and mount point from $CWD amrecover sethost hostname.ucr.edu 200 Dump host set to hostname.ucr.edu. amrecover setdisk /dev/hda1 Scanning /dumps/amanda... 200 Disk set to /dev/hda1. amrecover ls ... file file file file so this part i know that the index file is working. Now I am going to attempt to 'add' a file. amrecover add file Added /vmlinuz.old amrecover extract Extracting files using tape drive /dev/nst0 on host localhost. The following tapes are needed: EXA22 (yes the tape is loaded!) Restoring files into directory /root Continue? [Y/n]:Y Load tape EXA22 now Continue? [Y/n]:Y amrecover: error reading tape: Connection reset by peer extract_list - child returned non-zero status: 1 Continue? [Y/n]:Y and voila.. what the heck!? The tape is loaded, all is well.. until I try to restore. Am I supposed to fast forward the tape to the right index? Or does Amrecover take care of that for me? No where can I find in the man pages that suggest that I should do any sort of mt -f /dev/nst0 fsf 6(arbitrary #) or something.. just the usual mt -f /dev/nst0 rewind. Help.. I started to use TAR because of active file system errors that dump was giving me. But I WILL change how my users work on the servers if TAR is a POS! So just to recap: The right tape is in the right drive.(CHECK) The tapedev is /dev/nst0 and is correctly pointed(CHECK) The configuration file has all of its settings correct.(CHECK) I ran an amrestore interactively to make sure that my dumps were working and that my tape wasn't bad. (CHECK) Tons of space on the dump disk (CHECK) /etc/hosts.allow allows amindexd to run (CHECK) I have access to the tapes by 'cat'ing the tape devices (CHECK) Help. (uncheck) Thanks. Tanniel Simonian
(EDIT) Amrecover erroring when extracting
Hello, Please let the gods of Amrecover hear my request! Here is the list of events that I do to get to the certain point of error. $ amrecover config AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 yohko AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-05-17) 200 Working date set to 2002-05-17. 200 Config set to exa. 200 Dump host set to yohko. Can't determine disk and mount point from $CWD amrecover sethost hostname.ucr.edu 200 Dump host set to hostname.ucr.edu. amrecover setdisk /dev/hda1 Scanning /dumps/amanda... 200 Disk set to /dev/hda1. amrecover ls ... file file file file so this part i know that the index file is working. Now I am going to attempt to 'add' a file. amrecover add file Added /vmlinuz.old amrecover extract Extracting files using tape drive /dev/nst0 on host localhost. The following tapes are needed: EXA22 (yes the tape is loaded!) Restoring files into directory /root Continue? [Y/n]:Y Load tape EXA22 now Continue? [Y/n]:Y amrecover: error reading tape: Connection reset by peer extract_list - child returned non-zero status: 1 Continue? [Y/n]:Y (NEW: I fixed this problem by adding in the /etc/hosts.allow the entry amidxtaped: ALL) This got rid of the error reading tape message. Stupid Debian does it to me again! It work.. as long as I made sure that the tape was rewinded I am in good shape. Tanniel
Re: Amanda install reality check
Use debian, can't go wrong with the installation. All you'll have to do is custom build your config and make sure that your hosts.allow allow amandad connection to go through. Total installation Time for Amanda on Debian was 5 minutes. Total installation time for Debian, 5 hours =) But its worth it in the end, and you'll get faster and faster. At 03:09 PM 2/6/2002 -0500, KEVIN ZEMBOWER wrote: For-what-it's-worth dept.: In the year that I've been a full-time Unix system administrator, I guess I've installed 40-50 different packages, mostly from source. Amanda was the second most time-consuming and difficult; only Xwindows was harder for me. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 gene [EMAIL PROTECTED] 02/06/02 01:49PM snip I seem to be really struggling to get this to work. I did think it would be easier than this ;-) /snip Gene
Re: Anyone see this error before?
I use an Intel 1 gig fiber network card in my server. On occasion the network card will lose the ability to communicate with the network, and just do nothing. Run an ifconfig and you'll see that it has massive amounts of errors, which lead my server to have APIC errors on both CPU's and finally an unexpected interrupt failure. Mind you, this happend 30 minutes into the backup, and therefore just tweaked Amanda. But man does 22 gigs go quick when its working. It won't ever happen again, because Im taking out the gig card. I'll have to check to see if their are updated drivers for my GNIC. On Mon, 11 Feb 2002, John R. Jackson wrote: server.xxx sda8 lev 0 FAILED [hmm, no error indicator!] Although I know what caused this problem, I just find it humerous to see programs send error message like the one above. The message means planner marked the estimate as failed for some reason, but did not record the reason. When reporting time came around it defaulted to the above message (better than de-referencing a NULL pointer :-). So what happened to cause this message? Maybe we can fix planner to recognize the situation and do a better job of reporting it. Tanniel Simonian John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Help, what is the cause of EXT2 Directory corruption?
Hello, I've all of a sudden gotten this error on my backup. Reading the content of the message I receive this output: /-- 138.23.89. sda6 lev 0 FAILED [/sbin/dump returned 3] sendbackup: start [138.23.89.40:sda6 level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f... - sendbackup: info end | DUMP: Date of this level 0 dump: Fri Feb 1 00:29:49 2002 | DUMP: Dumping /dev/sda6 (/home) to standard output | DUMP: Added inode 7 to exclude list (resize inode) | DUMP: Label: none | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 66251 tape blocks. | DUMP: Volume 1 started with block 1 at: Fri Feb 1 00:29:50 2002 | DUMP: dumping (Pass III) [directories] ? /dev/sda6: EXT2 directory corrupted while converting directory #15074 ? ? DUMP: error reading command pipe: Connection reset by peer ? DUMP: error reading command pipe: Connection reset by peer sendbackup: error [/sbin/dump returned 3] \ I've been running kernel 2.4.17 on the backup server, and 2.2.19 on the host. This just happend last night, and I've been able to backup for many many months. Google was no help on this problem. Tanniel Simonian
Interactive Restore with Tar?
I am trying to restore an NT partition from backup. Naturally one has to use GNUTAR to be able to backup the filesystem. However is there an interactive method to restore from tar, or must I untar to a holding disk first, then grab the files I need. Also a while back there was mention of restoring using amrestore then piping to smbclient. However, it didn't work out for me. If I have to untar to holding disk first, this would lead me to a small problem in case my holding disk is a little smaller than the filesystem I backed up. Hence this is the reason why I would like an interactive method. Otherwise Dump works well with restore but not with tar. Thanks! Tanniel Simonian P/A III UC Riverside Libraries
Supplement: Interactive Tar Restore?
One more thing: As a normal NT server, usually the hard drives are shared automagically, via a $ sign. therefore if you have C, D and E drive, they are shared respectively by //host/c$, //host/d$, and //host/e$. Assuming you got administrative privledge access. So i got lucky and was able to fully backup c$ like an ext2 partition. my disklist entry was: amanda-server //host/c$ user-tar now, here is the problem, I do want an interactive restore if such a possibility exists, but how the heck, do I restore that partition? right now if I just type in amrestore -p /dev/nst0 amanda-server |tar xvf - it will dump the contents of the tar in the current directory. But I could not tell if it would only do c$. and the output of amrestore while it spans through the 'files' shows that the NT server index is called hostname.__host_c$.date.0 so i tried: amrestore -p /dev/nst0 amanda-server hostname __host_c$ |tar xvf - but it just skips. i even tried c$, c\$, //host/c$ and so on.. just skips it. any ideas? =) Thanks!
chg-zd-mtx script is weirding out.
hello I am attempting to run an exabyte EZ 17 on a Debian 3.0 system running 2.4.2p2. I have tweaked my changer file to say firstslot 1 lastslot 7 and when I try to execute ./chg-zd-mtx -slot 1 this is what I get. The tape loader currently has the 3rd slot loaded into the tape drive. ./chg-zd-mtx: [: -eq: unary operator expected ./chg-zd-mtx: [: 1: unary operator expected ./chg-zd-mtx: [: 1: unary operator expected ./chg-zd-mtx: [: 1: unary operator expected ./chg-zd-mtx: [: too many arguments ./chg-zd-mtx: [: -gt: unary operator expected 1 Unloading Data Transfer Element into Storage Element 3...mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=70 (Current) mtx: Request Sense: Sense Key=Not Ready mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code = 04 mtx: Request Sense: Additional Sense Qualifier = 8E mtx: Request Sense: BPV=no mtx: Request Sense: Error in CDB=no mtx: Request Sense: SKSV=no mtx: MOVE MEDIUM from Element Address 82 to 3 Failed /dev/sg4 is the medium changer /dev/sg3 is the tape drive inside the ez17 When I attempt to run mtx -f /dev/sg4 first while the tape is loaded from slot 3 i get: Unloading Data Transfer Element into Storage Element 3...mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=70 (Current) mtx: Request Sense: Sense Key=Not Ready mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code = 04 mtx: Request Sense: Additional Sense Qualifier = 8E mtx: Request Sense: BPV=no mtx: Request Sense: Error in CDB=no mtx: Request Sense: SKSV=no mtx: MOVE MEDIUM from Element Address 82 to 3 Failed Is my problem with MTX or am I doing something wrong: I've got chg-multi to work, except it never knows what the current slot is. It just increments the slot by 1, whenever an eject occurs. Does anyone have particular experience with this unit. If so please please help! Thanks, Tanniel Simonian 909 787 2832
Re: Host Down Problem... again
Do you happen to have the amcheck output handy by chance? Does amcheck report any problems to connect to that client machine? On Tue, 8 Jan 2002, Joseph Myers wrote: I have AMANDA working on the server just fine. It is capable of backing up two computers already. Now I have to work on the other 4. The problem is the first 2 are running RedHat 7.1 and are thus using xinetd while the next 4 are running RedHat 6.2 and are thus using inetd. I can not figure out what the heck is wrong. Here is some info: in inetd.conf: amandadgram udp waitamanda /usr/local/libexec/amandad amandad amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped amidxtaped Here's the results from netstat -a | grep -i amanda: tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda*:* I have the permissions set on all of the files so that Amanda can read, write, and execute them. The .rhosts and .amandahosts files which are in both the root and amanda directories look like this: xxx.ornl.gov amanda On the server, in /tmp/amanda/*.debug, I get this message: amcheck: debug 1 pid 15215 ruid 1000 euid 0 start time Tue Jan 8 10:26:10 2002 amcheck: dgram_bind: socket bound to 0.0.0.0.769 amcheck: pid 15215 finish time Tue Jan 8 10:26:40 2002 The other two servers still work when I run amcheck so I don't think that there's anything wrong with the server side. It appears to be a client side problem. I am running the same version of Amanda on all of the machines. Another thing that I've heard people talk about is the IPChains firewall. We use an IPChains firewall.. but one of the other computers I back up is the firewall and the all of the computers are behind this firewall. So I can already backup another computer that is behind the firewall with no changes made to the IPChains so I don't believe that this is the problem. Please help me as soon as you can. I am stuck and this is holding up a major project. Thanks for any help you can give me. Joey
Re: Host Down Problem... again.
Just to ask, are you using dump? If you are, was dump installed when compiled in Amanda on that client pc. Is the amandahosts file owned by amanda? and sometimes, hosts.allow tends to be a problem with certain installations, becuase they rely on hosts to delegate which ports are open to hosts. On Tue, 8 Jan 2002, Joseph Myers wrote: The exact amcheck message is: Amanda Tape Server Host Check - ERROR: /no-such-device: No such file or directory (expecting a new tape) NOTE: skipping tape-writable test Server check took 0.002 seconds Amanda Backup Client Hosts Check WARNING: xxx.smpr.ornl.gov: selfcheck request timed out. Host down? Client check: 3 hosts checked in 30.025 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) There are no error files in the /tmp/amanda directory on the client. Thanks for your help Joey On 2002.01.08 11:19 Joshua Baker-LePain wrote: On Tue, 8 Jan 2002 at 10:51am, Joseph Myers wrote I have AMANDA working on the server just fine. It is capable of backing up two computers already. Now I have to work on the other 4. The problem is the first 2 are running RedHat 7.1 and are thus using xinetd while the next 4 are running RedHat 6.2 and are thus using inetd. I can not figure out what the heck is wrong. Here is some info: in inetd.conf: amandadgram udp waitamanda /usr/local/libexec/amandad amandad amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped amidxtaped On clients, you only need the amanda service. The other two are needed on the amanda server only. What is the exact output of amcheck on the server? Also, when you run amcheck, are any files getting created in /tmp/amanda *on the clients* you're having issues with? If so, what are the contents of /tmp/amanda/amandad*debug and (if it exists) /tmp/amanda/selfcheck*debug (again, on the problem clients). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Linus Torvald's opinion on Dump.
Anyone read from the kernel.org newsgroup a message from Linus Torvald about dump? here is his message: Note that dump simply won't work reliably at all even in 2.4.x: the buffer cache and the page cache (where all the actual data is) are not coherent. This is only going to get even worse in 2.5.x, when the directories are moved into the page cache as well. So anybody who depends on dump getting backups right is already playing russian rulette with their backups. It's not at all guaranteed to get the right results - you may end up having stale data in the buffer cache that ends up being backed up. Right now, the cpio/tar/xxx solutions are definitely the best ones, and will work on multiple filesystems (another limitation of dump). Whatever problems they have, they are still better than the _guaranteed_(*) data corruptions of dump. Dump was a stupid program in the first place. Leave it Behind He then finally notes: (*) Dump may work fine for you a thousand times. But it _will_ fail under the right circumstances. And there is nothing you can do about it. okay I've run dump THOUSANDS + 1 times, but have yet to have a problem with Amanda and especially restores. It has saved my ass repeatedly, especially when a hard disk has failed and everything has been running from memory for days. So please I need opinions. I've already rigged amanda to work with my exabyte EZ17 drive. I don't think I can rig it anymore to work with Tar. latz, Tanniel Simonian Programmer Analyst III University of California Riverside, Libraries.
Re: Exabyte Mammoth 2 users take note
Hey, Yeah I had called tech support on that particular reason and they said that premature EOTs were cause by the self cleaning engaging during middle of the dump.. I supposedly have a .i file that removes the autocleaning ability and that you'll hav to manually clean the tapes. Tano On Wed, 28 Mar 2001, Ross Johnson wrote: As of firmware upgrade 8ck3v03a (8ch3v03a for HVD drives), Exabyte have fixed a major problem with premature EOT errors. I have just upgraded and was able to do a full level 0 dump for the first time without getting inconsistent EOTs. So if you're getting this kind of error, it may be worth a trip to http://www.exabyte.com/support/online/downloads/firmware_tape.cfm Regards. -- +-+---+ | Ross Johnson| | "Come down off the cross | Management Technology |___| We can use the wood" - Tom Waits | Building 11 | | University of Canberra | eMail: [EMAIL PROTECTED] | ACT2601 | WWW: http://public.ise.canberra.edu.au/~rpj/ | AUSTRALIA | +-+
Average Dump Rate Question
Currently my average dump rate on a 100mbit full switched network
consisting of Cisco 2948G's and Dell Pentium III 800 mhz with 512 megs of
ram server is at:
Avg Dump Rate (k/s) 364.5 364.5--
How can I speed this up?
In amanda.conf I have set netusage to 5 kbits.
should I increase that number, decrease the number of dumps running
concurrently, shouldn't my network card be able to handle at least 4
megabytes per second, (3com 35905B 100mbit)? Does high compression play a
factor in the file transfer, or does the compression be done on the client
machine then sent over the network to the dump disk?
My hard disk also is set up as this:
define interface local {
comment "a local disk"
use 5 kbps
}
My local disk is an IBM Ultra 2 9 gig 1 RPM drive. I believe 5
kbps is sort of slow for a drive like this, but I don't get any
improvements by bumping this number up?
What can I do to increase my dump rate? Also does amanda ignore, when
defining a tape type the speed of what the tape drive is capable? Does it
leave determining the speed to the actual drive and interface?
define tapetype M2-AME225 {
comment "Exabyte EZ17 Mammoth2"
length 57487 mbytes
filemark 0 kbytes
speed 11765 kbytes
}
Avg Tp Write Rate (k/s) 6689.9 6689.9--
Im assuming that compression may play a role in the speed of the tape
drive copying content?
Any suggestions are greatly appreciated,
Thank you,
Tanniel Simonian
University of California Riverside Science Library
Linux Admin/Networking Admin
I/O error on tapetype program, help.
Hello, I've been getting weird errors on my nightly amanda job and saw
that there was a problem.
I currently use an EXABYTE EZ 17 Autoloader drive and had used the
TAPETYPE value given from this email group. After a few weird errors and
thinking that I had fixed them, I finally fell short when I got another
error.
I'm stuck because when I run the amdump manually Amanda runs without
hickups. When it runs on its own, it craps out on me and dumps the
remainder of the backups onto a holding disk.
I thought maybe my tapetype was wrong, so I ran it and produced the
following result: Note that this is on a 60/150 GB tape for a mammoth2
[root@quake tape-src]# tapetype -f /dev/nst1
wrote 110526 32Kb blocks in 338 files in 735 seconds (Input/output error)
wrote 102364 32Kb blocks in 628 files in 1040 seconds (Input/output error)
define tapetype unknown-tapetype {
comment "just produced by tapetype program"
length 3750 mbytes
filemark 900 kbytes
speed 3980 kps
}
Why am I getting I/O errors? I'm really confused. I get no errors when I
run amanda manually, but when it runs automagically I get this input out
error.
On amanda's email report i get:
Subject: AMANDA MAIL REPORT FOR January 29, 2001
These dumps were to tape EXA06
*** A TAPE ERROR OCCURRED: [[writing file: Input/ouput error]]/
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanada expects to use is: EXA07.
This has happend to all the tapes I have tried so far, I cannot believe
that I got a batch of bad tapes.
Tanniel Simonian
Re: Amanda/Sol8 + Exabyte X80 + HIARCjb
Check the december archives. I know someone who put in the tapetype of the
Mammoth 2 drive.
I know this is redundant but this is what was given:
define tapetype M2-AME225 {
comment "Mammoth2 with AME225"
length 57487 mbytes
filemark 0 kbytes
speed 11765 kbytes
}
As a rule of thumb, if you got a question, its most likely been
asked. =) I know, I had that same question.
I give thatnks to those who have spent the time finding these things
out for us.
Tanniel Simonian
UC Riverside Libraries
On Tue, 23 Jan 2001, Richard Michael wrote:
Hello,
I've researched a new backup config that I need to build and would like
to solicit comments from people who have been using Amanda for awhile
(this is my first config).
Does someone have tapetype entries for mammoth2 media? (I'd like to avoid
running the media through once wit tapetype. Though, if I run tapetype,
I'll post :)
Running on Solaris, what are the issues I should be aware of when
considering gnutar versus ufsrestore? (other than the xtr bug in Sol8's
ufsrestore from awhile back).
Can someone please email Josh Huston's perl script for the
HIARCjb driver to me? The eGroups archiver does a nice job of mutiliating
the text in the body.
Josh - Thanks for the work, your script will help me along immensely.
Thanks for any comments/advice.
Regards,
Richard
