RE: This is retarded.
On 8/30/05, Joe Rhett [EMAIL PROTECTED] wrote: tracking ability, but let's use 3 tapes and write not a single byte to them? On Aug 30, 2005, at 1:18 PM, Cam wrote: What's retarded? your configuration? you really didn't give enough information for anyone to help you. We've been running in this configuration for 5+ years now. The configuration works. Yes, I could supply the configuration but it really doesn't change anything. Amanda should not use 3 tapes and write 0 bytes to them, no matter what the configuration is. Joe, I find your response retarded, if we're going to name-call like we're 5. You don't go to the doctor and say My body has worked for 34 years, and now all of a sudden, this bad thing is happening... and not give the doctor any more information than that. My experience with computers and/or software is that anything that can happen will. And my experience with this forum is that we don't answer questions without all of the information. I'm not sure what you expect us to do to help you when you're not telling us anything. With what you've supplied, I'm saying it's hardware. Does that help you? Didn't think so. Rebecca.
dumper5 pid 10813 is messed up, ignoring it
Title: dumper5 pid 10813 is messed up, ignoring it Hi all - I've searched the archives and did a google search on the above error, and I found an old sourceforge archive from JJ that offered some suggestions, but I still can't get a handle on what's going on. Here's what I have: A server running amanda-2.4.4p4 running on RHE3 intel, and has been for a couple of years. A client running amanda-2.4.4p1 on Sol9, sparc. Here's what's happening: I've isolated the problem to this client because it's the only one where all of the results are missing, well almost all. I changed my disklist to include only this client since all others are backing up just fine. Basically the job just hangs and hangs and hangs, so I come in and manually kill dumper0-dumper5 and then the taper pid's go away, toothen I finally get the email from amanda: *** THE DUMPS DID NOT FINISH PROPERLY! Ignore this - I didn't have a tape in the drive at the time I was trying this testsame with taper stats below*** A TAPE ERROR OCCURRED: [rewinding tape: Input/output error]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: uadaily02. FAILURE AND STRANGE DUMP SUMMARY: smores.unt /usr RESULTS MISSING smores.unt /opt RESULTS MISSING smores.unt /export/home RESULTS MISSING smores.unt /var RESULTS MISSING STATISTICS: Total Full Daily Estimate Time (hrs:min) 0:01 Run Time (hrs:min) 0:01 Dump Time (hrs:min) 0:01 0:01 0:00 Output Size (meg) 2.3 2.3 0.0 Original Size (meg) 2.3 2.3 0.0 Avg Compressed Size (%) -- -- -- Filesystems Dumped 1 1 0 Avg Dump Rate (k/s) 45.0 45.0 -- Tape Time (hrs:min) 0:00 0:00 0:00 Tape Size (meg) 0.0 0.0 0.0 Tape Used (%) 0.0 0.0 0.0 Filesystems Taped 0 0 0 Avg Tp Write Rate (k/s) -- -- -- NOTES: driver: dumper5 pid 10813 is messed up, ignoring it. driver: dumper0 pid 10808 is messed up, ignoring it. driver: dumper0 died while dumping smores.unterlaw.com:/export/home lev 0. DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s --- -- smores.u /etc 0 2360 2360 -- 0:52 45.0 N/A N/A smores.u /export/home MISSING -- smores.u /opt MISSING -- smores.u /usr MISSING -- smores.u /var MISSING -- (brought to you by Amanda version 2.4.4p4) According the email a couple of years ago from JJ, I tried to run the amdump on just this client, while running gdb in another window on the dumper pid. I've never used gdb before, but basically it just gave me a bunch of library connection stuff and then sat there after I typed cont at the gdb prompt. Any suggestions?
RE: Backup to Hard Drive
On Thursday 16 June 2005 10:52, Cody Holland wrote: I'm a newb to Amanda, and would like to backup everything to a server running Raid0. I'm sure this is very possible, I just cannot find any docs on it. Any help would be greatly appreciated. Thanks, Cody Try looking in the amanda FAQ-omatic, here: http://amanda.sourceforge.net/cgi-bin/fom?_recurse=1file=25#file_191 This is the configuration I used and it works like a champ. ;-)
RE: dumper5 pid 10813 is messed up, ignoring it
Hello, Rebecca, on 16.06.2005, 19:47 you wrote to amanda-users@amanda.org: Here's what I have: A server running amanda-2.4.4p4 running on RHE3 intel, and has been for a couple of years. A client running amanda-2.4.4p1 on Sol9, sparc. Any suggestions? Is there any reasonable chance of getting some more recent version of AMANDA running on that client? 2.4.4p1 is pretty old now, there have been loads of changes and fixes since then ... Rolling your new and shiny AMANDA-client shouldn't take you longer than debugging the old one with gdb ... Best regards, Stefan G. Weichinger. Yeah, I thought about that, but if that were the problem, wouldn't it be happening on my other 2.4.4p1 clients? I'm looking for a little bit more information on what the problem could possibly be. What causes the dumper to tank all of a sudden? If there's something else failing on this box, I'd kind of like to know.
RE: Maybe OT but a big problem with SOLARIS
What version of Solaris are you running? Have you thought about installing the Solaris BSM to monitor what exactly is happening? There's a great article in the Solaris Administration magazine on the BSM with some scripts on how to use it effectively. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Schaller Sent: Tuesday, November 23, 2004 1:08 AM To: [EMAIL PROTECTED] Subject: Maybe OT but a big problem with SOLARIS Hey! Maybe this Thread is a little OT, maybe it isn't. During a few days we've big problems with one of our servers. It's a SUN FIRE V480R with external StorEdge an a external changer (Overland LoaderXpress with a single LTO-1 drive from HP) attached. As I wrote a few weeks ago the system run fine with AMANDA and the changer. Only in the fist night after configuring AMANDA with the changer the automatic backup started and the complete system crashed!! Solaris didn't give any messages in /var/adm/messages ... The system was frozen, the only way to get the system back to life was a poweroff. After that the system was really fine for a few weeks. Last week the same shit happend. The complete system was frozen. We opened a call but without any messages sun was not able to solve the problem. During the last two days the system crashed two times. But now the system does a automatic reboot. Anybody ANY hints?? I get crazy ... Thanks in advance Michael
RE: Amanda through a VPN?
I'm so frustrated with our networking group, which implements a single change in the firewall, then requires that we wait until the next morning to make a second trial if the first one doesn't work. I believe that no one really thorough understands the firewall software, an Elron CommandView firewall, which seems to be out of production. The last mention I can find of it through Google dates to 1999. Links to their website redirect to zixcorp.com. Consequently, I'm exploring other options to get Amanda to work through or around this firewall. The first I thought of was a VPN. However, I only know what I've read about VPNs; I've never set one up or worked with it. Would a VPN work? Is it the right tool to use, short of getting the firewall to work properly in the first place? Any recommendation on specific VPN solutions to use? Anyone done this before? I tried searching on 'vpn' in this list's archives, but didn't turn up anything. In short, Kevin - being one of those pesky network people myself - a vpn wouldn't solve your problem, it would probably add to it. You would still have to talk to your firewall administrators to configure the vpn and to make sure that it was compatible with your current firewall product. Some firewalls have some sort of VPN client dependent on what needs to happen: firewall-to-firewall vpn, client-to-firewall vpn...it's all different. Most want some sort of VPN community established with keys so it knows who to trust. Think of a VPN as a tunnel with a gate on either end - someone has to configure the gates and who is allowed through them, and what happens to the information once it gets through. If you're talking about a firewall at all, my guess is that you are trying to back up something that is not in your building or on another subnet? Maybe with more information about what you are trying to do I can suggest a workaround...but you are still not going to get to that backup if your firewall is misconfigured. *spoiled because I administer both my firewall and my backups*
RE: Amanda-Autoeject after dump
Hi! We're currently running Amanda to daily backup our server system. As we hand-exchange the tape every day, I've a question regarding speeding up this tedious task. How is the most elegent way to get amanda to auto-eject the tapes after it ran a dump? Would be also a nice easy in organisation, as you would see with one glimpse at the tape-server if the backup ran correcty, since then the tape would be ejected. Or you can easily see if not another has already exchanged the tape, if it is inserted it has already been swaped. Fellow greetings, Axel Not sure about 'elegance' - but I run my amdump from a script that cron calls... #!/bin/sh mt -f /dev/nst0 rewind su amanda -c /usr/local/sbin/amdump configname mt -f /dev/nst0 rewoff
RE: Unable to backup clients
But the backups fail. Checking the logs in /tmp/amanda (on the clients), I see things like: sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.33011 sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.33012 sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.33013 sendbackup: time 0.001: waiting for connect on 33011, then 33012, then 33013 sendbackup: time 29.991: stream_accept: timeout after 30 seconds sendbackup: time 29.991: timeout on data port 33011 sendbackup: time 59.991: stream_accept: timeout after 30 seconds sendbackup: time 59.991: timeout on mesg port 33012 sendbackup: time 89.991: stream_accept: timeout after 30 seconds sendbackup: time 89.991: timeout on index port 33013 sendbackup: time 89.991: pid 1873 finish time Thu Jan 8 01:05:15 2004 All hosts were configured with: --with-tcpportrange=850,854 --with-udpportrange=850,854 So why am I getting connections on port 33011? I have 850-854 opened on the firewall, but if it's trying to connect on 33xxx then of course it's not going to work. On the server, my /etc/services has: amanda 850/udp # amanda backup services amanda 850/tcp kamanda 851/tcp # amanda backup services (Kerberos) kamanda 851/udp # amanda backup services (Kerberos) amandaidx 852/tcp # amanda backup services amidxtape 853/tcp # amanda backup services The clients have: amanda 850/udp amanda 850/tcp kamanda 851/udp amandaidx 852/tcp All I can tell you is that for me to be able to back up my firewall, I had to create a rule that allowed my amanda server full access to all of my high ports (1023). I had this problem and this is what Joshua from this listserv came back with. Worked like a charm. I would suggest trying this.
RE: Help - recovering without amanda
Ditto everything that Joshua says AND, don't recover into anything but an empty directory on a largly empty file system unless you know, and have practiced, what you are doing. I have a pretty good idea what I'm doing, and I have practiced this technique. Yet I still recover to an empty directory. Then transfer things if I'm happy with what was recovered. This is sound advice and once I did this, all was basically well. Another point I would mention having successfully tackled this wonderful part of Amanda: make sure the good version of tar is first in your path when recovering. Part of the reason I had problems is that when I went to 'tar t' my image, it was using old, crappy tar in /usr/sbin/, not good, healthy tar in /usr/local/bin/ this led me to believe I was doing it wrong, when in fact I just needed to clarify my path situation. Thanks to Jon and Joshua, who as usual, have the answer and explain it well.
RE: Help - recovering without amanda
I always restore to a temp space, just in case. I should have done this...I never do direct restores...ugh # mt rewind # mt fsf 1 # dd if=/dev/rmt/0hn bs=1 skip=1 | /usr/local/bin/tar -xf - ^ Bad. It should be bs=32k, as above (and as in the header you got running the first command). Also, an even safer way is to not do the pipe: dd if=/dev/rmt/0hn bs=32k skip=1 of=output.file Then you can do 'tar t' on the output file to get a table of contents and *really* make sure it's what you want. The bs=1 was a typo...I can't cut and paste because this box is on a test LAN that's not even getting out the door...my bad. But skipping the pipe is a good suggestion. Here's a brief summary. Amanda stores several files on a tape. The first is the tape header. That's what you skip over with 'mt fsf 1'. The next file is the first dump image. The next is the second image, etc. Each dump image has a 32k amanda header, and then the image. The dd command with with 'bs=32k skip=1' reads the whole file, skipping over the first 32k -- the amanda header. It stops when it hits EOF of that dump image. If you run the exact same dd command again, you'll grab the next backup image. Thanks...I'll keep plugging away...
Help - recovering without amanda
Title: Help - recovering without amanda Has anyone ever done this? I'm finding the documentation confusing. We're working on disaster recovery and I'd really like to know how to do this Specifically - in 'the chapter' they outline the commands one is supposed to use, but I don't understand them Anyone? Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
RE: Help - recovering without amanda
docs/RESTORE is pretty clear, IMHO. Have a look at that, and then let us know *exactly* what you don't understand. As a short intro, you use 'mt' to position the tape, 'dd' to grab the raw image off the tape, and restore/'tar x' to extract the contents of the image. docs/RESTORE says the same thing as the chapter, basically. when I run: # mt rewind # mt fsf 1 # dd if=/dev/rmt/0hn bs=32k count=1 I get: AMANDA: FILE 20031127 spork.unterlaw.com /u05/oracle/admin/testua lev 0 comp N program /usr/local/bin/tar To restore position tape at start of file and run: dd if=tape bs=32k skip=1 | /usr/local/bin/tar -f... - 1+0 records in 1+0 records out GREAT...this is one of the two things I would like to restore. Fantastic. So it appears as if this is the first thing on the tape...so I cd /u05/oracle/admin and run # mt rewind # mt fsf 1 # dd if=/dev/rmt/0hn bs=1 skip=1 | /usr/local/bin/tar -xf - 107+0 records in 107+0 records out Great...now what? And now if I try to run that dd command again, it says: read: not enough space read: not enough space 0+0 records in 0+0 records out What 107 records is is talking about the first time?? The tape never appeared to be active after I ran my dd command the first time, so what did it do with the mysterious 107 records. The doc is clear on what commands to run, but I ran them, and nothing seems to have happened.
RE: Help - recovering without amanda
docs/RESTORE is pretty clear, IMHO. Have a look at that, and then let us know *exactly* what you don't understand. As a short intro, you use 'mt' to position the tape, 'dd' to grab the raw image off the tape, and restore/'tar x' to extract the contents of the image. docs/RESTORE says the same thing as the chapter, basically. when I run: # mt rewind # mt fsf 1 # dd if=/dev/rmt/0hn bs=32k count=1 I get: AMANDA: FILE 20031127 spork.unterlaw.com /u05/oracle/admin/testua lev 0 comp N program /usr/local/bin/tar To restore position tape at start of file and run: dd if=tape bs=32k skip=1 | /usr/local/bin/tar -f... - 1+0 records in 1+0 records out GREAT...this is one of the two things I would like to restore. Fantastic. So it appears as if this is the first thing on the tape...so I cd /u05/oracle/admin and run # mt rewind # mt fsf 1 # dd if=/dev/rmt/0hn bs=1 skip=1 | /usr/local/bin/tar -xf - 107+0 records in 107+0 records out Great...now what? And now if I try to run that dd command again, it says: read: not enough space read: not enough space 0+0 records in 0+0 records out What 107 records is is talking about the first time?? The tape never appeared to be active after I ran my dd command the first time, so what did it do with the mysterious 107 records. The doc is clear on what commands to run, but I ran them, and nothing seems to have happened. ACTUALLY - I take that back, something seems to have happened, because I now have 464 files in /u05/oracle/admin that were not there before, and are NOT /u05/oracle/admin/testua...it IS however the /etc slice from a different server. How did that happen if I looked at the header for after mt fsf 1 and it was /u05/oracle/admin/testua. OMG...this is horrible.
RE: What does..
In that case we'll need all the details -- copies of your amanda.conf, relevant amdump.N file, 'ls -l's of the appropriate devices, is this a new installation, amanda version, etc etc. If you do a simple mt -f /dev/nst0 status, does it return anything? If you go do /dev do you see nst0?? What OS/OE are you running?
RE: UPDATE: SOLVED:Cannot backup firewall
On Thu, 20 Nov 2003 at 8:26am, Rebecca Pakish Crum wrote I'm running amanda 2.4.2p2 on a RH box as my backup server. I installed the amanda client on my (sol8) firewall on Friday, and set up a rule for the server to get to the firewall for amanda services - amcheck runs fine and reports no errors. But when my amdump kicks off at night, my report says: firewall.unter /export/home/rebecca lev 0 FAILED [could not connect to firewall.unterlaw.com] You have to allow traffic on not just the amanda port, but also high numbered TCP ports for the data connections. On Linux clients, I put in the following iptables rules: # Amanda from chaos -A INPUT -p udp -s $SERVER_IP_ADDRESS -d 0/0 --dport 10080 -j ACCEPT -A INPUT -p tcp -m tcp -s $SERVER_IP_ADDRESS -d 0/0 --dport 1025:65535 -j ACCEPT With just the first rule (allowing UDP traffic to port 10080), the client will pass amcheck but fail amdump. The second rule (allowing TCP traffic to all non-priviledged ports) actually allows data to flow. Thought I should send a note and let everyone know that this fixed my problem. I forgot to update it last week. THANK YOU! -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Cannot backup firewall
Hi all I'm running amanda 2.4.2p2 on a RH box as my backup server. I installed the amanda client on my (sol8) firewall on Friday, and set up a rule for the server to get to the firewall for amanda services - amcheck runs fine and reports no errors. But when my amdump kicks off at night, my report says: firewall.unter /export/home/rebecca lev 0 FAILED [could not connect to firewall.unterlaw.com] In /tmp/amanda on the firewall, I have all of the *.debug files one would expect to see # cd /tmp/amanda # ls amandad.20031117153500.debug amandad.20031119041352.debug runtar.20031120030511.debug sendbackup.20031119041352.debug amandad.20031118030502.debug amandad.20031119153507.debug selfcheck.20031117153500.debug sendbackup.20031120030744.debug amandad.20031118030754.debug amandad.20031120030511.debug selfcheck.20031118153504.debug sendbackup.20031120041558.debug amandad.20031118041513.debug amandad.20031120030744.debug selfcheck.20031119153507.debug sendsize.20031118030503.debug amandad.20031118153503.debug amandad.20031120041558.debug sendbackup.20031118030754.debug sendsize.20031119030508.debug amandad.20031119030508.debug runtar.20031118030503.debug sendbackup.20031118041513.debug sendsize.20031120030511.debug amandad.20031119030759.debug runtar.20031119030508.debug sendbackup.20031119030759.debug # vi sendbackup.20031120030744.debug sendbackup: debug 1 pid 8244 ruid 1005 euid 1005 start time Thu Nov 20 03:07:44 2003 /usr/local/libexec/sendbackup: version 2.4.2p2 sendbackup: got input request: GNUTAR /export/home/rebecca 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/ama nda/exclude.gtar; parsed request as: program `GNUTAR' disk `/export/home/rebecca' lev 0 since 1970:1:1:0:0:0 opt `|;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar;' sendbackup: exclude list file /usr/local/lib/amanda/exclude.gtar does not exist, ignoring sendbackup: try_socksize: send buffer size is 65536 sendbackup: stream_server: waiting for connection: 0.0.0.0.32886 sendbackup: stream_server: waiting for connection: 0.0.0.0.32887 sendbackup: stream_server: waiting for connection: 0.0.0.0.32888 waiting for connect on 32886, then 32887, then 32888 sendbackup: stream_accept: timeout after 30 seconds sendbackup: timeout on data port 32886 sendbackup: stream_accept: timeout after 30 seconds sendbackup: timeout on mesg port 32887 sendbackup: stream_accept: timeout after 30 seconds sendbackup: timeout on index port 32888 sendbackup: pid 8244 finish time Thu Nov 20 03:09:14 2003 The firewall is trying to do it's thing..but it can't get back to the server...what's up with that? Help! Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
RE: Permission Denied error on client
Have you checked .amandahosts for proper entries? Does that file have the proper permissions? -rw--- 1 amanda amanda37 Nov 14 13:16 .amandahosts on the client .amandahosts should say bkup.server.com amanda and on the server the entry should be client.server.com root are you using the FQDN for both server and client? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Grover Sent: Monday, November 17, 2003 3:59 PM To: [EMAIL PROTECTED] Subject: Permission Denied error on client I've not been able to get one of my clients to back up using vxdump. Another, similarly configured client has no problem. Amcheck reports the following on the bad client ... Amanda Backup Client Hosts Check ERROR: host.domain.edu: [could not access /dev/vx/rdsk/var (/dev/vx/rdsk/var): Permission denied] ERROR: host.domain.edu: [could not access /dev/vx/rdsk/rootvol (/dev/vx/rdsk/rootvol): Permission denied] Client check: 1 host checked in 1.051 seconds, 2 problems found (brought to you by Amanda 2.4.4p1) Is this a read permission error on the filesystem or an execute error on vxdump? All seems identical on both systems. Thanks JG John W Grover, Systems and Database Administrator Lake Michigan College www.lakemichigancollege.edu
lev 0 FAILED [can't switch to incremental dump]
Hi there - I'm running amanda2.4.2p2 on a RH8.0 box - the client is a RH7.2 box also running amanda2.4.2p2. The client has two disks, the first disk is partitioned in a standard way - the second disk only has one partition /docs; and docs is the only thing I want to back up. Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda5 350021 66155265795 20% / /dev/hda177750 5957 67779 9% /boot /dev/hda2 1510060 35812 1397540 3% /home /dev/hdd1 19243804 6235232 12031016 35% /docs none 63352 0 63352 0% /dev/shm /dev/hda7 147766 4153135984 3% /tmp /dev/hda8 4759544898008 3619760 20% /usr /dev/hda3 1004052 51352901696 6% /var My disklist entry looks like this: client.unterlaw.com /docs user-tar amcheck runs fine, detects no problems, but the dump didn't run... client.u /docs lev 0 FAILED [can't switch to incremental dump] Why does amanda think I'm running an incremental dump on a this partition? Also - this dump went to holding disk due to a tape error...is it just saying that it couldn't drop this to a level 1? Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
RE: lev 0 FAILED [can't switch to incremental dump]
I guess the reserve parameter is configured to 100 (the default) or only so much that the 6.2 Gbyte full dump does not fit. The reserve parameter indicates how much to reserve to full dumps on holdingdisk when dumping in degraded mode. You had a tape error, and amanda decides to degrade some or all full dumps to incrementals and continue with dumps to holdingdisk. But, because (from the context) it seems it never did a full dump, amanda can't switch to incremental, because there is no previous full dump to base the increments on. Was this what happened? I'll check on the reserve parameter - I just checked my holding disk size and it was set at 15000 MB, which this 6.2 GB full dump would not fit on the holding disk with the over 10GB from my other disks...I increased the size of my holding disk so that would not be a problem. This would have been the first time I backed up this client, so that's why I didn't totally understand the error. You are absolutely right...how can I expect it to do an incremental due to lack of holding disk space when it's never done the full level 0 Amanda is so much smarter than me. With the hopes of no media errors on the horizon, I'm sure it will work tonight. Thanks for the input.
RE: odd problem setting up amanda on Linux
Hi, I'm just starting to set up Amanda, and am having trouble. I've got two Red Hat 9 Linux boxes, one as the server, and one as a client. The server backs itself up fine. But the client is timing out. I've determined that it's connecting, but the server isn't properly ack'ing the client! I attach a log file. I'm using the RPM of Amanda, and didn't compile it myself (I can if necessary). Version is 2.4.3. Couldn't figure out how to even search for this problem on the archives of this list! It's hard to describe! Any suggestions? Thanks, -Harlan What happens when you do amcheck? Does that give you a searchable error? Or is the amcheck working and just the dump is bombing?
RE: Not again !!!
On Wednesday 06 August 2003 14:36, barryc wrote: From: Gene Heskett [EMAIL PROTECTED] Remember Kevin, its only the winderz people it bothers. Not true. Windows users are the only ones with anything to fear from these messages. It bothers (read: annoys) most of us. NOTE: For the purpose of this correspondance, most is defined as 'Some number of amanda-users subscribers, greater than or equal to two.' The definition of bother is relative I guess. Well, with the delete button only centimeters away, its not a bother to me. Now IF I was running winderz (I do not have a copy on the property) and got myself a viri, then that would 'bother' me. It amazes me how often these two running arguments are repeatedly debated...using localhost and spam to the amanda list. For the love of pete...how many sys admins does it take to beat the dead horse? (I suppose I am now guilty as well by even responding to the tirades) Maybe there needs to be something addressed to the newbie's when they register with amanda.org as a part of the welcome email that says You are responsible for your own network...the list is open to everyone and everything, please don't complain about spam, viruses, etc. I find those who are bothered to be unprepared. Get a spam server...deal with it, move on. Or maybe those complaining would like to contribute and maintain a spam/virus server for the list. This is the 4th or 5th time this year this subject has gone on for far too long. Amanda is free, the knowledge everyone gains and contributes her is free, if the price is to be 'bothered' with extra emails, then pay for some other backup utility and you won't be bothered again.
Amrecover: 500 Access not allowed
Title: Amrecover: 500 Access not allowed Hi all: Okay, so I think I've royally screwed myself, so please don't hesitate to tell me that I did. My backup server was installed and configured with a different name, because it was built online to replace an existing box. Server 1: web.isymmetrics.com; Server 2 built as webby.isymmetrics.com. Then web.isymmetrics.com went away, and webby became web and took over that IP addy, 10.1.8.9. Apparently I rolled amanda when it was still webbythough I don't remember that being the case. So now I need to amrecover a file. At first it said that it couldn't find webby. Well of course not. So I added 'webby' with the 10.1.8.9 ip addy to my /etc/hosts file on web, thinking it would be all happy. Now I get this: [EMAIL PROTECTED] libexec]# amrecover isymmdaily AMRECOVER Version 2.4.2p2. Contacting server on webby ... 220 web AMANDA index server (2.4.2p2) ready. 500 Access not allowed: [ip address 10.1.8.9 is not in the ip list for web] WHAT? It is 10.1.8.9all of the index files live on 10.1.8.9. Is there something cached somewhere with webby's name and IP that I can tinker with? HELP. Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
RE: Amrecover: 500 Access not allowed
What happens if you try 'amrecover isymmdaily -s web -t web'? Hang on, I'll try it... WHAT? It is 10.1.8.9...all of the index files live on 10.1.8.9. Is there something cached somewhere with webby's name and IP that I can tinker with? HELP. If something is cached anywhere, it's in the DNS server. Can you fiddle with that? I tried listing webby CNAME to web in the DNS...dig finds it just fine pointing to web and resolving to 10.1.8.9.
RE: Amrecover: 500 Access not allowed
What happens if you try 'amrecover isymmdaily -s web -t web'? This worked like a charm. I think I'm in. I was able to set disk and set host based on this. Where are these options listed. I had previously checked out the man page for amrecover looking for some option to set my index and tape server, but didn't see anything?!?! I should probably rebuild amanda, eh?
RE: out of tape - why?
I'm trying to do an amamda backup to a disk file. The disk I'm backing up has 3.1GB used (4GB total), while the output tape I'm writing to has a length of 5GB. It should fit, but I get the following error message in the report: FAILURE AND STRANGE DUMP SUMMARY: catwoman.b / lev 0 FAILED [out of tape] Why? I'm using amanda 2.4.4, backing up an Irix disk to a Linux amanda server. Dan What else does the report say? What is the tape size and dump size listed in the report? (i.e. Output Size (meg) 11704.411704.40.0 Tape Size (meg) 11704.911704.90.0) What does your tapetype entry look like?
UPDATE: connection timeout
Title: UPDATE: connection timeout After pressing the hardware issue with some people with more say-so, we started evaluating the hardware on the network getting the client timeout. We never got to the client itselfwe never got past the firewall. Not because of bad rules or bad routing.but because of: 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 896810035 packets input, 4090731415 bytes Received 13577 broadcasts, 339279460 runts, 0 giants, 0 throttles 339279460 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored Yeah, that's right 330 million errorsand it's not the ethernet cable or the switch portit's on the 4 port NIC in the firewall. That particular subnet is feeding off of a bad NIC in the 4 port. I can't say for sure that this is what caused my amanda failures yet, but I have a sneaking suspicion that after I rectify the NIC problem, my amanda problems will go away, too. Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
Dump too big for tape
Title: Dump too big for tape
Hi all -
Well, here I am againsame server different issue. My backups are still failing on that client with a timeout and I'm still searching to figure out why. But that's not why I'm here today. Running amanda 2.4.2p2 on a RH8 box with a seagate stand alone with 125m DDS3 12/24GB DAT tapes and hardware compression is turned off.
Report says:
These dumps were to tape isymmdaily01.
The next tape Amanda expects to use is: isymmdaily06.
FAILURE AND STRANGE DUMP SUMMARY:
www.iclear / lev 0 FAILED [mesg read: Connection timed out]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min) 0:02
Run Time (hrs:min) 3:57
Dump Time (hrs:min) 0:58 0:58 0:00
Output Size (meg) 5798.6 5787.0 11.7
Original Size (meg) 5798.6 5787.0 11.7
Avg Compressed Size (%) -- -- -- (level:#disks ...)
Filesystems Dumped 10 9 1 (1:1)
Avg Dump Rate (k/s) 1717.8 1716.1 3433.8
Tape Time (hrs:min) 1:32 1:32 0:00
Tape Size (meg) 5798.9 5787.2 11.7
Tape Used (%) 50.1 50.0 0.1 (level:#disks ...)
Filesystems Taped 10 9 1 (1:1)
Avg Tp Write Rate (k/s) 1072.5 1072.4 1102.8
FAILED AND STRANGE DUMP DETAILS:
/-- www.iclear / lev 0 FAILED [mesg read: Connection timed out]
sendbackup: start [www.iclear.com:/ level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... -
sendbackup: info end
\
NOTES:
planner: Dump too big for tape: full dump of isymmdb:/var delayed.
taper: tape isymmdaily01 kb 5938112 fm 10 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
--- --
isymmdb /etc 0 2336 2336 -- 0:04 618.6 0:01 1739.3
isymmdb /export 0 78560 78560 -- 0:21 3803.3 1:25 922.7
isymmdb /opt 0 371488 371488 -- 2:08 2911.2 5:51 1058.6
isymmdb -oracle/admin 0 2897184 2897184 -- 9:27 5107.0 44:45 1079.1
isymmdb /usr 0 695872 695872 -- 5:30 2106.8 10:45 1079.1
isymmdb /var 1 11936 11936 -- 0:03 3432.9 0:11 1102.8
web.isym /etc 0 2688 2688 -- 0:01 2700.6 0:03 809.1
web.isym /home 0 64576 64576 -- 0:03 20024.3 1:01 1055.0
web.isym /var 0 229344 229344 -- 0:17 13575.1 3:33 1078.4
www.icle / 0 FAILED ---
xfer.icl / 0 1583808 1583808 -- 39:42 664.8 24:42 1069.0
(brought to you by Amanda version 2.4.2p2)
The interesting part is that for tape size it says: 5798.9 while my estimate says 5798.6and my entry in amanda.conf for this tape says:
define tapetype Verbatim-125m {
comment Verbatim 4mm-125m DAT
length 11576 mbytes
filemark 0 kbytes
speed 1077 kbytes
}
As I look back through my reports (2 days earlier my backup was 5950.2 and it says my tape size was 5950.5) I see that my tape size is always reading .3 over my estimated dump size.
First, is this normal that my tape size never displays what it actually is.
Should I chalk this up to a media problem? When my failing client was working, I was successfully backing up 10229.2.
Any input appreciated. THANKS.
rapc
Rebecca A. Crum
Systems Administrator
Unterberg Associates, P.C.
(219) 736-5579 ext. 184
RE: Dump too big for tape
Nope, that's normal. Output Size is the size of all the dump images. Remember that amanda puts a 32KB header on each of those before they go to tape. 10 filesystems * 32KB is 320KB, or about .3 MB. QED. Yeah, output size should be fine...not even 6 gigs on a 12 gig tape that used to be backing up almost 11 successfully. That's my concern. Even with the .3 megs amanda is throwing on there, I'm not even coming close to tape end. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Dump too big for tape
Well, how big is that /var? From yesterday's report: isymmdb /var 0176096 176096 --0:59 2985.8 2:43 1079.7 -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Dump too big for tape
Yes, but how big is it today? :) Check in last night's amdump.N file (should be amdump.1) to see how big the estimate was. got result for host isymmdb disk /var: 0 - 176050K, 1 - 11830K, -1 - -1K
RE: Dump too big for tape
But from the previous mails we found out, ananda did send the estimate before timing out. So planner set all up to include 5.6 GByte from this host too. And that seems to be too much for 11976 Mbyte tape capacity. So planner degraded one of the backups, and planned an incremental one instead. I'm not even addressing the timeout issue...that just will not resolve... I'm more concerned with why my 12GB tape will not backup ~5.8GB today, when it backed up ~5.9GB last night and every night since April, when it was backing up well over 10GB. This very tape, isymmdaily01, in its last rotation, backed up 5923MB. What I'm trying to find out is why 5.6 GB 'seems to be too much for the 11976 Mbyte tape capacity'. If it's a media error, I'll pull the tape...I'm asking if this could be indicative of something else. Completely aside: I would have expected a message named hostname diskname lev 0 FAILED [blabla] Any idea why the hostname is _www.iclear_ file://www.iclear in the message amanda sends you? I guess I always assumed that it was cutting the .com off of the www.iclear.com due to some reporting constraint. My disklist entry says: www.iclear.com / user-tar for that client. Sendbackup is looking for the right client: /-- www.iclear / lev 0 FAILED [mesg read: Connection timed out] sendbackup: start [www.iclear.com:/ level 0] And all of the information I sent you in those reports last week has the server going to the client and getting estimates...it's timing out after that, so it appears to know where it's going, it just can't complete it's mission (even though it chose to accept it), and it's self-destructing.
RE: Dump too big for tape
Ah, but what Pual is saying is that they're related. If you add up what did get backed up plus the disk that failed with the data timeout (but got an estimate), you're at capacity. So the full of that /var wouldn't fit, so amanda degraded it. Athe light is getting brighter, I'm walking towards it. This whole disk failing thing is causing more and more nonsense. I moved it back to it's old backup method for now, removing it from my amanda disklist, so I can get a solid level 0 of everything and sleep well. I just keep praying these boxes will go away soon. I don't have the resources or approval to test if that client is failing due to hardware issues. We dumped this company a year ago and I still can't shake them. It's my own little version of SARS.
RE: Dump too big for tape
But before timing out, planner got already an estimate. Look in the amdump file. It took 5.6+ Gbyte in its estimate from www.iclear.com plus the 5.9 Gbyte from the others plus 150 Mbyte from /var. And that total amount is over your estimated tapecapacity. So planner decided to switch one filesystem to an incremental one before even starting the backups themselves. It does not know that www.iclear.com will time out. When the backup was started, www.iclear.com timed out, just as always, but planner had already given instructions to the driver. Driver does not come back on the schedule delivered by planner to notice that suddenly, because some other dump failed, it has enough room on the tape to do a full instead of an incremental. Look (or post) the amdump file from that run, and notice the schedule planner generated. I get it now...it makes sense now that I see it on paper...but I wasn't thinking about it that way. (argh) Tunnel vision - sorry...
RE: amrecover problem
Hello, I setup Amanda for the first time and there is problem with amrecover. Only some of the directories and files dumped to the tape are listed in amrecover. The index files looks strange: 07664670563/./ 07664670563/./.ICAClient/ 07664670563/./.acrobat/ 07664670563/./.b3tools/ 07664670563/./.dt/ 07664670563/./.dt/Desktop/ 07664670563/./.dt/Trash/ 07664670563/./.dt/appmanager/ 07664670563/./.dt/help/ . . . Entries in the index file without these numbers can be listed in amrecover. The first dump of this user disk was a level 0 dump with GNUTAR and the capacity of the tape was sufficient, so everthing is dumped to the tape, but I cannot restore it. HINT: you are using a bad version of tar. If you believe you have a good version...be sure that you configured amanda with-gnutar=/your/path/to/non-sucky/tar. As an extra hint, you can tell by looking at the config.cache file and see what your ac_cv_path_GNUTAR entry is. If you are desperate to amrecover something from this dump, let me know...I may still have my notes on how to clean up this index mess and still recover from it. I have done it before thanks to help from John Jackson.
RE: Xinetd not starting amanda
Hallo all
when checking if amanda is listening on the correct ports.
netstat -a | grep -i amanda
any ideas how I can trouble shoot further?
According to me evereything there must work
Can you do a chkconfig --list and see the amanda services listed under xinetd based
services and are they turned on? Do you have amanda, amandaidx and amidxtape files in
your xinetd.d directory, and do they all look something like this (respectively):
service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
protocol= tcp
socket_type = stream
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
protocol= tcp
socket_type = stream
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
And the amanda services are listed in /etc/services? What version of RedHat are you
using?
RE: Help With Restore
I'm trying to restore a directory on one of our servers. First, I want the directory to reside in a temporary location before I move it to its original location. I ran the following command in the temp location: amrestore /dev/nst0 hostname /.1/shares Now I have a file in my temp directory named hostname._.1_shares.20030206.0. I've tried to tar it to expand the contents but the server just sits there, even when running tar overnight. I used: tar xvpS hostname._.1_shares.20030206.0 What am I doing wrong? I need to be able to pull a certain directory out and trash the rest. Any help will be appreciated. It's been my understanding that you can only use amrecover for individual files, and amrestore for entire filesystems. (I could be wrong) And in order to use amrecover, you have to have your dumptype index parameter set to yes somewhere in your config. Also, you need to have amindexd and amidxtaped installed. try: # amrecover configname you should see come connection information and then an amrecover prompt. from here you can set the date, the host, the disk. You can cd and ls within the amrecover session and then add the file, once it's added then extract. NOTE: wherever you are at the time in which you amrecover is where the file will restore. Hope this helps...good luck.
RE: Two more amanda questions
1) This morning, my amanda report said: These dumps were to tape Indyme010. The next tape Amanda expects to use is: a new tape. Instead of The next tape Amanda expects to use is: Indyme011. Here's the tapelist: 20030226 Indyme010 reuse 20030225 Indyme009 reuse 20030221 Indyme008 reuse 20030220 Indyme007 reuse 20030219 Indyme006 reuse 20030218 Indyme005 reuse 20030215 Indyme004 reuse 20030214 Indyme003 reuse 20030213 Indyme002 reuse 20030212 Indyme001 reuse 0 Indyme013 reuse 0 Indyme012 reuse 0 Indyme011 reuse There was a 014 and 015 in there, but I deleted them so, afetr this week, it would go back to using 001 on Monday. snip When did you label 011-013? Not to panic...those tapes haven't been used yet...as long as your tapecycle lists at least 13 tapes, it will take Indyme011 no problem. Then once it's been used and listed in the tapelist with a date, amanda will expect it after Indyme010. Pop it in and run amcheck...you'll see it's okay.
RE: dummy subscribe message again
Yes, I received it again as well.
RE: Re-registering?
Has anyone else already on the list gotten the message that Someone (possibly you) has requested that your email address be added? It is dated today. Yes, I have, I was wondering about it myself...
Tape running out of space, NOT possible
Hi all -
I have amanda 2.4.2p2 running on a RH 7.3 box with a Quantum SuperDLT 110GB tape
drive. I am currently sending 11-13GB to this drive depending on the day...
amanda is telling me my dump is too big and degrading my level 0's to level 1! How is
this possible? I run amdump from a script called by cron and have for some time. The
first line in my script rewinds the tape, just in case. I have tried multiple tapes,
so I don't believe it is a media issue. Here is my amdump report:
These dumps were to tape uamonthly200301.
The next tape Amanda expects to use is: uamonthly200301.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:03
Run Time (hrs:min) 1:01
Dump Time (hrs:min)0:55 0:54 0:00
Output Size (meg) 11552.611507.8 44.8
Original Size (meg) 11552.611507.8 44.8
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 15 10 5 (1:5)
Avg Dump Rate (k/s) 3608.1 3614.8 2444.7
Tape Time (hrs:min)0:19 0:19 0:00
Tape Size (meg) 11553.111508.2 44.9
Tape Used (%) 99.8 99.40.4 (level:#disks ...)
Filesystems Taped15 10 5 (1:5)
Avg Tp Write Rate (k/s) 10417.310525.0 2878.3
NOTES:
planner: Last full dump of slaw:/usr on tape overwritten in 1 run.
planner: Last full dump of slaw:/home on tape overwritten in 1 run.
planner: Last full dump of spork.unterlaw.com:/export/home on tape overwritten in 1
run.
planner: Last full dump of spork.unterlaw.com:/usr on tape overwritten in 1 run.
planner: Last full dump of spork.unterlaw.com:/u05/oracle/admin/ua on tape
overwritten in 1 run.
planner: Last full dump of spork.unterlaw.com:/u05/oracle/admin/testua on tape
overwritten in 1 run.
planner: Last full dump of spork.unterlaw.com:/var on tape overwritten in 1 run.
planner: Last full dump of smores.unterlaw.com:/usr on tape overwritten in 1 run.
planner: Last full dump of smores.unterlaw.com:/opt on tape overwritten in 1 run.
planner: Last full dump of smores.unterlaw.com:/export/home on tape overwritten in
1 run.
planner: Last full dump of smores.unterlaw.com:/etc on tape overwritten in 1 run.
planner: Last full dump of smores.unterlaw.com:/var on tape overwritten in 1 run.
planner: Last full dump of weber.unterlaw.com:/usr on tape overwritten in 1 run.
planner: Last full dump of weber.unterlaw.com:/opt on tape overwritten in 1 run.
planner: Last full dump of weber.unterlaw.com:/var on tape overwritten in 1 run.
planner: Incremental of weber.unterlaw.com:/var bumped to level 2.
planner: Dump too big for tape: full dump of slaw:/home delayed.
planner: Dump too big for tape: full dump of spork.unterlaw.com:/var delayed.
planner: Dump too big for tape: full dump of smores.unterlaw.com:/var delayed.
planner: Dump too big for tape: full dump of smores.unterlaw.com:/opt delayed.
planner: Dump too big for tape: full dump of spork.unterlaw.com:/usr delayed.
taper: tape uamonthly200301 kb 11830368 fm 15 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
slaw /home 11184 1184 --0:003792.9 0:011187.5
slaw /usr0 692672 692672 --3:453083.4 0:5612399.8
smores.unter /etc02400 2400 --0:011713.4 0:03 847.8
smores.unter -xport/home 0 14187521418752 --8:472693.6 1:4113983.4
smores.unter /opt1 34976 34976 --0:113233.3 0:103381.3
smores.unter /usr0 464576 464576 --3:96.3 0:2916027.7
smores.unter /var16464 6464 --0:041564.9 0:015722.3
spork.unterl -xport/home 0 15429761542976 --6:273982.5 1:2617908.4
spork.unterl -min/testua 0 18540481854048 --6:005156.1 3:069981.8
spork.unterl -e/admin/ua 0 43280324328032 -- 13:565175.1 6:5510435.5
spork.unterl /usr11216 1216 --0:02 529.6 0:02 711.7
spork.unterl /var12016 2016 --0:011675.4 0:021188.5
weber.unterl /opt0 17056 17056 --0:053723.8 0:0210528.9
weber.unterl /usr0 198272 198272 --1:092873.6 0:563546.9
weber.unterl /var0 12652481265248 -- 10:481952.6 3:066791.8
(brought to you by Amanda version 2.4.2p2)
Any ideas?
Rebecca A. Crum
Systems Administrator
Unterberg Associates, P.C.
(219) 736-5579 ext. 184
OMG, someone get me a vacation: Tape running out of space, NOT possible
Sure looks like your tapetype entry is telling amanda your tapes are about 11.6GB long. Are you sure the tapetype length is not just off 10X? Yes, Jay...as a matter of fact, it IS off 10X. I thought I checked that, but I checked the wrong conf file, so once again, I've emailed this group because I can't get it together. I must have copied an old one. Apologies to everyone...the next round's on me. Thank you for forcing me to do an idiot-check on myself and all of my configuration files.
amcheck not returning anything
Hi all...I have been using amanda for quite some time and never encountered this problem before... Installed 2.4.2p2 on a RH8.0 box... When I run su amanda -c amcheck isymmdaily I just get the prompt back at me. No errors in /var/log/messages, nothing in /tmp/amanda. Very strange. xinetd is configured and showing my 3 amanda services in chkconfig --list .amandahosts is configured /etc/hosts looks good Permissions on /tmp/amanda look good, permissions on /usr/local/etc/amanda/isymmdaily look good. I don't get it...I've got nothing to look at and tell me what is going on!! HELP. Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
Nevermind: amcheck not returning anything
I'm a moron...apparently I gave amanda /bin/false when I set her up as a user. She doesn't like that. Please disregard. -Original Message- From: Rebecca Pakish Crum Sent: Monday, February 10, 2003 5:20 PM To: Amanda Users (E-mail) Subject: amcheck not returning anything Hi all...I have been using amanda for quite some time and never encountered this problem before... Installed 2.4.2p2 on a RH8.0 box... When I run su amanda -c amcheck isymmdaily I just get the prompt back at me. No errors in /var/log/messages, nothing in /tmp/amanda. Very strange. xinetd is configured and showing my 3 amanda services in chkconfig --list .amandahosts is configured /etc/hosts looks good Permissions on /tmp/amanda look good, permissions on /usr/local/etc/amanda/isymmdaily look good. I don't get it...I've got nothing to look at and tell me what is going on!! HELP. Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
Tape error problems
I've been successfully using amanda for over a year now and all of a sudden it's all screwed up! I'm using amanda 2.4.2p2 on a RH7.2 box. amcheck is happy when it runs daily at 3 pm before I leave: Amanda Tape Server Host Check - Holding disk /dumps/amanda: 13770716 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape isymmdaily09 label ok Server check took 10.881 seconds Amanda Backup Client Hosts Check Client check: 3 hosts checked in 0.273 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) But that same night when my cron job tried to kick off the backup: *** A TAPE ERROR OCCURRED: [rewinding tape: No medium found]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: isymmdaily09. And yes, the tape is in the drive. It's still in there now, hasn't been touched. This has happened to me almost every day for the last week. So it's not just this tape. I've cleaned the drive, turned the drive off, bounced the box...all of the little things. Thoughts? Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
RE: Tape error problems
Yes and yes. It gets curiouser and curiouser. -Original Message- From: Martin Hepworth [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 22, 2003 8:57 AM To: Amanda Users (E-mail) Subject: Re: Tape error problems Rebecca Pakish Crum wrote: I've been successfully using amanda for over a year now and all of a sudden it's all screwed up! I'm using amanda 2.4.2p2 on a RH7.2 box. amcheck is happy when it runs daily at 3 pm before I leave: Amanda Tape Server Host Check - Holding disk /dumps/amanda: 13770716 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape isymmdaily09 label ok Server check took 10.881 seconds Amanda Backup Client Hosts Check Client check: 3 hosts checked in 0.273 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) But that same night when my cron job tried to kick off the backup: *** A TAPE ERROR OCCURRED: [rewinding tape: No medium found]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: isymmdaily09. And yes, the tape is in the drive. It's still in there now, hasn't been touched. This has happened to me almost every day for the last week. So it's not just this tape. I've cleaned the drive, turned the drive off, bounced the box...all of the little things. Thoughts? Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184 Does amcheck see the tape? can the amanda backup user access the tape drive? -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
RE: Tape error problems
Yes, it has a light...and sometimes it comes on and sometimes it doesn't. After this happened a couple of times I cleaned it even though the light wasn't on. -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 22, 2003 1:00 PM To: Rebecca Pakish Crum; Amanda Users (E-mail) Subject: Re: Tape error problems On Wednesday 22 January 2003 09:17, Rebecca Pakish Crum wrote: I've been successfully using amanda for over a year now and all of a sudden it's all screwed up! I'm using amanda 2.4.2p2 on a RH7.2 box. amcheck is happy when it runs daily at 3 pm before I leave: Amanda Tape Server Host Check - Holding disk /dumps/amanda: 13770716 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape isymmdaily09 label ok Server check took 10.881 seconds Amanda Backup Client Hosts Check Client check: 3 hosts checked in 0.273 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) But that same night when my cron job tried to kick off the backup: *** A TAPE ERROR OCCURRED: [rewinding tape: No medium found]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: isymmdaily09. And yes, the tape is in the drive. It's still in there now, hasn't been touched. This has happened to me almost every day for the last week. So it's not just this tape. I've cleaned the drive, turned the drive off, bounced the box...all of the little things. Thoughts? Does this drive have an led on it that indicates when it needs cleaning? (mine does) And does it come back on very quickly after the cleaning operation has been done? If so, then it sounds as if the drive needs a trip to the maker for refurbishing. Or an outright replacement if you have outgrown it. Otherwise has anythng else in the data cableing and so on been touched at about the time this started? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly
RE: Backup Oracle
I use amanda to back up oracle. Basically I backup the cold backups that oracle does on it's own. I've restored from it as well. It's clean. I've never tried to just back up individual tables. In my opinion, oracle wouldn't restore cleanly that way no matter what was backing it up. Oracle likes to restore from it's own backups. -Original Message- From: Aline [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 6:42 AM To: [EMAIL PROTECTED] Subject: Backup Oracle Hi, I would like to use the Amanda Software in order to make backup of some oracle's tables. Is it possible? Is it good? Thanks, Aline __ E-mail Premium BOL Antivírus, anti-spam e até 100 MB de espaço. Assine já! http://email.bol.com.br/
RE: help
Post your question with as many details as you can about what version you are using, what your problems are and what you're trying to achieve. It always helps to make your subject line meaningful to the question. Good luck. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Sent: Monday, December 09, 2002 11:21 PMTo: [EMAIL PROTECTED]Subject: helpCan anyone offer me some assistance? im really new to this whole mailist sort of thing and im not sure if im doing this right
Backing up over different subnets, domains
Has anyone had to back up with amanda using different subnets, different domains? I'm getting errors, and I realize it's not amanda's problem...but I was wondering if anyone had any experience with it? I'm getting an amandad.xxx.debug file in /tmp/amanda on the client, so clearly the communication from the backup server to the client is running, but then I get a hostname lookup error, so what's actually failing? DNS? A firewall issue? Anyone have any clues? Backup server is RH7.2 running amanda2.4.2p2, client is solaris 2.6 running amanda2.4.2p2 as well. amandad.xxx.debug: amandad: debug 1 pid 9243 ruid 1003 euid 1003 start time Tue Dec 3 14:45:22 2002 amandad: version 2.4.2p2 amandad: build: VERSION=Amanda-2.4.2p2 amandad:BUILT_DATE=Tue Dec 3 10:50:50 CST 2002 amandad:BUILT_MACH=SunOS www 5.6 Generic_105181-21 sun4u sparc SUNW,Ultra-60 amandad:CC=gcc amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/dsk/ amandad:RDEV_PREFIX=/dev/rdsk/ DUMP=/usr/sbin/ufsdump amandad:RESTORE=/usr/sbin/ufsrestore GNUTAR=/usr/local/bin/tar amandad:COMPRESS_PATH=/opt/OSE/bin/gzip amandad:UNCOMPRESS_PATH=/opt/OSE/bin/gzip MAILER=/bin/mailx amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=web.isymmetrics.com amandad:DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=web.isymmetrics.com amandad:DEFAULT_TAPE_DEVICE=/dev/rmt/0bn HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc got packet: Amanda 2.4 REQ HANDLE 000-E0A70708 SEQ 1038949202 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR / 0 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; sending ack: Amanda 2.4 ACK HANDLE 000-E0A70708 SEQ 1038949202 amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-E0A70708 SEQ 1038949202 ERROR [addr xxx.xxx.xxx.xxx: hostname lookup failed] amandad: got packet: Amanda 2.4 ACK HANDLE 000-E0A70708 SEQ 1038949202 Any help would be greatly appreciated... Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
NEVERMIND: Backing up over different subnets, domains
Entry for backup server in client /etc/hosts fixed the problem...I had a brain hemorrhage for a moment. -Original Message- From: Rebecca Pakish Crum Sent: Tuesday, December 03, 2002 4:18 PM To: Amanda Users (E-mail) Subject: Backing up over different subnets, domains Has anyone had to back up with amanda using different subnets, different domains? I'm getting errors, and I realize it's not amanda's problem...but I was wondering if anyone had any experience with it? I'm getting an amandad.xxx.debug file in /tmp/amanda on the client, so clearly the communication from the backup server to the client is running, but then I get a hostname lookup error, so what's actually failing? DNS? A firewall issue? Anyone have any clues? Backup server is RH7.2 running amanda2.4.2p2, client is solaris 2.6 running amanda2.4.2p2 as well. amandad.xxx.debug: amandad: debug 1 pid 9243 ruid 1003 euid 1003 start time Tue Dec 3 14:45:22 2002 amandad: version 2.4.2p2 amandad: build: VERSION=Amanda-2.4.2p2 amandad:BUILT_DATE=Tue Dec 3 10:50:50 CST 2002 amandad:BUILT_MACH=SunOS www 5.6 Generic_105181-21 sun4u sparc SUNW,Ultra-60 amandad:CC=gcc amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/dsk/ amandad:RDEV_PREFIX=/dev/rdsk/ DUMP=/usr/sbin/ufsdump amandad:RESTORE=/usr/sbin/ufsrestore GNUTAR=/usr/local/bin/tar amandad:COMPRESS_PATH=/opt/OSE/bin/gzip amandad:UNCOMPRESS_PATH=/opt/OSE/bin/gzip MAILER=/bin/mailx amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=web.isymmetrics.com amandad:DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=web.isymmetrics.com amandad:DEFAULT_TAPE_DEVICE=/dev/rmt/0bn HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc got packet: Amanda 2.4 REQ HANDLE 000-E0A70708 SEQ 1038949202 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR / 0 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; sending ack: Amanda 2.4 ACK HANDLE 000-E0A70708 SEQ 1038949202 amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-E0A70708 SEQ 1038949202 ERROR [addr xxx.xxx.xxx.xxx: hostname lookup failed] amandad: got packet: Amanda 2.4 ACK HANDLE 000-E0A70708 SEQ 1038949202 Any help would be greatly appreciated... Rebecca A. Crum Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
RE: file not found on Tape
What do you see when you run this command as root: su amanda -c amadmin configname find clientcomputername filenameyouwanttorestore Is it, in fact, listed as being backed up to the tape you're using? Is the tape rewound? (sounds stupid, but this has gotten me before...) Is this dump or tar? If tar, are you using a good version? A crappy version of tar leaves gibberish in your index file and it won't give you an error on backup and it won't find file on restore. -Original Message- From: Jon LaBadie [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 12:09 PM To: [EMAIL PROTECTED] Subject: Re: file not found on Tape On Wed, Nov 27, 2002 at 12:55:58PM -0500, Axel Haenssen wrote: Hi Guys, I am running amanda on a linux cluster. The backup reports no errors but when I try to restore amanda tells me that the requested file is not on the tape (It should be there since I can see it with the ls command under amrecover). Following is the amidxtaped.debug report: amidxtaped: debug 1 pid 4738 ruid 33 euid 33 start time Wed Nov 27 11:06:18 2002 amidxtaped: version 2.4.3b3 SECURITY USER root bsd security: remote host localhost.localdomain user root local user amanda amandahosts security check passed 6 amrestore_nargs=6 -h -p /dev/nst0 node16 ^/home$ 20021123 Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = amrestore argv[1] = -h argv[2] = -p argv[3] = /dev/nst0 argv[4] = node16 argv[5] = ^/home$ argv[6] = 20021123 amrestore: 0: skipping start of tape: date 20021123 label DMP004 amrestore: 1: skipping node9._scratch.20021123.1 amrestore: 2: skipping node12._scratch.20021123.1 amrestore: 3: skipping node14._scratch.20021123.1 amrestore: 4: skipping node2._scratch.20021123.1 amrestore: 5: skipping node6._scratch.20021123.1 amrestore: 6: skipping node17._scratch.20021123.1 amrestore: 7: skipping node7._scratch.20021123.1 amrestore: 8: skipping node8._scratch.20021123.2 amrestore: 9: skipping node11._scratch.20021123.1 amrestore: 10: skipping node13._scratch.20021123.1 amrestore: 11: skipping node5._scratch.20021123.1 amrestore: 12: skipping node10._scratch.20021123.1 amrestore: 13: skipping node4._scratch.20021123.2 amrestore: 14: skipping node3._scratch.20021123.2 amrestore: 15: restoring node16._home.20021123.0 incomplete distance tree gzip: stdin: invalid compressed data--format violated Error 32 (Broken pipe) offset 1150746624+32768, wrote 0 amrestore: pipe reader has quit in middle of file. amidxtaped: amrestore terminated normally with status: 2 Rewinding tape: done amidxtaped: pid 4738 finish time Wed Nov 27 12:08:57 2002 What went wrong? Do you use multiple tapes per run? If so, maybe this is the last file attempted for this tape before it filled. In that case, I think the complete file would be the first file on the next tape. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: file not found on Tape
Okay, that was my mistake...I forgot you can't find individual files listed...just the disks you wanted to do su amanda -c amadmin configname find clientcomputername disk ...that was my fault. So it looks like your last level 0 was to DMP004 on 11-23, has the file changed since then? Would it have been on the DMP005 or DMP006 tapes level 1? Can you cut and paste the output of amrecover? What version of gnu-tar comes with RH7.1? Can you do tar --version and tell me what you see? -Original Message- From: Axel Haenssen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 2:04 PM To: Rebecca Pakish Crum Subject: RE: file not found on Tape On Wed, 2002-11-27 at 13:54, Rebecca Pakish Crum wrote: What do you see when you run this command as root: su amanda -c amadmin configname find clientcomputername filenameyouwanttorestore If I do su amanda -c amadmin DailySet1 find node16 /home I get Scanning /home/amanda... 20020620: found Amanda directory. 20020705: found Amanda directory. 20020706: found Amanda directory. 20020910: found Amanda directory. date host disk lv tape or file file status 2002-09-10 node16 /home 2 /home/amanda/20020910/node16._home.20 OK 2002-11-14 node16 /home 1 DMP007 14 OK 2002-11-15 node16 /home 2 DMP008 14 OK 2002-11-16 node16 /home 2 DMP009 14 OK 2002-11-19 node16 /home 2 DMP010 13 OK 2002-11-20 node16 /home 2 DMP001 13 OK 2002-11-21 node16 /home 3 DMP002 14 OK 2002-11-22 node16 /home 3 DMP003 13 OK 2002-11-23 node16 /home 0 DMP004 15 OK 2002-11-26 node16 /home 1 DMP005 14 OK 2002-11-27 node16 /home 1 DMP006 14 OK Amanda is set to backup the /home directory on this machine If I do su amanda -c amadmin Dailyset find node16 /home/axel/boot.img I get Scanning /home/amanda... 20020620: found Amanda directory. 20020705: found Amanda directory. 20020706: found Amanda directory. 20020910: found Amanda directory. No dump to list boot.img the file I wanted to restore Is it, in fact, listed as being backed up to the tape you're using? Is the tape rewound? (sounds stupid, but this has gotten me before...) Is this dump or tar? If tar, are you using a good version? A crappy version of tar leaves gibberish in your index file and it won't give you an error on backup and it won't find file on restore. I think tar, oehm, and I use gnu-tar standard on RedHat Linux 7.1 Thanks Axel -- Axel Haenssen Department of Ecology Evolutionary Biology Princeton University Princeton, NJ 08540 USA phone: +1-609-258-6999 email: [EMAIL PROTECTED] find my public key at: www.princeton.edu/~axel
RE: tape error
No, actually I think it means it's not rewound (Is this a word? Bah!). Try doing an mt -f /dev/nst0 rewind and then run an amcheck on that tape and see if it's happy. -Original Message- From: John Koenig [mailto:[EMAIL PROTECTED]] Sent: Friday, September 13, 2002 1:56 PM To: [EMAIL PROTECTED] Subject: tape error Anyone seen this tape error message before? Does this indicate a bad tape or a tape wherein the AMANDA label has been inadvertently removed? thanks, J ### Subject: DailySet2 AMFLUSH MAIL REPORT FOR September 13, 2002 *** A TAPE ERROR OCCURRED: [reading label: No space left on device]. ^^ -- *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.265187 secs) *** Qmail-Scanner Envelope Details End ***
RE: hi
ENOUGH ALREADY... Take this battle off list, please. -Original Message- From: Dave Sherohman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 10, 2002 12:08 PM To: [EMAIL PROTECTED] Subject: Re: hi On Tue, Sep 10, 2002 at 04:08:22PM +0100, Spicer, Kevin wrote: One possibility is to allow anonymous users to post through a web page, but only list members to post via email. If a non-member attempts to post via email they should recieve a polite bounce referring them to the website. Seems reasonable, provided that the web page is suffficiently intelligent to allow nonsubscribers to respond to any replies they receive without breaking threading (and, preferably, with quoting). Some questions require the submission of additional information, etc.
RE: added gnutar after install
You need to recompile...and for added umph, I'd use the --with-gnutar=/path/to/tar option with my .config file just in case my path is screwy or I have multiple versions of tar hanging around on that box. Make sure to make clean, make distclean and check that config.cache is empty. Then .config again... -Original Message- From: Marvin Davenport [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 2:45 PM To: [EMAIL PROTECTED] Subject: added gnutar after install help... I added gtar after install and now I get an error [GNUTAR Program not available] can I setup gnutar after client install or do I have to reinstall? __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com
RE: C Compiler cannot create executables
I was also getting some advice from Jon LaBadie about which gcc pkg I used. I downloaded from sunfreeware, as I have done in the past but it wasn't working. I used the version from the companion cd, and on pkgadd, it listed 3 different dependencies I was missing, the gnu common pkg, a header pkg and an archived lib pkg. I installed all of those and voila! I can now ./config amanda... Thanks to all for your suggestions. I tried everything anyone threw my way. Just to add a little to Joshua's and Scott Sanders' recommendations, which are excellent. Rebecca, try looking at your config.log to see what error is created when configure attempted to test gcc. I have run into a situation with an incomplete Solaris 8 installation in which certain object files (used by both Sun's C compiler and gcc) where not installed. Consequently, compilation fails. These referenced object files reside in /usr/lib and /usr/ccs/lib with names values-Xa.o, values-Xc.o, values-Xs.o, values-Xt.o and values-xpg4.o.
C Compiler cannot create executables
Hi all...
Trying to build amanda on a new sparc-sol8 box. Downloaded pkgs for make and
gcc from sunfreeware and installed them with your basic pkgadd -d pkg-name
command they seemed to install no problem.
# which gcc
/usr/local/bin/gcc
# echo $PATH
/usr/local/bin:/usr/local:/usr/local/sbin:/usr/sbin:/usr/bin
On ./configure, however, I get this:
# ./configure --with-user=amanda --with-group=sys --without-server
--with-amandahosts --with-tape-server=slaw.unterlaw.com --with
creating cache ./config.cache
checking host system type... sparc-sun-solaris2.8
checking target system type... sparc-sun-solaris2.8
checking build system type... sparc-sun-solaris2.8
checking cached system tuple... ok
checking for a BSD compatible install... config/install-sh -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for non-rewinding tape device... /dev/null
checking for raw ftape device... /dev/null
checking for Kerberos and Amanda kerberos4 bits... no
checking for gcc... gcc
checking whether the C compiler (gcc ) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
What is happening with this compiler...I used gcc-2.95.3-sol8-sparc-local, I
thought this was a stable release, am I wrong? I'm pretty sure I've used it
before...
Rebecca A. Pakish
Systems Administrator
Unterberg Associates, P.C.
(219) 736-5579 ext. 184
tape out of space??
Hi all
I have been using amanda 2.4.2p2 on my 7.2 RH server for quite some time now
backing up both linux and solaris clients.
Today something strange happened...
a tape that has been in rotation and working properly all of sudden ran out
of space?
The last time I used this tape the stats showed:
These dumps were to tape dailytape03.
The next tape Amanda expects to use is: dailytape04.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 3:04
Dump Time (hrs:min)0:39 0:39 0:00
Output Size (meg) 11082.411082.40.0
Original Size (meg) 11082.411082.40.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped 14 14 0
Avg Dump Rate (k/s) 4852.5 4852.5--
Tape Time (hrs:min)3:02 3:02 0:00
Tape Size (meg) 11082.911082.90.0
Tape Used (%) 95.7 95.70.0
Filesystems Taped14 14 0
Avg Tp Write Rate (k/s) 1037.5 1037.5--
This time the stats showed:
These dumps were to tape dailytape03.
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: dailytape04.
FAILURE AND STRANGE DUMP SUMMARY:
in-db3.unt /etc lev 1 FAILED [no estimate]
in-db3.unt /export/home lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 3:12
Dump Time (hrs:min)0:41 0:41 0:00
Output Size (meg) 11574.111565.78.4
Original Size (meg) 11574.111565.78.4
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 13 8 5 (1:5)
Avg Dump Rate (k/s) 4827.4 4831.4 2264.7
Tape Time (hrs:min)1:55 1:54 0:00
Tape Size (meg) 6808.3 6799.78.6
Tape Used (%) 58.8 58.70.1 (level:#disks ...)
Filesystems Taped12 7 5 (1:5)
Avg Tp Write Rate (k/s) 1013.5 1013.7 882.1
As you can see my tape size was cut in half all of a sudden. I haven't made
any changes to the configuration or drive...
Maybe it's just a media error...but I wanted to throw it out here just in
case.
Any insight is much appreciated...
Thanks and have a great day. :)
Rebecca A. Pakish
Systems Administrator
Unterberg Associates, P.C.
(219) 736-5579 ext. 184
RE: getting further
Your version of tar is broken...get the latest from ftp://alpha.gnu.org/gnu/tar/ . You want 1.13.19 or later. -Original Message- From: Mike Heller [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 11:57 AM To: [EMAIL PROTECTED] Subject: getting further I am getting further with Amanda. I ran a backup last night but had a problem: error [/bin/tar returned 2] This problem has come up in the past (searched the group) but there seems to be no specific reason for this. I'm using tar version: tar (GNU tar) 1.13.11 I'm trying to backup: /boot always-full / comp-root-tar /bigcomp-root-tar With the result: DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - 216.13.244.1 / 0 FAILED --- 216.13.244.1 /big0 1216126011274432 92.7 144:011304.7 144:021304.7 216.13.244.1 /boot 0 14560 14592 --0:027555.8 0:111374.2 I'm not exactly sure why I can backup two partitions but not the third (root). Is this a permissions issue? I exclude the following: ./mnt ./proc ./no_backup ./backup ./download ./usr/doc ./usr/man ./usr/src ./var/spool/mqueue Thanks for any help or direction you can provide. Mike
Hmmmm...all of a sudden I'm strange
Which wouldn't be so shocking, if it were just me. But it's my amanda backup report, and that makes me uncomfortable. Is this something to worry about? I can see the index file in question, and it looks okay. What's the deal with the .tmp? FAILED AND STRANGE DUMP DETAILS: /-- slaw /home lev 0 STRANGE sendbackup: start [slaw:/home level 0] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gtar -f... - sendbackup: info end ? gtar: ./amanda/uadaily/index/in-db2.unterlaw.com/_var_www/20020608_0.gz.tmp: Warning: Cannot stat: No such file or directory | Total bytes written: 15011840 (14MB, 3.6MB/s) sendbackup: size 14660 sendbackup: end \ Rebecca A. Pakish Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
Amrecover connection refused - again!
Hello all, I know this topic was just covered, but the answers really don't seem to be helping me. I've been running amanda for almost a year now, and have been indexing and successfully recovering individual files. All of a sudden I'm getting this error: [root@ants root]# amrecover uadaily AMRECOVER Version 2.4.2p2. Contacting server on slaw.unterlaw.com ... amrecover: cannot connect to slaw.unterlaw.com: Connection refused ***amrecover debut says: amrecover: debug 1 pid 8047 ruid 0 euid 0 start time Mon Jun 3 08:21:40 2002 amrecover: stream_client: connect(10082) failed: Connection refused cannot connect to slaw.unterlaw.com: Connection refused amrecover: pid 8047 finish time Mon Jun 3 08:21:40 2002 In previous posts they said something about 10082 port not running. I haven't changed a thing on my /etc/xinetd.d/amanda file. I did recently change tape drives, but that shouldn't have anything to do with it, should it??? I restarted xinetd just in case and it gave no errors on restart. Oh! Amanda 2.4.2p2 on RH7.2... Any suggestions would be appreciated. Thanks, rap Rebecca A. Pakish Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
RE: Amrecover connection refused - again!
That's not the file you're looking for. I believe it's
/etc/xinetd.d/amandaidx that allows amrecover to work remotely.
I don't have that file...I have a file /etc/xinetd.d/amanda that looks like
this...
service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
protocol= tcp
socket_type = stream
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
protocol= tcp
socket_type = stream
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
I get the same error when I try to run amrecover on the amanda server, as
well, so it's not a remote issue.
You'll also need to make sure that the service is allowed in
/etc/hosts.allow
(it's amindexd) on slaw from ants.
I currently don't have anything in /etc/hosts.allow, but I never have, and
I've run amrecover before. (?) What do I need to add, just a line that says
amindexd?
rap
RE: Amrecover connection refused - again!
I've got wait=no there, but I don't know that that is your issue. There's a reason I have wait=yes, but for the life of me I can't remember what it is. What's the output of 'chkconfig --list'? [root@slaw etc]# chkconfig --list keytable0:off 1:on2:on3:on4:on5:on6:off atd 0:off 1:off 2:off 3:on4:on5:on6:off kdcrotate 0:off 1:off 2:off 3:off 4:off 5:off 6:off syslog 0:off 1:off 2:on3:on4:on5:on6:off gpm 0:off 1:off 2:on3:on4:on5:on6:off kudzu 0:off 1:off 2:off 3:on4:on5:on6:off sendmail0:off 1:off 2:on3:on4:on5:on6:off netfs 0:off 1:off 2:off 3:on4:on5:on6:off network 0:off 1:off 2:on3:on4:on5:on6:off random 0:off 1:off 2:on3:on4:on5:on6:off rawdevices 0:off 1:off 2:off 3:on4:on5:on6:off apmd0:off 1:off 2:on3:on4:on5:on6:off ipchains0:off 1:off 2:on3:on4:on5:on6:off iptables0:off 1:off 2:on3:on4:on5:on6:off crond 0:off 1:off 2:on3:on4:on5:on6:off anacron 0:off 1:off 2:on3:on4:on5:on6:off lpd 0:off 1:off 2:on3:on4:on5:on6:off xfs 0:off 1:off 2:on3:on4:on5:on6:off ntpd0:off 1:off 2:off 3:off 4:off 5:off 6:off portmap 0:off 1:off 2:off 3:on4:on5:on6:off xinetd 0:off 1:off 2:off 3:on4:on5:on6:off autofs 0:off 1:off 2:off 3:on4:on5:on6:off nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off nfslock 0:off 1:off 2:off 3:on4:on5:on6:off nscd0:off 1:off 2:off 3:off 4:off 5:off 6:off identd 0:off 1:off 2:off 3:off 4:off 5:off 6:off radvd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rwhod 0:off 1:off 2:off 3:off 4:off 5:off 6:off snmpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rhnsd 0:off 1:off 2:off 3:off 4:off 5:off 6:off ypbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off isdn0:off 1:off 2:on3:on4:on5:on6:off sshd0:off 1:off 2:on3:on4:on5:on6:off rstatd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rusersd 0:off 1:off 2:off 3:off 4:off 5:off 6:off rwalld 0:off 1:off 2:off 3:off 4:off 5:off 6:off vncserver 0:off 1:off 2:off 3:off 4:off 5:off 6:off yppasswdd 0:off 1:off 2:off 3:off 4:off 5:off 6:off ypserv 0:off 1:off 2:off 3:off 4:off 5:off 6:off ypxfrd 0:off 1:off 2:off 3:off 4:off 5:off 6:off wine0:off 1:off 2:on3:on4:on5:on6:off mserver 0:off 1:off 2:off 3:on4:on5:on6:off xinetd based services: chargen-udp:off chargen:off daytime-udp:off daytime:off echo-udp: off echo: off time-udp: off time: off amanda: on sgi_fam:on finger: off rexec: off rlogin: off rsh:off ntalk: off talk: off telnet: off wu-ftpd:off rsync: off Do you have anything in /etc/hosts.deny? If not, I really hope you have ipchains set up... Nothing in /etc/hosts.deny...would ipchains really benefit me? I'm blocking everything at the firewall, so I don't fell I need to worry about 'who' is using my services...
RE: Amrecover connection refused - again!
There's your problem -- the service isn't running. Maybe an xinetd
upgrade changed the functionality such that the three services in one
file method doesn't work any longer. In any case, break your
/etc/xinetd.d/amanda file into three files -- amanda, amandaidx, and
amidxtape -- and restart xinetd. All three services should then show up
in the above output.
I did that and no change...
[root@slaw root]# amrecover uadaily
AMRECOVER Version 2.4.2p2. Contacting server on slaw.unterlaw.com ...
amrecover: Error reading line from server: Connection reset by peer
[root@slaw root]# amrecover uadaily
AMRECOVER Version 2.4.2p2. Contacting server on slaw.unterlaw.com ...
amrecover: cannot connect to slaw.unterlaw.com: Connection refused
[root@slaw root]#
I can, however, see amandaidx and amidxtape when I chkconfig...
xinetd based services:
chargen-udp:off
chargen:off
daytime-udp:off
daytime:off
echo-udp: off
echo: off
time-udp: off
time: off
amanda: on
sgi_fam:on
finger: off
rexec: off
rlogin: off
rsh:off
ntalk: off
talk: off
telnet: off
wu-ftpd:off
rsync: off
amandaidx: on
amidxtape: on
Well, I'm paranoid, so I always set up both ipchains and
hosts.{allow,deny} fairly tightly. Of course, I'm also in academentia,
where every host (just about) is connected to the Big Bad Internet.
Ah...I see. I probably should be more paranoid...but we tightly
configured our big bad checkpoint firewall, so I think we're okay.
RE: Amrecover connection refused - again!
Can you telnet to each of thes ports?
$ telent target amandaix (use 'quit' to exit)
[root@slaw etc]# telnet slaw.unterlaw.com amandaidx
Trying 10.1.7.23...
telnet: connect to address 10.1.7.23: Connection refused
$ telnet target amidxtape ('quit' or CR to exit)
[root@slaw etc]# telnet slaw.unterlaw.com amidxtape
Trying 10.1.7.23...
Connected to slaw.unterlaw.com.
Escape character is '^]'.
If not, reload xinetd and check the messages file for any errors.
Also make sure that ipchains or iptables is not filtering the port.
I don't see where they are...
RE: Amrecover connection refused - again!
If not, reload xinetd and check the messages file for any errors. Also make sure that ipchains or iptables is not filtering the port. I don't see where they are... That was very unclear of me...I meant I don't see where they are filtering the port. (There I go having half the conversation in my head again!) I ipconfig and iptables scripts default their configs to /etc/sysconfig/ipchains and /etc/sysconfig/iptables respectively. I am not filtering this port in these files.
RE: Amrecover connection refused - again!
I'm not so sure. I have a similar setup -- all three in one file -- and chkconfig reports the same thing to me. However, amrecover works fine for me. I've been using the one-file method for some time now and it's always worked for me, as well. That's what's so confusing about this...it's all of a sudden. I haven't changed a thing!!!
RE: Amrecover connection refused - again!
Do you have nmap ? Try: # nmap -sT -p 10082 chena [root@slaw etc]# nmap -sT -p 10082 slaw.unterlaw.com Starting nmap V. 2.54BETA22 ( www.insecure.org/nmap/ ) The 1 scanned port on slaw.unterlaw.com (10.1.7.23) is: closed Nmap run completed -- 1 IP address (1 host up) scanned in 1 second That doesn't look happy...further investigation revealed: [root@slaw etc]# nmap -v slaw.unterlaw.com Starting nmap V. 2.54BETA22 ( www.insecure.org/nmap/ ) No tcp,udp, or ICMP scantype specified, assuming vanilla tcp connect() scan. Use -sP if you really don't want to portscan (and just want to see what hosts are up). Host slaw.unterlaw.com (10.1.7.23) appears to be up ... good. Initiating Connect() Scan against slaw.unterlaw.com (10.1.7.23) Adding TCP port 22 (state open). Adding TCP port 224 (state open). Adding TCP port 10083 (state open). Adding TCP port 111 (state open). The Connect() Scan took 1 second to scan 1542 ports. Interesting ports on slaw.unterlaw.com (10.1.7.23): (The 1538 ports scanned but not shown below are in state: closed) Port State Service 22/tcp openssh 111/tcpopensunrpc 224/tcpopenunknown 10083/tcp openamidxtape Where the heck is 10082/tcp amandaidx??? Do an ldd on /usr/local/libexec/amindexd. JIC. I get somerhing like this on my Linux server: I get that, too. Make sure that /usr/local/libexec/amindexd is executable and will start up. as the amanda user try: $ /usr/local/libexec/amindexd You should see somethng like: amindexd: getpeername: Socket operation on non-socket Yes, I get this as well. Try telneting to the port again. Then go to /tmp/amanda and locate the amindexd.bunchanumbers.debug file. Look in there for a hint. There are probably lots of these files so be sure to get the right one. (OR just delete all of them before telnetting :-) amrecover.bunchanumbers.debug: amrecover: debug 1 pid 1602 ruid 0 euid 0 start time Mon Jun 3 13:56:07 2002 amrecover: stream_client: connect(10082) failed: Connection refused cannot connect to slaw.unterlaw.com: Connection refused amrecover: pid 1602 finish time Mon Jun 3 13:56:07 2002 ~ If you are using Linux, look in /var/log/secure to see if xinetd is erally starting amandidx is. /var/log secure: snip Jun 3 13:52:22 slaw xinetd[843]: START: amidxtape pid=1595 from=10.1.7.23 is all that was in there from the last time I tried amrecover I saw this in there from this morning: Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1134 from=0.0.0.0 Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1135 from=0.0.0.0 Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1136 from=0.0.0.0 Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1137 from=0.0.0.0 Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1138 from=0.0.0.0 Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1139 from=0.0.0.0 Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1140 from=0.0.0.0 Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1141 from=0.0.0.0 Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1142 from=0.0.0.0 Jun 3 09:51:58 slaw xinetd[843]: START: amandaidx pid=1143 from=0.0.0.0 Can't think of anything else off hand.
RE: Amrecover connection refused - again!
Summation: amandaidx is looping and looping and looping until xinetd can't take it any more and kills it. After a fresh restart of xinetd, nmap reveals: [root@slaw amanda]# nmap slaw.unterlaw.com Starting nmap V. 2.54BETA22 ( www.insecure.org/nmap/ ) Interesting ports on slaw.unterlaw.com (10.1.7.23): (The 1537 ports scanned but not shown below are in state: closed) Port State Service 22/tcp openssh 111/tcpopensunrpc 224/tcpopenunknown 10082/tcp openamandaidx 10083/tcp openamidxtape Look at that happy little amandaidx service just waiting to be used!!! :-) But if I try to use it (i.e. amrecover uadaily), /var/log/messages says: Jun 3 14:42:28 slaw xinetd[1802]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1803]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1804]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1805]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1806]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1807]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1808]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1809]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1810]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1811]: warning: can't get client address: Transport endpoint is not connected Jun 3 14:42:28 slaw xinetd[1792]: amandaidx service was deactivated because of looping And I have 8 little amindexd*debug files for each of these little looping processes that say: amindexd: debug 1 pid 1861 ruid 502 euid 502 start time Mon Jun 3 14:44:35 2002 amindexd: version 2.4.2p2 Ew
RE: Amrecover connection refused - again!
You're right, that worked. Joshua, I should have tried that sooner when you suggested it. But I'm racking my notes trying to remember why I changed that to yes in the first place. I know I just used this configuration to recover a file a couple of months ago and the wait=yes was in place then!! Thanks, all for helping. Sorry I wasted everyone's time with such an easy fix. rap
tape out of space??
Hi all
I have been using amanda 2.4.2p2 on my 7.2 RH server for quite some time now
backing up both linux and solaris clients.
Today something strange happened...
a tape that has been in rotation and working properly all of sudden ran out
of space?
The last time I used this tape the stats showed:
These dumps were to tape dailytape03.
The next tape Amanda expects to use is: dailytape04.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 3:04
Dump Time (hrs:min)0:39 0:39 0:00
Output Size (meg) 11082.411082.40.0
Original Size (meg) 11082.411082.40.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped 14 14 0
Avg Dump Rate (k/s) 4852.5 4852.5--
Tape Time (hrs:min)3:02 3:02 0:00
Tape Size (meg) 11082.911082.90.0
Tape Used (%) 95.7 95.70.0
Filesystems Taped14 14 0
Avg Tp Write Rate (k/s) 1037.5 1037.5--
This time the stats showed:
These dumps were to tape dailytape03.
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: dailytape04.
FAILURE AND STRANGE DUMP SUMMARY:
in-db3.unt /etc lev 1 FAILED [no estimate]
in-db3.unt /export/home lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 3:12
Dump Time (hrs:min)0:41 0:41 0:00
Output Size (meg) 11574.111565.78.4
Original Size (meg) 11574.111565.78.4
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 13 8 5 (1:5)
Avg Dump Rate (k/s) 4827.4 4831.4 2264.7
Tape Time (hrs:min)1:55 1:54 0:00
Tape Size (meg) 6808.3 6799.78.6
Tape Used (%) 58.8 58.70.1 (level:#disks ...)
Filesystems Taped12 7 5 (1:5)
Avg Tp Write Rate (k/s) 1013.5 1013.7 882.1
As you can see my tape size was cut in half all of a sudden. I haven't made
any changes to the configuration or drive...
Maybe it's just a media error...but I wanted to throw it out here just in
case.
Any insight is much appreciated...
Thanks and have a great day. :)
Rebecca A. Pakish
Systems Administrator
Unterberg Associates, P.C.
(219) 736-5579 ext. 184
RE: tape out of space??
Look in /var/log/messages (or the output of 'dmesg') -- there's probably an entry from the tape driver letting you know what the error was. E.g., when this happens with my Eliant 820, I get: Nothing in messages that's telling me anything about my tape drive... On my drive, this just means that the drive needs to be cleaned. I was going to give it a good cleaning because it happens with my sun DAT drive sometimes (dumps failing when the drive is dirty); but never with this Seagate (until now??). We'll see what happens. Thanks! rap
RE: tape out of space??
What about the SCSI bus? Any sort of messages at approximately the time of the error? No errors at all actually...I see the session opening and closing for amanda...and that's it. What sort of drive? It's a Seagate 12/24 DAT...nothing fancy...I'm pushing it to it's limits right now backing up 11GB...trying to get the $$ for a DLT drive. rap
RE: Cron and Amdump
What does it say it /etc/group? Is amanda listed in the users for disk there? Did you reconfig amanda with-group=disk after you made this change? -Original Message- From: Karl Bellve [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 05, 2002 9:38 AM To: Amanda Subject: Cron and Amdump For some strange reason, cron has stopped running Amdump for me at night. I do see that cron is trying to run amdump at night. cron.log: Feb 5 00:45:00 itchy CROND[6620]: (amanda) CMD (/usr/sbin/amdump BIG1) Here is Amanda's crontab: 0 16 * * 1-5/usr/sbin/amcheck -m BIG1 45 0 * * 2-6/usr/sbin/amdump BIG1 There is nothing in /tmp/amanda, as if amdump never runs. If I manually run amdump: su amanda -c /usr/sbin/amdump BIG1 It works. I get logs in /tmp/amanda, and a report emailed to me. I changed group permissions for Amanda about a week ago. I noticed that I still had Amanda in the group operator from a previous install from a redhat rpm. Now, amanda is part of group disk (6). Amanda is set up like the following: amanda:x:33:6:Amanda user:/var/lib/amanda:/bin/bash Any thoughts? -- Cheers, Karl Bellve, Ph.D. ICQ # 13956200 Biomedical Imaging Group TLCA# 7938 University of Massachusetts Email: [EMAIL PROTECTED] Phone: (508) 856-6514 Fax: (508) 856-1840 PGP Public key: finger [EMAIL PROTECTED]
RE: Help a Newbie --Can't create info directories
Don't sweat this: amanda will create these the first time it runs amdump. -Original Message- From: Alvaro Rosales R. [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 31, 2002 1:03 PM To: [EMAIL PROTECTED] Subject: Help a Newbie --Can't create info directories Hi fellows , I'm a new Amanda user,I've herad that Amanda is very powerfull Im running amanda 2.4.2p2 on a FreeBSD 4.3 server , I have just finished setting up amanda, but Im having some trouble when I run amcheck, it seems that amanda can't create some directories (Do I have to create them for amanda or it is automatic??, the user amanda has ownership of the directories mentioned in the message). Im using amanda only to backup my tape server This are the messages I get: inka# su amanda -c amcheck daily Amanda Tape Server Host Check - Holding disk /home3/amandadsk: 13855764 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet1-002 label ok NOTE: info dir /home/amanda/DailySet1/curinfo/inka.wintersperu.com.pe: does not exist NOTE: index dir /home/amanda/DailySet1/index/inka.wintersperu.com.pe: does not e xist Server check took 5.905 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.058 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) Alvaro A. Rosales Rojas. a.k.a. RAZA Proud user of Pegasus Mail Soporte Tecnico de Sistemas Procacao S.A 3368113 ext 260 You'll never know how far you can go until you break the chains that tie your soul
RE: Newbie: Can't get amanda user to work
Yet, I have a .amandahosts file with what I think are the proper contents and permissions: admin:/home/amanda # ll /home/amanda/.amandahosts -rw-r--r--1 amanda disk 30 Dec 10 16:36 /home/amanda/.amandahosts admin:/home/amanda # cat /home/amanda/.amandahosts admin [EMAIL PROTECTED] admin:/home/amanda # In .amandahosts on the server, you want an entry that reads: clientname root In .amandahosts on the client, you want an entry that reads: servername amanda Your permissions look fine. (Though I chmod 600 .amandahosts myself) Make sure clientname and servername are fully qualified (i.e. servername.jhuccp.org, clientname.jhuccp.org) Good luck! rap
RE: Shit
If you know how to read...and I'm assuming you do since you can type...go to www.amanda.org and read the instructions. If that is too difficult I've pasted them below. (And in the future keep your profanity to yourself, it's unprofessional and uncalled for) pasted from amanda site Please note: To subscribe or unsubscribe to a mailing list, DO NOT, EVER, send mail to that list. Send mail to listname[EMAIL PROTECTED] with the following line in the body of the message: subscribe your-email-address and when you want to unsubscribe, use the following line in the body: unsubscribe your-email-address where listname is one of the following: amanda-announce The amanda-announce mailing list is for important announcements related to the Amanda Network Backup Manager package, including new versions, contributions, and fixes. NOTE: the amanda-users list is itself on the amanda-announce distribution, so you only need to subscribe to one of the two lists, not both. To subscribe, send a message to [EMAIL PROTECTED] amanda-users The amanda-users mailing list is for questions and general discussion about the Amanda Network Backup Manager. This package and related files are available via anonymous FTP from ftp.amanda.org in the pub/amanda directory. NOTE: the amanda-users list is itself on the amanda-announce distribution, so you only need to subscribe to one of the two lists, not both. To subscribe, send a message to [EMAIL PROTECTED] amanda-hackers The amanda-hackers mailing list is for discussion of the technical details of the Amanda package, including extensions, ports, bugs, fixes, and alpha testing of new versions. To subscribe, send a message to [EMAIL PROTECTED] -Original Message- From: Roy Andrè Tollefsen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 05, 2001 10:22 AM To: [EMAIL PROTECTED] Subject: Shit Hello amanda-users, Can someone please tell how we can unsubscribe from this list? For the last time ... I call this spam -- geworth
Failed/strange dump report - newbie question
Hi all... I checked the FAQ-o-matic (now that it's up and running again!! Thanks to whomever did that!) and I didn't see anything pertaining to my problem... I'm getting this message in my report: FAILED AND STRANGE DUMP DETAILS: /-- in-db2.unt /var/www lev 0 FAILED [/sbin/dump returned 1] sendbackup: start [in-db2.unterlaw.com:/var/www level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f... - sendbackup: info end ? You can't update the dumpdates file when dumping a subdirectory sendbackup: error [/sbin/dump returned 1] \ /-- in-db2.unt /etc lev 0 FAILED [/sbin/dump returned 1] sendbackup: start [in-db2.unterlaw.com:/etc level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f... - sendbackup: info end ? You can't update the dumpdates file when dumping a subdirectory sendbackup: error [/sbin/dump returned 1] \ What is the dumpdates file? How do I rectify this? Thanks and have a great day... rap Rebecca A. Pakish Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
RE: AMANDA WEBSITE ???
We might want to think about doing this during off-hours as well. Ahm, should we take a survey to figure out which timezone most users are in first? Oh, we have a recent backup of the internet in case the reboot fail, right? -- Seeya, Paul Can we wait until next week? That level 0 dump I've been working on for the past 6 weeks just hasn't finished yet. Besides...DST is this Saturday...best to wait until after that...
FAQ-o-matic down?!
What's up with the FAQ's...trying to get my linux RH amanda server to backup an NT box through samba...figured there was some guidance in the FAQ but it's FORBIDDEN!! Rebecca A. Pakish Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
Solaris client timeout
Hi John... I am quite certain this has been addressed and answered in the users group, but I have been scanning through everything and trying things here and there. I finally got amanda loaded on my solaris box...at least I believe I did. I got ./configure and make and make install to all work...or at least complete. I'm getting WARNING: ribs.unterlaw.com: selfcheck request timed out. Host down? ctimeout in amanda.conf set to 60 (was 30) My client is the sun box running solaris8...I did a hostname on it and it said ribs, so I changed it # hostname ribs.unterlaw.com so it would be fully qualified As you may recall, my hostname on my server is salad, and I changed it # hostname salad.unterlaw.com as well. On salad: .amandahosts lists salad.unterlaw.com salad.unterlaw.com root salad.unterlaw.com amanda ribs.unterlaw.com ribs.unterlaw.com root ribs.unterlaw.com amanda Disklist lists: salad.unterlaw.com /usr nocomp-root -1 local ribs.unterlaw.com /etc always-full le0 Both client and server have # Local services amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp in /etc/services ***though amandaidx is nowhere to be found on ribs, or at least not that I could see!*** I also listed this at the bottom of inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad amidxtaped stream tcp nowait amanda /usr/local/libexec/amidxtaped amidxtaped On ribs I created .amandahosts and it says: salad.unterlaw.com salad.unterlaw.com root salad.unterlaw.com amanda What am I missing? Thanks, rap Rebecca A. Pakish Systems Administrator Unterberg Associates, P.C. (219) 736-5579 ext. 184
RE: can somebody help
when I am running amdump, everything works fine and the files are being dumped on to the holding disk. but when I am running amrecover, nothing happens. Do you have index set to yes in your dump type? Amrecover cannot work without indexing. If you know you always want to use amrecover, why don't you make sure that you have index yes in your global dumptype, because almost all dumptypes include the global type in their definitions. rap -Ari
FW: can somebody help
i have set the index to yes in the dumptype. i am dumpint the file on my holding disk specified on the backup server which is the directory /var/tmp. the holding file is /var/tmp/20010913/client IP/_dev_sda5.0 which command do i use : amrecover or amrestore also what is the syntax of the command. i tried the syntax from man page, but i think i am making some mistake in that and its not working
Amcheck time out...xinetd.conf file screwy
Again...running RH7.1 with kernel upgraded to 2.4.6.
^
The all important fact. Redhat 7.1 (and 7.0, IIRC) use xinetd, not inetd.
Rather than a single .conf file, xinetd uses a number of files in the
/etc/xinetd.d directory. I've attached 3 files -- amanda, amandaidx and
amidxtape. On the clients (including the server itself), you only need
amanda in /etc/xinetd.d. The other two go on the server to allow you to
use amrecover from the clients.
The other difference is that to restart xinetd, you need to issue the
command '/etc/init.d/xinetd restart'.
I copied the files over that you gave me...right now my xinetd.conf seems to
be missing my user and group information, though I ran ./configure
--with-user=amanda --with-group=disk --with-config=backup. I'm not really
sure what the syntax is for xinetd.conf as far as that information is
concerned. Here's what it has:
#
# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/
defaults
{
instances = 60
log_type= SYSLOG authpriv
log_on_success = HOST PID
log_on_failure = HOST
}
includedir /etc/xinetd.d
amandadgram udp wait amanda /usr/local/libexec/amandadamandad
amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd amindexd
amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped amidxtaped
I checked my /var/log/messages and here's what I found...
Found my xinetd.conf file...but it had nothing in it!
Aug 29 15:31:03 salad xinetd: xinetd shutdown succeeded
Aug 29 15:31:03 salad xinetd[3708]: Protocol udp^M not in /etc/protocols
[line=3]
Aug 29 15:31:03 salad xinetd[3708]: Bad socket type: dgram^M [line=4]
Aug 29 15:31:03 salad xinetd[3708]: Bad value for wait: yes^M [line=5]
Aug 29 15:31:03 salad xinetd[3708]: Unknown user: amanda^M [line=6]
Aug 29 15:31:03 salad xinetd[3708]: Unknown group: disk^M [line=7]
Aug 29 15:31:03 salad xinetd[3708]: Server /usr/local/libexec/amandad^M is
not executable [line=8]
Aug 29 15:31:03 salad xinetd[3708]: Bad socket type: stream^M [line=7]
Aug 29 15:31:03 salad xinetd[3708]: Protocol tcp^M not in /etc/protocols
[line=8]
Aug 29 15:31:03 salad xinetd[3708]: Bad value for wait: no^M [line=9]
Aug 29 15:31:03 salad xinetd[3708]: Unknown user: amanda^M [line=10]
Aug 29 15:31:03 salad xinetd[3708]: attribute server expects 1 values and 2
values were specified [line=11]
Aug 29 15:31:03 salad xinetd[3708]: Bad socket type: stream^M [line=8]
Aug 29 15:31:03 salad xinetd[3708]: Protocol tcp^M not in /etc/protocols
[line=9]
Aug 29 15:31:03 salad xinetd[3708]: Bad value for wait: no^M [line=10]
Aug 29 15:31:03 salad xinetd[3708]: Unknown user: amanda^M [line=11]
Aug 29 15:31:03 salad xinetd[3708]: Server /usr/local/libexec/amidxtaped^M
is not executable [line=12]
Aug 29 15:31:03 salad xinetd[3708]: missing service keyword [line=17]
Aug 29 15:31:03 salad xinetd[3708]: missing } in last service entry
[line=19]
Aug 29 15:31:03 salad xinetd[3708]: chargen disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: chargen-udp disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: time disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: time disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: daytime disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: talk disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: rsync disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: ntalk disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: echo-udp disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: echo disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: daytime-udp disabled, removing
Aug 29 15:31:03 salad xinetd[3708]: Service amanda^M missing attribute
socket_type
Aug 29 15:31:03 salad xinetd[3708]: Service amanda^M missing attribute user
Aug 29 15:31:03 salad xinetd[3708]: Service amanda^M missing attribute
server
Aug 29 15:31:03 salad xinetd[3708]: Service amandaidx^M missing attribute
socket_type
Aug 29 15:31:03 salad xinetd[3708]: Service amandaidx^M missing attribute
user
Aug 29 15:31:03 salad xinetd[3708]: Service amandaidx^M missing attribute
server
Aug 29 15:31:03 salad xinetd[3708]: Service amidxtape^M missing attribute
socket_type
Aug 29 15:31:03 salad xinetd[3708]: Service amidxtape^M missing attribute
user
Aug 29 15:31:03 salad xinetd[3708]: Service amidxtape^M missing attribute
server
Aug 29 15:31:03 salad xinetd[3708]: xinetd Version 2.1.8.9pre14 started with
Aug 29 15:31:03 salad xinetd[3708]: libwrap
Aug 29 15:31:03 salad xinetd[3708]: options compiled in.
Aug 29 15:31:03 salad xinetd[3708]: Started working: 2 available services
Aug 29 15:31:06 salad xinetd: xinetd startup succeeded
Can someone help me with syntax?
RE: Still a newbie...but getting somewhere...amlabel troubles
Hi Paul... I tried that, and I got bash:/root/.bashrc:Permission denied -Original Message- From: Bort, Paul [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 3:50 PM To: 'Rebecca Pakish'; '[EMAIL PROTECTED]' Subject: RE: Still a newbie...but getting somewhere...amlabel troubles In the same directory as amanda.conf, try this: su -c amanda touch tapetype This will create a blank tapetype file that amanda can store info about tapes in. -Original Message- From: Rebecca Pakish [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 3:46 PM To: '[EMAIL PROTECTED]' Subject: Still a newbie...but getting somewhere...amlabel troubles Hi all... Thank you for all of your help on the ./tapetype issue. I learned a lot about my drive from the Seagate site (they have excellent documentation as far as I'm concerned) got my hardware compression turned off. Been working on the amanda.conf file, feel like I'm prepared to label my first tape and dump something! Again, running RH 7.1 on a Dell 333 with a SCSI Seagate external and just a 90mm tape for starters. (Had to download the mt command from the rpm site, but everything seems to be effectively communicating) In amanda.conf: labelstr ^testtape[0-9][0-9] (**amanda.conf is in /usr/local/etc/amanda/backup**) What's happening... $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied And then I looked for the file called tapelist that the amlabel man page said it would write to, and I couldn't find it to change it's permissions. When I went back to re-execute the amlabel command so I could write down the error, this is what happens: $su amanda -c amlabel backup testtape01 bash: /root.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking labelamlabel: couldn't write tapelist: Permission denied Which, I have to admit, for a girl who just learned how to tar on Friday and rpm yesterday, I'm pretty jacked to see that it read the label as testtape01 that second time! But of course, it still isn't right. oops. Can someone please help point me in the right direction? Thanks!! Rebecca
RE: Still a newbie...but getting somewhere...amlabel troubles
I compiled amanda...tried rpm but something strange happened. (Can't remember what now) Actually when I checked my /etc/passwd file $HOME for amanda was set to /var/lib/amanda, so I changed it to /home/amanda. The entry in passwd now looks like this: amanda:x:33:6:Amanda user:/home/amanda:/bin/bash I had already changed the ownership on the amanda directory...in fact /usr/local/etc shows ownership to amanda and group ownership disk (group 6, to which amanda belongs) Actually I ran an $su amanda -c touch tapetype which did create a tapetype file in my /usr/local/etc/amanda/backup dir. Then I was able to run my $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking label, done. I now have a tapelist file in my /usr/local/etc/amanda/backup file...so it appears to have worked...but how do I get rid of this bash permission denied message??? -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 4:03 PM To: Rebecca Pakish Cc: '[EMAIL PROTECTED]' Subject: Re: Still a newbie...but getting somewhere...amlabel troubles On Tue, 28 Aug 2001 at 2:46pm, Rebecca Pakish wrote Been working on the amanda.conf file, feel like I'm prepared to label my first tape and dump something! Again, running RH 7.1 on a Dell 333 with a SCSI Seagate external and just a 90mm tape for starters. (Had to download the mt command from the rpm site, but everything seems to be effectively communicating) Did you compile amanda or install the RPM? In amanda.conf: labelstr ^testtape[0-9][0-9] (**amanda.conf is in /usr/local/etc/amanda/backup**) What's happening... $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied This says that the $HOME of the user amanda specified in /etc/passwd is /root, but the amanda user does not have read access to that directory. I would fix this by giving amanda a different $HOME (like /home/amanda). rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied The file 'tapelist' is created after the first successful amlabel, which is why you don't have one yet. It lives in the same directory as the amanda.conf and disklist for the configuration -- in this case /usr/local/etc/amanda/backup. So, amanda must not have write permissions in that directory. The easiest way to fix that would be 'chown -R amanda /usr/local/etc/amanda', which will give the user amanda ownership of /usr/local/etc/amanda and all the files and directories inside it. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Still a newbie...but getting somewhere...amlabel troubles
Hi all... Thank you for all of your help on the ./tapetype issue. I learned a lot about my drive from the Seagate site (they have excellent documentation as far as I'm concerned) got my hardware compression turned off. Been working on the amanda.conf file, feel like I'm prepared to label my first tape and dump something! Again, running RH 7.1 on a Dell 333 with a SCSI Seagate external and just a 90mm tape for starters. (Had to download the mt command from the rpm site, but everything seems to be effectively communicating) In amanda.conf: labelstr ^testtape[0-9][0-9] (**amanda.conf is in /usr/local/etc/amanda/backup**) What's happening... $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied And then I looked for the file called tapelist that the amlabel man page said it would write to, and I couldn't find it to change it's permissions. When I went back to re-execute the amlabel command so I could write down the error, this is what happens: $su amanda -c amlabel backup testtape01 bash: /root.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking labelamlabel: couldn't write tapelist: Permission denied Which, I have to admit, for a girl who just learned how to tar on Friday and rpm yesterday, I'm pretty jacked to see that it read the label as testtape01 that second time! But of course, it still isn't right. oops. Can someone please help point me in the right direction? Thanks!! Rebecca
RE: Still a newbie...but getting somewhere...amlabel troubles
I'm not sure why this posted again...sorry everyone...I've already had some responses I'm going to look into tomorrow. :) -Original Message- From: Rebecca Pakish [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 2:46 PM To: '[EMAIL PROTECTED]' Subject: Still a newbie...but getting somewhere...amlabel troubles Hi all... Thank you for all of your help on the ./tapetype issue. I learned a lot about my drive from the Seagate site (they have excellent documentation as far as I'm concerned) got my hardware compression turned off. Been working on the amanda.conf file, feel like I'm prepared to label my first tape and dump something! Again, running RH 7.1 on a Dell 333 with a SCSI Seagate external and just a 90mm tape for starters. (Had to download the mt command from the rpm site, but everything seems to be effectively communicating) In amanda.conf: labelstr ^testtape[0-9][0-9] (**amanda.conf is in /usr/local/etc/amanda/backup**) What's happening... $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied And then I looked for the file called tapelist that the amlabel man page said it would write to, and I couldn't find it to change it's permissions. When I went back to re-execute the amlabel command so I could write down the error, this is what happens: $su amanda -c amlabel backup testtape01 bash: /root.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking labelamlabel: couldn't write tapelist: Permission denied Which, I have to admit, for a girl who just learned how to tar on Friday and rpm yesterday, I'm pretty jacked to see that it read the label as testtape01 that second time! But of course, it still isn't right. oops. Can someone please help point me in the right direction? Thanks!! Rebecca
Help I'm a newbie and I can't backup
Let me apologize in advance for my lack of knowledge and experience. Being thrown into the world of Unix/Linux (willingly) and my first task is amanda. I'm running RH 7.1 on an old Dell 333 with an IDE drive and an external 12/24 SCSI Seagate. I'm reading and re-reading The Chapter and am now trying to run the ./tapetype, so I can config and practice with a Verbatim 90mm (I know this is too small, but I'm just practicing)... apparantly my syntax is all screwed up. I tried man tapetype and there's nothing. Make tapetype was successful because now when I enter it I get make: 'tapetype' is up to date. I also noted that it says to disable hardware compression everywhere, but I don't know what the flag is for this in RH 7.1 (like the n flag for no rewind) Please help...anyone! *How do you know she's a witch? She turned me into a newt once. A newt? Well, I got better*
