chg-chio problem on Freebsd 4.6-stable?
I'm getting errors from chg-chio. It would appear that it doesn't work with the newer perl in freebsd. A basic amcheck generates the following: === %su operator -c "amcheck -t DailySet" Amanda Tape Server Host Check - amcheck-server: could not get changer info: string "fi" may clash with future reserved word at /usr/local/libexec/amanda/chg-chio line 369. === When I replace the 'fi' with a '}', I get : === %su operator -c "amcheck DailySet" Amanda Tape Server Host Check - Holding disk /usr/tapecache: 14241114 KB disk space available, that's plenty amcheck-server: could not get changer info: "main::prefix" used only once: possible typo at /usr/local/libexec/amanda/chg-chio line 58. Amanda Backup Client Hosts Check Client check: 1 host checked in 0.105 seconds, 0 problems found (brought to you by Amanda 2.4.3b2) === amcheck.20020703223926.debug contains: === amcheck: debug 1 pid 4072 ruid 2 euid 0 start time Wed Jul 3 22:39:26 2002 amcheck: dgram_bind: socket bound to 0.0.0.0.854 changer: got exit: 2 str: Name "main::prefix" used only once: possible typo at /usr/local/libexec/amand a/chg-chio line 58. could not get changer info: "main::prefix" used only once: possible typo at /usr/local/libexec/amanda/c hg-chio line 58. amcheck-server: pid 4073 finish time Wed Jul 3 22:39:26 2002 amcheck: pid 4072 finish time Wed Jul 3 22:39:26 2002 === I set $prefix="/usr/local"; in chg-chio just to be sure. (I had problems with that earlier) but i get the same error message for line 58. pkg_info shows the amanda ports i installed: == amanda-client-2.4.3b2 The Advanced Maryland Automatic Network Disk Archiver amanda-server-2.4.3b2_2 The Advanced Maryland Automatic Network Disk Archiver == changer.debug shows: Wed Jul 3 22:42:48 2002: enter: getTapeParams Wed Jul 3 22:42:48 2002: running: /bin/chio -f /dev/null params Wed Jul 3 22:44:14 2002: enter: getTapeParams Wed Jul 3 22:44:14 2002: running: /bin/chio -f /dev/null params Wed Jul 3 22:48:29 2002: enter: getTapeParams Wed Jul 3 22:48:29 2002: running: /bin/chio -f /dev/null params Obviously, this is not right. I move changerdev into amanda.conf and changer.debug does: - Wed Jul 3 22:56:50 2002: enter: getTapeParams Wed Jul 3 22:56:50 2002: running: /bin/chio -f /dev/ch0 params Wed Jul 3 22:56:50 2002: /dev/ch0: 10 slots, 2 drives, 1 picker Wed Jul 3 22:56:50 2002: /dev/ch0: current picker: 0 Wed Jul 3 22:56:50 2002: leave: getTapeParams: 10, 2, 1 Wed Jul 3 22:56:50 2002: enter: getTapeStatus Wed Jul 3 22:56:50 2002: running: /bin/chio -f /dev/ch0 status Wed Jul 3 22:56:50 2002: picker 0: Wed Jul 3 22:56:50 2002: slot 0: Wed Jul 3 22:56:50 2002: slot 1: Wed Jul 3 22:56:50 2002: slot 2: Wed Jul 3 22:56:50 2002: slot 3: Wed Jul 3 22:56:50 2002: slot 4: Wed Jul 3 22:56:50 2002: slot 5: Wed Jul 3 22:56:50 2002: slot 6: Wed Jul 3 22:56:50 2002: slot 7: Wed Jul 3 22:56:50 2002: slot 8: Wed Jul 3 22:56:50 2002: slot 9: Wed Jul 3 22:56:50 2002: drive 0: Wed Jul 3 22:56:50 2002: drive 1: Wed Jul 3 22:56:50 2002: enter: getCurrentTape Wed Jul 3 22:56:50 2002: leave: getCurrentTape: 0 Wed Jul 3 22:56:50 2002: leave: getTapeStatus: 3 Wed Jul 3 22:56:50 2002MT -> /usr/local/sbin/ammt -f Wed Jul 3 22:56:50 2002: enter: Load: 1 Wed Jul 3 22:56:50 2002: running: /bin/chio -f /dev/ch0 move slot 0 drive 0 Wed Jul 3 22:57:08 2002: leave: Load Wed Jul 3 22:57:08 2002: 1 10 1 Since I don't know perl, OBVIOUSLY it's a perl issue ;) Any ideas on what could be causing: %su operator -c "amcheck DailySet" Amanda Tape Server Host Check - Holding disk /usr/tapecache: 14241150 KB disk space available, that's plenty amcheck-server: could not get changer info: badly formed result from changer: "Name "main::prefix" used only once: possible typo at /usr/local/libexec/amanda/chg-chio line 58." manually running chio seems to work fine for all commands, but when amanda tries it just goes to hell. All (reasonably sane) suggestions are welcome. Thank you. -Stephen Apologies if you get a duplicate. My mailer crashed during the send.
Re: syncronize backups
On Wed, 3 Jul 2002, Scaglione Ermanno wrote: > This is a CISCO document explaining NAT: > http://www.cisco.com/warp/public/cc/pd/iosw/ioft/ionetn/prodlit/1195_pp.htm > > It states that "Any TCP/UDP traffic that does not carry source and/or > destination IP addresses in the application data stream" is supported and > without the sendsize problem also amanda UDP traffic is supported. > > When port translation is configured, there is finer control over translation > entry timeouts, because each entry contains more context about the traffic > using it. Non-DNS UDP translations time out after 5 minutes; DNS times out > in 1 minute. TCP translations time out after 24 hours, unless a RST or FIN > is seen on the stream, in which case it times out in 1 minute. > > The problem exists certainly also with linux firewall using iptables becouse > it uses even smaller timeouts. Worse yet, iptables in Red Hat 7.x doesn't allow control of the timeout value. A huge step backwards from ipchains in Red Hat 6.x, which did allow tuning this parameter. Amanda is not the only thing that breaks without this feature. -Mitch
Compaq tl810 DLT libary and AMANDA server on TRU64 v4.0f
Hi People, I have amanda 2.4.2p2 installed on a server running TRU64 v4.0f. This server is also connected to a Compaq tl810 DLT Tape library. I have been able to do successful backups and restores as a test when just using a single tape out of the changer but now I want to be able to use the changer correctly. Initially I thought I would be able to use chg-scsi but upon checking the libexec directory this file doesnt exist. Is this a issue with the installation just for TRU64 or do you need to pass special options to the configure ? The configure that I used was CC=cc ./configure --prefix=/usr/local/amanda --with-changer-device=/dev/mc0 --with-user=amanda --with-group=system --with-fqdn This along with the make and make install works fine ans as I mentioned I can do backups/restores. So have I missed something obvious about how to create chg-scsi ?? Does anyone have a system similar to what I need up and running ? I had a hunt through some of the previous postings and am going to try and get mtx working to talk to the changer. If this works then I will be able use chg-mtx. So if anyone has any suggestions on how I can get this going please let me know :) Also relating to this has anyone written a changer glue script that uses mcutil to control the changer ?? Thank you for your time :) __ The contents of this e-mail are privileged and/or confidential to the named recipient and are not to be used by any other person and/or organisation. If you have received this e-mail in error, please notify the sender and delete all material pertaining to this e-mail. __
Enabling SCSI emulation for IDE tape drives ( Was - RE: Taper hangs and my backup fails)
Joshua, That was the problem. Thanks for the help. Here is what I did in case anyone wants a quick reference. This configuration is for Linux kernel 2.4.17 using 'make menuconfig' 01) Select 'ATA/IDE/MFM/RLL support' 02) Select 'IDE, ATA and ATAPI Block devices' 03) Enable 'SCSI emulation support' 04) Go back to the Main Menu and choose 'SCSI support' 05) Enable 'SCSI support' and 'SCSI generic support' 06) Make your new kernel 07) Add the line 'append="=ide-scsi"' to lilo.conf where is your tape drive. Here is what mine looks like: image=/vmlinuz label=Linux read-only append="hdd=ide-scsi" 08) Run 'lilo' 09) Add 'modprobe ide-scsi' to the bottom of your /etc/rc.d/rc.local file 10) Reboot 11) Run 'lsmod' and make sure you see 'ide-scsi' in the list of modules 12) Give the amanda group (or whatever you specified in --with-user=) permission to write to '/dev/nst0' - 'chown root.amanda /dev/nst0' 13) Link '/dev/tape' to '/dev/nst0' - 'ln -s /dev/nst0 /dev/tape' 14) Use 'mt' to see if it worked - 'mt status' I hope that is everything. --Cassidy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Joshua Baker-LePain Sent: Tuesday, July 02, 2002 2:50 PM To: Cassidy Kern Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Taper hangs and my backup fails On Tue, 2 Jul 2002 at 2:40pm, Cassidy Kern wrote > tapedev "/dev/nht0" > > # tapetype section > tapetype Seagate_Travan_20 > labelstr "^Daily[0-9][0-9]*" There has been some discussion of IDE tape drives recently, and the consensus seemed to be to use ide-scsi and use them as SCSI devices. Search the list archives for details, and give that a shot. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: syncronize backups
This is a CISCO document explaining NAT: http://www.cisco.com/warp/public/cc/pd/iosw/ioft/ionetn/prodlit/1195_pp.htm It states that "Any TCP/UDP traffic that does not carry source and/or destination IP addresses in the application data stream" is supported and without the sendsize problem also amanda UDP traffic is supported. When port translation is configured, there is finer control over translation entry timeouts, because each entry contains more context about the traffic using it. Non-DNS UDP translations time out after 5 minutes; DNS times out in 1 minute. TCP translations time out after 24 hours, unless a RST or FIN is seen on the stream, in which case it times out in 1 minute. The problem exists certainly also with linux firewall using iptables becouse it uses even smaller timeouts. - Original Message - From: "Lee Fellows" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 03, 2002 7:02 PM Subject: Re: syncronize backups > On Wed, 2002-07-03 at 10:47, Scaglione Ermanno wrote: > > thanks but I found the real problem: there is a cisco router doing NAT > > between the amanda server and the two server. I found that it had a nat udp > > timeout of 6 minutes (CISCO default). What happens is that amanda gets the > > estimates from the first server that answers and starts the backup on that > > server, then the link becomes too busy, the UDP connection with the second > > server times out on the router and the second backup doesn't work .. > > Well we could consider this an amanda bug maybe, the problem is that amanda > > doesn't do keepalive while sendsize runs, and sendsize itself doesn't do > > keepalive. I have been told that most CISCO routers doing NAT have this 6 > > minutes nat udp timeout thus if the estimate takes more than 6 minutes the > > backup will probably fails if there is such a router in between . > > > > - Original Message - > > From: "Chris Marble" <[EMAIL PROTECTED]> > > To: "Scaglione Ermanno" <[EMAIL PROTECTED]> > > Sent: Wednesday, July 03, 2002 4:39 AM > > Subject: Re: syncronize backups > > > > > > > Scaglione Ermanno wrote: > > > > > > > > I have a strange problem with amanda, I am backing up 6 servers with the > > > > same disklist and 2 of them alternatively fails with a timeout in > > sendsize. > > > > Server A works for a couple of days and server B doesn't in the same > > days, > > > > then server B works and server A doesn't. I suppose the reason is that > > both > > > > server are behind a slow link. How can I tell Amanda not to backup > > > > simultaneously the two servers using 1 disklist? > > > > > > Hmm, I was going to tell you to lie to Amanda and tell it that all the > > disks > > > are on the same spindle. But then I realized that the spindle parameter > > is > > > on a per-machine basis. You could set an earlier starttime for those > > servers and > > > set inparallel to 1 just for a while. > > > -- > > > [EMAIL PROTECTED] - HMC UNIX Systems Manager > > > > > > > > > > Interesting. Do I understand your suggestion correctly to imply that > keepalive be done on udp sockets. If so, might I suggest that this > is not the solution. Its been several years since I programmed tcp > and udp clients and servers, but if memory serves me correctly, > keepalive is only available in the tcp-family of protocols. Keepalive > was intended to maintain an otherwise idle connection for some period > of time. Udp by definition is not a connected protocol and such an > option would be meaningless for it. > > > >
Re: syncronize backups
On Wednesday 03 July 2002 13:02, Lee Fellows wrote: >On Wed, 2002-07-03 at 10:47, Scaglione Ermanno wrote: >> thanks but I found the real problem: there is a cisco router >> doing NAT between the amanda server and the two server. I found >> that it had a nat udp timeout of 6 minutes (CISCO default). What >> happens is that amanda gets the estimates from the first server >> that answers and starts the backup on that server, then the link >> becomes too busy, the UDP connection with the second server >> times out on the router and the second backup doesn't work >> .. Well we could consider this an amanda bug maybe, the >> problem is that amanda doesn't do keepalive while sendsize runs, >> and sendsize itself doesn't do keepalive. I have been told that >> most CISCO routers doing NAT have this 6 minutes nat udp timeout >> thus if the estimate takes more than 6 minutes the backup will >> probably fails if there is such a router in between . >> >> - Original Message - >> From: "Chris Marble" <[EMAIL PROTECTED]> >> To: "Scaglione Ermanno" <[EMAIL PROTECTED]> >> Sent: Wednesday, July 03, 2002 4:39 AM >> Subject: Re: syncronize backups >> >> > Scaglione Ermanno wrote: >> > > I have a strange problem with amanda, I am backing up 6 >> > > servers with the same disklist and 2 of them alternatively >> > > fails with a timeout in >> >> sendsize. >> >> > > Server A works for a couple of days and server B doesn't in >> > > the same >> >> days, >> >> > > then server B works and server A doesn't. I suppose the >> > > reason is that >> >> both >> >> > > server are behind a slow link. How can I tell Amanda not to >> > > backup simultaneously the two servers using 1 disklist? >> > >> > Hmm, I was going to tell you to lie to Amanda and tell it that >> > all the >> >> disks >> >> > are on the same spindle. But then I realized that the spindle >> > parameter >> >> is >> >> > on a per-machine basis. You could set an earlier starttime >> > for those >> >> servers and >> >> > set inparallel to 1 just for a while. >> > -- >> > [EMAIL PROTECTED] - HMC UNIX Systems Manager > > Interesting. Do I understand your suggestion correctly to imply > that keepalive be done on udp sockets. If so, might I suggest > that this is not the solution. Its been several years since I > programmed tcp and udp clients and servers, but if memory serves > me correctly, keepalive is only available in the tcp-family of > protocols. Keepalive was intended to maintain an otherwise idle > connection for some period of time. Udp by definition is not a > connected protocol and such an option would be meaningless for > it. On a FWIW note, the new iptstate-1.3.1 is showing that the cups daemons on my two machines are exchanging udp packets, effectively doing a keepalive on udp port 631. Its setting a TTL of 30 seconds, and renewing it at about 25 second intervals. So its not impossible to keep a udp connection alive full time. As to the RFC legality of such, I'll leave that to the experts. This connection isn't nat'd though as its between 192.168.x.x addresses. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.04% setiathome rank, not too shabby for a WV hillbilly
Re: sendbackup dump processes hang for days
On Wed, 3 Jul 2002 at 10:57am, tammy wrote > exit? What causes them to hang like this? I have larger drives that dump > level 0's fine. The processes hang on my amanda server running RedHat > 7.1. > > For instance... > > Processes: > > amanda 20216 0.0 0.0 18640 ?SW Jun05 0:00 dump 0usf > 1048576 - /dev/sda6 > amanda 20219 0.0 3346.6 1880 4294967292 ? SJun05 0:05 dump 0usf > 1048576 - /dev/sda6 > amanda 20220 0.0 0.0 18640 ?SW Jun05 0:09 dump 0usf > 1048576 - /dev/sda6 > amanda 20221 0.0 0.0 18640 ?SW Jun05 0:08 dump 0usf > 1048576 - /dev/sda6 > amanda 20222 0.0 0.0 18640 ?SW Jun05 0:09 dump 0usf > 1048576 - /dev/sda6 This is a known issue with ext2 dump and certain 2.4 series kernels. I've heard rumors that the issues are somewhat resolved with recent kernels *and* (not or) recent versions of dump, but I've not tested this. Your other option is to switch to tar for Linux backups. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
sendbackup dump processes hang for days
Hi I am having a sporadic problem with sendbackup. Sometimes the process fails to ever terminate! On those days, the backup of the disk being dumped gives a failure timeout message. The timeout failure on a drive is fine occasionally but why would the processes hang around and not exit? What causes them to hang like this? I have larger drives that dump level 0's fine. The processes hang on my amanda server running RedHat 7.1. For instance... Processes: amanda 20216 0.0 0.0 18640 ?SW Jun05 0:00 dump 0usf 1048576 - /dev/sda6 amanda 20219 0.0 3346.6 1880 4294967292 ? SJun05 0:05 dump 0usf 1048576 - /dev/sda6 amanda 20220 0.0 0.0 18640 ?SW Jun05 0:09 dump 0usf 1048576 - /dev/sda6 amanda 20221 0.0 0.0 18640 ?SW Jun05 0:08 dump 0usf 1048576 - /dev/sda6 amanda 20222 0.0 0.0 18640 ?SW Jun05 0:09 dump 0usf 1048576 - /dev/sda6 and again amanda 10090 0.0 0.1 1888 828 ?SJun18 0:00 /usr/local/libexec/sendbackup amanda 10092 0.0 0.1 1876 616 ?SJun18 0:01 /usr/local/libexec/sendbackup amanda 10093 0.0 0.1 1896 1024 ?SJun18 0:00 dump 0usf 1048576 - /dev/sdb6 amanda 10094 0.0 0.0 00 ?ZJun18 0:00 [sh] amanda 10097 0.0 0.1 1984 1016 ?SJun18 0:00 dump 0usf 1048576 - /dev/sdb6 amanda 10098 0.0 0.1 1896 692 ?SJun18 0:00 dump 0usf 1048576 - /dev/sdb6 amanda 10099 0.0 0.1 1896 692 ?SJun18 0:00 dump 0usf 1048576 - /dev/sdb6 amanda 10100 0.0 0.1 1896 692 ?SJun18 0:00 dump 0usf 1048576 - /dev/sdb6 have been running for days, weeks even;( Thanks for any insight! -- [EMAIL PROTECTED]
Re: syncronize backups
ok maybe I did not explained correctly what I found out and keepalive is possibly not the right term for it. this is my scenario: Amanda server--> CISCO router doing NAT > Server to backup (A) I did a tcpdump und the amanda server and another one on server A. What I see is: Amanda server sends a udp paket to server it ack it and starts sendsize, no more upd packets are sent while sendsize runs. Send size terminates, server A sends a udp packet to the amanda server with the results and the backup begins. Inevitably if sendsize takes longer than 6 minutes the backup fails, now with nat udp timeout 3600 the backup always works. In client-src/amandad.c the client answers wit a ACK to every P_REQ it recieves, there is also this interesting comment: /* * Under normal conditions, the master will resend the REQ packet * to be sure we are still alive. It expects an ACK back right away. * * XXX- Arguably we should parse and security check the new packet, * only sending an ACK if it passes and the request is identical to * the original one. However, that's too much work for now. :-) * * It should suffice to ACK whenever the sender is identical. */ Now this is keeping the connection alive and it works also over nat until there is a pause longer than 6 minutes between P_REQ and ACK. setting a bigger ACK_TIMEOUT in client-src/amandad.c doesn't help because the timeout takes place on the router. The problem is that UDP is stateless as you know, modern routers do something called connection tracking to permit UDP connection over NAT.(http://www.cs.princeton.edu/~jns/security/iptables/iptables_conntrack.h tml) so when the amanda server sends the first UDP packet to server A the NAT router saves this information in its tables (until they time out) and when server A acknowledges the request is able to forward it to the right server. To allow safe backups over NAT using UDP the server and the client should exchange P_REQ and ACK every 2 minutes or something like that just to keep the connection tracking timeout happy!! - Original Message - From: "Lee Fellows" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 03, 2002 7:02 PM Subject: Re: syncronize backups > On Wed, 2002-07-03 at 10:47, Scaglione Ermanno wrote: > > thanks but I found the real problem: there is a cisco router doing NAT > > between the amanda server and the two server. I found that it had a nat udp > > timeout of 6 minutes (CISCO default). What happens is that amanda gets the > > estimates from the first server that answers and starts the backup on that > > server, then the link becomes too busy, the UDP connection with the second > > server times out on the router and the second backup doesn't work .. > > Well we could consider this an amanda bug maybe, the problem is that amanda > > doesn't do keepalive while sendsize runs, and sendsize itself doesn't do > > keepalive. I have been told that most CISCO routers doing NAT have this 6 > > minutes nat udp timeout thus if the estimate takes more than 6 minutes the > > backup will probably fails if there is such a router in between . > > > > - Original Message - > > From: "Chris Marble" <[EMAIL PROTECTED]> > > To: "Scaglione Ermanno" <[EMAIL PROTECTED]> > > Sent: Wednesday, July 03, 2002 4:39 AM > > Subject: Re: syncronize backups > > > > > > > Scaglione Ermanno wrote: > > > > > > > > I have a strange problem with amanda, I am backing up 6 servers with the > > > > same disklist and 2 of them alternatively fails with a timeout in > > sendsize. > > > > Server A works for a couple of days and server B doesn't in the same > > days, > > > > then server B works and server A doesn't. I suppose the reason is that > > both > > > > server are behind a slow link. How can I tell Amanda not to backup > > > > simultaneously the two servers using 1 disklist? > > > > > > Hmm, I was going to tell you to lie to Amanda and tell it that all the > > disks > > > are on the same spindle. But then I realized that the spindle parameter > > is > > > on a per-machine basis. You could set an earlier starttime for those > > servers and > > > set inparallel to 1 just for a while. > > > -- > > > [EMAIL PROTECTED] - HMC UNIX Systems Manager > > > > > > > > > > Interesting. Do I understand your suggestion correctly to imply that > keepalive be done on udp sockets. If so, might I suggest that this > is not the solution. Its been several years since I programmed tcp > and udp clients and servers, but if memory serves me correctly, > keepalive is only available in the tcp-family of protocols. Keepalive > was intended to maintain an otherwise idle connection for some period > of time. Udp by definition is not a connected protocol and such an > option would be meaningless for it. > > > >
Re: syncronize backups
On Wed, 2002-07-03 at 10:47, Scaglione Ermanno wrote: > thanks but I found the real problem: there is a cisco router doing NAT > between the amanda server and the two server. I found that it had a nat udp > timeout of 6 minutes (CISCO default). What happens is that amanda gets the > estimates from the first server that answers and starts the backup on that > server, then the link becomes too busy, the UDP connection with the second > server times out on the router and the second backup doesn't work .. > Well we could consider this an amanda bug maybe, the problem is that amanda > doesn't do keepalive while sendsize runs, and sendsize itself doesn't do > keepalive. I have been told that most CISCO routers doing NAT have this 6 > minutes nat udp timeout thus if the estimate takes more than 6 minutes the > backup will probably fails if there is such a router in between . > > - Original Message - > From: "Chris Marble" <[EMAIL PROTECTED]> > To: "Scaglione Ermanno" <[EMAIL PROTECTED]> > Sent: Wednesday, July 03, 2002 4:39 AM > Subject: Re: syncronize backups > > > > Scaglione Ermanno wrote: > > > > > > I have a strange problem with amanda, I am backing up 6 servers with the > > > same disklist and 2 of them alternatively fails with a timeout in > sendsize. > > > Server A works for a couple of days and server B doesn't in the same > days, > > > then server B works and server A doesn't. I suppose the reason is that > both > > > server are behind a slow link. How can I tell Amanda not to backup > > > simultaneously the two servers using 1 disklist? > > > > Hmm, I was going to tell you to lie to Amanda and tell it that all the > disks > > are on the same spindle. But then I realized that the spindle parameter > is > > on a per-machine basis. You could set an earlier starttime for those > servers and > > set inparallel to 1 just for a while. > > -- > > [EMAIL PROTECTED] - HMC UNIX Systems Manager > > > > Interesting. Do I understand your suggestion correctly to imply that keepalive be done on udp sockets. If so, might I suggest that this is not the solution. Its been several years since I programmed tcp and udp clients and servers, but if memory serves me correctly, keepalive is only available in the tcp-family of protocols. Keepalive was intended to maintain an otherwise idle connection for some period of time. Udp by definition is not a connected protocol and such an option would be meaningless for it.
Re: syncronize backups
thanks but I found the real problem: there is a cisco router doing NAT between the amanda server and the two server. I found that it had a nat udp timeout of 6 minutes (CISCO default). What happens is that amanda gets the estimates from the first server that answers and starts the backup on that server, then the link becomes too busy, the UDP connection with the second server times out on the router and the second backup doesn't work .. Well we could consider this an amanda bug maybe, the problem is that amanda doesn't do keepalive while sendsize runs, and sendsize itself doesn't do keepalive. I have been told that most CISCO routers doing NAT have this 6 minutes nat udp timeout thus if the estimate takes more than 6 minutes the backup will probably fails if there is such a router in between . - Original Message - From: "Chris Marble" <[EMAIL PROTECTED]> To: "Scaglione Ermanno" <[EMAIL PROTECTED]> Sent: Wednesday, July 03, 2002 4:39 AM Subject: Re: syncronize backups > Scaglione Ermanno wrote: > > > > I have a strange problem with amanda, I am backing up 6 servers with the > > same disklist and 2 of them alternatively fails with a timeout in sendsize. > > Server A works for a couple of days and server B doesn't in the same days, > > then server B works and server A doesn't. I suppose the reason is that both > > server are behind a slow link. How can I tell Amanda not to backup > > simultaneously the two servers using 1 disklist? > > Hmm, I was going to tell you to lie to Amanda and tell it that all the disks > are on the same spindle. But then I realized that the spindle parameter is > on a per-machine basis. You could set an earlier starttime for those servers and > set inparallel to 1 just for a while. > -- > [EMAIL PROTECTED] - HMC UNIX Systems Manager >
Re: [AMANDA]Q: amanda/udp: socket: Protocol not supported
On Wed, 2002-07-03 at 03:18, Hertog, den, Rene wrote: > Hello List, > > Please help, any info appreciated on the following : > > after installation of Amanda on a Sun Solaris 8 host > I recieve the following error when restarting inetd : > > "inetd[320]: [ID 220303 daemon.error] amanda/udp: socket: Protocol not supported" > > Checked /etc/inet/services, inetd.conf, .amandahosts, nsswitch.conf, nslookup > found no (obvious) typos. > I've copied the lines in the services files an inetd.conf to five other Solaris 8 > hosts, future clients, sighup the inetd's and no problems, amandad listening. > > So, where to look on. Any suggestions ? > Thanks in advance, > greetings, Rene > > R. den Hertog > Corporate Unix Administrator Computer & Netwerk Services > Rotterdam Municipal Port Management > > Phone+31 (0)10 - 252 15 73 > Fax +31 (0)10 - 252 28 21 > E-mail [EMAIL PROTECTED] > Internet www.portofrotterdam.com > > World Port Center > Wilhelminakade 909 > 3072 AP Rotterdam > The Netherlands > Hi, Can you show us the actual line from the inetd.conf file on the system that is being problematical? Also the /etc/services entry for amanda may be helpful. Thank you.
tapeless configuration
hi, I'm trying to amrecover file which were backed up with tapeless amanda.conf (amanda-2.4.3b3). 1)amanda.conf tapedev "file:/unige/amanda/bckp/" 2) ls -l /unige/amanda/bckp/ lrwxrwxrwx 1 root other 30 Jul 2 16:15 DSD01 -> /net/atalante/export/diskF// 3)creating the data link: ln -s /unige/amanda/bckp/DSD01/ data 4)ls -l /unige/amanda/bckp/ lrwxrwxrwx 1 root other 30 Jul 2 16:15 DSD01 -> /net/atalante/export/diskF// lrwxrwxrwx 1 root other 24 Jul 3 09:20 data -> /unige/amanda/bckp/DSD01/ -rw--- 1 root other 11 Jul 3 11:32 info 5)amlabel DailySet DSD01 rewinding, reading label, not an amanda tape rewinding, writing label DSD01, checking label, done. 6) ls -l /unige/amanda/bckp/DSD01 7) amdump DailySet 35.37u 469.11s 11:29.31 73.1% 8) ls /unige/amanda/bckp/DSD01 0-DSD01 3-obssb12._export_diskA1.0 6-obssb10._export_diskA1.0 0.DSD01 3.obssb12._export_diskA1.0 6.obssb10._export_diskA1.0 1-obssb13._export_diskA1.0 4-obssb11._export_diskA1.0 7-TAPEEND 1.obssb13._export_diskA1.0 4.obssb11._export_diskA1.0 7.TAPEEND 2-obssb14._export_diskA1.0 5-obssb1._export_diskA1.0 2.obssb14._export_diskA1.0 5.obssb1._export_diskA1.0 7)when I do amrecover, it asks me "The following tapes are needed: DSD01": : 2002-07-03 Disques amrecover> add Disques Added /bartho/system/sysinfo/Disques amrecover> extract Extracting files using tape drive file:/unige/amanda/bckp/ on host atalante. The following tapes are needed: DSD01 Restoring files into directory /export/diskE/amanda-2.4.3b3/sbin Continue? [Y/n]: Y Load tape DSD01 now Continue? [Y/n/t]: Y EOF, check amidxtaped.debug file on atalante. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue? [Y/n]: Y amrecover> quit So how should I do to use amrecover...! -- * * * -- **--- * :( BRINER Cédric* o + Observatory of Geneva, Switzerland .:oO0Oo:. cedricîbriner@obsóunigeùch* * o ( ^--- hint:replace the odd letters by dot ):*
[AMANDA]Q: amanda/udp: socket: Protocol not supported
Hello List, Please help, any info appreciated on the following : after installation of Amanda on a Sun Solaris 8 host I recieve the following error when restarting inetd : "inetd[320]: [ID 220303 daemon.error] amanda/udp: socket: Protocol not supported" Checked /etc/inet/services, inetd.conf, .amandahosts, nsswitch.conf, nslookup found no (obvious) typos. I've copied the lines in the services files an inetd.conf to five other Solaris 8 hosts, future clients, sighup the inetd's and no problems, amandad listening. So, where to look on. Any suggestions ? Thanks in advance, greetings, Rene R. den Hertog Corporate Unix Administrator Computer & Netwerk Services Rotterdam Municipal Port Management Phone +31 (0)10 - 252 15 73 Fax+31 (0)10 - 252 28 21 E-mail [EMAIL PROTECTED] Internet www.portofrotterdam.com World Port Center Wilhelminakade 909 3072 AP Rotterdam The Netherlands
