Re: Faster dump on tape
Hi Paul, Hi John, I use the little perl-script in attachment to measure my tapespeed. Use like: On the first step, I used Paul perl script to try to get the minimum transfer rate needed to keep the tape streaming. I used the script with various buffer size, until the tape stopped streaming. - With compression disabled on the tape device: Uncompressable data: Buffer size Transfert rate MB/s 1 MB5.026 512 k 4.974 256 k 5.013 128 k 4.949 64 k5.026 32 k5.014 24 k5.000 23 k4.688 does not stream Compressable data would give the same rate, it proves the tape drive does not try to compress them. - With compression activated: 32% compressable data: 6.909 MB/s 85% compressable data: 23.469 MB/s (the drives achieves 78% compression rate) From this checking, I assume I need 5MB/s transfer rate to keep the tape drive streaming. -- On the second step, I conducted the checks suggested by John. You need to split these into dumps that were written to tape from the holding disk vs. those written directly to tape from the network. To do that, look at the amdump.nn file(s). Those with FILE-WRITE are holding disk - tape. Those with PORT-WRITE are network/dumper - tape. The DONE line from taper tells you the KBytes/s rate. Transfert rate from amdump reports, FILE-WRITE Only chuncks bigger than 200MB are shown. Transfert rate is almost enought, except on dump 3 when many parallel dumpers were running. amdump.1: dump size 2152.2 MB, transfert rate 5095.6 kbps amdump.2: dump size 270.7 MB,transfert rate 4837.0 kbps amdump.2: dump size 1383.4 MB, transfert rate 5117.2 kbps amdump.2: dump size 339.6 MB,transfert rate 5087.1 kbps amdump.2: dump size 271.2 MB,transfert rate 4628.5 kbps amdump.3: dump size 431.1 MB,transfert rate 4741.1 kbps amdump.3: dump size 233 MB, transfert rate 4459.9 kbps amdump.3: dump size 203.6 MB,transfert rate 4508.8 kbps amdump.3: dump size 1840 MB, transfert rate 4719.7 kbps amdump.3: dump size 1940.4 MB, transfert rate 4998.5 kbps amdump.3: dump size 2166 MB, transfert rate 4874.6 kbps amdump.3: dump size 864.3 MB,transfert rate 5006.2 kbps amdump.3: dump size 470.6 MB,transfert rate 2736.9 kbps amdump.3: dump size 1837.6 MB, transfert rate 5036.4 kbps amdump.3: dump size 3558.5 MB, transfert rate 5126.8 kbps amdump.3: dump size 267 MB, transfert rate 4247.4 kbps amdump.3: dump size 621.8 MB,transfert rate 4898.4 kbps amdump.3: dump size 5562.8 MB, transfert rate 5136.0 kbps amdump.7: dump size 1262.6 MB, transfert rate 4607.2 kbps amdump.8: dump size 270.7 MB,transfert rate 4435.8 kbps amdump.8: dump size 271.2 MB,transfert rate 4563.2 kbps amdump.8: dump size 339.6 MB,transfert rate 4172.3 kbps amdump.8: dump size 250.1 MB,transfert rate 4549.9 kbps * Reload a good sized (10's to 100's of MBytes) image from some tape into the holding disk. Actually, I'd store it in a temp area within the holding disk, then create the holding disk datestamp directory and That chuck is 2 GB. - iostat during amrestore -r reading tape to disk at 5MB/s, the tape is streaming tty da0 acd0 sa0 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 229 64.00 82 5.13 0.00 0 0.00 32.00 163 5.10 91 0 6 3 0 0 76 62.64 83 5.09 0.00 0 0.00 32.00 162 5.08 92 0 5 2 0 0 76 64.00 82 5.13 0.00 0 0.00 32.00 165 5.16 94 0 4 2 0 0 76 64.00 83 5.20 0.00 0 0.00 32.00 167 5.20 95 0 3 2 0 0 76 62.66 84 5.15 0.00 0 0.00 32.00 164 5.14 91 0 7 2 0 0 76 55.85 96 5.24 0.00 0 0.00 32.00 163 5.11 92 0 5 3 0 0 76 64.00 81 5.07 0.00 0 0.00 32.00 163 5.10 92 0 6 2 0 0 76 62.67 85 5.22 0.00 0 0.00 32.00 166 5.17 95 0 2 2 0 0 76 64.00 82 5.14 0.00 0 0.00 32.00 164 5.14 95 0 3 2 0 0 76 64.00 81 5.07 0.00 0 0.00 32.00 163 5.11 96 0 2 2 0 * dd the image from the holding disk to /dev/null with bs=32k and see what kind of rate you get. - iostat during dd if=file of=/dev/null bs=32k the disk (da0) transfert rate is about 23 MB/s dd comand reports 26.8 MB/s tty da0 acd0 sa0 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 229 63.74 425 26.46 0.00 0 0.00 0.00 0 0.00 85 0 12 2 0 0 76 63.73 416 25.92 0.00 0 0.00 0.00 0 0.00 81 0 13 6 0 0 76 63.74 425 26.44 0.00 0 0.00 0.00 0 0.00 88 0 9 2 0 0 76 63.74 425 26.44 0.00 0 0.00 0.00 0 0.00 84 0 12 4 0 0 76 63.87 426 26.59 0.00 0 0.00 0.00 0 0.00 84 0 12 4 0 0 76 63.74 425 26.47 0.00 0
Re: Changer problems
Hi, On Sun, Jun 03, 2001 at 03:41:15PM -0500, Gene Heskett wrote: Hi all; I've been lurking for about a day, but haven't seen any messages that relate to my problem. Specifically, even though I've recompiled amanda with the changer device (/dev/sg/2) defined, no amanda tape utils can find the changer. Hmm, can you give some more Infos, whcih OS, which amanda-version I can run it just fine with mtx. Also, it seem every version of the scripts in changer-src has their own idea of where the config files should be, can't this be consolidated, I've now got amanda stuffs in 8 or 9 different directories! Ups, the syntax might be different, but you can keep all config files in one directory .. The changer is a Seagate 4586NP, brand new, and I sure could use some hand-holding till I get the feel of how and what this program is doing. OK lets try it. If you have a linux/bsd system you can try to get the development version of amanda 2.5.0 and use the chg-scsi prgramm from there. (this version is available through CVS, see www.amanda.org) After compiling but not installaing this version you can try to run cd to_your_amanda_conifg_directory /path_to_the_source/changer-src/chg-scsi -genconf If this works you can copy the chg-scsi version to your libexec directory, save the ouput from the above in a file chg-scsi.conf, and add the following to amanda.conf tpchanger chg-scsi# the tape-changer glue script tapedev 0 changerfile /path_to_your_config/chg-scsi.conf remove everything like changerdev, tapedev from the amanda.conf No you can try to get a known state for the robot amtape reset and write a label amlabel conf xxx slot current (xxx must be a valid label name) Hope this helps a little bit Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
amlabel problem
When I try to label a tape, I get the following: hcuxtstest01% amlabel archive archive00 rewinding amlabel: no tape online Amanda is installed and configured on SUN Ultra I, Solaris 8. I don't have a tape drive physically connected to this machine, I am accessing a tape device on another SUN box. Thank you, Dave Warchol Technical Consultant Information Services Hartford Hospital Voice: 860.545.4222 Fax: 860.545.3321 [EMAIL PROTECTED]
Re: FreeBSD 4.3/inetd failing
This is when I manually ran it. # cat amandad.out.63688 Sat Jun 2 10:20:24 PDT 2001: starting amandad Sat Jun 2 10:20:54 PDT 2001: amandad done: status is 1 more /tmp/amanda/amandad.xxx.debug amandad: debug 1 pid 63690 ruid 0 euid 0 start time Sat Jun 2 10:20:24 2001 [compile info - snip] amandad: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout error receiving message: timeout amandad: pid 63690 finish time Sat Jun 2 10:20:54 2001 /var/log/messages: Jun 1 10:55:05 mail inetd[152]: amanda/udp server failing (looping), service terminated Jun 1 10:57:58 mail inetd[152]: amanda/udp server failing (looping), service terminated Here's the inetd.conf entry: amanda dgram udp waitroot/usr/local/libexec/amandad.test amandad As best as I can tell, no, amanda is not executing, even though with tcpdump I see two udp packets showing up at the machine. It seems that inetd shuts off that service after the first packet gets there. Inetd is also running pop and imap, so it's not as if inetd isn't working for other services. Any other suggestions? Thanks! -doug On Fri, 1 Jun 2001, John R. Jackson wrote: Done. The script still doesn't execute ... Doesn't execute at all??? Is anything logged to /var/adm/messages (or wherever inetd puts stuff)? What happens if you run the script as your Amanda user (root?). It should sit for 30 seconds and then terminate, and you should get the script output file. -doug John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- ~ Doug Silver Quantified Systems, Inc ~
changer questions
Hi everybody: I have a HP surestore 24X6 autoloader and I using chg-zd-mtx configuration file with dev /dev/nst0 scsitapedev /dev/sgb startuse0 enduse 5 statfile/usr/local/etc/amanda/miro_daily/tape0-slot the thing is that I have three files on /usr/local/etc/amanda/miro_daily that really I don't know what they are mean. the files are: changer.conf-access changer.conf-clean changer.conf-slot the true is that I don't have my tape cleaner yet so I don't know if it is a big deal. Please any explanation, I would really appreciated Sandra
More info: Exabyte 220 / Solaris 7 x86
Some more details of my problem: I can get sst to compile on SPARC. It gives me the same exact warnings as on the Intel box. No problem... as per the docs, these warnings can be ignored. So, I truss'd gcc on the two boxes to see where things go wrong, and this is what I found... Both boxes fork a copy of 'cc1' (this child is responsible for printing out the warning messages). This is where things get funky. On the SPARC box, the child 'cc1' does an exit(0) and the parent goes on to run 'as' as a new child, which produces the sst.o file. However, on the Intel box, the child 'cc1' exits with exit(33), and then the parent immediately does an exit(1). No sst.o ever gets produced. I've never run into this before, and the truss doesn't indicate any other problems. I've tried with gcc 2.95.1 and 2.95.2, with same results. I absolutely need this sucker to run on an Intel box, but if worse comes to worse, I'll have to scrap Solaris and try a different OS for the amanda tape server. Virtually all of the cliets that are to be backed up are Intel Solaris, so I was trying to keep things consitent. So, two questions: Does anyone know what causes an exit(33) in gcc (cc1)? And has *anybody* successfully compiled sst on Intel Solaris 7, or should I give up and go make better use of my time by smoking a fat rock instead? Thanks, __Jason On Fri, 1 Jun 2001, Jason Tucker wrote: On Fri, 1 Jun 2001, John R. Jackson wrote: What version of Amanda? What version of sst (i.e. did you get it from the Amanda sources)? Are you building for 32 bit or 64 bit? Amanda 2.4.2p2 It's the sst that came with amanda. Intel Solaris is only 32 bit capable. The Amanda 2.4.2p2 contrib/sst/README.Amanda file talks about the very errors you're seeing. Unfortunately, it simply says to ignore them. That's fine, but I'm still left with a failed compilation. Am I missing something painfully obvious? Thanks, __Jason --
Re: Thank you again
Files restored with no problem at all. On Fri, 1 Jun 2001, John R. Jackson wrote: Amanda backs-up both machines and the solaris machine (the host) has my tape unit configured on it. Understood. Can I not restore client images to the client machine? (since my host and client machines are different) Yes, you can do this. But that doesn't appear to be what you're doing. Amrecover tried to run ufsrestore. It would only do that when amrecover was running from a Solaris box. But you said the client is a Linux box. You need to run amrecover on the client (the Linux box). It will reach out to the tape server (Solaris box) and read the tape from there. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: FreeBSD 4.3/inetd failing
I had a similar problem with amanda 2.4.1p2 on Solaris 8 client (no auditing..). After much of the same kinds of debugging techniques (this list is great!) I discovered that the client side amandad was dying due to inability to find a shared library. The problem only showed up when amandad was called by inetd, i.e. if you ran amandad manually on the client as the backup user, it worked. I discovered this by doing the shell script hack that John suggested. The fix was ugly and dumb - 1) set LD_LIBRARY_PATH in /etc/init.d/inetsvc to include the amanda libs. 2) copy the shared lib it was missing into the $AMANDA/libexec directory. One would think that including the path to the libs should have been enough, but it wasn't. I did not spend more cycles trying to figure out why. Hope this helps, alex Doug Silver wrote: This is when I manually ran it. # cat amandad.out.63688 Sat Jun 2 10:20:24 PDT 2001: starting amandad Sat Jun 2 10:20:54 PDT 2001: amandad done: status is 1 more /tmp/amanda/amandad.xxx.debug amandad: debug 1 pid 63690 ruid 0 euid 0 start time Sat Jun 2 10:20:24 2001 [compile info - snip] amandad: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout error receiving message: timeout amandad: pid 63690 finish time Sat Jun 2 10:20:54 2001 /var/log/messages: Jun 1 10:55:05 mail inetd[152]: amanda/udp server failing (looping), service terminated Jun 1 10:57:58 mail inetd[152]: amanda/udp server failing (looping), service terminated Here's the inetd.conf entry: amanda dgram udp waitroot/usr/local/libexec/amandad.test amandad As best as I can tell, no, amanda is not executing, even though with tcpdump I see two udp packets showing up at the machine. It seems that inetd shuts off that service after the first packet gets there. Inetd is also running pop and imap, so it's not as if inetd isn't working for other services. Any other suggestions? Thanks! -doug On Fri, 1 Jun 2001, John R. Jackson wrote: Done. The script still doesn't execute ... Doesn't execute at all??? Is anything logged to /var/adm/messages (or wherever inetd puts stuff)? What happens if you run the script as your Amanda user (root?). It should sit for 30 seconds and then terminate, and you should get the script output file. -doug John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- ~ Doug Silver Quantified Systems, Inc ~
Re: changer questions
On Mon, 04 Jun 2001, Sandra Panesso wrote: Hi everybody: I have a HP surestore 24X6 autoloader and I using chg-zd-mtx configuration file with dev /dev/nst0 scsitapedev /dev/sgb startuse 0 enduse5 statfile /usr/local/etc/amanda/miro_daily/tape0-slot the thing is that I have three files on /usr/local/etc/amanda/miro_daily that really I don't know what they are mean. the files are: changer.conf-access Tries to count how many times the drive is accessed. Once a certain number is reached, the cleaning process should kick in. Only matters if AUTOCLEAN is turned on. changer.conf-clean Tells which slot the cleaning tape is in. Since I don't have one either, I had set in my config for it to be 0. Again, only matters if AUTOCLEAN is on. changer.conf-slot It is an indicator of what the next slot to be loaded will be. the true is that I don't have my tape cleaner yet so I don't know if it is a big deal. Please any explanation, I would really appreciated Sandra -- Jason Hollinden MH5 Systems Admin
Re: More info: Exabyte 220 / Solaris 7 x86
Well, problem solved... sort of. It seems that gcc on Sol7 (i386) is simply incapable of compiling sst. Fortunately, I learned that I had a copy of Sun's CC available here, so I tried that and she compiled with no problem! Now, if I can only get everything configured properly, I might just make this work... Thanks to those who offered advice. __Jason On Mon, 4 Jun 2001, Jason Tucker wrote: Some more details of my problem: I can get sst to compile on SPARC. It gives me the same exact warnings as on the Intel box. No problem... as per the docs, these warnings can be ignored. So, I truss'd gcc on the two boxes to see where things go wrong, and this is what I found... Both boxes fork a copy of 'cc1' (this child is responsible for printing out the warning messages). This is where things get funky. On the SPARC box, the child 'cc1' does an exit(0) and the parent goes on to run 'as' as a new child, which produces the sst.o file. However, on the Intel box, the child 'cc1' exits with exit(33), and then the parent immediately does an exit(1). No sst.o ever gets produced. I've never run into this before, and the truss doesn't indicate any other problems. I've tried with gcc 2.95.1 and 2.95.2, with same results. I absolutely need this sucker to run on an Intel box, but if worse comes to worse, I'll have to scrap Solaris and try a different OS for the amanda tape server. Virtually all of the cliets that are to be backed up are Intel Solaris, so I was trying to keep things consitent. So, two questions: Does anyone know what causes an exit(33) in gcc (cc1)? And has *anybody* successfully compiled sst on Intel Solaris 7, or should I give up and go make better use of my time by smoking a fat rock instead? Thanks, __Jason
Re: amlabel problem
Dave, Amanda is installed and configured on SUN Ultra I, Solaris 8. I don't have a tape drive physically connected to this machine, I am accessing a tape device on another SUN box. Run amlabel on the machine with the tape drive... You anyway need physical access to that machine, if only to load the tape, so you could even run the command from that machine too. I don't know if there is a way to do remote amlabel (well something else that rsh other.machine.com amlabel...) but I wouldn't see much use for it, except if you have a tape robot that can handle 200 cartridges (and in that case you have big $$ and would go by something else than Amanda I beleive). Olivier
Re: More info: Exabyte 220 / Solaris 7 x86
Jason, So, two questions: Does anyone know what causes an exit(33) in gcc (cc1)? And has *anybody* successfully compiled sst on Intel Solaris 7, or should I give up and go make better use of my time by smoking a fat rock instead? have you asked on GNU lists/news too? It seems to me it is a problem linked to the OS or the compiler and it should not be limited to Amanda. Olivier
Some questions
Hello, Here is a couple of questions... 1) I beleive gzip command is activated by the dumper, not by the taper? Am I right? 2) In case I want to speed up gzip, what should I increase on my system? CPU? Memory? I have a dedicated Pentium III 800 as amanda server, and I do gzip best on the server. 3) I have defined a chunck size of 1Gb chunksize 1Gb # size of chunk if you want big dump to be # dumped on multiple files on holding disks Yesterday, while running some tests suggested by JRJ, I could amrestore a file that was 2GB, how does it come? That's all folks Best regards, Olivier
