Problem with amrecover
Hi All :) I am trying to restore from a tape using amrecover. If I use amrecover DailyBackup it says: > AMRECOVER Version 2.4.2p2. Contacting server on localhost ... > amrecover: cannot connect to localhost: Connection refused If I use the -s backup and/or -t backup I also get the same: > AMRECOVER Version 2.4.2p2. Contacting server on backup ... > amrecover: cannot connect to backup: Connection refused I previously had a similar problem and rectified this by editing the /var/lib/amanda/.amandahosts and added localhost root to the file. Tried this as I am running amrecover as root but still could not fix it. Any suggestions on what I am missing?? -- # Bartho Saaiman # Network Administrator # Stellenbosch Automotive Engineering # Tel :: 27 21 882 8820 x 215 # Email :: bartho @ cae.co.za
Re: 'not an Amanda tape' after FreeBSD upgrade
On Thu, Mar 27, 2003 at 11:15:52AM +0200, Toomas Aas wrote: > Hello! > > My Amanda server is running 2.4.3b4. Three days ago I upgraded the > operating system from FreeBSD 4.7-RELEASE-p6 to 4.7-RELEASE-p9. This is > really just some security patches to sendmail, libc and openssl. Since > the upgrade Amanda thinks that all the backup tapes that were written > before the upgrade are "not Amanda tapes". > > After I re-label the tape, Amanda agrees to write the backup to it and Could the compression bit have been toggled in you tape drive? -- Scott LambertKC5MLE Unix SysAdmin [EMAIL PROTECTED]
Re: Problems restoring from amanda server
I installed it using the rpms. I do have the server host name in the .amandahosts file, but I didn't tell the client what tape server to use any other way. Is there a conf file somewhere where I specify this? This seems like something totally straightforward to me, but I can't find any instruction anywhere about how to tell the client what server it should use. Alex Thurlow At 01:25 PM 3/27/2003 -0800, you wrote: I just ran a similar amrecover as you describe, it goes straight to the amanda backup server. This is because i use --with-tape-server=amanda_server and --with-index-server=amanda_server when i compiled amanda. Did you compile it?? One more thing worth pointing out is that do you have the amanda server host's name in your .amandahosts file?? Also, try using host name and FQDN instead of localhost. I and some others have experienced that localhost doesn't work. I don't know if it has been fixed or not. Hope it helps you Alex Thurlow wrote: Forgive me if this is a stupid question, but I just switched to amanda from a custom setup and am having a problem when I try to restore. If I do: amrecover DailyBackup it says: AMRECOVER Version 2.4.2p2. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused I didn't backup to the local server. How do I tell the amanda client where to restore from? Thanks, Alex Thurlow
Re: Problems restoring from amanda server
On Thursday March 27 2003 12:20 pm, Alex Thurlow wrote: > Forgive me if this is a stupid question, but I just switched to amanda from > a custom setup and am having a problem when I try to restore. If I do: > amrecover DailyBackup > it says: > AMRECOVER Version 2.4.2p2. Contacting server on localhost ... > amrecover: cannot connect to localhost: Connection refused > > I didn't backup to the local server. How do I tell the amanda client where > to restore from? # amrecover -C -s -t
Re: Problems restoring from amanda server
On Thu, Mar 27, 2003 at 02:20:26PM -0600, Alex Thurlow wrote: > Forgive me if this is a stupid question, but I just switched to amanda from > a custom setup and am having a problem when I try to restore. If I do: > amrecover DailyBackup > it says: > AMRECOVER Version 2.4.2p2. Contacting server on localhost ... > amrecover: cannot connect to localhost: Connection refused > > I didn't backup to the local server. How do I tell the amanda client where > to restore from? > It is called the "tapeserver" and "indexserver". Check the manpage for amrecover. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Problems restoring from amanda server
Forgive me if this is a stupid question, but I just switched to amanda from a custom setup and am having a problem when I try to restore. If I do: amrecover DailyBackup it says: AMRECOVER Version 2.4.2p2. Contacting server on localhost ... amrecover: cannot connect to localhost: Connection refused I didn't backup to the local server. How do I tell the amanda client where to restore from? Thanks, Alex Thurlow
BOYKOT
Title: New Page 1 -Original Message- From: Esra [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 26, 2003 1:22 PM To: eda Subject: Fw: Boykot - Original Message - Subject: İlet: Boykot English: If the USA finally goes ahead with a unilateral attack, which they did, contravening the decisions of the UN Security Council, let's boycott all American products (hamburgers, cigarettes, soft drinks, films, petrol -SHELL, ESSO, EXXON, MOBIL and GULF- etc., etc.,). This letter has been sent to 30 persons. If everybody sends it to another 10 (30 x 10 = 300), it will have reached over 300 million people in a week. Let's act together to put the pressure on. Turkish: Eger ABD , birlesmis milletler kararina ragmen hala atak yaparsa -ki yapti-, yababilecegimiz eylemlerden birtanesi de onlarin butun urunlerine boykot baslatmak. Hamburger, sigara, coca cola, pepsi, filmler, petrol : ESSO, EXXON, MOBIL, SHELL, etc. Bu e-maili 30 kisiye gonderilmistir, her alan 10 kisiye gonderirse (30x10=300), bir haftada 300 milyondan fazla kisiye ulasir. Hadi hep birlikte bu baskiyi surdurelim. Spanish: Si finalmente se produce el ataque unilateral de EE.UU. ignorando los acuerdos del Consejo de Seguridad de la ONU, boicoteemos sus productos (hamburguesas, tabaco, bebidas, películas, gasolina -SHELL, ESSO, EXXON, MOBIL y GULF- etc., etc.,) Esta carta ha sido transmitida a 30 personas, si cada una se la envía a 10 más (30x10=300), en 8 días habremos sensibilizado más de 300 millones de personas. ¡Actuemos todos a una para hacer la fuerza! French: Si l'attaque unilatérale des États-Unis a finalement lieu, ignorant les accords du Conseil de Sécurité de l'ONU, boycottons leurs produits (hamburgers, tabac, boissons, films, essence -SHELL, ESSO, EXXON, MOBIL et GULF- etc., etc.) Cette lettre a été transmise à 30 personnes, si chacune l'envoie à 10 autres personnes (30x10=300), en 8 jours nous aurons ensibilisé plus de 300 millions de personnes. Agissons tous pour faire force! German: Sollte es schließlich doch zu einem einseitigen Angriff der USA entgegen den Vereinbarungen des UN- icherheitsrates kommen, dann besteht Handlungsbedarf: Boykottiert Erzeugnisse aus den USA (wie Hamburger, Zigaretten, Getränke, Filme, Benzin - SHELL, ESSO, EXXON, MOBIL und GULF -, usw). Dies ist ein Kettenbrief, der an 30 Adressaten versendet worden ist. Wenn jeder davon 10 weitere Mails verschickt (30x30=300), wären in 8 Tagen über 300 Mio. Verbraucher sensibilisiert. Alle zusammen haben wir Kraft genug, um Druck zu machen. Italian: Se, alla fine, gli Stati Uniti sferreranno un attacco unilaterale a dispetto degli accordi del Consiglio di Sicurezza dell'ONU, boicottiamone i prodotti (hamburger, sigarette, bibite, film, benzina -SHELL, ESSO, EXXON, MOBIL, GULF- ecc., ecc.). Questa lettera è stata inviata a 30 persone. Se ognuno la spedirà ad altre 10 persone (30x10=300), in 8 gg. ne avremo sensibilizzato oltre 300 milioni. Passiamo all'azione tutti insieme per fare forza. Portuguese: Se finalmente se realizar o ataque unilateral dos Estados Unidos, ignorando os acordos do Conselho de Segurança da ONU, boicoteemos os produtos deles (hambúrgueres, tabaco, bebidas, filmes, gasolina -SHELL, ESSO, EXXON, MOBIL e GULF- etc., etc.,) Esta carta foi transmitida a 30 pessoas, se cada uma enviar a mesma a mais 10 (30x10=300), em 8 dias teremos sensibilizado mais de 300 milhões de pessoas. Actuemos todos juntos para fazer a força!
amstatus wha?
Below is the output of amstatus. It struck me as a bit odd that the backup wasn't finished yet since it normally only takes 3 hours, and starts at 3:00 AM. As such it's usually done once I get in. It's not done. The part that caught my attention is big-kahuna:/db -- is that number supposed to be negative, or am I just reading it wrong? ===snip!=== bash-2.03$ /usr/local/sbin/amstatus daily Using /var/amanda/Daily/amdump wipeout:/0 19616k finished wipeout:/usr 0 516224k finished wipeout:/var 0 112736k finished wipeout:/db 1 62624k finished wipeout:/work0 2731712k finished longboard:/ 0 10240k finished longboard:/usr 0 659456k finished longboard:/var 0 421760k finished longboard:/data 0 3054688k finished longboard:/home 0 5994240k writing to tape longboard:/work 12592k finished intergate:da0a 09472k finished intergate:/usr 0 43808k finished intergate:/var 0 1939680k finished tidal:/ 0 12608k finished tidal:/usr 0 359872k finished tidal:/data 0 269344k finished tidal:/mail 1 142176k finished tidal:/var 0 364064k finished tidal:/web 11984k finished big-kahuna:/ 0 22144k finished big-kahuna:/usr 0 576800k finished big-kahuna:/var 0 160224k finished big-kahuna:/db 0 2399012k dumping-1981216k (-82.58%) big-kahuna:/work 1 445312k finished cachebox:/ 0 20192k finished cachebox:/usr0 439936k finished cachebox:/var0 40832k finished wammer:/ 0 44352k finished wammer:/usr 1 107360k finished wammer:/var 02656k finished iguard:/ 0 19584k finished iguard:/usr 0 384768k finished iguard:/var 1 19456k finished iguard:/work 0 64k finished iguard:/db 1 1559072k finished iguard:/db/wal 1 32864k finished ns2:/0 16000k finished ns2:/usr 0 301728k finished ns2:/var 18736k finished SUMMARY part real estimated size size partition : 40 estimated : 40 22791952k failed : 0 0k wait for dumping: 0 0k dumping to tape : 0 0k dumping : 1 -1981216k 2399012k dumped : 39 20930976k 20392940k wait for writing: 00k0k writing to tape : 1 5994240k 5817576k failed to tape : 00k0k taped : 38 14936736k 14575364k 7 dumpers idle : not-idle taper writing, tapeq: 0 network free kps: 14775 holding space : 17206684 ===snip!=== -- David Olbersen iGuard Engineer 11415 West Bernardo Court San Diego, CA 92127 1-858-676-2277 x2152
Re: amstatus wha?
Nevermind, it finished about 10 seconds after I hit 'Send'. Typical... -- David Olbersen iGuard Engineer 11415 West Bernardo Court San Diego, CA 92127 1-858-676-2277 x2152
Re: can't backup a remote machine
My guess would be a firewall issue. On Wed, 2003-03-26 at 16:30, Glen Kaukola wrote: > Hi, > > I've installed Amanda 2.4.2p2-9 installed on a Red Hat 7.3 system so I > can back up some of our data. I've got it working for backing up the > /etc directory on the local machine, but it fails to back up the data > from a remote machine even though I get no errors when I run amcheck. > > In the summary email I get after running amdump it says this about the > remote machine: > > FAILURE AND STRANGE DUMP SUMMARY: >ammonia/home/web lev 0 FAILED [missing result for /home/web > in ammonia response] > > When I look at the logs it's telling me that my remote machine is > failing to send back estimates. So would anyone know why this is > happening and how I can fix it? > > Thanks for your time. > > -- > Glen Kaukola > [EMAIL PROTECTED] > (909) 781-5630 > CE-CERT > UC Riverside > >
Re: 'not an Amanda tape' after FreeBSD upgrade
I have the same problem with my amanda 2.4.3 (FreeBSD 4.7) I upgraded my FreeBSD ports collection and to upgrade KDE 3.0 -> 3.1 and didn't think of this as a major upgrade (that would affect my systems stability) and therefore have no numbers or anything to bring here for information. But come to think of it, exactly from the point when i upgraded, i'm getting these messages. At first i thought that my one of my tapes is buggy and erased it before relabeling and running amflush. Now second one failed. That made me curious... i was firightened that all of my tapes are ruined (by some magnetic smth or what ever) as they are all in one place. After flushing this tape i put in next one and ran amcheck (i didn't think of this as a sticky problem in the first place and hoped only one of my tapes was problematic therefore didn't precheck previous tapes). Amcheck ran fine and without any errors... i'll find out tomorrow, if amdump also has no errors. Also i can restore from the tape written before upgrade (at least when using dummy hostname amrestore lists all files, I did not try actual restore) If the problem persists, i dig further more into it, so far this is ment as information that this problem has occured elsewere too. Laas Toom Now i put a next tape in and run am On Thu, 27 Mar 2003, Toomas Aas wrote: > Hello! > > My Amanda server is running 2.4.3b4. Three days ago I upgraded the > operating system from FreeBSD 4.7-RELEASE-p6 to 4.7-RELEASE-p9. This is > really just some security patches to sendmail, libc and openssl. Since > the upgrade Amanda thinks that all the backup tapes that were written > before the upgrade are "not Amanda tapes". > > After I re-label the tape, Amanda agrees to write the backup to it and > also I can successfully amrestore it later. But it seems that, should > the need arise to restore from a pre-upgrade tape, I would be in > trouble because those tapes are 'not Amanda tapes'. I suppose I could > still read the dump images with dd, though? > > Over the last couple of years I've done many OS upgrades on this Amanda > server and this is the first time I see such problem. Has anyone else > seen it? > -- > Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ > * It's always darkest right before you step on the cat. >
Re: 'not an Amanda tape' after FreeBSD upgrade
* Toomas Aas <[EMAIL PROTECTED]> (Thu, Mar 27, 2003 at 11:15:52AM +0200) > Hello! > > My Amanda server is running 2.4.3b4. Three days ago I upgraded the > operating system from FreeBSD 4.7-RELEASE-p6 to 4.7-RELEASE-p9. This is > really just some security patches to sendmail, libc and openssl. Since > the upgrade Amanda thinks that all the backup tapes that were written > before the upgrade are "not Amanda tapes". > > After I re-label the tape, Amanda agrees to write the backup to it and > also I can successfully amrestore it later. But it seems that, should > the need arise to restore from a pre-upgrade tape, I would be in > trouble because those tapes are 'not Amanda tapes'. I suppose I could > still read the dump images with dd, though? > > Over the last couple of years I've done many OS upgrades on this Amanda > server and this is the first time I see such problem. Has anyone else > seen it? IIRC amanda checks the tapelabel by basically doing dd if=/dev/tape bs=32k count=1 If you do this manually, what comes back ? It sounds like some default setting for your tapedevice has changed. Kind regards, -- Gerhard den Hollander Phone :+31-10.280.1515 Global IT Support manager Direct:+31-10.280.1539 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.
AW: amandapass - Domain Account
Thanks, it worked out fine :-)) -Ursprüngliche Nachricht- Von: Galen Johnson [mailto:[EMAIL PROTECTED] Gesendet: Samstag, 22. März 2003 00:32 An: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Betreff: Re: amandapass - Domain Account Have you tried: //bv-miene/test/ amanda%password agki ? =G= Matthias Unger wrote: > Hello, > > I want to save a windows share on am win2k-workstation. I test the > share with smbmount //bv-miene/test -o username=amanda/agki (amanda is > the backup account in the agki domain). And it works. > Now I want to register it in the disklist and amandapass. > But how can I register it in amandapass? > //bv-miene/test/ amanda/agki%password or > //bv-miene/test/ amanda%password doesn't work! Because it is a domain > account and not a local account. > > Thanks > > > *Matthias Unger > *Universität Bremen >
'not an Amanda tape' after FreeBSD upgrade
Hello! My Amanda server is running 2.4.3b4. Three days ago I upgraded the operating system from FreeBSD 4.7-RELEASE-p6 to 4.7-RELEASE-p9. This is really just some security patches to sendmail, libc and openssl. Since the upgrade Amanda thinks that all the backup tapes that were written before the upgrade are "not Amanda tapes". After I re-label the tape, Amanda agrees to write the backup to it and also I can successfully amrestore it later. But it seems that, should the need arise to restore from a pre-upgrade tape, I would be in trouble because those tapes are 'not Amanda tapes'. I suppose I could still read the dump images with dd, though? Over the last couple of years I've done many OS upgrades on this Amanda server and this is the first time I see such problem. Has anyone else seen it? -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * It's always darkest right before you step on the cat.
