Re: [bugzilla-daemon@bugs.gentoo.org: [Bug 19403] amanda-2.4.3.ebuild (New)]
>That's really funny after no sleep all night. ;] I think at this point >I'd even enjoy Vogon poetry. M-X miss-point I can make no sense whatsoever of this statement in the context of AMANDA (or in any other): "An AMANDA ebuild for Gentoo will be available shortly in portage. Yay!" >And if you follow the link and read the bug text Life's too short to cut/paste misplaced URL's. Most are spam. It's akin to hardware dealers with big ads that quote "$CALL" as the price on everything. If the text were worth reading, it would have been inlined.
Re: [bugzilla-daemon@bugs.gentoo.org: [Bug 19403] amanda-2.4.3.eb uild (New)]
Oh yeah, I forgot to mention that. Plus its good for rolling out to Gentoo clients. The gentoo guy kept my xinetd configs for setting up amanda with a tapeserver, so you can do: # AMANDA_SERVER=mytapeserver.mydomain.com emerge amanda Pretty easy. You'll need xinetd, and you'll need to restart xinetd afterwards, but a two line rollout to the clients rocks. The tapeserver still requires mondo configuration, but thats normal. Russell On Thu, Jun 26, 2003 at 05:57:21PM -0400, Bort, Paul wrote: > And if you follow the link and read the bug text, it's 2.4.4, too! I know > what my Gentoo box is getting this weekend! > > > -Original Message- > > From: Anthony A. D. Talltree [mailto:[EMAIL PROTECTED] > > Sent: Thursday, June 26, 2003 5:49 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [EMAIL PROTECTED]: [Bug 19403] > > amanda-2.4.3.ebuild (New)] > > > > > > >An AMANDA ebuild for Gentoo will be available shortly in > > portage. Yay! > > > > You're one zassy frood who really knows where his towel's at. > >
Re: [bugzilla-daemon@bugs.gentoo.org: [Bug 19403] amanda-2.4.3.ebuild (New)]
That's really funny after no sleep all night. ;] I think at this point I'd even enjoy Vogon poetry. Russell On Thu, Jun 26, 2003 at 02:49:18PM -0700, Anthony A. D. Talltree wrote: > >An AMANDA ebuild for Gentoo will be available shortly in portage. Yay! > > You're one zassy frood who really knows where his towel's at.
RE: [bugzilla-daemon@bugs.gentoo.org: [Bug 19403] amanda-2.4.3.ebuild (New)]
And if you follow the link and read the bug text, it's 2.4.4, too! I know what my Gentoo box is getting this weekend! > -Original Message- > From: Anthony A. D. Talltree [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2003 5:49 PM > To: [EMAIL PROTECTED] > Subject: Re: [EMAIL PROTECTED]: [Bug 19403] > amanda-2.4.3.ebuild (New)] > > > >An AMANDA ebuild for Gentoo will be available shortly in > portage. Yay! > > You're one zassy frood who really knows where his towel's at. >
Re: [bugzilla-daemon@bugs.gentoo.org: [Bug 19403] amanda-2.4.3.ebuild (New)]
>An AMANDA ebuild for Gentoo will be available shortly in portage. Yay! You're one zassy frood who really knows where his towel's at.
[bugzilla-daemon@bugs.gentoo.org: [Bug 19403] amanda-2.4.3.ebuild (New)]
An AMANDA ebuild for Gentoo will be available shortly in portage. Yay! Russell - Forwarded message from [EMAIL PROTECTED] - Date: Thu, 26 Jun 2003 12:51:09 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Bug 19403] amanda-2.4.3.ebuild (New) http://bugs.gentoo.org/show_bug.cgi?id=19403 --- Additional Comments From [EMAIL PROTECTED] 2003-26-06 12:51 EST --- Russell: thanks for this. It's in CVS now. app-admin/amanda. Your ebuild was the best of the many available. --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. You are on the CC list for the bug, or are watching someone who is. - End forwarded message -
Re: How do I force Amanda do the backup
Lucio.yahoo wrote: The last thing is that I dont wont Amanda to look at the label of tape, if there is a tape in the drive it should do the backup no matter what - How do I tell Amanda that?? amlabel -f DailySet1 anylabel Put this in your crontab so that it gets executed just a few minutes before the amdump command. That's a bad and dangerous idea. If you leave a tape in that has nothing to do with amanda backups (like a customers files, like your special backup with your nobel prize project), it gets blindly overwritten. "That doesn't happen", is just in invitation for disaster. (Why do you make backups anyway?) Instead, specify "tapecycle 1" (or zero, I never tried that), and amanda will not complain if any *amanda* tape is in the drive. The actual number of tapes in the cycle that you feed amanda is unimportant, as long as it is larger than the tapecycle you specified in the config.
VXA-2 tapetype?
This is the configuration I'm using for my VXA-2 tape type Exabyte V23.
define tapetype v23 { comment "V23 tape used with VXA-2" length 63917 mbytes filemark 3272 kbytes speed 3301 kps}
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
Re: VXA-2 tapetype?
This is what works for us.
define tapetype VXA {
comment "Exabyte VXA-2 V17"
length 30609 mbytes
filemark 2141 kbytes
speed 3892 kbytes
}
Joe Benson
IDI
Steven J. Backus wrote:
Can someone give me the tapetype entry for VXA-2?
Thanks,
Steve
VXA-2 tapetype?
Can someone give me the tapetype entry for VXA-2? Thanks, Steve
Re: help with backup problems please
Thanks to everybody for your patience, now it works. The problem was precisely the .amandahosts file. Special thanks to Paul Bijnens for being the first to point out the real problem.
Re: How do I force Amanda do the backup
> The last thing is that I dont wont Amanda to look at the label of tape, > if there is a tape in the drive it should do the backup no matter what - > How do I tell Amanda that?? amlabel -f DailySet1 anylabel Put this in your crontab so that it gets executed just a few minutes before the amdump command. Cheers, Lucio.
Re: trying to be removed
On Thu, 26 Jun 2003 at 11:43am, Gowen, Siobhan wrote > my email address when i subscribed was [EMAIL PROTECTED] we have since > been taken over and my new address is [EMAIL PROTECTED] although > old address still fwds. So when I try to unsubscribe you tell me that > i'm not on the list because the address you're seeing is > [EMAIL PROTECTED] not [EMAIL PROTECTED] in either case can I > please be unsubscribed to this list. Any help would be much appreciated. 1) Try 'unsubscribe [EMAIL PROTECTED]'. 2) Change your From line in your client, if it'll allow it. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
trying to be removed
Title: Message my email address when i subscribed was [EMAIL PROTECTED] we have since been taken over and my new address is [EMAIL PROTECTED] although old address still fwds. So when I try to unsubscribe you tell me that i'm not on the list because the address you're seeing is [EMAIL PROTECTED] not [EMAIL PROTECTED] in either case can I please be unsubscribed to this list. Any help would be much appreciated. Siobhan Gowen Unix Admin Its-ux-app 781-865-7623
Optimizing AMANDA in a small environment (1 vxa tape-drive, 3 exabyte [80gig] tapes, 3 servers)
1. Is it possible to force amanda to use one tape --
writing to it in
a contiguious manner (i.e., not overwriting it every
dump)?
2. As I am quite new to AMANDA in general I would
greatly appreciate
any suggestions one could provide in helping me
optimize my current
configuration. All of the setup information, backup
schemes, and
configuration files have been added to this post.
The Setup
---
I am currently working in a very small environment
consisting of two
Red Hat Linux servers, and one windows server. The
tape drive is a
VXA-2 tape drive and we currently have three v23
Exabyte tapes (~80
gigs).
Problem area:
I am at school only 3 days out of the week, becuase of
this only one
tape can be used a week.
The backup Scheme
--
1 tape per week would backup 3 servers. (at least 2
full dumps per
week)
On the first day of the week (mon) a new tape will be
used.
++
+ AMANDA.conf
+
++
org "CESSDaily"
mailto "[EMAIL PROTECTED]"
dumpuser "amanda"
inparallel 4
netusage 600 Kbps
dumpcycle 1 weeks
tapecycle 1 tapes
bumpsize 20 Mb
bumpdays 1
bumpmult 4
etimeout 300
tapedev "/dev/nst0"
tapetype v23
labelstr "^CESSDaily[0-9][0-9]*$"
holdingdisk hd1 {
comment "main holding disk"
directory "/var/tmp"
use -117 Mb
}
infofile "/var/lib/amanda/CESSDaily/curinfo"
logdir "/var/lib/amanda/CESSDaily"
indexdir "/var/lib/amanda/CESSDaily/index"
define tapetype v23 {
comment "V23 tape used with VXA-2"
length 63917 mbytes
filemark 3272 kbytes
speed 3301 kps
}
define dumptype global {
comment "Global definitions"
}
Note: Nothing below this line has been edited
+---+
+ disklist
+
+---+
# fooserver1, or 192.168.1.2 (Backup Server)
fooserver1 hda3nocomp-high -1 local
fooserver1 hda1nocomp-high -1 local
fooserver1 hda7nocomp-high -1 local
fooserver1 hda8nocomp-high -1 local
fooserver1 hda9nocomp-high -1 local
fooserver1 hda2nocomp-high -1 local
fooserver1 hda5nocomp-high -1 local
fooserver1 hda6nocomp-high -1 local
# fooserver2, or 192.168.1.3 (Backup Client)
fooserver2 /dev/sda5 comp-high
fooserver2 /dev/sda1 comp-high
fooserver2 /dev/sda3 comp-high
fooserver2 /dev/sda2 comp-high
fooserver2 /dev/sda6 comp-high
#Windows server ommited for brevity.
Thank you,
Anwar
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
Re: problem with amplot
Ean Kingston wrote: I'm trying to run amplot and get the following error message: /var/amanda/test/logs$ amplot amdump.1 Displaying graph on the screen, for next graph cat: cannot open amdump.1 Is there a file "amdump.1"? and is it readable by the user running amplot? "ls -lL amdump.1" -- "cat amdump.1" etc. The rest are errors resulting from not being able to read that file. So, what should I do to fix this? In case it matters; this is Amanda 2.4.4 built from source on solaris 8 using gcc 3.2.2. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
problem with amplot
I'm trying to run amplot and get the following error message: /var/amanda/test/logs$ amplot amdump.1 Displaying graph on the screen, for next graph cat: cannot open amdump.1 : MISSING SPACE DECLARATION gnuplot> load 'title' ^ Cannot open load file 'title' "/opt/amanda/libexec/amplot.gp", line 61: (No such file or directory) So, what should I do to fix this? In case it matters; this is Amanda 2.4.4 built from source on solaris 8 using gcc 3.2.2. Ean Kingston ([EMAIL PROTECTED]) Analyst Kanetix Ltd. (www.kanetix.com) Phone: (416) 599-9779 x216
Re: Q: tape problem
On Thu, 26 Jun 2003 at 3:10pm, Raúl Wild-Spain wrote > Unusual System Events > =-=-=-=-=-=-=-=-=-=-= > Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key > Medium Error > Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors > Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key > Medium Error > Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors > Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark. > Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key > Medium Error > Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors > Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key > Medium Error > Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors > Jun 24 03:06:06 xaloc sendbackup[20682]: index tee cannot write [Broken pipe] > Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key > Medium Error > Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors > Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key > Medium Error > Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors > Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark. Bad tape, or dirty tape drive. From my (limited) experience with DDS2 drives, they need *frequent* cleanings. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Q: tape problem
Hi Jon, > > 1. you are writing to a dds2 tape, 3.8GB max size, and /dev/sdc2 is more > than 4 GB, even compressed. it's a dds4 tape, you know, 20Gb and 40Gb compressed. My backups aren't greater than 6Gb totally ( when full dump ). these indications aren't normal , the tape must to have more than 3.8 Gb > > 2. you have no holding disk available for /dev/sdc2 so it is writing > directly to tape. for some reason this is too slow and some timeout > is kicking in. I add below notifications from my Debian ( log check). You can see many strange errors, specially "Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark." repeatedly. I don't understand what happens ... > > 3. you have holding disk space available but have not set a chunk size > below the maximum file size limit of your holding disk. --- LOG CHECK --- Unusual System Events =-=-=-=-=-=-=-=-=-=-= Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark. Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc sendbackup[20682]: index tee cannot write [Broken pipe] Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error with sense data: Current st09:00: sense key Medium Error Jun 24 03:06:06 xaloc kernel: Additional sense indicates Excessive write errors Jun 24 03:06:06 xaloc kernel: st0: Error on write filemark.
Re: Multiple Tapes in Single run issue
On Thu, 26 Jun 2003 at 12:14pm, Vijay wrote > >Amanda can use multiple tapes in one amdump, but it can't span a single > >image across multiple tapes. You'll have to divide up that image, using > >tar to grab subdirectories rather than the whole FS. > > I suppose dividing the image using tar actually means putting different > entries for each directory of the partiion in the disklist as a separate > partition. Is there something i miss? You can do that, or you can play with exclude (lists) and include (lists). There are examples in the example disklist in the amanda tarball. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: help with backup problems please
On Thursday 26 June 2003 06:51, Onime Clement wrote: >Next Step >Add the following line in the file ~amanda/.amandahosts >(/var/lib/amanda/.amandahosts) > >fmserver amanda > >The file should already have entries for >localhost amanda >localhost.localdomain amanda > >If not please add them. > >> >Pay special attention to typos in inetd.conf; >> >> I've edited /etc/xinetd.d/amanda, then I restarted xinetd. Now > >Let's hope it remains on! I suspect that using chkconfig keeps a > system status on each server.. AFAIK chkconfig doesn't keep a database, but reads the status of each 'server' from its file in order to generate an up2date display for the query function. For amanda stuffs I've always just edited the starter file and restarted xinetd. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: help with backup problems please
On Thursday 26 June 2003 06:39, Paul Bijnens wrote: >Gene Heskett wrote: >> That file should exist in /home/"amanda-user"/.amandahosts, and >> look something like this: >> --- >> FQDN amanda >> FQDN root >> --- >> Where my amanda-user is amanda. And I'm not sure if the second >> line is needed at all. FQDN is the servers full name of course. >> This file must also exist on the clients, in the same location, >> which gives the server access rights there too. > >On the client the first line is needed so that the user "amanda" >can start a backup on this client; FQDN = name of server in this > case. > >On the server the second line is needed so that "root" on the client >can start a restore; FQDN = name of the client in this case. > >The meaning is: when some "username" from "host" connects, let him > in. > >So, usually you have a oneliner on each client, and a large list on > the server. (Also remember the server is also a client in most > cases.) You can leave most of entries on the server commented > out(*), so that someone from workstation A with root access cannot > restore files from or SecretServer B, if security is a concern. > >(*) commented out = there is no real comment sign but if you add a >#-sign in front of the name, the hostname effectively never matches, >(unless you really have a host named "#" or '#host' :-) ). Thanks for clarifying that Paul. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
EN HESAPLI REKLAM SERViSiNiZ.. www.eservis.gen.tr
Title: Eservis.gen.tr Sanal reklam Merkezi , E-mail List Kendi Reklamınızı Kendiniz Yapın! Düşük maliyet ve sınırsız kullanım... KONTROLÜ ELİNİZE ALIN..! E-mail gönderemiyorum problemlerine son! Hazırlamış olduğumuz CD'ler içerisindeki programlar ile çok rahat ve max. performansda e-mail gönderebilirsiniz. Detaylar için web sayfamızı ziyaret ediniz... www.eservis.gen.tr TR GUIDE 15 ve WORLD GUIDE 5.0 birlikte sadece 99$ Bu kampanya çok kısa bir süre için geçerlidir.. TR GUIDE 15 Bu ürünümüz Türkiye içinde 7 milyon kişiye e-mail göndermenizi sağlayacaktır. Sınıflandırılmış 7 milyon e-mail adresi, Full sürüm toplam 1000$ değerinde yazılımlar, Güncelleme 10 Haziran 2003 Sadece 69$ WORLD GUIDE 5.0 Bu ürünümüz dünya genelinde 400 milyon kisiye e-mail göndermenizi saglayacaktir. Sınıflandırılmış 400 milyon e-mail adresi, Full sürüm toplam 1000$ değerinde yazılımlar, Güncelleme 10 Haziran 2003 Sadece 69$ GOLD GUIDE 5.0 Bu ürünümüz 500 bin Türk firmasının detaylı (adı, açık adresi, telefonu, faxı, e-mail adresi, web adresi gibi) bilgilerinin bulunduğu bir rehberdir. 250 Ana meslek grubu ve 500 alt meslek grubuna göre hazırlandı. Sadece 49$ Detaylı bilgi için : 0 505 309 22 69 no'lu telefonu arayabilir yada www.eservis.gen.tr adresini ziyaret edebilirsiniz.. Mail : [EMAIL PROTECTED] Bizden email almak istemiyor ve bu rehber CD'ler içerisinden çıkarılmak istiyorsanız aşağıdaki linki tıklayınız.. Listeden çıkmak istiyorum
was [strange am-label issue] Issue Resolved
> Hi, > > Trying to label a set of 6 tapes in a DDS4 autoloader. For some reason after > i load the first tape into the slot and try and do a amlabel the tape is > unloaded and another one loaded into the slot instead. See below. > > Any idea why this might be? > > Tom > > $ mtx -f /dev/sg2 status > Storage Changer /dev/sg2:1 Drives, 6 Slots ( 0 Import/Export ) > Data Transfer Element 0:Empty > Storage Element 1:Full > Storage Element 2:Full > Storage Element 3:Full > Storage Element 4:Full > Storage Element 5:Full > Storage Element 6:Full > > so i load tape 1 > > $ mtx -f /dev/sg2 load 1 > > and > > $ mtx -f /dev/sg2 status > Storage Changer /dev/sg2:1 Drives, 6 Slots ( 0 Import/Export ) > Data Transfer Element 0:Full (Storage Element 1 Loaded) > Storage Element 1:Empty > Storage Element 2:Full > Storage Element 3:Full > Storage Element 4:Full > Storage Element 5:Full > Storage Element 6:Full > > then i try and label it > > $ amlabel -f gt-log gt-log01 > labeling tape in slot 6 (/dev/nst0): > rewinding, reading label gtlog06, tape is in another amanda configuration > rewinding, writing label gt-log01, checking label, done. > > and now tape 6 is loaded > > $ mtx -f /dev/sg2 status > Storage Changer /dev/sg2:1 Drives, 6 Slots ( 0 Import/Export ) > Data Transfer Element 0:Full (Storage Element 6 Loaded) > Storage Element 1:Full > Storage Element 2:Full > Storage Element 3:Full > Storage Element 4:Full > Storage Element 5:Full > Storage Element 6:Empty > > thanks > This also appeared as an issue on a 10 tape LTO autoloader from NEC. The only similarities between the machines was the fact that they both ran RedHat6.2. When the test setup was upgraded to RedHat7.3 the problem went away. The issue was resolved by installing a newer version of sort on the RedHat6.2 system compared to the one it was shipped with. There is a part of the chg-zd-mtx code that collects the data from an "mtx status" run. The code is the function get_slot_list, lines 506-564. It seems that the cerion of sort in RedHat6.2 was not sorting the list of storage elements and this was causing the whole process to trip up. Thanks to all on the list who offerred help - Seems i've finally go there with my 3 systems and they are all happy. thanks again Tom
How do I force Amanda do the backup
Hi! My setup looks like this: I have 5 tapes, and I would like to do a backup every working day (monday to friday), therefor my amanda.conf looks like: dumpcycle 5 runspercycle 5 tapecycle 5 tapes Is that right?? Next I would like Amanda to do a full dump every day therefor I have put "dumpcycle 0" in my "define dumptype". The last thing is that I dont wont Amanda to look at the label of tape, if there is a tape in the drive it should do the backup no matter what - How do I tell Amanda that?? Please help - Christoffer
Re: amtapetype problem
> > can anyone advise me how to determine the block size of this tape? > > mt -f /dev/... status > > reports the blocksize that the device is configured (not that tape > that is in it). > > If you read a tape, specify a blocksize larger than then one on > tape (maybe it has to be an exact multiple of it, never tried all > possible combinations. e.g. try: > >dd if=/dev/... bs=256k > > Some implementation of dd need "ibs=..." instead of "bs=..." to > force a blocksize when reading (and obs=... to force for writing). > > It's best to specify variable blocksize (by specifying 0 for the > command). It's the most flexible, for those drives that support it > (any modern drive, I believe). seems the issue was a dodgy SCSI cable from the box to the drive. Swapped it out and it all works fine. thanks all. Tom
Re: help with backup problems please
Next Step Add the following line in the file ~amanda/.amandahosts (/var/lib/amanda/.amandahosts) fmserver amanda The file should already have entries for localhost amanda localhost.localdomain amanda If not please add them. > >Pay special attention to typos in inetd.conf; > > I've edited /etc/xinetd.d/amanda, then I restarted xinetd. Now Let's hope it remains on! I suspect that using chkconfig keeps a system status on each server.. > the problem is: > > > planner: ERROR localhost: [access as amanda not allowed from [EMAIL PROTECTED] > amandahostsauth failed > > > Note that amanda had been running as root for a while yesterday, so I suspect > it chowned some file somewhere, and now the amanda user is not able to cope > with them anymore, but I'm not sure at all of this. > > > What could be the next step? >
150 Milyon TL/m2
siparişleriniz için;
Re: help with backup problems please
Gene Heskett wrote: That file should exist in /home/"amanda-user"/.amandahosts, and look something like this: --- FQDN amanda FQDN root --- Where my amanda-user is amanda. And I'm not sure if the second line is needed at all. FQDN is the servers full name of course. This file must also exist on the clients, in the same location, which gives the server access rights there too. On the client the first line is needed so that the user "amanda" can start a backup on this client; FQDN = name of server in this case. On the server the second line is needed so that "root" on the client can start a restore; FQDN = name of the client in this case. The meaning is: when some "username" from "host" connects, let him in. So, usually you have a oneliner on each client, and a large list on the server. (Also remember the server is also a client in most cases.) You can leave most of entries on the server commented out(*), so that someone from workstation A with root access cannot restore files from or SecretServer B, if security is a concern. (*) commented out = there is no real comment sign but if you add a #-sign in front of the name, the hostname effectively never matches, (unless you really have a host named "#" or '#host' :-) ). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: help with backup problems please
On Thursday 26 June 2003 06:27, Lucio.yahoo, (by way of Lucio.yahoo wrote: >> For RedHat 9 >> Try the following command as root >> >> chkconfig amanda on > >I've edited /etc/xinetd.d/amanda by hand instead, then I restarted > xinetd. Now the problem is: > >planner: ERROR localhost: [access as amanda not allowed from > [EMAIL PROTECTED] amandahostsauth failed That file should exist in /home/"amanda-user"/.amandahosts, and look something like this: --- FQDNamanda FQDNroot --- Where my amanda-user is amanda. And I'm not sure if the second line is needed at all. FQDN is the servers full name of course. This file must also exist on the clients, in the same location, which gives the server access rights there too. >Note that amanda had been running as root for a while yesterday, so > I suspect it chowned some file somewhere, and now the amanda user > is not able to cope with them anymore, but I'm not sure at all of > this. > >What could be the next step? -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: help with backup problems please
Hi, two things: 1.) never use localhost in a disklist entry, it will come back and bite you later always use the full name of the host. 2.) in the homedirectory of the amanda-user create a file ".amandahosts" owned by the amanda user and with permisions 0600, containing at least the line: fmserveramanda then test your setup with " amcheck christoph Lucio.yahoo schrieb: Pay special attention to typos in inetd.conf; I've edited /etc/xinetd.d/amanda, then I restarted xinetd. Now the problem is: planner: ERROR localhost: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Note that amanda had been running as root for a while yesterday, so I suspect it chowned some file somewhere, and now the amanda user is not able to cope with them anymore, but I'm not sure at all of this. What could be the next step?
Re: amdump to many taper retries
On Thursday 26 June 2003 05:13, Susanne und Stefan Noll wrote: >Alexander JOLK wrote: >>>NOTES: >>>taper: tape met053 kb 17996640 fm 21 writing file: No space left >>> on device taper: retrying >>> localhost:/home/samba/projekte/Laufende.0 on new tape: [writing >>> file: No space left on device] >>>taper: tape met055 kb 17488544 fm 1 writing file: Input/output >>> error taper: retrying localhost:/home/samba/projekte/Laufende.0 >>> on new tape: [writing file: Input/output error] >>>taper: tape met054 kb 0 fm 0 [OK] >> >>You seem to be running out of space on a 20GB tape after 18GB have >> been written. That sounds a little bit like you are using >> hardware compression (that actually expands your pre-compressed >> data when writing to tape). This issue has been discussed several >> times already on the list. >> >>Apart from that, the second error message reads `Input/output >> error' rather than `No space left', so it might be you ran into a >> bad tape. >> >>Alex > >Thanks for your tipps. >I disabled the hardware compression with: >mt -f /dev/nst0 compression off This may be insufficient to make it stay off. It will reset to the dipswitch set default when the next tape is inserted. So first, find the dip switch that sets that up and turn it off. I've found here, on DDS tapes, that a tape once written to with compression turned on, really wants to be compressed forever and its rather convoluted to get it turned back off because this is actually recorded on the tape in a header that apparently only the drive knows about. Some drives will still report that its on, but only for the label block even after having been thru this 'fixcomp' script: --- #!/bin/sh if [ `whoami` != 'root' ]; then echo echo "! Warning !!" echo "fixcomp needs to be run by the user root," echo "else the perms on some commands will be denied." echo exit 1 fi # I have a seperate from amanda stuff dir where I play with things # like this. cd /amanda # blatently stolen from the bash manual NUMBERS="0 1 2 3" for number in $NUMBERS do echo "amtape DailySet1 slot "$number su amanda -c 'amtape DailySet1 slot '$number # set variable block size mt -f /dev/nst0 setblk 0 mt -f /dev/nst0 rewind # ask for a read thats going to be bigger than the label block # a normal label file is 32k. dd if=/dev/st0 of=./scratch bs=64K count=1 ls -l ./scratch # show how big if you care mt -f /dev/nst0 compression off mt -f /dev/nst0 defcompression -1 # re-write the label blocks with orig info dd if=./scratch of=/dev/nst0 bs=32K conv=sync mt -f /dev/nst0 tell # show how many blocks it was # This _might_ get rid of compressed headers echo "forcing buffer flush with an 4+ meg write to tape # "$number # it doesn't always work! dd if=/dev/zero bs=32K count=130 of=/dev/st0 echo "Now reading the label" dd if=/dev/st0 bs=32K mt -f /dev/st0 status done exit 0 --- adjust NUMBERS for however many tapes fits in your magazine if you have a changer. Mine holds 4 tapes and I run this everytime I change the tapes in the magazine. Or remove the loop completely if doing it one tape at a time. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: amdump to many taper retries
Frank Smith wrote: --On Tuesday, June 17, 2003 10:01:23 +0200 Stefan Noll <[EMAIL PROTECTED]> wrote: hi, 4 months ago I installed amanda 2.4.2p and it worked fine. but now I get following strange error: FAILURE AND STRANGE DUMP SUMMARY: localhost /home/samba/projekte/Laufende lev 0 FAILED [too many taper retries] NOTES: taper: tape met053 kb 17996640 fm 21 writing file: No space left on device taper: retrying localhost:/home/samba/projekte/Laufende.0 on new tape: [writing file: No space left on device] As others have pointed out you hit EOT, probably because you were using hardware compression on already compressed data. taper: tape met055 kb 17488544 fm 1 writing file: Input/output error taper: retrying localhost:/home/samba/projekte/Laufende.0 on new tape: [writing file: Input/output error] taper: tape met054 kb 0 fm 0 [OK] Possibly met055 is a bad tape, or you may need to add a sleep in your changer script. It takes awhile for most changers to unload and load a new tape. I had to add some sleep time to mine to keep from getting I/O errors trying to read the label while the new tape was still being loaded. Frank Thanks for advice. I added some sleep in my changerscript after unload tape and after load tape. Greetings Stefan Noll
Re: help with backup problems please
On Thursday 26 June 2003 04:20, Lucio.yahoo wrote: >> You should get an e-mail with error messages and statistics. > >Here is the mail I receive (mailto "root"), but, to be honest, it > doesn't help me very much... > >From [EMAIL PROTECTED] Thu Jun 26 08:11:16 2003 >Date: Thu, 26 Jun 2003 08:11:15 +0200 From: root <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: MyOrg AMANDA MAIL REPORT FOR June 26, 2003 > >These dumps were to tape DailySet1n4. >The next tape Amanda expects to use is: a new tape. > >FAILURE AND STRANGE DUMP SUMMARY: > planner: ERROR Request to localhost timed out. > localhost /dev/md0 RESULTS MISSING Aha! Since the error came from planner, it looks as if the etimeout value set in your amanda.conf might be too small. As /dev/md0 is a software raid, its probably pretty big, and the estimate phase is going to take extra time. I know of one such 360 gig setup, and its not particularly fast, only makeing about 30Mb a second in an hdparm test. I'd expect it would take at least 45 minutes to get an estimate back from that one. Heres a grep for mine, where the raid is not involved: etimeout 600# number of seconds per filesystem for estimates. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 5 # maximum number of seconds that amcheck waits which translates to 10 minutes, 30 minutes, and 5 seconds. One of my clients is a dog by todays standards. [...] -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: amdump to many taper retries
Susanne und Stefan Noll wrote: taper: tape met053 kb 17996640 fm 21 writing file: No space left on device Here you hit into EOT. Could be that you have indeed hardware and software compression at the same time. See below. taper: retrying localhost:/home/samba/projekte/Laufende.0 on new tape: [writing file: No space left on device] taper: tape met055 kb 17488544 fm 1 writing file: Input/output error taper: retrying localhost:/home/samba/projekte/Laufende.0 on new tape: [writing file: Input/output error] taper: tape met054 kb 0 fm 0 [OK] But here you get an error on a fresh new tape. Is the blocksize correct? Is it indeed a bad tape? Is the tape not yet ready, and the program is unpatient? I disabled the hardware compression with: mt -f /dev/nst0 compression off Linux. Maybe that's not enough. After USING the tape (e.g. after "amcheck -s YourConfig"), what does "mt status" say? Instead of repeating myself over and over on this list, I just added a link to one of the last times I've tried to explain it: http://groups.yahoo.com/group/amanda-users/message/44453 -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: amdump to many taper retries
Alexander JOLK wrote: NOTES: taper: tape met053 kb 17996640 fm 21 writing file: No space left on device taper: retrying localhost:/home/samba/projekte/Laufende.0 on new tape: [writing file: No space left on device] taper: tape met055 kb 17488544 fm 1 writing file: Input/output error taper: retrying localhost:/home/samba/projekte/Laufende.0 on new tape: [writing file: Input/output error] taper: tape met054 kb 0 fm 0 [OK] You seem to be running out of space on a 20GB tape after 18GB have been written. That sounds a little bit like you are using hardware compression (that actually expands your pre-compressed data when writing to tape). This issue has been discussed several times already on the list. Apart from that, the second error message reads `Input/output error' rather than `No space left', so it might be you ran into a bad tape. Alex Thanks for your tipps. I disabled the hardware compression with: mt -f /dev/nst0 compression off Greetings Stefan Noll
Re: help with backup problems please
>Pay special attention to typos in inetd.conf; I've edited /etc/xinetd.d/amanda, then I restarted xinetd. Now the problem is: planner: ERROR localhost: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Note that amanda had been running as root for a while yesterday, so I suspect it chowned some file somewhere, and now the amanda user is not able to cope with them anymore, but I'm not sure at all of this. What could be the next step?
Re: help with backup problems please
> For RedHat 9 > Try the following command as root > > chkconfig amanda on I've edited /etc/xinetd.d/amanda by hand instead, then I restarted xinetd. Now the problem is: planner: ERROR localhost: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Note that amanda had been running as root for a while yesterday, so I suspect it chowned some file somewhere, and now the amanda user is not able to cope with them anymore, but I'm not sure at all of this. What could be the next step?
Re: help with backup problems please
On Thu, Jun 26, 2003 at 08:20:29AM +, Lucio.yahoo wrote: > > You should get an e-mail with error messages and statistics. > > Here is the mail I receive (mailto "root"), but, to be honest, it doesn't help > me very much... > Yes, the mail is not very helpful for a newbie. OTOH i cannot offer any help without error messages. > FAILURE AND STRANGE DUMP SUMMARY: > planner: ERROR Request to localhost timed out. The server couldn't reach the client. (Doesn't matter if client and server are the same machine. Amanda is always communicating over an UDP and TCP) Please start with amcheck debugging and follow these tips from the FAQ. My personal favourite is clear debug files rm -r /tmp/amanda stop inetd fuser -k /usr/sbin/inetd and starting it with -d option. inetd -d Then run amcheck and watch if inetd gives output. If you cannot find the problem, please post the file under /tmp/amanda. See also http://amanda.sourceforge.net/fom-serve/cache/13.html FAQ: Q: Why does `amcheck' report `selfcheck request timed out'? A: This can occur under several different situations. First, make sure this problem is repeatable; if Amanda programs are NFS-auto-mounted, some clients may fail to mount the Amanda binaries in time. If the error is repeatable, log into the client, and check whether the directory /tmp/amanda exists, and a file named amandad.debug exists in there: amandad will create this file whenever it starts. If this file does not exist, amandad is not starting properly, or it lacks permission to create /tmp/amanda/amandad.debug. In the latter case, wipe out /tmp/amanda, and amandad should create it next time it runs. In the former case, check your inetd configuration. Make sure you have added the Amanda services to /etc/services (or the NIS services map), that /etc/inetd.conf was properly configured, and that you have signalled inetd to reread this file (some systems may need rebooting). Check section 2.2 from the INSTALL file for details. Check the inetd man-page for possible differences between the standard inetd.conf format and the one in your system. Pay special attention to typos in inetd.conf; error messages will probably appear in /var/adm/messages or /var/log/messages if you have typed the amandad program name incorrectly. Make sure the same user that you have specified at configure-time (--with-user=) is listed in inetd.conf. Check whether this user has permission to run amandad, as well as any shared libraries amandad depends upon, by running the specified amandad command by hand, as the Amanda user. It should just time-out after 30 seconds waiting for a UDP packet. If you type anything, it will abort immediately, because it can't read a UDP packet from the keyboard. As soon as you have properly configured inetd.conf so as to run amandad, you should no longer get the `selfcheck request timed out' message. A nice tool to help make sure inetd is really listening on the amandad port is lsof, available at ftp://vic.cc.purdue.edu/pub/tools/unix/lsof. -- Alles Gute / best wishes Dietmar Goldbeck E-Mail: [EMAIL PROTECTED] Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea.
unsubscribe
unsubscribe
Re: Multiple Tapes in Single run issue
>Amanda can use multiple tapes in one amdump, but it can't span a single >image across multiple tapes. You'll have to divide up that image, using >tar to grab subdirectories rather than the whole FS. I suppose dividing the image using tar actually means putting different entries for each directory of the partiion in the disklist as a separate partition. Is there something i miss? Vijay Nilgiri Networks
Re: help with backup problems please
For RedHat 9 Try the following command as root chkconfig amanda on The client aspect of amanda (run via xinetd) is disabled by default! The above command turns it on. If that fails then check to see if it works after you issue the command service iptables stop In which case it is a firewall issue. Thanks Clement Onime On Thu, 26 Jun 2003, Lucio.yahoo wrote: > > What does 'amcheck DailySet1' say? > > Amanda Tape Server Host Check > - > Holding disk /var/tmp: 30819288 KB disk space available, using 25576408 KB > NOTE: skipping tape-writable test > Tape DailySet1n4 label ok > NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist > NOTE: it will be created on the next run > NOTE: index dir /var/lib/amanda/DailySet1/index/localhost: does not exist > Server check took 8.201 seconds > > Amanda Backup Client Hosts Check > > WARNING: localhost: selfcheck request timed out. Host down? > Client check: 1 host checked in 29.995 seconds, 1 problem found > > (brought to you by Amanda 2.4.3) > > Wow! It has found a problem on the client host (wich is phisically the server, > btw). But, why this problem? What am I missing? > > > > > How about 'amstatus DailySet1 --file logdir/amdump.1'? (where ever > > your "logdir" is...) > > > > # amstatus DailySet1 --file /var/lib/amanda/DailySet1 > Using /var/lib/amanda/DailySet1 > > > SUMMARY part real estimated > size size > partition : 0 > estimated : 0 0k > flush : 00k > failed : 0 0k ( 0.00%) > wait for dumping: 0 0k ( 0.00%) > dumping to tape : 0 0k ( 0.00%) > dumping : 00k0k ( 0.00%) ( 0.00%) > dumped : 00k0k ( 0.00%) ( 0.00%) > wait for writing: 00k0k ( 0.00%) ( 0.00%) > wait to flush : 00k0k (100.00%) ( 0.00%) > writing to tape : 00k0k ( 0.00%) ( 0.00%) > failed to tape : 00k0k ( 0.00%) ( 0.00%) > taped : 00k0k ( 0.00%) ( 0.00%) > all dumpers active > taper idle > > Can you see anything strange here? > > > How about 'amreport DailySet1 -l logdir/log.20030625.0 -f /tmp/foo' > > (again, logdir and whatever the appropriate logfile name is). > > Please refer to my reply to Dietmar Goldbeck for this. > > > > > How about /tmp/amanda/* on the client and server? > > *** amtrmidx.debug *** > could not open index directory > "/var/lib/amanda/DailySet1/index/localhost/_dev_md0/"amtrmidx: pid 4997 > > # The first missing subdir is localhost > > There are lots of other debug files down there, I've checked only a few but > the one above seems the only interesting one (along with the others from the > same process). > >
