Re: Still get No index records...
On Mon, Dec 30, 2002 at 09:24:33PM -0500, Gene Heskett wrote: On Monday 30 December 2002 19:26, John Oliver wrote: [root@backup root]# amrecover AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 backup AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-12-30) 200 Working date set to 2002-12-30. 200 Config set to DailySet1. 501 No index records for host: backup.indyme.local. Invalid? Trying backup.indyme.local ... 501 No index records for host: backup.indyme.local. Invalid? Trying backup ... 501 No index records for host: backup. Invalid? I do have index yes in amanda.conf. Why is it still unhappy? Where specifically in amanda.conf? This is supposed to be a dumptype by dumptype configuration option. That leaves the posibility that someplace in the chain of defines, its turned back off by your choice of dumptypes. Yes, I put it in the dumptype I'm using. There may be a dim possibility that your particular tar is fubar, what version are you useing? Minimum generally speaking is 1.13-19, with 1.13-25 being in wide use now. 1.13 with no suffix is usually grounds enough to replace it with the newer release. Get 1.13-25 from alpha.gnu.org. I have 1.13-25 -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Still get No index records...
On Tue, Dec 31, 2002 at 08:22:10AM +0300, Hery Zo RAKOTONDRAMANANA wrote: Gene Heskett wrote: On Monday 30 December 2002 19:26, John Oliver wrote: [root@backup root]# amrecover I had this problem but solvd it when launched amrecover with the name of your config. [root@backup root]# amrecover YourBackupConfig Nope. But I'm noticing that amrecover is wanting to talk to localhost instead of backup. I'm not sure where/how to change that. -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
RE: Still get No index records...
I would forget about trying to get amrecover to recognize index records. I was never able to do it. And to this day, I don't use amrecover, I use amrestore instead. Michael Martinez -Original Message- From: John Oliver [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 31, 2002 6:07 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Still get No index records... On Mon, Dec 30, 2002 at 09:24:33PM -0500, Gene Heskett wrote: On Monday 30 December 2002 19:26, John Oliver wrote: [root@backup root]# amrecover AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 backup AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-12-30) 200 Working date set to 2002-12-30. 200 Config set to DailySet1. 501 No index records for host: backup.indyme.local. Invalid? Trying backup.indyme.local ... 501 No index records for host: backup.indyme.local. Invalid? Trying backup ... 501 No index records for host: backup. Invalid? I do have index yes in amanda.conf. Why is it still unhappy? Where specifically in amanda.conf? This is supposed to be a dumptype by dumptype configuration option. That leaves the posibility that someplace in the chain of defines, its turned back off by your choice of dumptypes. Yes, I put it in the dumptype I'm using. There may be a dim possibility that your particular tar is fubar, what version are you useing? Minimum generally speaking is 1.13-19, with 1.13-25 being in wide use now. 1.13 with no suffix is usually grounds enough to replace it with the newer release. Get 1.13-25 from alpha.gnu.org. I have 1.13-25 -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Still get No index records...
On Tuesday 31 December 2002 18:10, John Oliver wrote: On Tue, Dec 31, 2002 at 08:22:10AM +0300, Hery Zo RAKOTONDRAMANANA wrote: Gene Heskett wrote: No, I did not write this. On Monday 30 December 2002 19:26, John Oliver wrote: [root@backup root]# amrecover I had this problem but solvd it when launched amrecover with the name of your config. [root@backup root]# amrecover YourBackupConfig Nope. But I'm noticing that amrecover is wanting to talk to localhost instead of backup. I'm not sure where/how to change that. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.21% setiathome rank, not too shabby for a WV hillbilly
Re: Still get No index records...
On Tue, Dec 31, 2002 at 03:10:50PM -0800, John Oliver wrote: On Tue, Dec 31, 2002 at 08:22:10AM +0300, Hery Zo RAKOTONDRAMANANA wrote: Gene Heskett wrote: On Monday 30 December 2002 19:26, John Oliver wrote: [root@backup root]# amrecover I had this problem but solvd it when launched amrecover with the name of your config. [root@backup root]# amrecover YourBackupConfig Nope. But I'm noticing that amrecover is wanting to talk to localhost instead of backup. I'm not sure where/how to change that. $ man amrecover AMANDA INDEX AMRECOVER(8) NAME amrecover - Amanda index database browser SYNOPSIS amrecover [ [ -C ] config ] [ -s index-server ] [ -t tape- server ] [ -d tape-device ] -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Still get No index records...
On Thu, Jan 02, 2003 at 10:35:50AM -0500, Martinez, Michael - CSREES/ISTM wrote: I would forget about trying to get amrecover to recognize index records. I was never able to do it. And to this day, I don't use amrecover, I use amrestore instead. Just another datapoint ... I've never used amrestore (not that it failed, just never used it). I've only used amrecover with its index records. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Still get No index records...
On Monday 30 December 2002 19:26, John Oliver wrote: [root@backup root]# amrecover AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 backup AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-12-30) 200 Working date set to 2002-12-30. 200 Config set to DailySet1. 501 No index records for host: backup.indyme.local. Invalid? Trying backup.indyme.local ... 501 No index records for host: backup.indyme.local. Invalid? Trying backup ... 501 No index records for host: backup. Invalid? I do have index yes in amanda.conf. Why is it still unhappy? Where specifically in amanda.conf? This is supposed to be a dumptype by dumptype configuration option. That leaves the posibility that someplace in the chain of defines, its turned back off by your choice of dumptypes. There may be a dim possibility that your particular tar is fubar, what version are you useing? Minimum generally speaking is 1.13-19, with 1.13-25 being in wide use now. 1.13 with no suffix is usually grounds enough to replace it with the newer release. Get 1.13-25 from alpha.gnu.org. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.21% setiathome rank, not too shabby for a WV hillbilly
Re: Still get No index records...
Gene Heskett wrote: On Monday 30 December 2002 19:26, John Oliver wrote: [root@backup root]# amrecover I had this problem but solvd it when launched amrecover with the name of your config. [root@backup root]# amrecover YourBackupConfig cheers. Hery Zo RAKOTONDRAMANANA AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 backup AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-12-30) 200 Working date set to 2002-12-30. 200 Config set to DailySet1. 501 No index records for host: backup.indyme.local. Invalid? Trying backup.indyme.local ... 501 No index records for host: backup.indyme.local. Invalid? Trying backup ... 501 No index records for host: backup. Invalid? I do have index yes in amanda.conf. Why is it still unhappy? Where specifically in amanda.conf? This is supposed to be a dumptype by dumptype configuration option. That leaves the posibility that someplace in the chain of defines, its turned back off by your choice of dumptypes. There may be a dim possibility that your particular tar is fubar, what version are you useing? Minimum generally speaking is 1.13-19, with 1.13-25 being in wide use now. 1.13 with no suffix is usually grounds enough to replace it with the newer release. Get 1.13-25 from alpha.gnu.org.
Re: Still get No index records...
On Mon, 30 Dec 2002, John Oliver wrote: 501 No index records for host: backup.indyme.local. Invalid? Trying backup.indyme.local ... 501 No index records for host: backup.indyme.local. Invalid? Trying backup ... 501 No index records for host: backup. Invalid? What did you use for the hostname for this client in disklist? -Mitch
