Re: trouble (?) with amrecover (gtar in fact)
>here is a sample of the gnutar list for 1.13 (looks bad) : > >2555905 43008 ./kretzsch/mail/communication_OBS >2555905 40960 ./kretzsch/mail/SOHO-news That's the wrong file. I'm talking about the index files. Those look like the incremental list file. Look up the indexdir value from amanda.conf and check down in there. >Is there any document dealing with the advantages/disadvantages >of using gtar or the system's dump/restore? This has been discussed over and over on this mailing list. Check the archives. >I also believe that a gtar archive could be extracted from nearly >any platform, but a classic dump archive won't because it's >OS specific. (true/false?) Pretty much true. Sometimes dump format can be read between platforms, but you should not plan on it. >Pierre. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing files
>The last problem i found by looking at sendsize*debug as you suggested: it >showed that it didn't expect /etc/amandates to be a directory so i deleted >it and made a _file_ with that name instead. (amcheck didn't pick on this >problem.) ... It's on the TODO list to detect this. Now if I could just figure out how so many people manage to create it as a directory ... >But i have a question as to why, according to a tar on the tape afterwards, >only four out of the nine items in the directory to dump were actually >backed up. ... What version of GNU tar are you using? If it's not at least 1.13.17 (and probably 1.13.19 would be better), you should upgrade. Did Amanda do a full dump (level 0) or an incremental (level > 0)? >Also, am I supposed to create a info file and directory for every line in >disklist? ... No. Those are just informational messages from amcheck. Those directories will be automatically created for you by amdump (et al). >george John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: holding space estimates
>Ideally amanda should look every time a chunk is written to disk how much >space ios free ... That's probably a good idea. I've added it to the TODO list. >Gerhard den Hollander John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
missing files
It worked! I got a backup on tape and amdump sent me a success email! The last problem i found by looking at sendsize*debug as you suggested: it showed that it didn't expect /etc/amandates to be a directory so i deleted it and made a _file_ with that name instead. (amcheck didn't pick on this problem.) I also made a couple other small changes, for the record, not sure if they helped any. But i have a question as to why, according to a tar on the tape afterwards, only four out of the nine items in the directory to dump were actually backed up. Here's the nine items in the dir: # ls -l /home/amanda total 44 drwx--3 amanda amanda 4096 May 4 13:13 . drwxr-xr-x 11 root root 4096 Apr 27 13:45 .. -rw-rw-r--1 amanda amanda 46 May 4 13:09 .amandahosts -rw-rw-r--1 amanda amanda 21 Apr 30 16:07 .amandahosts~ -rw---1 amanda amanda 2388 May 2 18:26 .bash_history -rw-r--r--1 amanda amanda 24 Apr 27 13:45 .bash_logout -rw-r--r--1 amanda amanda230 Apr 27 13:45 .bash_profile -rw-r--r--1 amanda amanda124 Apr 27 13:45 .bashrc -rwxr-xr-x1 amanda amanda333 Apr 27 13:45 .emacs -rw-r--r--1 amanda amanda 3394 Apr 27 13:45 .screenrc drwx--2 amanda root 4096 Apr 30 14:20 .xauth What appears on the tape after the amdump: # tar tvv -rw-r--r-- amanda/amanda 230 2001-04-27 13:45 ./.bash_profile -rw-r--r-- amanda/amanda 124 2001-04-27 13:45 ./.bashrc -rwxr-xr-x amanda/amanda 333 2001-04-27 13:45 ./.emacs -rw-r--r-- amanda/amanda 3394 2001-04-27 13:45 ./.screenrc Also, am I supposed to create a info file and directory for every line in disklist? For example, creating /var/log/amanda/curinfo/dellmachine/ _home_amanda/info was necessary to make an amcheck complaint go away. thx again, george "John R. Jackson" wrote: > >What causes missing results? > > Usually a timeout. Take a look at /tmp/amanda/sendsize*debug on the > client and figure out the total time (look at the first and last lines). > Amanda allows five minutes per disk. If that's not enough, crank up > the etimeout value in amanda.conf. > > >george herson > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: "missing result"
>What causes missing results? Usually a timeout. Take a look at /tmp/amanda/sendsize*debug on the client and figure out the total time (look at the first and last lines). Amanda allows five minutes per disk. If that's not enough, crank up the etimeout value in amanda.conf. >george herson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
"missing result"
Yes, i amlabel'ed the tape i'm using. You were correct: I didn't comment out the tpchanger definition on my single-slotted server, sorry. Now i'm up to an email failure report that says: "FAILURE AND STRANGE DUMP SUMMARY: dellmachin /home/amanda lev 0 FAILED [missing result for /home/amanda in dellmachine response]" What causes missing results? My disklist is "dellmachine /home/amanda root-tar". thx, george herson "John R. Jackson" wrote: > >Thanks for your advice below (setting changerfile) as I am much further > >along, past amlabel and amcheck and up to trying to use amdump. > > So you've amlabel'd all your tapes? > > >Amanda seems to thinks i have a tape changer ... > > You've apparently told it to use chg-manual in amanda.conf. That's a > "manual" tape changer, i.e. it uses all the Amanda changer hooks but > expects to talk to a human to do the work. > > If you don't want to do that, comment out tpchanger and make sure tapedev > points to your tape device. > > >when i enter "amdump > >Dell-Full" I'm told to keep putting in more tapes. Why? > > I don't know. What's in /tmp/amanda/changer*debug? > > >george herson > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
PLease remove
Pkease remove [EMAIL PROTECTED] from all lists on amanda.org. He is no longer an employee here. You may verify this by writing shammond@thestandard and receiving a bounced message. Please implement a remove-upon-bounced-messages on your list. Thanks, Ben C Ben Campbell Desktop Support Specialist The Industry Standard 315 Pacific Ave San Francisco, CA 94111 [EMAIL PROTECTED] 415.617.4104
Re: amlabel not seeing tape
>Thanks for your advice below (setting changerfile) as I am much further >along, past amlabel and amcheck and up to trying to use amdump. So you've amlabel'd all your tapes? >Amanda seems to thinks i have a tape changer ... You've apparently told it to use chg-manual in amanda.conf. That's a "manual" tape changer, i.e. it uses all the Amanda changer hooks but expects to talk to a human to do the work. If you don't want to do that, comment out tpchanger and make sure tapedev points to your tape device. >when i enter "amdump >Dell-Full" I'm told to keep putting in more tapes. Why? I don't know. What's in /tmp/amanda/changer*debug? >george herson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amlabel not seeing tape
John, Thanks for your advice below (setting changerfile) as I am much further along, past amlabel and amcheck and up to trying to use amdump. Amanda seems to thinks i have a tape changer: when i enter "amdump Dell-Full" I'm told to keep putting in more tapes. Why? Here i'm simply taking out the same tape and re-inserting it: insert tape into slot 1 and press return insert tape into slot 2 and press return insert tape into slot 3 and press return insert tape into slot 4 and press return Then I put in a fresh, blank tape and got: insert tape into slot 5 and press return ^C'ing out and retrying produces much the same thing. What could be wrong? I have very simple setup: 1 machine as both client and server, with 1 tape drive with 1 slot. I have just "dellmachine /boot root-tar" in disklist. thank you, george herson "John R. Jackson" wrote: > >(/usr/adm/amanda/changer-status-clean: No such file or directory): > > The Amanda changers now want to store three "state" files. All the file > names are based on the "changerfile" variable in your amanda.conf. > > My guess is you have not set that variable, it's defaulting to > /usr/adm/amanda/changer and directory /usr/adm/amanda does not exist. > This is not your fault -- I think some new ideas slipped in without > fully comprehending their impact. Sorry. > > Try setting "changerfile" to someplace Amanda can write, such as the > directory that holds your tapelist file. Make sure the name ends in > "/changer" because the other names add a suffix on to that. > > For instance, if tapelist is in directory /usr/local/etc/amanda/xxx, > add this to amanda.conf: > > changerfile "/usr/local/etc/amanda/xxx/changer" > > This will cause these files to be created: > > /usr/local/etc/amanda/xxx/changer-clean > /usr/local/etc/amanda/xxx/changer-access > /usr/local/etc/amanda/xxx/changer-slot > > Or you can pick some other directory. Just as long as the Amanda user > has write access to it. > > >george herson > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Segmentation Fault at getservbyname
First of all the answer to all the other questions is yes. "John R. Jackson" wrote: > About the only other idea I have is to set up ./configure to not optimize > (i.e. do not use -O with gcc). That's always the first guess at a > compiler problem. This won't matter too much to Amanda because it > (at least the actual Amanda parts) are not CPU bound. > This is the answer that did the trick. I had looked at the gcc optimization, but decided it defaulted to none and didn't see where it was getting turned on. I modified the configure script to remove optimization from the gcc compiler. And presto, I don't get the seg faults any more. Thanks, now I am able to successfully backup and recover using amanda and the gcc compiler. Now to write all my notes down, so I'll remember how I got here. -- [EMAIL PROTECTED] LAN Engineer/Administrator RS Information Systems, Inc. (405)366-6545 ext. 3249 begin:vcard n:Cole;Russell tel;fax:(405)366-2961 tel;work:(405)366-6545 ext.3221 x-mozilla-html:FALSE url:http://www.noaa.gov org:RS Information Systems, Inc.;Engineering - Software adr:;;3200 Marshall Avenue, Suite 100;Norman;OK;73072;USA version:2.1 email;internet:[EMAIL PROTECTED] title:LAN Engineer/Administrator fn:Russell C. Cole end:vcard
Where is kerberos support for 2.4.2p2?
On the FTP site, all I see is: amanda-krb4-2.4.0-2.4.0p1.diff.gz amanda-krb4-2.4.0p1.tar.gz old-versions So where can I get the kerberos bits for 2.4.2p2? -- Tom Schutter (mailto:[EMAIL PROTECTED]) Platte River Associates, Inc. (http://www.platte.com)
Re: Strange Amanda Error: sendbackup: index tee cannot write [Broken pipe]
The problem ended up being the autosensing media. I have never run into a problem with a media autosense before but I think from now on I will try to set that every time I setup a network card. Thanks for the Help, Ryan Williams - Original Message - From: "John R. Jackson" <[EMAIL PROTECTED]> To: "Ryan Williams" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, May 01, 2001 6:59 PM Subject: Re: Strange Amanda Error: sendbackup: index tee cannot write [Broken pipe] > >It is a 100meg card set to autoselect between all of the 100 and 10 base T. > > Uh, huh. On Solaris, at least, autoselect is death. No matter what > you try to do, it will pick wrong and really bad things start to happen. > We **always** force the issue with an explicit config file entry. > > I don't know that's what's happening to you, but it's been a common > problem. > > >The network is a 10baseT. I am not shure if it is full or half duplex. ... > > I'm out of my depth here, but I think if the cable is actually 10Mbit, > duplex does not matter. Only 100Mbit bring duplex into the picture. > > >What do you make of that. I dont see anywhere that it says what it is > >actually set at. ... > > Which might make sense if it does not apply because you're really only > doing 10Mbit. > > >> It would also be useful to go to the client and look at sendbackup*debug > >> in /tmp/amanda, in particular the start and stop time (first and last > >> lines). > > > >/usr/local/libexec/sendbackup: got input request: DUMP ad0s1e 0 > >1970:1:1:0:0:0 OPTIONS |;bsd-auth;srvcomp-fast;index; > > parsed request as: program `DUMP' disk `ad0s1e' lev 0 since 1970:1:1:0:0:0 > >opt `|;bsd-auth;srvcomp-fast;index;' > > waiting for connect on 2622, then 2623, then 2624 > >/usr/local/libexec/sendbackup: timeout on mesg port 2623 > >/usr/local/libexec/sendbackup: timeout on index port 2624 > >sendbackup: pid 79500 finish time Tue May 1 01:47:00 2001 > > You cut off the first line, but in any case, this indicates something else > is going on. It says sendbackup on the client got tired (30 seconds) > of waiting on dumper on the server side to make the connections on > those ports. The next line after "waiting for connect ..." should have > been "got all connections". > > The sequence of events is: > > dumper connects to the amandad port on the client > > they do some security stuff (UDP packets) then dumper tells it to > start sendbackup > > sendbackup starts listening on two or three new ports and sends their > numbers (UDP packet) back to dumper on the server > > dumper connects to those ports (TCP) on the client and data starts > to flow > > So either dumper never got the list of ports, or the connections it > tried to make didn't work. It looks like dumper would log an error if > the connection failed, which implies sendbackup never saw it. > > If you upgrade at least the server to 2.4.2p2, you'll get messages > like this in the amdump.NN file showing that dumper did its part: > > dumper: stream_client: connected to 128.210.10.26.63832 > dumper: stream_client: our side is 0.0.0.0.63834 > > Upgrading the client would show similar extra detail on that side. > > I don't know why this would be happening. Any firewalls or other > protection between the two machines that would not allow these ports to > go through? Any help from the FreeBSD folks? > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
amandad
Hi, I'm having trouble with amanda 2.4.1-p1 running on a RedHat-Linux-Server. Everything is working fine.. except the problem, that sonetimes the amandad is stopped. Can anyone tell me why? This is the message in /var/log/messages: May 4 14:59:56 earth xinetd[12802]: amanda service was deactivated because of looping May 4 14:59:56 earth xinetd[12802]: recv: Ungueltiger Dateideskriptor (errno=9) THX, Annette
Re: [amrestore] file too large
> > On May 3, 2001, Pierre Volcke <[EMAIL PROTECTED]> wrote: > > > amrestore: 4: restoring planeto._home_zone10.20010502.0 > > amrestore: write error: File too large > Alexandre Oliva wrote: > > You seem to be bumping into file size limits of the host filesystem. > You may want to pipe the output of amrestore -p directly to tar, or to > bsplit. > Bort Paul wrote: > Perhaps your operating system cannot handle files over 2Gb? Most Linuxes > can't. I don't know about *BSD or Solaris/SunOS. > that seems to be the problem : the host is a Linux RH7, with kernel 2.2.16. thanks, Pierre.
Re: trouble (?) with amrecover (gtar in fact)
"John R. Jackson" wrote: > > > Scanning /the/holdingdisk ... > > 20010328: found Amanda directory. (*) > > 20010416: found Amanda directory. > >... > > (*) these directories are empty. > > Just for my own curiosity, why are they still there if they are empty? > I don't know why exactly, sorry. According to your question, I shouldn't wait for them to be deleted automatically! They look rather old and I was maybe performing some tests that failed at this time. > > > the 'ls' command only shows me a very small part > > of what is supposed to be backed up, I mean only a > > few directories & files out of hundreds. > > I take it you're using GNU tar? What version? If it's older than > 1.13.17 (even better, 1.13.19), the index files may be corrupt. > that's a good guess, on my client machine (AIX) this is gtar 1.13 ! > > Go to your index directory and look at one of the files. If each line > has a very large number on it, that's a symptom of a broken tar. > here is a sample of the gnutar list for 1.13 (looks bad) : 2555905 43008 ./kretzsch/mail/communication_OBS 2555905 40960 ./kretzsch/mail/SOHO-news and a sample of gnutar list for 1.13.17 on my tape server (looks better!): 2070 407572 ./doute/Missions_inst/NIMS/Data 2070 407569 ./doute/Missions_inst/NIMS/Tools so the problem is now pointed out, thanks! now it involves another question : Is there any document dealing with the advantages/disadvantages of using gtar or the system's dump/restore? I've read in the Amanda docs that 'gtar' provides me with exclude-lists, but 'restore' has an interactive restoration mode (restore -i) that may be useful when using it with amrestore. I also believe that a gtar archive could be extracted from nearly any platform, but a classic dump archive won't because it's OS specific. (true/false?) thanks again for helping, Pierre. * Laboratoire de Planetologie de Grenoble * http://lpg.obs.ujf-grenoble.fr * Bat D de Physique, BP53, 38041 Grenoble Cedex 9 / FRA * tel. 04.76.51.41.55 , fax. 04.76.51.41.46 * e-mail. [EMAIL PROTECTED]
Re: Problem with device sg*
Hi! > >Host: scsi0 Channel: 00 Id: 08 Lun: 00 > > Vendor: QUANTUM Model: DLT8000 Rev: 0119 > > Type: Sequential-AccessANSI SCSI revision: 02 > > Here's a thought. Are you sure everything on that bus is wide SCSI? Yes! > You cannot have ID's >= 8 on narrow SCSI. Maybe somthing is wrapping > that back around to SCSI ID zero? Hm... i have deinstalled the new harddrive and changed the config files and then i started all procedures to run the changer, but nothing. The same error. Well, i will make a new install from the Server ant than i will looking if amanda works fine. I think that i can make it next weekend. Aftert the new installation i will mailing you the result. Bye Juergen -- Dies ist eine Microsoft freie Mail!
holding space estimates
I've set amanda's holding space to be ``all of the disk, but leave XXX
free''
(
holdingdisk hd1 {
comment "main holding disk"
directory "/whopper/amanda/lto" # where the holding disk is
use -10 Gb # how much space can we use on it
# a non-positive value means:
#use all space but that value
}
It looks like amanda treats this as:
Upon startup, check how much free diskspace is there, subtract 10G from
that, and use that as the disksize.
My amanda dumps take all night (well over 12 hours) and the disks are
active, meaning that the amount of free diskspace is fluctuating.
However amanda does *NOT* adapt her idea of how much disksapce is
available.
She simply calculates at startup how much she can use, and uses that number
for the rest of the night.
Ideally amanda should look every time a chunk is written to disk how much
space ios free, but at least she should check at the start of each new
dump/tar how much diskspace is free.
% amstatus lto
Using /volume/amanda/share/amanda/lto/amdump from Thu May 3 18:00:01 MET
DST 2001
[snipped]
james:/whopper/data/autotest 033409192k wait for dumping
[snipped]
james:/whopper/newhome2 038438112k writing to tape (7:59:55)
All the other dumps are finished.
SUMMARY part real estimated
size size
partition : 27
estimated : 27 125219454k
failed : 12860734k ( 2.28%)
wait for dumping: 1 33409192k ( 26.68%)
dumping to tape : 0 0k ( 0.00%)
dumping : 00k0k ( 0.00%) ( 0.00%)
dumped : 25 85863904k 88949528k ( 96.53%) ( 68.57%)
wait for writing: 00k0k ( 0.00%) ( 0.00%)
writing to tape : 1 38438112k 38678328k ( 99.38%) ( 30.70%)
failed to tape : 00k0k ( 0.00%) ( 0.00%)
taped : 24 47425792k 50271200k ( 94.34%) ( 37.87%)
6 dumpers idle : no-diskspace
taper writing, tapeq: 0
network free kps: 126880
holding space : 4672463k ( 10.84%)
dumper0 busy : 12:37:57 ( 96.85%)
dumper1 busy : 7:37:54 ( 58.51%)
dumper2 busy : 8:24:40 ( 64.49%)
dumper3 busy : 9:06:01 ( 69.77%)
taper busy : 2:39:11 ( 20.34%)
0 dumpers busy : 0:23:56 ( 3.06%)no-diskspace: 0:23:56 (100.00%)
1 dumper busy : 3:31:44 ( 27.06%)no-diskspace: 3:31:13 ( 99.76%)
start-wait: 0:00:31 ( 0.24%)
2 dumpers busy : 0:41:29 ( 5.30%)no-diskspace: 0:41:00 ( 98.86%)
start-wait: 0:00:28 ( 1.14%)
3 dumpers busy : 0:47:51 ( 6.11%)no-diskspace: 0:47:16 ( 98.79%)
start-wait: 0:00:34 ( 1.21%)
4 dumpers busy : 7:37:35 ( 58.47%)no-diskspace: 7:32:38 ( 98.92%)
start-wait: 0:04:56 ( 1.08%)
james:/home/netscradd/Mail # df -k /whopper
Filesystemkbytesused avail capacity Mounted on
/dev/md/dsk/d99 433727332 391286116 3810394392%/whopper
Note that holding space sais it has only 4 G free
Whereas the df shows that the holding disk should have approx 28G free
Kind regards,
--
Gerhard den Hollander Phone +31-10.280.1515
Technical Support Jason Geosystems BV Fax +31-10.280.1511
(When calling please note: we are in GMT+1)
[EMAIL PROTECTED] POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam
JASON...#1 in Reservoir CharacterizationThe Netherlands
This e-mail and any attachment is/are intended solely for the named
addressee(s) and may contain information that is confidential and privileged.
If you are not the intended recipient, we request that you do not
disseminate, forward, distribute or copy this e-mail message.
If you have received this e-mail message in error, please notify us
immediately by telephone and destroy the original message.
