Re: Amrecover: No index records for disk for specified date: Done
Jon LaBadie said: On Wed, Apr 27, 2005 at 11:46:49AM -0700, Tanniel Simonian wrote: Hello Group, I tend to figure things out on my own fairly quickly, however I can't seem to figure this problem out. I have a tape that I archived on February 25th, 2005. My tape cycle is 5 weeks and therefore February 25th has long been gone. A tapecycle has no units. It is a simple integer, number of tapes in rotation. I had stopped backing up this particular host on that date due to stability issues. However, I need to restore a tar'd file from this tape off that host. How do you mean you archived that tape? Is that a different archive config? Or did you just pull it out of rotation? Possibly replacing it with another of the same label so amanda thinks it might have been overwritten? Pulled the tape out of rotation and placed a new tape with the same label. At first I figured that since the tape was old, that the index record has been rotated or removed. I check /var/lib/amanda/xes/index/brimstone/sdb1 and noticed that the index file does index exist for that date. Was that a level 0? I wonder if a level is needed for amrecover to work - I don't know the answer. Yes the tape is a level 0. Does it have a list of files? Or might the dump have failed that day? You mentioned some type of stability problems. The instability did not affect the backups of that particular machine. The instability was due to old hardware and the proactive need to replace it. If it is not possible to use amrecover at this point, someone one to point me on how to restore a file from tape that has a combination of zipped tar's and dumps. Joshua pointed you in the right direction. Yes, thanks for the point. I was able to find the correct tape file and restore all the files from the tape. Then grabbed what I needed and deleted the rest. Not as elegant as the interactive amrestore or amrecover, but it got the job done. Thanks for the responses. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amrecover: No index records for disk for specified date
On Wed, 27 Apr 2005 at 11:46am, Tanniel Simonian wrote If it is not possible to use amrecover at this point, someone one to point me on how to restore a file from tape that has a combination of zipped tar's and dumps. This bit is easy. The instructions are in docs/RESTORE in the tarball. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Amrecover: No index records for disk for specified date
On Wed, Apr 27, 2005 at 11:46:49AM -0700, Tanniel Simonian wrote: Hello Group, I tend to figure things out on my own fairly quickly, however I can't seem to figure this problem out. I have a tape that I archived on February 25th, 2005. My tape cycle is 5 weeks and therefore February 25th has long been gone. A tapecycle has no units. It is a simple integer, number of tapes in rotation. I had stopped backing up this particular host on that date due to stability issues. However, I need to restore a tar'd file from this tape off that host. How do you mean you archived that tape? Is that a different archive config? Or did you just pull it out of rotation? Possibly replacing it with another of the same label so amanda thinks it might have been overwritten? At first I figured that since the tape was old, that the index record has been rotated or removed. I check /var/lib/amanda/xes/index/brimstone/sdb1 and noticed that the index file does index exist for that date. Was that a level 0? I wonder if a level 0 is needed for amrecover to work - I don't know the answer. Does it have a list of files? Or might the dump have failed that day? You mentioned some type of stability problems. If it is not possible to use amrecover at this point, someone one to point me on how to restore a file from tape that has a combination of zipped tar's and dumps. Joshua pointed you in the right direction. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover - No index records
Hi, I had the same problem a little while ago and it seemed I was using an outdated version of tar on the particular client... Maybe you should try updating tar? It solved my problems... Martin I am running Amanda on a RH9 box. I have indexing turned on in my amanda.conf and the index file is created during amdump. I can unzip the file and view it with no problems. However, whenever I run an amrecover, I get No index records for disk for specified date. I've set the date, host, and disk, but can't get this feature to work. Thanks for the help. Here is an example of the error: # amrecover normal AMRECOVER Version 2.4.3. Contacting server on localhost ... 220 Linx AMANDA index server (2.4.3) ready. 200 Access OK Setting restore date to today (2003-10-09) 200 Working date set to 2003-10-09. 200 Config set to normal. 501 No index records for host: Linx. Invalid? Trying host Linx ... 501 No index records for host: Linx. Invalid? Trying host localhost.localdomain ... 501 No index records for host: localhost.localdomain. Invalid? Trying host localhost ... 501 No index records for host: localhost. Invalid? amrecover sethost linx 200 Dump host set to linx. amrecover ls Must select a disk before listing files amrecover setdisk /home Scanning /var/tmp... 200 Disk set to /home. No index records for disk for specified date If date correct, notify system administrator amrecover
Re: amrecover - No index records
Sector Unknown wrote: --- Paul Bijnens [EMAIL PROTECTED] wrote: What is the result of the amrecover command history at this moment? Does it line up with the contents of the index directory? ... amrecover history 200- Dump history for config normal host linx disk /home 200 Dump history for config normal host linx disk /home And what *is* the contents of the index/linx/_home directory? It should contain files like 20031009_0.gz (notice they are normally gzipped; only when being in use, they are unzipped AND sorted by amindexd). Are the permissions correct i.e. can user amanda read the gzipped files, and write in the directory to unzip them? -- Paul @ Home
Re: amrecover - No index records
--- Paul Bijnens [EMAIL PROTECTED] wrote: Sector Unknown wrote: --- Paul Bijnens [EMAIL PROTECTED] wrote: What is the result of the amrecover command history at this moment? Does it line up with the contents of the index directory? ... amrecover history 200- Dump history for config normal host linx disk /home 200 Dump history for config normal host linx disk /home And what *is* the contents of the index/linx/_home directory? It should contain files like 20031009_0.gz (notice they are normally gzipped; only when being in use, they are unzipped AND sorted by amindexd). Are the permissions correct i.e. can user amanda read the gzipped files, and write in the directory to unzip them? -- Paul @ Home index/linx/_home currently has a file called 20031009_0.gz in it and I've temporarily set the rights on the directory so anyone can write to it (its a test server). Also, I'm running running amrecover as root. __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
Re: amrecover: No index records for disk for specified date
[ ... ] What's the output of 'amadmin ks find mercedes-benz /usr/people/jfo'? Trying this helped me figure out what was wrong ;-) The command would list the expected dates and tape names when executed as root, but as amanda, I got No dump to list, which made it quite obvious that the permissions of some file required were wrong (I suspected that all along, but I wasn't able to spot the exact problem earlier.) It then turned out that tapelist was no longer readable by amanda, for some reason. After a simple chmod, I was able to restore the backup correctly. Question: Why didn't amrecover or the amindexd log tell me that the tapelist was unreadable? If you ran amrecover as amanda-user, why didn't it tell you: I didn't. The configs aren't read by amrecover, but by amindexd, which is always executed as amanda-user (as far as I can tell.) - Toralf
Re: amrecover: No index records for disk for specified date
On Tue, Feb 11, 2003 at 05:31:04PM +0100, Toralf Lund wrote: I'm getting error message No index records for disk for specified date when trying to recover a certain DLE using amrecover (version 2.4.3.) The full output from the session + some of the debug messages are included below. The index looks good to me; [ ... ] An index file doesn't mean that the backup is still available. Really? What's the output of 'amadmin ks find mercedes-benz /usr/people/jfo'? Trying this helped me figure out what was wrong ;-) The command would list the expected dates and tape names when executed as root, but as amanda, I got No dump to list, which made it quite obvious that the permissions of some file required were wrong (I suspected that all along, but I wasn't able to spot the exact problem earlier.) It then turned out that tapelist was no longer readable by amanda, for some reason. After a simple chmod, I was able to restore the backup correctly. Question: Why didn't amrecover or the amindexd log tell me that the tapelist was unreadable? - Toralf
Re: amrecover: No index records for disk for specified date
On Wed, Feb 12, 2003 at 02:10:52PM +0100, Toralf Lund wrote: On Tue, Feb 11, 2003 at 05:31:04PM +0100, Toralf Lund wrote: I'm getting error message No index records for disk for specified date when trying to recover a certain DLE using amrecover (version 2.4.3.) The full output from the session + some of the debug messages are included below. The index looks good to me; [ ... ] An index file doesn't mean that the backup is still available. Really? What's the output of 'amadmin ks find mercedes-benz /usr/people/jfo'? Trying this helped me figure out what was wrong ;-) The command would list the expected dates and tape names when executed as root, but as amanda, I got No dump to list, which made it quite obvious that the permissions of some file required were wrong (I suspected that all along, but I wasn't able to spot the exact problem earlier.) It then turned out that tapelist was no longer readable by amanda, for some reason. After a simple chmod, I was able to restore the backup correctly. Question: Why didn't amrecover or the amindexd log tell me that the tapelist was unreadable? If you ran amrecover as amanda-user, why didn't it tell you: $ amrecover amrecover: amrecover must be run by root jon - Toralf End of included message -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover: No index records for disk for specified date
On Wed, Feb 12, 2003 at 02:10:52PM +0100, Toralf Lund wrote: Question: Why didn't amrecover or the amindexd log tell me that the tapelist was unreadable? Because there was a bug. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: amrecover: No index records for disk for specified date
On Tue, Feb 11, 2003 at 05:31:04PM +0100, Toralf Lund wrote: I'm getting error message No index records for disk for specified date when trying to recover a certain DLE using amrecover (version 2.4.3.) The full output from the session + some of the debug messages are included below. The index looks good to me; I have # ls -lR /dumps/amanda/ks/index/mercedes-benz total 0 drwxr-sr-x2 amanda disk 97 Feb 11 01:43 _usr_people_jfo /dumps/amanda/ks/index/mercedes-benz/_usr_people_jfo: total 192 -rw---1 amanda disk 18539 Nov 14 22:16 20021114_0.gz -rw---1 amanda disk 23757 Dec 9 22:17 20021209_0.gz -rw---1 amanda disk 23043 Jan 6 22:13 20030106_0.gz -rw---1 amanda disk 26515 Jan 31 22:16 20030131_0.gz An index file doesn't mean that the backup is still available. What's the output of 'amadmin ks find mercedes-benz /usr/people/jfo'? What's the output of the 'history' command in amrecover? Also, I successfully ran a similar recovery yesterday - same DLE, but different date, as I didn't have the latest tape available, then - but something must have changed in the meantime, or I'm doing it in a slightly different way (I've tried other dates again today, though, but all with the same result.) Any ideas what is wrong? Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
RE: amrecover: No index records for disk for specified date
Hi folks.
i am having the exact same problem.
I have checked the following:
1. Version of tar is upgraded
2. The backups themselves are successfull
3. The index files are indeed present where they should be
4. the correct index directory is specified in amanda.conf
5. the amanidx/tcp service is specified in /etc/services on the client machine eg. :
amanda 10080/udp # amanda added by jdb 2002-05-15
amandaidx 10082/tcp # amanda added by jdb 2002-05-15
amidxtape 10083/tcp # amanda added by jdb 2002-05-15
6. these services are available on the server machine (redhat 7.2) and in addition
being in /etc/services, are also correctly present in xinetd.
7. If it type the history command, the backup for that particular host is listed
correctly.
Can someone please point me in the right direction?
thanks,
john.
Here is the output from amrecover (domain names removed to protect the innocent).
bash-2.05# amrecover -s serverhost..net
AMRECOVER Version 2.4.2p2. Contacting server on monitor.rvbs.net ...
220 monitor AMANDA index server (2.4.3b3) ready.
200 Access OK
Setting restore date to today (2002-05-29)
200 Working date set to 2002-05-29.
200 Config set to DailySet1.
501 No index records for host: www. Invalid?
Trying www.(client domain).com ...
200 Dump host set to www.(client domain).com.
$CWD '/usr/local/src' is on disk '/' mounted at '/'.
200 Disk set to /.
No index records for disk for specified date
If date correct, notify system administrator
Invalid directory - /usr/local/src
amrecover quit
200 Good bye.
Simas Cepaitis wrote:
Hello,
-Original Message-
From: Jon LaBadie [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 27, 2002 8:35 PM
To: Simas Cepaitis
Subject: Re: amrecover: No index records for disk for specified date
Any chance your disklist uses localhost rather than a hostname?
No, I use full hostname. For example,
sunny.5ci.lt /usr {
always-full
exclude list /usr/local/etc/amanda/test/.exclude
compress server fast
} -1 local
If using tar, maybe a bad release of tar. gunzip one of the
indexs. See if each line begins with a long number. That is
one sign of a bad tar.
I tried using both gnutar (version 1.13.25) and native FreeBSD tar.
# pwd
/usr/local/etc/amanda/test/index/sunny.5ci.lt/_usr
#zmore 20020527_0.gz
/
/bin/
/bin/cu
/bin/uucp
/bin/uulog
/bin/uuname
/bin/uupick
/bin/uusched
...
...
I don't think that is a tar problem. Somehow I believe that rather
directory with indexes is not found. Is there any option to enable
debug mode or something to see more in logs? Because now
they aren't providing much use (amrecover for example)... :(
Simas Cepaitis
[EMAIL PROTECTED]
ME TOO RE: amrecover: No index records for disk for specified date: ME TOO
i'm getting the same problem too. Makes it impossible to use amrecover to
restore data
Michael Martinez
System Administrator (Contractor)
Information Systems and Technology Management
CSREES - United States Department of Agriculture
(202) 720-6223
-Original Message-
From: John D. Bickle [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 12:06 PM
To: Simas Cepaitis
Cc: 'Jon LaBadie'; '[EMAIL PROTECTED]'
Subject: RE: amrecover: No index records for disk for specified date
Hi folks.
i am having the exact same problem.
I have checked the following:
1. Version of tar is upgraded
2. The backups themselves are successfull
3. The index files are indeed present where they should be
4. the correct index directory is specified in amanda.conf
5. the amanidx/tcp service is specified in /etc/services on the client
machine eg. :
amanda 10080/udp # amanda added by jdb 2002-05-15
amandaidx 10082/tcp # amanda added by jdb 2002-05-15
amidxtape 10083/tcp # amanda added by jdb 2002-05-15
6. these services are available on the server machine (redhat 7.2) and in
addition being in /etc/services, are also correctly present in xinetd.
7. If it type the history command, the backup for that particular host is
listed correctly.
Can someone please point me in the right direction?
thanks,
john.
Here is the output from amrecover (domain names removed to protect the
innocent).
bash-2.05# amrecover -s serverhost..net
AMRECOVER Version 2.4.2p2. Contacting server on monitor.rvbs.net ...
220 monitor AMANDA index server (2.4.3b3) ready.
200 Access OK
Setting restore date to today (2002-05-29)
200 Working date set to 2002-05-29.
200 Config set to DailySet1.
501 No index records for host: www. Invalid?
Trying www.(client domain).com ...
200 Dump host set to www.(client domain).com.
$CWD '/usr/local/src' is on disk '/' mounted at '/'.
200 Disk set to /.
No index records for disk for specified date
If date correct, notify system administrator
Invalid directory - /usr/local/src
amrecover quit
200 Good bye.
Simas Cepaitis wrote:
Hello,
-Original Message-
From: Jon LaBadie [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 27, 2002 8:35 PM
To: Simas Cepaitis
Subject: Re: amrecover: No index records for disk for specified date
Any chance your disklist uses localhost rather than a hostname?
No, I use full hostname. For example,
sunny.5ci.lt /usr {
always-full
exclude list /usr/local/etc/amanda/test/.exclude
compress server fast
} -1 local
If using tar, maybe a bad release of tar. gunzip one of the
indexs. See if each line begins with a long number. That is
one sign of a bad tar.
I tried using both gnutar (version 1.13.25) and native FreeBSD tar.
# pwd
/usr/local/etc/amanda/test/index/sunny.5ci.lt/_usr
#zmore 20020527_0.gz
/
/bin/
/bin/cu
/bin/uucp
/bin/uulog
/bin/uuname
/bin/uupick
/bin/uusched
...
...
I don't think that is a tar problem. Somehow I believe that rather
directory with indexes is not found. Is there any option to enable
debug mode or something to see more in logs? Because now
they aren't providing much use (amrecover for example)... :(
Simas Cepaitis
[EMAIL PROTECTED]
RE: amrecover: No index records for disk for specified date
Hi! i am having the exact same problem. (the problem being that amrecover says index records not present) I have checked the following: 1. Version of tar is upgraded 2. The backups themselves are successfull 3. The index files are indeed present where they should be 4. the correct index directory is specified in amanda.conf 5. the amanidx/tcp service is specified in /etc/services on the client machine eg. : 6. Are the log files present in Amanda's log directory? -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Mcmxlogist: An expert translator of Roman numerals.
RE: amrecover: No index records for disk for specified date
yes. the log files in /tmp/amanda/amindexd-[date,etc.] do not really say anything other than exhibit the following behavior: when using amrecover, i cd to the appropriate directory (meaning the directory which was backed up last night and which i want to test a restore on). the log file then says that the directory i tried to cd to was an invalid directory. Further info: if i look in the index directory for that host, i find the file which includes the directory in question. if i look in /tmp/amanda/amtrmidx, i see the host and the directory listed (although i don't know what this program does). thanks in advance for your help! cheers, john. Toomas Aas wrote: Hi! i am having the exact same problem. (the problem being that amrecover says index records not present) I have checked the following: 1. Version of tar is upgraded 2. The backups themselves are successfull 3. The index files are indeed present where they should be 4. the correct index directory is specified in amanda.conf 5. the amanidx/tcp service is specified in /etc/services on the client machine eg. : 6. Are the log files present in Amanda's log directory? -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Mcmxlogist: An expert translator of Roman numerals.
RE: amrecover: No index records for disk for specified date
Hi! the log files in /tmp/amanda/amindexd-[date,etc.] do not really say anything other than exhibit the following behavior: Actually, I meant the logfiles in the directory that is specified as 'logdir' in amanda.conf. In my case it's /var/log/amanda/MyConfig/ These files, in addition to index files, are also necessary for amrecover. An unrelated note, if I may. Top-posting and sending out entire paragraphs as single long lines makes replying to your messages somewhat cumbersome. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * How can i miss you if you won't go away?
RE: amrecover: No index records for disk for specified date
Toomas Aas wrote: Actually, I meant the logfiles in the directory that is specified as 'logdir' in amanda.conf. In my case it's /var/log/amanda/MyConfig/ in my case they are specified in amanda.conf as /var/log/amanda, and yes, they are indeed there and given permissions 700. Is there a way of putting amrecover into debug mode? These files, in addition to index files, are also necessary for amrecover. An unrelated note, if I may. Top-posting and sending out entire paragraphs as single long lines makes replying to your messages somewhat cumbersome. Sorry. cheers, john.
RE: amrecover: No index records for disk for specified date
Hello,
-Original Message-
From: Jon LaBadie [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 27, 2002 8:35 PM
To: Simas Cepaitis
Subject: Re: amrecover: No index records for disk for specified date
Any chance your disklist uses localhost rather than a hostname?
No, I use full hostname. For example,
sunny.5ci.lt /usr {
always-full
exclude list /usr/local/etc/amanda/test/.exclude
compress server fast
} -1 local
If using tar, maybe a bad release of tar. gunzip one of the
indexs. See if each line begins with a long number. That is
one sign of a bad tar.
I tried using both gnutar (version 1.13.25) and native FreeBSD tar.
# pwd
/usr/local/etc/amanda/test/index/sunny.5ci.lt/_usr
#zmore 20020527_0.gz
/
/bin/
/bin/cu
/bin/uucp
/bin/uulog
/bin/uuname
/bin/uupick
/bin/uusched
...
...
I don't think that is a tar problem. Somehow I believe that rather
directory with indexes is not found. Is there any option to enable
debug mode or something to see more in logs? Because now
they aren't providing much use (amrecover for example)... :(
Simas Cepaitis
[EMAIL PROTECTED]
Re: amrecover: No index records for host?
On Fri, 7 Dec 2001 at 9:46am, Stavros Patiniotis wrote I get the error, No index records for host? I've upgraded tar, linked the old tar location to the new (ln -s /usr/local/bin/tar /usr/bin/tar), and still get the above error. In the /tmp/amanda dir I get no errors in the amrecover files, however in the amandaindexd files, I get an error like: OISD / 500 No dumps available on or before date 2001-12-07 OISD / 500 No dumps available on or before date 2001-12-07 The partition in question definately has a backup as the Amanda daily report says its been backed up. Obvious question: Is indexing turned on? Do the index files exist? What do the contents look like? I do not record to tape, but leave my backups on the holding disk. What version of amanda? I think 2.4.2p2 may be needed to read backups from disk. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover: No index records for host?
Hello, --- Stavros Patiniotis [EMAIL PROTECTED] escribió: Hello, I don't have the record tag but seems ok to me :) Great! On the client when running ./configure I get [cut] checking for gtar... no checking for gnutar... no checking for tar... /usr/local/bin/tar [cut] But there is a parameter called with-gnu-tar or something (do a ./configure --help). Then it should work. This is what I ran it as ./configure --with-user=amanda --with-group=amanda --with-config=incrementat --with-gnutar --without-server --with-index-server=fil.esc.net.au Yes but you should provide the whole path to the tar program, like: --with-gnutar=/usr/local/bin/tar however, www# which tar /usr/local/bin/tar www# tar --version tar (GNU tar) 1.13.25 Copyright (C) 2001 Free Software Foundation, Inc. This program comes with NO WARRANTY, to the extent permitted by law. You may redistribute it under the terms of the GNU General Public License; see the file named COPYING for details. Written by John Gilmore and Jay Fenlason. Any more suggestions? Hope this helps JV. --- Stavros Patiniotis [EMAIL PROTECTED] escribió: Hello, I get the error, No index records for host? I've upgraded tar, linked the old tar location to the new (ln -s /usr/local/bin/tar /usr/bin/tar), and still get the above error. In the /tmp/amanda dir I get no errors in the amrecover files, however in the amandaindexd files, I get an error like: OISD / 500 No dumps available on or before date 2001-12-07 OISD / 500 No dumps available on or before date 2001-12-07 The partition in question definately has a backup as the Amanda daily report says its been backed up. I do not record to tape, but leave my backups on the holding disk. Any suggestion? Kind Regards, 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 escape net m a k i n g t h e n e t w o r k f o r y o u 465b South Road ph 8293 2526 KESWICK SA 5035 fx 8293 2949 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com
Re: amrecover: No index records for host?
Hello, I don't have the record tag but seems ok to me :) Great! On the client when running ./configure I get [cut] checking for gtar... no checking for gnutar... no checking for tar... /usr/local/bin/tar [cut] But there is a parameter called with-gnu-tar or something (do a ./configure --help). Then it should work. This is what I ran it as ./configure --with-user=amanda --with-group=amanda --with-config=incrementat --with-gnutar --without-server --with-index-server=fil.esc.net.au however, www# which tar /usr/local/bin/tar www# tar --version tar (GNU tar) 1.13.25 Copyright (C) 2001 Free Software Foundation, Inc. This program comes with NO WARRANTY, to the extent permitted by law. You may redistribute it under the terms of the GNU General Public License; see the file named COPYING for details. Written by John Gilmore and Jay Fenlason. Any more suggestions? Hope this helps JV. --- Stavros Patiniotis [EMAIL PROTECTED] escribió: Hello, I get the error, No index records for host? I've upgraded tar, linked the old tar location to the new (ln -s /usr/local/bin/tar /usr/bin/tar), and still get the above error. In the /tmp/amanda dir I get no errors in the amrecover files, however in the amandaindexd files, I get an error like: OISD / 500 No dumps available on or before date 2001-12-07 OISD / 500 No dumps available on or before date 2001-12-07 The partition in question definately has a backup as the Amanda daily report says its been backed up. I do not record to tape, but leave my backups on the holding disk. Any suggestion? Kind Regards, 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 escape net m a k i n g t h e n e t w o r k f o r y o u 465b South Road ph 8293 2526 KESWICK SA 5035 fx 8293 2949 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com
Re: amrecover: No index records for host?
Hello,
--- Stavros Patiniotis [EMAIL PROTECTED] escribió:
Hello,
Hi!
What i did was to recompile the amanda server and
also
added the option index to the dumpiles type (for
example comp-user) in the amanda.conf file. I got
it
working for Tar, and i let you know if that fixes
my
dump errors too (i got that error with dump).
Ok, I have now recomplied the server and client
after installing tar
1.13.25, previously I had only link the old tar
location to the new
tar. I have the following in amanda.conf:
define dumptype incremental {
comment General Data Backup
priority medium
program GNUTAR
compress client fast
index yes
record yes
}
I don't have the record tag but seems ok to me :)
On the client when running ./configure I get
[cut]
checking for gtar... no
checking for gnutar... no
checking for tar... /usr/local/bin/tar
[cut]
But there is a parameter called with-gnu-tar or
something (do a ./configure --help). Then it should
work.
however,
www# which tar
/usr/local/bin/tar
www# tar --version
tar (GNU tar) 1.13.25
Copyright (C) 2001 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent
permitted by law.
You may redistribute it under the terms of the GNU
General Public License;
see the file named COPYING for details.
Written by John Gilmore and Jay Fenlason.
Any more suggestions?
Hope this helps
JV.
--- Stavros Patiniotis [EMAIL PROTECTED]
escribió:
Hello,
I get the error, No index records for host?
I've
upgraded tar, linked the
old tar location to the new (ln -s
/usr/local/bin/tar /usr/bin/tar), and
still get the above error. In the /tmp/amanda
dir I
get no errors in the
amrecover files, however in the amandaindexd
files,
I get an error like:
OISD /
500 No dumps available on or before date
2001-12-07
OISD /
500 No dumps available on or before date
2001-12-07
The partition in question definately has a
backup as
the Amanda daily
report says its been backed up.
I do not record to tape, but leave my backups on
the
holding disk.
Any suggestion?
Kind Regards,
0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
escape net
m a k i n g t h e n e t w o r k f o
r
y o u
465b South Road
ph 8293 2526
KESWICK SA 5035
fx 8293 2949
0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
=
System Engineer, José Vicente Nuñez Zuleta
([EMAIL PROTECTED])
Newbreak System Administrator
(http://www.newbreak.com)
Phone: 203-355-1511, 203-355-1510
Java 2 Certified Programmer
Java 2 Certified Developer
_
Do You Yahoo!?
¿Quieres armar tu própia página Web pero no sabes
HTML?
Usa los asistentes de edición de Yahoo! Geocities
y tendrás un sitio en sólo unos minutos.
Visítanos en http://espanol.geocities.yahoo.com
=
System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED])
Newbreak System Administrator (http://www.newbreak.com)
Phone: 203-355-1511, 203-355-1510
Java 2 Certified Programmer
Java 2 Certified Developer
_
Do You Yahoo!?
¿Quieres armar tu própia página Web pero no sabes HTML?
Usa los asistentes de edición de Yahoo! Geocities
y tendrás un sitio en sólo unos minutos.
Visítanos en http://espanol.geocities.yahoo.com
Re: amrecover: No index records for host?
Thanks guys, worked like a charm. I figured that must have been it, didn't see a version of tar later than 1.13 at the mirror I went to initially. I'm using gnu tar 1.13.25 now with no problems (yet!) Thanks again, Rafe On Tue, 4 Dec 2001, Joshua Baker-LePain wrote: On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote 06573011000/./security/dev/audio 06573011000/./security/dev/fd0 06573011000/./security/dev/sr0 06573011000/./security/dev/st0 06573011000/./security/dev/st1 (these are just the contents of /etc on each host). The version of tar on the solaris machine is 1.13. I've heard tar can cause some problems. Do you think that might be it? Those are corrupted index files due to a bad version of tar. You need at least 1.13.17, or 1.13.19. They're available from alpha.gnu.org. If the location of GNUtar moves when you reinstall it, make sure to recompile amanda so that it picks up the correct version. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover: No index records for host?
On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote 06573011000/./security/dev/audio 06573011000/./security/dev/fd0 06573011000/./security/dev/sr0 06573011000/./security/dev/st0 06573011000/./security/dev/st1 (these are just the contents of /etc on each host). The version of tar on the solaris machine is 1.13. I've heard tar can cause some problems. Do you think that might be it? Those are corrupted index files due to a bad version of tar. You need at least 1.13.17, or 1.13.19. They're available from alpha.gnu.org. If the location of GNUtar moves when you reinstall it, make sure to recompile amanda so that it picks up the correct version. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover: No index records for host?
On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote Hi Folks, Another question for ya. After I did an amdump to test out dumping our disks to tape, I tried to do an amrecover to see if restoring the data would work. It seems to work for our linux machines, but the solaris box has some trouble. When I start up amrecover, it reports: ... 200 Config set to imash. 501 No index records for host: hostname. Invalid? Trying hostname.domainname... 200 Dump host set to hostname.domainname ... Then I do a setdisk /etc and it reports: 200 Disk set to /etc. No index records for disk for specified date If date correct, notify system administrator So I figured that the index must not have been created for some reason, but I checked that out on the server and it looks fine. Has the right permissions and ownership. The wierd thing is, if I look into the index files for the host that's giving me trouble, they look a little different than the others. It looks like this: 06573011000/./security/dev/audio 06573011000/./security/dev/fd0 06573011000/./security/dev/sr0 06573011000/./security/dev/st0 06573011000/./security/dev/st1 ... Whereas for the linux hosts, the index looks like this: / /CORBA/ /CORBA/servers/ /X11/ ... (these are just the contents of /etc on each host). The version of tar on the solaris machine is 1.13. I've heard tar can cause some problems. Do you think that might be it? Thanks for your help! Rafe -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover: No index records for host?
This one burned me too :-) Update tar to at least 1.13.17. I've found that 1.13.17 and 1.13.19 both work On Mon, 3 Dec 2001, Rafe Thayer wrote: - Hi Folks, - Another question for ya. After I did an amdump to test out dumping our - disks to tape, I tried to do an amrecover to see if restoring the data - would work. It seems to work for our linux machines, but the solaris box - has some trouble. When I start up amrecover, it reports: - ... - 200 Config set to imash. - 501 No index records for host: hostname. Invalid? - Trying hostname.domainname... - 200 Dump host set to hostname.domainname - ... - - - Then I do a setdisk /etc and it reports: - - 200 Disk set to /etc. - No index records for disk for specified date - If date correct, notify system administrator - - So I figured that the index must not have been created for some reason, - but I checked that out on the server and it looks fine. Has the right - permissions and ownership. The wierd thing is, if I look into the index - files for the host that's giving me trouble, they look a little different - than the others. It looks like this: - - 06573011000/./security/dev/audio - 06573011000/./security/dev/fd0 - 06573011000/./security/dev/sr0 - 06573011000/./security/dev/st0 - 06573011000/./security/dev/st1 - ... - - Whereas for the linux hosts, the index looks like this: - - / - /CORBA/ - /CORBA/servers/ - /X11/ - ... - - (these are just the contents of /etc on each host). The version of tar on - the solaris machine is 1.13. I've heard tar can cause some problems. Do - you think that might be it? - - Thanks for your help! - - Rafe - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
Re: amrecover: No index records for host?
Hi Rafe: I had a similar problem while setting up my configuration last week and I think it was realted with not specifying the fully qualified name of the clients in the disklist and .amandahosts file. You may try with that. Hope this helps. Sincerely... Ana Maria Quoting Rafe Thayer [EMAIL PROTECTED]: Hi Folks, Another question for ya. After I did an amdump to test out dumping our disks to tape, I tried to do an amrecover to see if restoring the data would work. It seems to work for our linux machines, but the solaris box has some trouble. When I start up amrecover, it reports: ... 200 Config set to imash. 501 No index records for host: hostname. Invalid? Trying hostname.domainname... 200 Dump host set to hostname.domainname ... Then I do a setdisk /etc and it reports: 200 Disk set to /etc. No index records for disk for specified date If date correct, notify system administrator So I figured that the index must not have been created for some reason, but I checked that out on the server and it looks fine. Has the right permissions and ownership. The wierd thing is, if I look into the index files for the host that's giving me trouble, they look a little different than the others. It looks like this: 06573011000/./security/dev/audio 06573011000/./security/dev/fd0 06573011000/./security/dev/sr0 06573011000/./security/dev/st0 06573011000/./security/dev/st1 ... Whereas for the linux hosts, the index looks like this: / /CORBA/ /CORBA/servers/ /X11/ ... (these are just the contents of /etc on each host). The version of tar on the solaris machine is 1.13. I've heard tar can cause some problems. Do you think that might be it? Thanks for your help! Rafe - This mail sent through IMP: http://horde.org/imp/
Re: amrecover: No index records for host?
On Mon, 3 Dec 2001 [EMAIL PROTECTED] wrote: Hi Rafe: I had a similar problem while setting up my configuration last week and I think it was realted with not specifying the fully qualified name of the clients in the disklist and .amandahosts file. You may try with that. Hope this helps. Sincerely... Ana Maria Hi Ana Maria, I checked them, and they are using the fully qualified name for the client. Any other suggestions? Rafe Quoting Rafe Thayer [EMAIL PROTECTED]: Hi Folks, Another question for ya. After I did an amdump to test out dumping our disks to tape, I tried to do an amrecover to see if restoring the data would work. It seems to work for our linux machines, but the solaris box has some trouble. When I start up amrecover, it reports: ... 200 Config set to imash. 501 No index records for host: hostname. Invalid? Trying hostname.domainname... 200 Dump host set to hostname.domainname ... Then I do a setdisk /etc and it reports: 200 Disk set to /etc. No index records for disk for specified date If date correct, notify system administrator So I figured that the index must not have been created for some reason, but I checked that out on the server and it looks fine. Has the right permissions and ownership. The wierd thing is, if I look into the index files for the host that's giving me trouble, they look a little different than the others. It looks like this: 06573011000/./security/dev/audio 06573011000/./security/dev/fd0 06573011000/./security/dev/sr0 06573011000/./security/dev/st0 06573011000/./security/dev/st1 ... Whereas for the linux hosts, the index looks like this: / /CORBA/ /CORBA/servers/ /X11/ ... (these are just the contents of /etc on each host). The version of tar on the solaris machine is 1.13. I've heard tar can cause some problems. Do you think that might be it? Thanks for your help! Rafe - This mail sent through IMP: http://horde.org/imp/
