Simple Q
Howdy, I've lost my marbles and need help finding one. :) I installed AMANDA as a client on a machine only I can't use /usr as it has no space. I've chosen just to put it in / (/amanda), but the 'dailies' config is being looked for in /usr/local/etc/amanda/dailies How do I tell AMANDA to look in my /amanda directory for that stuff? I'd really appreciate this marble. Thanks! Chris I'm a free-range carnivore.
unsubscribe
unsubscribe
Re: Too many filesystems to AMANDA?
"John R. Jackson" wrote: > > >GNUTAR /var/xxx// 0 1970:1:1:0:0:0 1 > >exclude-file=*hh.yy.zz* ** > > Two questions about this part of the file. First, was the line really > split like above, or is that just an artifac of you getting the data > into the E-mail? No, dosn't split. Is an artifac. > Second, I realize (or assume) you changed the data and replaced sensitive > things with repeated characters (e.g. "xxx"), which is fine. But is > that what the "exclude-file=" part of that line really looked like > (aside from the character substitution)? In particular, were those > asterisks there? And was the space there between the two parts? This is a real line in my /tmp/amanda/amandad.20010626104712.debug GNUTAR /xxx/r/ttt/ 0 1970:1:1:0:0:0 1 exclude-file=*bbb..es* *mmm* The asterisks are there ok. But also there are lines without asterisk: GNUTAR //oo.x.es/C 0 1970:1:1:0:0:0 1 and also are problematics. > What does the dumptype for this client/disk look like? In particular, > the "exclude" information. > > >Do you have any other clue? > > I originally thought the problem was overflowing a packet, but the > above makes me think it might be a syntax problem for this disk in > your amanda.conf. > > If that does not turn out to be it, I sent you a patch I recently posted > to amanda-hackers to get around the 64 KByte UDP packet size. You might > give it a try. > > Make sure you use the "third try" version :-), as I've posted it more > than once. > > > Enrique Rodríguez Lázaro > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Thanks for all. -- Enrique Rodríguez Lázaro
Re: Compression with /dev/rmt/0n?
* Drew Raines <[EMAIL PROTECTED]> (Mon, Jul 02, 2001 at 11:26:30PM -0500) > > This might be a question better suited for sunmanagers, but I'll try it > here. > > I'm running Solaris 2.7 on an E450, with a DDS-3 changer. amanda's been > calling my tape drive by /dev/rmt/0n, which is the OS default. From the > st(7D) manpage, it looks like by not specifying a `u' or a `c' in my device > name that hardware compression has not been used (contrary to popular > opinion). The `n' simply means non-rewinding. So does Solaris default to > using compression or not? Do I need to specify a `l' flag (low density) > like so? > > /dev/rmt/0ln > > Everything in the /kernel/drv/st.conf file is set to default (all > commented). i's been awhile since Iv'e read these things, but the entry for the dds3 looks like this HP_DAT_3 = 1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,1; but the 4 gives the number of densities, and the 4 hex numbers after that (0x00 0x8c 0x8c 0x8c) give the 4 different density modes. IIRC the first one (0x00 is for /dev/rmt/Xl) the other for Xc Xh and one other I forgot). So, yes, /dev/rmt/0l should give different characteristics. Currently listening to: Phish - La Grange () Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\<, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: How to configure AMANDA to take backup of raw filesystems?
>DUMP cannot take the backup of raw filesystems, but DD can. > >Can you please tell me how we can make AMANDA use DD to take the backup? First turn off HTML encoding when you send email Then you could trick Amanda and use a Gnu tar wrapper. 1) you make a wrapper Shell Script 2) You build amanda giving the chell path as if it was your GNU tar program Of course the shell script should behave like tar (i.e. return the correct values when needed, size, etc.) There was a post a couple a weeks ago, about turning off anf on database, before a back-up, the answer had a pointer to an example of such shell script. You'll need to really understand what you are doing there. Good luck Olivier
Re: How to configure AMANDA to take backup of raw filesystems?
Hi, DUMP cannot take the backup of raw filesystems, but DD can. Can you please tell me how we can make AMANDA use DD to take the backup? Thanks, Sajith Olivier Nicole wrote: [EMAIL PROTECTED]"> How can we configure AMANDA to take backup of "raw" filesystems that areused for storing INFORMIX / ORACLE databases..? If dump (ufsdump) can back-up this, Amanda can, if not, you'll have tofind a work-around.Amanda is just a super meta caller for dump (or tar, or other).Olivier -- Sajith Mannadiar SDE Support [ Nortel Lab ] Wipro Technologies 72, Electronics City Bangalore 561 229 Ph: +91-80-8520408 @ 3216 ESN: 877-8465
Really weird Error.
All, I have a weird(!) problem: The message during amcheck was: NAT: amandad busy I checked the archives and found a reasonable number of answers: * some people said to make sure that not two cron jobs at the same time trying to access the tape. (now I have not set this up yet, I still start it by hand ...) * I checked with 'ps' whether there was a damon already running (no there wasnt) * The disklist might contain ONE host refered to by different names, (No, the host is known ONLY by one name and this setup has been working fine!). So I looked thrugh the full listing of "ps -edf | sort -n" and saw that user amanda was running the program: /usr/local/libexe/selfcheck Now I tried (as root) to throw everything I could at that process to kill it, I even RESTARTED xinetd with NO amanda options, killed every shell, killed X (not that this matters as PPID of selfcheck is "1", so init). All I had running was ONE shell and my normal deamons (httpd,sendmail,squid etc). Tried it as amanda. Nothing. Zilch. What does it do? Sadly, I used my last option; my uptime is rather small now and it was pretty big :-(((. Amanda works fine now again, but I dont like the reboot option! [1] I just did a combo of amlabel, amcheck and an amdump and its fine and whats left over is the shell I su'ed into: [218] [piquet:root] / #ROOT# >ps -edf | sort -nr | /bin/grep -i aman | grep -v /bin/grep root 1496 1461 0 12:30 pts/700:00:00 su amanda amanda1499 1496 0 12:30 pts/700:00:00 -csh [219] [piquet:root] / #ROOT# > jobst [1] A little bit of trivia: A downloaded a fix for "rdisk" for WinNT. This fix was an executable which did not have any libararies but got rid if a scary security flaw. I installed this on a server but double clicking on the hotfix. It rebooted the server, the main domain/file server without warning! This was a Microsoft HOTFIX! No wonder I dont like them. -- Sometimes, the sharpest sword is not enough, but usually...it is. |__, Jobst Schmalenbach, [EMAIL PROTECTED], Technical Director| | _ _.--'-n_/ Barrett Consulting Group P/L & The Meditation Room P/L | |-(_)--(_)= +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia|
Re: Compression with /dev/rmt/0n?
On Tue, Jul 03, 2001 at 09:18:37AM +0200, Gerhard den Hollander wrote: > * Drew Raines <[EMAIL PROTECTED]> (Mon, Jul 02, 2001 at 11:26:30PM -0500) > > > > This might be a question better suited for sunmanagers, but I'll try it > > here. > > > > I'm running Solaris 2.7 on an E450, with a DDS-3 changer. amanda's been > > calling my tape drive by /dev/rmt/0n, which is the OS default. From the > > st(7D) manpage, it looks like by not specifying a `u' or a `c' in my device > > name that hardware compression has not been used (contrary to popular > > opinion). The `n' simply means non-rewinding. So does Solaris default to > > using compression or not? Do I need to specify a `l' flag (low density) > > like so? > > > > /dev/rmt/0ln > > > > Everything in the /kernel/drv/st.conf file is set to default (all > > commented). I don't "think" your tape drive would work if all were commented. > i's been awhile since Iv'e read these things, but the entry for the dds3 > looks like this > > HP_DAT_3 = 1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,1; > but the 4 gives the number of densities, and the 4 hex numbers after that > (0x00 0x8c 0x8c 0x8c) give the 4 different density modes. > > IIRC the first one (0x00 is for /dev/rmt/Xl) the other for Xc Xh and one > other I forgot). > > So, yes, /dev/rmt/0l should give different characteristics. Clarification: The default density is that specified by the last number in the entry. Not the hex nums themselves, but the single digit following the hex nums. It specifies which of the 4 density specific devices names (l, m, h, or [cu]) is the same as the non-specific device name. This number is base zero, not one. In the entry above the default is "1", the second density entry, or the "0m" device (density number 0x8c) is the same as the "0" device. My Solaris st.conf entry differs: HPdds3 = 1,0x34,0,0xd639,4,0x00,0x13,0x24,0x3,3; ^ _| | Here the fourth density (number 3 with base 0), i.e. the highest density is the default. Thus device 0 is the same as device 0c or 0u. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing [EMAIL PROTECTED] 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Manual Tape changing
Hello John, Thanks for your prompt help! Everything seems to work great. One thing remains though. I find it strange that I get this line in the backup report: ### These dumps were to tapes Monthly-03, Monthly-04. The next 2 tapes Amanda expects to used are: a new tape, a new tape. ### The next tapes in the "tapelist" file clearly indicate the sequence of empty tapes: ### 20010630 Monthly-04 no-reuse 20010630 Monthly-03 no-reuse 20010519 Monthly-02 no-reuse 0 Monthly-13 reuse 0 Monthly-12 reuse 0 Monthly-11 reuse 0 Monthly-10 reuse 0 Monthly-09 reuse 0 Monthly-08 reuse 0 Monthly-07 reuse 0 Monthly-06 reuse 0 Monthly-05 reuse ### Why is it not asking for Montly-05 and Monthly-06 for the next backup? Also, I accidently did an "amrmtape" of Monthly-01. What are the steps to recover the indexes? Thanks. "John R. Jackson" wrote: > >When we change the "request()" in "src/changer-src/chg-manual.sh.in" to > >include notification every 60 minutes will AMDUMP automatically detect > >the inserted tape and continue the backup? ... > > That depends on how you changed request(). :-) > > If you took the code in the comments and put that in the changer.conf > file so it overrides the builtin request, it will check for the tape being > mounted every minute (not every hour). As soon as the drive goes ready, > amdump (or amcheck, etc) will continue. > > The one hour timer in the script is for the E-mail notification only. > > >Also, suppose that I want I don't want to be mailed every hour but > >instead I want Amanda to dump to the holding disk and wait for me to > >make the next tape available in the morning. How would I change the > >"request()"? > > I think you'll have to do more than just change request() to accomplish > this. Here's how I'd try it: > > * Change request to set "tape" to "skip" (or some non-/dev name) > after an hour. > > * Change the code in loadslot that calls request() to look for $tape > being "skip" after the call, and if so, return an error back to the > caller (e.g. look at how eject() handles an error). Amanda will > handle this and do the rest of the dumps in degraded mode (into the > holding disk). > > >My understanding of the need for the changer.conf file is for automatic > >tape changers...is this correct? > > Not necessarily. Contents of the changer.conf file (or files) is entirely > up to the changer. For most, it is configuration information, such as > the range of slots, and other hardware characteristics. For chg-manual, > the file is sourced into the script, which means it can do things like > override the request() function. > > >Finally, do I need to put some special label sequence on the tapes for > >this configuration (ie Monthly-XXX-Slot-X)? ... > > No, although it might make your life easier. As long as you know what > slot 14 is when the changer asks for it, Amanda doesn't care what the > actual label is on the tape. > > Actually, the slot number is pretty meaningless to chg-manual. As long > as you load the next tape Amanda wants, the slot number itself is not > used for anything. In fact, if you do an "amtape eject" after > each run, the slot number will be reset to zero. If you do an "amadmin > tape" before the run, slot zero means the first tape, slot 1 > means the second and so on. > > >Luc Lalonde > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Luc Lalonde, Responsable du reseau GIREF Telephone: (418) 656-2131 poste 6623 Courriel: [EMAIL PROTECTED] begin:vcard n:Lalonde;Luc x-mozilla-html:FALSE org:Universite Laval;GIREF adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Administateur de reseau x-mozilla-cpt:;0 fn:Luc Lalonde end:vcard
Re: Simple Q
>I installed AMANDA as a client on a machine only I can't use /usr as it >has no space. I've chosen just to put it in / (/amanda), but the >'dailies' config is being looked for in /usr/local/etc/amanda/dailies I don't understand. The clients know nothing about "configurations". What, exactly, did it say that led you to think it was looking in /usr/local/etc/amanda/dailies? >Chris John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Manual Tape changing
>The next tapes in the "tapelist" file clearly indicate the sequence of empty >tapes: >... >Why is it not asking for Montly-05 and Monthly-06 for the next backup? What is "tapecycle" set to in amanda.conf? If it's bigger than 12 (the number of tapelist entries), that would explain why Amanda thinks it needs "new" tapes. >Also, I accidently did an "amrmtape" of Monthly-01. What are the steps to >recover the indexes? What do you mean by "indexes"? If you mean the catalogues that amrecover uses, you can't. This is a harder problem than it might seem because the image has to be sent back to the client to regenerate the catalogue (in the general case). For instance, my tape servers are Solaris boxes and they don't have the AIX restore program to do a catalogue. It's possible a special case could be made for GNU tar, but nobody has done the work. If you mean the other information Amanda uses to remember a tape (the curinfo database, the log.MMDD.NN files, etc), that's also probably not possible (and now you know why I create several backups of my Amanda areas :-). Yet another item for the TODO list. Actually, if you have not made any Amanda runs since you did the amrmtape, it looks like the previous tapelist file is in .../tapelist~ (note the trailing tilde character) and the exported curinfo database is in .../curinfo.orig.$$ (depending somewhat on what "infofile" is set to in your amanda.conf). So if you have those two files, you could put the tapelist back (I'd diff it to make sure all you're doing is adding the missing tape back in) and you can do an "amadmin import" to restore the curinfo area. I'd tar the existing curinfo area first and look very, very carefully at the results. You might even do an "amadmin export" and diff that with the *.orig.$$ file to see what will be changing. If you just want to know what's on the tape for your own use (i.e. so if you need to do a restore you can do it "by hand"), you can use amrestore: mt rewind amrestore -p $TAPE no-such-host > /dev/null This will search the tape for a client named "no-such-host" and, of course, not find it. But along the way it will report all the images it skips. >Luc Lalonde John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Really weird Error.
>Now I tried (as root) to throw everything I could at that process to kill it, >I even RESTARTED xinetd with NO amanda options, killed every shell, killed >X (not that this matters as PPID of selfcheck is "1", so init). All I had >running was ONE shell and my normal deamons (httpd,sendmail,squid etc). >Tried it as amanda. Nothing. Zilch. That usually means the process is hung in the kernel someplace. >What does it do? It does a number of things. Many of the tests are optional, depending on other dumptype settings. For instance, it only looks for GNU tar if there is a disk that will be backed up with GNU tar. Anyway, here are the things 2.4.2p2 (you didn't say what version you were running) does (all I'm doing is looking through the code and translating it to English): * Look for the Amanda runtar and rundump programs. * Look for the system dump and restore programs, GNU tar and smbclient. * Look for the compress program. * Make sure /etc/amandapass, /etc/dumpdates and/or /etc/vdumpdates are accessible. * Make sure /dev/null is accessible. * Make sure there is enough space in the Amanda temp directory, the debug directory and /etc (for /etc/dumpdates). * Make sure each device or directory to be backed up is accessible. For Samba shares, this involves actually connecting to the share and doing a dummy command. Most of this is done with the access() system call. Other than the smbclient check of a share, selfcheck is trivial. >Sadly, I used my last option; my uptime is rather small now and it was >pretty big :-(((. I doubt you had any choice. Something in your kernel got lost and there was probably no hope of unwedging it without the reboot. You'd have to dig into kernel debugging to track down exactly where it was at. >jobst John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Connection reset by peer problem again
>... Firewall is present between the client and amanda server. But we already ope >ned a full hole for amanda traffic. >... > sugar /export/home lev 0 FAILED [mesg read: Connection reset by peer] This says the client (or the firewall) closed this connection and dumper on the server was not happy about that. There are either two or three connections between the client and dumper. The mesg one passes log message from the client back to dumper. It is (usually) very low activity. The data path sends the actual dump image and should be very active. The index path is optional and sends the catalogue. It can either be high activity at the beginning (if you're using dump) or sporadic (GNU tar). >From above report, we can observe that amanda can perform backup on other dire >ctories on the host 'sugar'. But it can't perform backup on the /export/home d >irectory. About my only guess is that the firewall timed out the connection. There would be very little traffic on the mesg path. So you may need to tweak the firewall configuration some more. You might take a look at the /tmp/amanda/sendbackup*debug file on the client that goes along with this file system (if you used --with-pid-debug-files on ./configure or are running 2.4.2p2) and see what kinds of timestamps it shows. Take a look at the last modification time on the file as well (ls -l). >Edward. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
tpchanger command clarification
Hello all. I am looking for some clarification of the functions of the tape changer script. The TAPE.CHANGER file says: The tape changer program must support the following commands: -slot changes to a particular slot Does this mean to move the robot arm to that slot and stop, or to load the tape from that slot into the drive? Then is says: -eject ejects the currently loaded tape, if appropriate. Output and error handling are the same as the -slot command. Does this mean to eject the tape but leave it in the drive, or to eject the tape and put it backup into it's original slot? Thanks in advance! Anthony Valentine Unix System Admin/Oracle DBA Spenard Builders Supply [EMAIL PROTECTED]
interestng developments
If I use another Linux machine, instead of local host - I get the following from Amcheck. It looks like the same problem, but why would the connection be refused on Linux but not Irix? Amanda Tape Server Host Check - /backup: 2686228 KB disk space available, using 2583828 KB. amcheck-server: slot 4: date 20010623 label DailySet1-04a (exact label match) NOTE: skipping tape-writable test. Tape DailySet1-04a label ok. Server check took 7.877 seconds. protocol packet receive: Connection refused protocol packet receive: Connection refused protocol packet receive: Connection refused Amanda Backup Client Hosts Check WARNING: inwood: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.098 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1)
Re: Simple Q
*Light bulb goes from totally dark to a dim luminescence* I ran amcheck from the client side (I had installed it without the --without-server tag). I guess one doesn't use AMANDA server-side programs on the client when it's supposed to be a client eh? :) Doh. Thanks! Chris On Tue, 3 Jul 2001, John R. Jackson wrote: > >I installed AMANDA as a client on a machine only I can't use /usr as it > >has no space. I've chosen just to put it in / (/amanda), but the > >'dailies' config is being looked for in /usr/local/etc/amanda/dailies > > I don't understand. The clients know nothing about "configurations". > What, exactly, did it say that led you to think it was looking in > /usr/local/etc/amanda/dailies? > > >Chris > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] > I'm a free-range carnivore.
strange dump error
Hi All, I am very new to this. So if the question I ask has been answered before, please bare with me and point me to the right direction. My problem is a "strange dump" error which seemed to occur more and more often. I think I know what the problem is but not know how to fix it or work around it. Here is the report from Amanda: === These dumps were to tape Datapark08. Tonight's dumps should go onto 1 tape: Datapark10. FAILURE AND STRANGE DUMP SUMMARY: freeway.da /dev/sda2 lev 0 STRANGE STATISTICS: Total Full Daily Dump Time (hrs:min) 1:06 0:33 0:00 (0:02 start, 0:31 idle) Output Size (meg) 1054.3 1054.3 0.0 Original Size (meg) 2091.3 2091.3 0.0 Avg Compressed Size (%) 50.4 50.4 -- Tape Used (%) 17.6 17.6 0.0 Filesystems Dumped 1 1 0 Avg Dump Rate (k/s) 617.2 617.2 -- Avg Tp Write Rate (k/s) 552.1 552.1 -- FAILED AND STRANGE DUMP DETAILS: /-- freeway.da /dev/sda2 lev 0 STRANGE sendbackup: start [freeway.datapark.com:/dev/sda2 level 0] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/local/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: Cannot add file ./var/spool/mqueue/xfMAA07342: No such file or directory | Total bytes written: 2192885760 sendbackup: size 2141490 sendbackup: end \ NOTES: driver: WARNING: /dump/data: 3072000 KB requested, but only 2790624 KB available. planner: Last full dump of freeway.datapark.com:/dev/sda2 on tape Datapark10 overwritten in 1 run. taper: tape Datapark08 kb 1079616 fm 1 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- -- -- freeway.d /dev/sda2 0 2141490 1079584 50.4 29:09 617.2 32:35 552.1 (brought to you by Amanda version 2.4.1) === I think the file that it can't find is a sendmail file. After the message is being sent, it will delete that file. So of course it is not there.Is there a way that I can by pass a certain directory so that it won't back up the temporary files? thanx. Jean
RE: Connection reset by peer problem again
Hi there, I found some debug message on the client sugar. Please help me to check. Please don't mind that I masked the IP address of backup server. Successful Backup Run for sugar (Another directories) debug file === sendbackup: debug 1 pid 18955 ruid 5023 euid 5023 start time Wed Jul 4 03:43:13 2001 /usr/local/amanda/libexec/sendbackup: version 2.4.2p2 sendbackup: got input request: GNUTAR /usr/local/mysql 1 2001:6:27:19:16:16 OPTI ONS |;bsd-auth;compress-best;index; parsed request as: program `GNUTAR' disk `/usr/local/mysql' lev 1 since 2001:6:27:19:16:16 opt `|;bsd-auth;compress-best;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: stream_server: waiting for connection: 0.0.0.0.34388 sendbackup: stream_server: waiting for connection: 0.0.0.0.34389 sendbackup: stream_server: waiting for connection: 0.0.0.0.34390 waiting for connect on 34388, then 34389, then 34390 sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62714 sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62715 sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62716 got all connections sendbackup: spawning /bin/gzip in pipeline sendbackup: argument list: /bin/gzip --best sendbackup-gnutar: pid 18956: /bin/gzip --best sendbackup-gnutar: doing level 1 dump as listed-incremental from /usr/local/aman da/var/gnutar-lists/sugar_usr_local_mysql_0 to /usr/local/amanda/var/gnutar-list s/sugar_usr_local_mysql_1.new sendbackup-gnutar: doing level 1 dump from date: 2001-06-27 19:16:16 GMT sendbackup: spawning /usr/local/amanda/libexec/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /usr/local/mysql - -one-file-system --listed-incremental /usr/local/amanda/var/gnutar-lists/sugar_u sr_local_mysql_1.new --sparse --ignore-failed-read --totals . sendbackup-gnutar: /usr/local/amanda/libexec/runtar: pid 18958 sendbackup: started index creator: "/bin/gtar -tf - 2>/dev/null | sed -e 's/^\./ /'" sendbackup: index created successfully sendbackup: pid 18955 finish time Wed Jul 4 03:43:21 2001 Failed Sugar Dump File === sendbackup: debug 1 pid 18993 ruid 5023 euid 5023 start time Wed Jul 4 03:43:28 2001 /usr/local/amanda/libexec/sendbackup: version 2.4.2p2 sendbackup: got input request: GNUTAR /export/home 0 1970:1:1:0:0:0 OPTIONS |;bs d-auth;compress-fast;index; parsed request as: program `GNUTAR' disk `/export/home' lev 0 since 1970:1:1:0:0:0 opt `|;bsd-auth;compress-fast;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: stream_server: waiting for connection: 0.0.0.0.34398 sendbackup: stream_server: waiting for connection: 0.0.0.0.34399 sendbackup: stream_server: waiting for connection: 0.0.0.0.34400 waiting for connect on 34398, then 34399, then 34400 sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62717 sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62718 sendbackup: stream_accept: connection from 202.XXX.XXX.XXX.62719 got all connections sendbackup: spawning /bin/gzip in pipeline sendbackup: argument list: /bin/gzip --fast sendbackup-gnutar: pid 18994: /bin/gzip --fast sendbackup-gnutar: doing level 0 dump as listed-incremental to /usr/local/amanda /var/gnutar-lists/sugar_export_home_0.new sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: spawning /usr/local/amanda/libexec/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /export/home --one -file-system --listed-incremental /usr/local/amanda/var/gnutar-lists/sugar_expor t_home_0.new --sparse --ignore-failed-read --totals . sendbackup-gnutar: /usr/local/amanda/libexec/runtar: pid 18996 sendbackup: started index creator: "/bin/gtar -tf - 2>/dev/null | sed -e 's/^\./ /'" index tee cannot write [Broken pipe] sendbackup: pid 18995 finish time Wed Jul 4 05:43:45 2001 Failed backup occured because the index tee cannot write. Is it related to local client or server-side ? In my firewall, connection timeout is 60 minutes. I think that it's pretty long. Regards, Edward. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John R. Jackson Sent: Wednesday, July 04, 2001 2:42 AM To: Edward Tsang Cc: [EMAIL PROTECTED] Subject: Re: Connection reset by peer problem again >... Firewall is present between the client and amanda server. But we already ope >ned a full hole for amanda traffic. >... > sugar /export/home lev 0 FAILED [mesg read: Connection reset by peer] This says the client (or the firewall) closed this connection and dumper on the server was not happy about that. There are either two or three connections between the client and dumper. The mesg one passes log message from the client back to dumper. It is (usually) very l
Symbolic Link and Next Tape Prediction ?
Hi there, I had 2 questions related to our new amanda setup. 1) How can I use gtar to backup directories with symbolic links ? For example, in directory A, there are 3 symbolic links pointing to C, D, E directories. Is it possible to backup those files in C, D, E? Any special patches need to be applied ? 2) How Amanda use the tape sequence ? For example, I have 15 tapes for backup purpose. Will it use the tape 1 after the tape 15 is used ? I asked this question because our servers are housed in remote data center. Data Center operator uses predefined tape schedule to change tape manually. They will not receive amanda email to check for next tape name. Regards, Edward.
