Re: LTO drives
We've had great luck with equipment from Overland Storage. We've kept a Neo-2000 library with dual LTO-3 drives busy for 3 years now with no problems so far. Other departments here have had similar experience with Overland equipment: not fancy, but very solid. -Roy On Mon, 27 Oct 2008, Nick Brockner wrote: Howdy, Time to replace the aging DAT changer. Just looking for some input on what LTO3/4 drives (or libraries) work well with amanda. Thanks in advance, Nick
client times out
We're running amanda-2.4.5p1 server on a white box under debian/sarge. We're backing up from 8 hosts without any problems beyond an occasional client timeout. Working clients are running debian/sarge, RHAS 2.1, and AIX 5, and the same 2.4.5p1 release of amanda. We have a CentOS 4.1 client that is failing consistently with client-side timeouts. The client starts, dumps 35 MB to the server, then times out. The partition being dumped is around 1 GB. The time out occurs when iptables on the client is turned on, and also when it is turned off. Gtar is 1.15.1. Timeout messages in /tmp/amanda/sendbackup.* on the client look like this: --- sendbackup: debug 1 pid 18885 ruid 518 euid 518: start at Fri Feb 10 02:20:02 2006 [snip] sendbackup: time 0.001: got all connections [snip] sendbackup-gnutar: time 0.062: doing level 0 dump from date: 1970-01-01 0:00:00 GMT [snip] sendbackup-gnutar: time 0.064: /usr/local/amanda/2.4.5p1/libexec/runtar: pid 18889 sendbackup: time 958.026: index tee cannot write [Connection timed out] sendbackup: time 958.026: pid 18887 finish time Fri Feb 10 02:36:00 2006 sendbackup: time 958.026: 125: strange(?): sendbackup: index tee cannot write [Connection timed out] sendbackup: time 958.028: error [/usr/local/amanda/2.4.5p1/bin/gtar got signal 13] sendbackup: time 958.028: pid 18885 finish time Fri Feb 10 02:36:00 2006 --- We reduced the keepalive interval on both client and server but didn't see a change. Any suggestions would be welcome. Thanks, Roy Heimbach -- Roy Heimbach [EMAIL PROTECTED] / 505-277-8348 User Services / [EMAIL PROTECTED] / University of New Mexico
amanda performance
We have amanda 2.4.5p1 server running under debian linux on a dual opteron that's driving a new overland tape library with an ultrium3 drive. For now, the holding disk is a dedicated local 120 GB drive. There's an amanda 2.4.5p1 client also running under debian linux on another dual opteron that's connected to the amanda server host via a dedicated gig network. This host is a moderately loaded fileserver with hardware raid. Backing up a 10 GB test partition, we're seeing dumper and taper performance around 2.5 MB/sec, a fraction of what the hardware is capable of. The amanda server was configured with max tape blocksize set to 8192kb. None of the other configure script options are unusual-- prefix, user, group, amandahosts, db=text, gnutar. The dumptype does not specify software commpression on either end. Feels like we're overlooking something basic, but so far we're not seeing what it is. Any suggestions would be welcome. Roy Heimbach -- Roy Heimbach 505-277-8348 / User Services / [EMAIL PROTECTED] University of New Mexico, Albuquerque
Re: amanda performance
Thanks, and thanks also to everyone who replied. Turns out dma was disabled. With dma disabled, read/write rates on the holding disk were a little over 3 MB/sec. The dumper and taper reported different average performance, but both were in the same ballpark, from 2.4 to 2.6 something MB/sec. Not bad at all, considering the speed of the holding disk. Thanks again to everyone who replied. Roy Heimbach -- Roy Heimbach 505-277-8348 / User Services / [EMAIL PROTECTED] University of New Mexico, Albuquerque On Fri, 16 Dec 2005, Gene Heskett wrote: On Friday 16 December 2005 13:30, Joshua Baker-LePain wrote: On Fri, 16 Dec 2005 at 1:08pm, Gene Heskett wrote That almost sounds like he would need a dedicated hardware raid to use as a holdng disk then. Ouch. And maybe futile unless that same controller can also handle the tape library, in which case the devices could negotiate their own transfers between themselves, at I've got a 4 disk SATA RAID0 on a 3ware controller for the holding disk. And what speeds are reported by hdparm -tT /dev/md0? whatever the limiting speed of the cable might be. This library is I take it, a scsi3 wide interface? 320mb/sec rated? Yep. In my case, the library is the only thing on the SCSI chain. Which means the data has to piped thru the pci bus, so the maximum on a non-pci-x buss is 133MB/sec. And the average will be somethat less than that when the handshaking is factored in. But only 2.5MB/Sec says there is a very small pinhole someplace its being forced through.
