Re: 'no index records...' or Linux -- FreeBSD migration
On Thu, 30 Jan 2014 08:42:51 -0500 Jean-Louis Martineau martin...@zmanda.com wrote: A downgrade of the server is not expected to works, the format of the amanda database (log files) might have changed. What's the output of 'amadmin CONF find'? If it report 'no log files found for tapes...' then either the 'logdir' is not set correctly or 3.3.2 can't read the log file from 3.3.3. If it report all dumps, then the 'indexdir' is nor set correctly. Just to report that I was not able to restore my backup even after bumping amanda to 3.3 and had to re-do backup on new set of tapes with the plain tar and then restored on Free/PC-BSD. Strange thing is that besides my 'backup' config, I also copied other config containing my multimedia collectioni (slides, video...) and amanda recognizes them: [gour@atmarama] /usr/home/gour# sudo -u amanda amadmin hi8 find datehost disk lv tape or file file part status 2011-08-31 21:51:23 atmarama.noip.me /hi8/tape1 0 hi8-4 1 1/1 OK 2011-08-31 21:51:23 atmarama.noip.me /hi8/tape2 0 hi8-2 1 1/1 OK 2011-08-31 21:51:23 atmarama.noip.me /hi8/tape3 0 hi8-1 1 1/1 OK 2011-08-31 21:51:23 atmarama.noip.me /hi8/tape4 0 hi8-3 1 1/1 OK [gour@atmarama] /usr/home/gour# sudo -u amanda amadmin slides find datehost disk lv tape or file file part status 2011-08-30 16:12:46 atmarama.noip.me /slides/tape1 0 slides-21 1/1 OK 2011-08-30 16:12:46 atmarama.noip.me /slides/tape2 0 slides-11 1/1 OK 2011-08-30 16:12:46 atmarama.noip.me /slides/tape3 0 slides-41 1/1 OK 2011-08-30 16:12:46 atmarama.noip.me /slides/tape4 0 slides-31 1/1 OK [gour@atmarama] /usr/home/gour# sudo -u amanda amadmin vhs find datehost disk lv tape or file file part status 2011-09-02 11:48:29 atmarama.noip.me /vhs/tape1 0 vhs-4 1 1/1 OK 2011-09-02 11:48:29 atmarama.noip.me /vhs/tape2 0 vhs-1 1 1/1 OK 2011-09-02 11:48:29 atmarama.noip.me /vhs/tape3 0 vhs-3 1 1/1 OK 2011-09-02 11:48:29 atmarama.noip.me /vhs/tape4 0 vhs-5 1 1/1 OK 2011-09-02 11:48:29 atmarama.noip.me /vhs/tape5 0 vhs-2 1 1/1 OK but, it failed with the most important config for me at the moment of migration. :-( I feel that I might re-do all by backups with bacula... Sincerely, Sasa
Re: 'no index records...' or Linux -- FreeBSD migration
Saša Janiška sjani...@gmail.com (Do 30 Jan 2014 09:44:09 CET): Hello! I'm migrating from Linux to Free/PC-BSD and have problem amrecovering backup due to 'no index records'. On Linux amrecover works and I did cp-ed (on smaller USB disk) all my / including amanda setup. The difference is that on Linux state files are under /var/lib/amanda/... while on FreeBSD I put them under /var/db/amanda/... and adjusted entries in my amanda.conf config file accordingly. Amanda on Linux is 3.3.3, while the one on FreeBSD is 3.3.2. Both OS-es have same gnutar-1.27. Is the version mismatch cause of 'no index records' and/or some hint what is required to be able to restore my files via amrecover? The directory reported by amgetconf CONFIG INDEXDIR should contain folders named according the DLEs you backed up. (With some substitutions for '/') These folders contain *.gz and *.header files. The *.gz are simple compressed text files, having line by line the names of the saved object. I'd think, somehow you're missing these files on you new system. -- Heiko signature.asc Description: Digital signature
Re: 'no index records...' or Linux -- FreeBSD migration
Saša Janiška sjani...@gmail.com (Di 04 Feb 2014 12:51:01 CET):
On Tue, 4 Feb 2014 11:48:44 +0100
Heiko Schlittermann h...@schlittermann.de wrote:
The directory reported by
amgetconf CONFIG INDEXDIR
should contain folders named according the DLEs you backed up.
(With some substitutions for '/')
gour atmarama ~ $ amgetconf backup INDEXDIR
/var/db/amanda/state/index
These folders contain *.gz and *.header files. The *.gz are simple
compressed text files, having line by line the names of the saved
object.
[gour@atmarama] /usr/home/gour# ls -l
/var/db/amanda/state/index/localhost/_home/
total 10044
-rw--- 1 amanda amanda49152 Jan 25 08:38 20140125082842_0.gz.tmp
-rw--- 1 amanda amanda 5079040 Jan 26 14:24 20140126100822_0.gz.tmp
-rw--- 1 amanda amanda 5079040 Jan 29 14:58 20140129103910_0.gz.tmp
The .tmp is somehow suspicious…
I'd say the backup broke. At least the indexing broke.
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de internet unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --- key ID: 7CBF764A -
gnupg fingerprint: 9288 F17D BBF9 9625 5ABC 285C 26A9 687E 7CBF 764A -
(gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B)-
signature.asc
Description: Digital signature
Re: 'no index records...' or Linux -- FreeBSD migration
On Tue, 4 Feb 2014 13:12:49 +0100 Heiko Schlittermann h...@schlittermann.de wrote: The .tmp is somehow suspicious… I'd say the backup broke. At least the indexing broke. That's true, but on Jan 29th I did another full backup which I can restore on Linux, but on Free/PC-BSD. Sincerely, Sasa p.s. I'll now unsubscribe from the amanda list. signature.asc Description: PGP signature
Re: 'no index records...' or Linux -- FreeBSD migration
A downgrade of the server is not expected to works, the format of the amanda database (log files) might have changed. What's the output of 'amadmin CONF find'? If it report 'no log files found for tapes...' then either the 'logdir' is not set correctly or 3.3.2 can't read the log file from 3.3.3. If it report all dumps, then the 'indexdir' is nor set correctly. Jean-Louis On 01/30/2014 03:44 AM, Saša Janiška wrote: Hello! I'm migrating from Linux to Free/PC-BSD and have problem amrecovering backup due to 'no index records'. On Linux amrecover works and I did cp-ed (on smaller USB disk) all my / including amanda setup. The difference is that on Linux state files are under /var/lib/amanda/... while on FreeBSD I put them under /var/db/amanda/... and adjusted entries in my amanda.conf config file accordingly. Amanda on Linux is 3.3.3, while the one on FreeBSD is 3.3.2. Both OS-es have same gnutar-1.27. Is the version mismatch cause of 'no index records' and/or some hint what is required to be able to restore my files via amrecover?
Re: 'no index records...' or Linux -- FreeBSD migration
On Thu, Jan 30, 2014 at 2:42 PM, Jean-Louis Martineau martin...@zmanda.comwrote: A downgrade of the server is not expected to works, the format of the amanda database (log files) might have changed. Ahh...that sucks. I was expected that the same major version 3.3.x should work. :-( What's the output of 'amadmin CONF find'? If it report 'no log files found for tapes...' then either the 'logdir' is not set correctly or 3.3.2 can't read the log file from 3.3.3. That's it. Too bad. I'll try to bump amanda version on FreeBSD or build 3.3.3 from source.
'no index records...' or Linux -- FreeBSD migration
Hello! I'm migrating from Linux to Free/PC-BSD and have problem amrecovering backup due to 'no index records'. On Linux amrecover works and I did cp-ed (on smaller USB disk) all my / including amanda setup. The difference is that on Linux state files are under /var/lib/amanda/... while on FreeBSD I put them under /var/db/amanda/... and adjusted entries in my amanda.conf config file accordingly. Amanda on Linux is 3.3.3, while the one on FreeBSD is 3.3.2. Both OS-es have same gnutar-1.27. Is the version mismatch cause of 'no index records' and/or some hint what is required to be able to restore my files via amrecover?
No index records after upgrade
Hello!
I just finished a major system upgrade on a small one-machine setup
(client=server). This involved upgrading the OS from FreeBSD 6.4 to
8.1 and also upgrading or at least rebuilding all the installed
applications. Amanda was upgraded from 2.5.1 to 3.2.0, and GNU tar
from 1.15.1 to 1.23.
The directories that are used as indexdir and logdir were preserved.
Amanda configuration file was brought over from the old setup and
following changes were made:
removed deprecated keywords: tapebufs, amrecover_do_fsf, amrecover_check_label
repaced the old chg-disk changer with new chg-disk changer, defined so:
tapedev ext-disk
define changer ext-disk {
tpchanger chg-disk:/backup
}
The user who amanda runs as is the same as before (backup). Hostname
is also same, and the name resolution in DNS is correct.
Amcheck passes with no problems.
However, I can't restore anything using amrecover:
amrecover BACKUP
AMRECOVER Version 3.2.0. Contacting server on mail.mydomain.ee ...
220 mail AMANDA index server (3.2.0) ready.
Setting restore date to today (2010-12-13)
200 Working date set to 2010-12-13.
200 Config set to BACKUP.
200 Dump host set to mail.mydomain.ee.
Use the setdisk command to choose dump disk to recover
amrecover setdisk /usr
200 Disk set to /usr.
500 No dumps available on or before date 2010-12-13
No index records for disk for specified date
If date correct, notify system administrator
The result is same for any disk, not just /usr
In my amanda.conf I have:
infofile /var/amanda/BACKUP/curinfo # database DIRECTORY
logdir /var/amanda/BACKUP # log directory
indexdir /var/amanda/BACKUP/index # index directory
All the files seem to be there in /var/amanda and are owned by the
backup user, but for reasons I don't understand Amanda isn't using
them. I've looked at amrecover.debug and amindexd.debug files, but
nothing stands up.
This is not a critical problem, because I can recover manually using
tar and gzip, and I'll overwrite all the vtapes in couple of weeks
anyway (hoping that I *can* recover the backups I'll be making from
now on). But I still think that it should work and would like to
understand why it doesn't.
--
Toomas Aas
Re: No index records after upgrade
Do all tapes are listed in the tapelist file?
Do all log.dataestamp are in logdir?
What's the output of: amadmin BACKUP find
Toomas Aas wrote:
Hello!
I just finished a major system upgrade on a small one-machine setup
(client=server). This involved upgrading the OS from FreeBSD 6.4 to
8.1 and also upgrading or at least rebuilding all the installed
applications. Amanda was upgraded from 2.5.1 to 3.2.0, and GNU tar
from 1.15.1 to 1.23.
The directories that are used as indexdir and logdir were preserved.
Amanda configuration file was brought over from the old setup and
following changes were made:
removed deprecated keywords: tapebufs, amrecover_do_fsf,
amrecover_check_label
repaced the old chg-disk changer with new chg-disk changer,
defined so:
tapedev ext-disk
define changer ext-disk {
tpchanger chg-disk:/backup
}
The user who amanda runs as is the same as before (backup). Hostname
is also same, and the name resolution in DNS is correct.
Amcheck passes with no problems.
However, I can't restore anything using amrecover:
amrecover BACKUP
AMRECOVER Version 3.2.0. Contacting server on mail.mydomain.ee ...
220 mail AMANDA index server (3.2.0) ready.
Setting restore date to today (2010-12-13)
200 Working date set to 2010-12-13.
200 Config set to BACKUP.
200 Dump host set to mail.mydomain.ee.
Use the setdisk command to choose dump disk to recover
amrecover setdisk /usr
200 Disk set to /usr.
500 No dumps available on or before date 2010-12-13
No index records for disk for specified date
If date correct, notify system administrator
The result is same for any disk, not just /usr
In my amanda.conf I have:
infofile /var/amanda/BACKUP/curinfo # database DIRECTORY
logdir /var/amanda/BACKUP # log directory
indexdir /var/amanda/BACKUP/index # index directory
All the files seem to be there in /var/amanda and are owned by the
backup user, but for reasons I don't understand Amanda isn't using
them. I've looked at amrecover.debug and amindexd.debug files, but
nothing stands up.
This is not a critical problem, because I can recover manually using
tar and gzip, and I'll overwrite all the vtapes in couple of weeks
anyway (hoping that I *can* recover the backups I'll be making from
now on). But I still think that it should work and would like to
understand why it doesn't.
Re: no index records
McGraw, Robert P wrote: Jean-Louis, Thanks for your reply. Sorry I did not indicate that I had the following in my tapelist. 20060701 071012 no-reuse 20060701 071011 no-reuse 20060701 071010 no-reuse 20060701 071009 no-reuse This is a grep of my log file. ##R##-zorn-[90] ## grep 0710 log.20060701.0 START taper datestamp 20060701 label archive:071012 tape 0 INFO taper tape archive:071012 kb 186554848 fm 19 writing file: short write START taper datestamp 20060701 label archive:071009 tape 1 INFO taper tape archive:071009 kb 160484512 fm 10 writing file: short write START taper datestamp 20060701 label archive:071010 tape 2 INFO taper tape archive:071010 kb 137568928 fm 8 writing file: short write START taper datestamp 20060701 label archive:071011 tape 3 INFO taper tape archive:071011 kb 146858624 fm 7 writing file: short write Labels are archive:071012, archive:071009, archive:071010 and archive:071011 That's what you must have in the tapelist file: 20060701 archive:071012 no-reuse 20060701 archive:071011 no-reuse 20060701 archive:071010 no-reuse 20060701 archive:071009 no-reuse The labelstr must also match it. Jean-Louis
no index records
I am trying to manually merge some old amanda index data into my present date. When I run amrecover I get the following message. 200 Working date set to 2006-07-02. amrecover listdisk 200- List of disk for host zorn 201- /export/users-q 201- /export/users-r 201- /export/users-s 201- /export/users-t amrecover setdisk /export/users-r 200 Disk set to /export/users-r. No index records for disk for specified date If date correct, notify system administrator I have the log.20060701.0 in my /var/amanda/archive and the following is an ls of my index files. ##R##-zorn-[675] ## ls -al _export_users-r/ total 14692 drwxr-sr-x 2 amanda operator 512 Sep 14 17:02 ./ drwxr-sr-x 35 amanda operator1024 Sep 14 16:44 ../ -rw--- 1 amanda operator 314390 May 6 2006 20060506_0.gz -rw--- 1 amanda operator 312220 Jun 3 2006 20060603_0.gz -rw--- 1 amanda operator 317825 Jul 1 2006 20060701_0.gz -rw--- 1 amanda operator 340959 Sep 5 2006 20060905_0.gz -rw--- 1 amanda operator 364639 Oct 8 2006 20061007200937_0.gz -rw--- 1 amanda operator 406334 Nov 5 2006 20061104201036_0.gz -rw--- 1 amanda operator 443114 Jan 7 2007 20070106201039_0.gz What am I missing that would cause this error. Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 smime.p7s Description: S/MIME cryptographic signature
Re: no index records
The tapelist file must list the label from the log.20060701.0 file. Jean-Louis McGraw, Robert P wrote: I am trying to manually merge some old amanda index data into my present date. When I run amrecover I get the following message. 200 Working date set to 2006-07-02. amrecover listdisk 200- List of disk for host zorn 201- /export/users-q 201- /export/users-r 201- /export/users-s 201- /export/users-t amrecover setdisk /export/users-r 200 Disk set to /export/users-r. No index records for disk for specified date If date correct, notify system administrator I have the log.20060701.0 in my /var/amanda/archive and the following is an ls of my index files. ##R##-zorn-[675] ## ls -al _export_users-r/ total 14692 drwxr-sr-x 2 amanda operator 512 Sep 14 17:02 ./ drwxr-sr-x 35 amanda operator1024 Sep 14 16:44 ../ -rw--- 1 amanda operator 314390 May 6 2006 20060506_0.gz -rw--- 1 amanda operator 312220 Jun 3 2006 20060603_0.gz -rw--- 1 amanda operator 317825 Jul 1 2006 20060701_0.gz -rw--- 1 amanda operator 340959 Sep 5 2006 20060905_0.gz -rw--- 1 amanda operator 364639 Oct 8 2006 20061007200937_0.gz -rw--- 1 amanda operator 406334 Nov 5 2006 20061104201036_0.gz -rw--- 1 amanda operator 443114 Jan 7 2007 20070106201039_0.gz What am I missing that would cause this error. Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067
amrecover: no index records for host
I added 'index yes' in the dumptype Comp-root-tar. I ran amdump using that dumptype with no error reporting. When I use amrecover C myconfig name, I still got the same errorno index records for host. amandaidx service is enabled in xinetd. Please help. Thank you, lei
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)
Amrecover: No index records for disk for specified date
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. 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. I run amrecover -C xes setdate 2005-02-25 sethost brimstone setdisk sdb1 and this message pops up: No index records for disk for specified date If date correct, notify system administrator 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. My question is this. If the tapecycle (which I tried to change temporarily in the config but no such luck) is less than the date you're trying to restore, will amanda not be able to restore it and automatically fail with the message above? Or am I not doing something wrong? 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. Thanks for any knowledge.
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: no index records
Mike Delaney wrote: On Sun, Oct 17, 2004 at 10:25:17PM -0400, Joe Konecny wrote: snip I think I may have found the problem. Somehow I screwed up permissions on /tmp to drwxr-xr-x. Changed to drwxrwxrwx and things look much better. I'll know more after I switch the tape in the morning. /tmp is normally mode 1777, not 0777 (that last 'x' should be a 't'). Thank you! Now I think I know what happened... When amrestore finishes it asks if it should set the mode. I assumed it was the file mode that I had restored but it appeared to change the mode of /tmp which is what I restored to. That is why the next amrestore didn't work. What is amrestore asking me about the mode?
Re: no index records
On Mon, Oct 18, 2004 at 11:39:50AM -0400, Joe Konecny wrote: /tmp is normally mode 1777, not 0777 (that last 'x' should be a 't'). Thank you! Now I think I know what happened... When amrestore finishes it asks if it should set the mode. I assumed it was the file mode that I had restored but it appeared to change the mode of /tmp which is what I restored to. That is why the next amrestore didn't work. What is amrestore asking me about the mode? A guess only, When you backed up, there was a starting directory at the top of the tree . When you restored, there was also a starting directory, ., to which you were restoring into. But that one is not coming from the backup tape, it existed when you started amrecover. If those two don't match in ownership/permissions, maybe amrecover is asking if it is allowed to reset the recovery . to the permissions of the backed up . -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: no index records
Frank Smith wrote: --On Saturday, October 16, 2004 22:58:47 -0400 Joe Konecny [EMAIL PROTECTED] wrote: Using 3.0.4 with FreeBSD 5.2.1... That's confusing to me. The current stable release is 2.4.4p3, and I thing the dev branch is at 2.5.something. Is is an Amanda you built from source or installed from a package? Sorry I was thinking about Samba. I'm on 2.4.4p2. Testing amrecover everything went smooth restoring one file. Tried it again right afterwards and amrecover says no index records. Couldn't figure out what I did to cause it but figured it was me. You may have run amrecover on a filesystem containing the index directory, and it removed all the files not present at the time the backup ran. Its safest to recover into a scratch directory and move the files where you need them. Restoring individual files should work, but if you pick a directory it will remove extra files. Even on individual files you might want to diff them before overwriting, in case there are edits made after the backup you might need to save, so restoring into a scratch dir would still be helpful. I was in /tmp. Ran amdump several times since and no index records are being created. In the index dir last night it created on file called 20041015_0.gz size was 20 bytes. Indexing is turned on. Any ideas on where to look? If you unzip or zcat that file is it totally empty or might it just contain the directory name? Look in the debug files on the client and server to look for clues. Another possibility is that your DLE is a link so all you are backing up is the link itself and not the directory it points to, or you are trying to use dump on a subdirectory (some versions of dump will, some won't). Frank The file is totally empty. I'm doing a full dump of the server running amanda.
Re: no index records
snip I think I may have found the problem. Somehow I screwed up permissions on /tmp to drwxr-xr-x. Changed to drwxrwxrwx and things look much better. I'll know more after I switch the tape in the morning.
Re: no index records
On Sun, Oct 17, 2004 at 10:25:17PM -0400, Joe Konecny wrote: snip I think I may have found the problem. Somehow I screwed up permissions on /tmp to drwxr-xr-x. Changed to drwxrwxrwx and things look much better. I'll know more after I switch the tape in the morning. /tmp is normally mode 1777, not 0777 (that last 'x' should be a 't').
no index records
Using 3.0.4 with FreeBSD 5.2.1... Testing amrecover everything went smooth restoring one file. Tried it again right afterwards and amrecover says no index records. Couldn't figure out what I did to cause it but figured it was me. Ran amdump several times since and no index records are being created. In the index dir last night it created on file called 20041015_0.gz size was 20 bytes. Indexing is turned on. Any ideas on where to look?
Re: no index records
--On Saturday, October 16, 2004 22:58:47 -0400 Joe Konecny [EMAIL PROTECTED] wrote: Using 3.0.4 with FreeBSD 5.2.1... That's confusing to me. The current stable release is 2.4.4p3, and I thing the dev branch is at 2.5.something. Is is an Amanda you built from source or installed from a package? Testing amrecover everything went smooth restoring one file. Tried it again right afterwards and amrecover says no index records. Couldn't figure out what I did to cause it but figured it was me. You may have run amrecover on a filesystem containing the index directory, and it removed all the files not present at the time the backup ran. Its safest to recover into a scratch directory and move the files where you need them. Restoring individual files should work, but if you pick a directory it will remove extra files. Even on individual files you might want to diff them before overwriting, in case there are edits made after the backup you might need to save, so restoring into a scratch dir would still be helpful. Ran amdump several times since and no index records are being created. In the index dir last night it created on file called 20041015_0.gz size was 20 bytes. Indexing is turned on. Any ideas on where to look? If you unzip or zcat that file is it totally empty or might it just contain the directory name? Look in the debug files on the client and server to look for clues. Another possibility is that your DLE is a link so all you are backing up is the link itself and not the directory it points to, or you are trying to use dump on a subdirectory (some versions of dump will, some won't). Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
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
amrecover - No index records
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 __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
Re: No index records problem
Yep, I installed newer tar and it solved my problems on that client! Thanks alot! Martin On Fri, 26 Sep 2003 at 6:16pm, Martin wrote Jon, I have successfully gunzipped the indexfile. Amanda is backing up exactly one directory on the client and that directory contains just one file. Here are the contents of the gunzipped file: 07735043175/./ 07735042527/./pc28_21092003_03.tar.gz The filename above is indeed the file amanda should backup. Does this look like a correct index file? It does to me. Any suggestions? Your index is corrupt because you're using a bad version of tar. You need 1.13.19 or 1.13.25 (available at alpha.gnu.org).
No index records problem
Hi, I'm having some trouble using amrecover. When I try restoringone particular client's fileson theamanda server, amrecover tells me: No index records for disk for specified dateIf date correct, notify system administrator This results in no files being shown when I do an ls, and so I am not able to recover any files. Strangely, otherclients in the same backup-run do not have this problem, only that particular client. The amdump was done without any errors/warnings. Since I am doing the dump to my harddisk in stead of tape, I can actually see the amanda backupfile sitting there, so there's been no error in transfering the data. I checked /usr/adm/amanda/fulldaily/index/pc28/somedir and there is a file named 20030926_0.gz in it, so I suppose the indexfile has been created ok? I'm getting desperate herebecause by the end of next week amanda has to take over our current windows backupsystem :) Thanks for any help! Martin
Re: No index records problem
Jon, I have successfully gunzipped the indexfile. Amanda is backing up exactly one directory on the client and that directory contains just one file. Here are the contents of the gunzipped file: 07735043175/./ 07735042527/./pc28_21092003_03.tar.gz The filename above is indeed the file amanda should backup. Does this look like a correct index file? It does to me. Any suggestions? Thanks! Martin On Fri, Sep 26, 2003 at 04:20:11PM +0200, Martin wrote: Hi, I'm having some trouble using amrecover. When I try restoring one particular client's files on the amanda server, amrecover tells me: No index records for disk for specified date If date correct, notify system administrator This results in no files being shown when I do an ls, and so I am not able to recover any files. Strangely, other clients in the same backup-run do not have this problem, only that particular client. The amdump was done without any errors/warnings. Since I am doing the dump to my harddisk in stead of tape, I can actually see the amanda backupfile sitting there, so there's been no error in transfering the data. I checked /usr/adm/amanda/fulldaily/index/pc28/somedir and there is a file named 20030926_0.gz in it, so I suppose the indexfile has been created ok? Does it seem ok? Do a gzmore on the file if you have it, or gunzip 20030926_0.gz | more if you don't. It should start with a list of directory full pathnames starting from the root of the DLE, not the system. The directory entries IIRC end with a / also. This will be followed by the list of files.
Re: No index records problem
On Fri, 26 Sep 2003 at 6:16pm, Martin wrote Jon, I have successfully gunzipped the indexfile. Amanda is backing up exactly one directory on the client and that directory contains just one file. Here are the contents of the gunzipped file: 07735043175/./ 07735042527/./pc28_21092003_03.tar.gz The filename above is indeed the file amanda should backup. Does this look like a correct index file? It does to me. Any suggestions? Your index is corrupt because you're using a bad version of tar. You need 1.13.19 or 1.13.25 (available at alpha.gnu.org). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: No index records problem
Martin wrote: Jon, I have successfully gunzipped the indexfile. Amanda is backing up exactly one directory on the client and that directory contains just one file. Here are the contents of the gunzipped file: 07735043175/./ 07735042527/./pc28_21092003_03.tar.gz You're using tar 1.13. Bad, very bad. you need at least tar.1.13.19 or better 1.13.25 from: ftp://alpha.gnu.org/gnu/tar/tar-1.13.25.tar.gz -- 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: No index records problem
On Fri, Sep 26, 2003 at 04:20:11PM +0200, Martin wrote: Hi, I'm having some trouble using amrecover. When I try restoring one particular client's files on the amanda server, amrecover tells me: No index records for disk for specified date If date correct, notify system administrator This results in no files being shown when I do an ls, and so I am not able to recover any files. Strangely, other clients in the same backup-run do not have this problem, only that particular client. The amdump was done without any errors/warnings. Since I am doing the dump to my harddisk in stead of tape, I can actually see the amanda backupfile sitting there, so there's been no error in transfering the data. I checked /usr/adm/amanda/fulldaily/index/pc28/somedir and there is a file named 20030926_0.gz in it, so I suppose the indexfile has been created ok? Does it seem ok? Do a gzmore on the file if you have it, or gunzip 20030926_0.gz | more if you don't. It should start with a list of directory full pathnames starting from the root of the DLE, not the system. The directory entries IIRC end with a / also. This will be followed by the list of files. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: No index records problem
If you cut 07735042527/./ from the line and you tar again the file you'll see that restore works. The resulting line will be: pc28_21092003_03.tar.gz However you have to use the latest tar version to get properly generated index files. -- Stefano Coletta http://www.mindcreations.com Martin wrote: Jon, I have successfully gunzipped the indexfile. Amanda is backing up exactly one directory on the client and that directory contains just one file. Here are the contents of the gunzipped file: 07735043175/./ 07735042527/./pc28_21092003_03.tar.gz The filename above is indeed the file amanda should backup. Does this look like a correct index file? It does to me. Any suggestions? Thanks! Martin On Fri, Sep 26, 2003 at 04:20:11PM +0200, Martin wrote: Hi, I'm having some trouble using amrecover. When I try restoring one particular client's files on the amanda server, amrecover tells me: No index records for disk for specified date If date correct, notify system administrator This results in no files being shown when I do an ls, and so I am not able to recover any files. Strangely, other clients in the same backup-run do not have this problem, only that particular client. The amdump was done without any errors/warnings. Since I am doing the dump to my harddisk in stead of tape, I can actually see the amanda backupfile sitting there, so there's been no error in transfering the data. I checked /usr/adm/amanda/fulldaily/index/pc28/somedir and there is a file named 20030926_0.gz in it, so I suppose the indexfile has been created ok? Does it seem ok? Do a gzmore on the file if you have it, or gunzip 20030926_0.gz | more if you don't. It should start with a list of directory full pathnames starting from the root of the DLE, not the system. The directory entries IIRC end with a / also. This will be followed by the list of files.
Re: No index records problem
On Fri, Sep 26, 2003 at 07:01:42PM +0200, Stefano Coletta wrote: If you cut 07735042527/./ from the line and you tar again the file you'll see that restore works. The resulting line will be: pc28_21092003_03.tar.gz However you have to use the latest tar version to get properly generated index files. This is dredged up from long unused memory cells so may be inaccurate. When I had a similar problem the directory path was lost as well. So everything seemed to be under the root dir. Or something like that. Whatever you do, do not recover back to the original directory structure with that corrupted index, even an edited one. Recover into an empty directory and after checking it seems alright, copy what you want to the locations you want them. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
changing number of index records
How do I change the number of indexes kept, right now my dumpcycle is over a month but only have indexes from the last few days. I would rather keep all the indexes until the tape is overwritten. Or am I missing something? Thanks, Per olof
Re: changing number of index records
On Thu, Aug 21, 2003 at 01:11:04PM +0200, Per olof Ljungmark wrote: How do I change the number of indexes kept, right now my dumpcycle is over a month but only have indexes from the last few days. I would rather keep all the indexes until the tape is overwritten. That is the way my index files are kept, retained until overwritten. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: changing number of index records
Jon LaBadie wrote: On Thu, Aug 21, 2003 at 01:11:04PM +0200, Per olof Ljungmark wrote: How do I change the number of indexes kept, right now my dumpcycle is over a month but only have indexes from the last few days. I would rather keep all the indexes until the tape is overwritten. That is the way my index files are kept, retained until overwritten. Makes me wonder what parameter would change that? I have only three days of indexes in /usr/local/var/amanda/index! Or is it the size of the database that controls it? Anybody that could enlighten me out there? Thanks,
Re: changing number of index records
Jon LaBadie wrote: On Thu, Aug 21, 2003 at 03:39:39PM +0200, Per olof Ljungmark wrote: Jon LaBadie wrote: On Thu, Aug 21, 2003 at 01:11:04PM +0200, Per olof Ljungmark wrote: How do I change the number of indexes kept, right now my dumpcycle is over a month but only have indexes from the last few days. I would rather keep all the indexes until the tape is overwritten. That is the way my index files are kept, retained until overwritten. Makes me wonder what parameter would change that? I have only three days of indexes in /usr/local/var/amanda/index! None I've ever heard of. Other than the obvious tapecycle/dumpcycle/runtapes settings. Are they the most recent? Do they change daily? What are the the timestamps on the directories containing the index files? The ls -ld and ls -ldc timestamps should show when changes were made to the directory contents (files added or removed). Are these different than the times of your dumps? I'd be looking at some outside factor as well as some amanda facility. Like maybe a crontab entry that is getting rid of the index files older than 'xxx'. I do something like that to maintain the /tmp/amanda debug directory differently than amanda wants to maintain it. Well, I've got: dumpcycle 4 weeks runspercycle 20 tapecycle 23 tapes The timestamps appears to be in sync with backups. I'm trying to understand your last paragraph, are the index files in /usr/local/var/amanda/ dependant on /tmp/amanda? If that is the case that is probably the reason. Can one set the age of the /tmp/amanda entries as well? Thanks again!
Re: changing number of index records
On Thu, Aug 21, 2003 at 08:43:59PM +0200, Per olof Ljungmark wrote: Jon LaBadie wrote: On Thu, Aug 21, 2003 at 03:39:39PM +0200, Per olof Ljungmark wrote: I'm trying to understand your last paragraph, are the index files in /usr/local/var/amanda/ dependant on /tmp/amanda? If that is the case that is probably the reason. I just meant I run a cron job daily to collect one days' worth of the debug files into a dated directory and remove any dated directory older than 30 days. That is not a builtin amanda facility. Something similar 'might' be doing nasty things to your index files. Are they the most recent? Do they change daily? What were the answers to these queries? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: changing number of index records
I just meant I run a cron job daily to collect one days' worth of the debug files into a dated directory and remove any dated directory older than 30 days. That is not a builtin amanda facility. Something similar 'might' be doing nasty things to your index files. Are they the most recent? Yes. Do they change daily? Yes. I do have a cron job that occasionally clears /tmp but much more infrequent than every three days. However, this machine does other housekeeping activities so it may be that I configured another script or program to clear out things. I'll keep an eye on that from now, it seems that this is the most likely reason. /per olof
Copying index records
We're happily using Amanda with a bunch of IDE disks giving us about 3 months worth of backups. But now the boss has taken a notion to do monthly archive backups of certain filesystems too. That's OK - I've a DDS3 in the backup box, and that should be just big enough to backup what I need to archive, and setting up a config for level 0 only should be OK - already do that for our offsite backups. BUT i would like, if it's not TOO troublesome, to be able to archive the files which I currently have in the regular rotation. So I'd take the backup files which are on the disks and put them on tape, and put the index records from the daily config into the archive config. But how do I do that, or is there any reasonable way ? I thought amadmin import/export might be what I wanted, but that's only the curinfo records. All thoughts welcome, Niall
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
amrecover: No index records for disk for specified date
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 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? # amrecover ks AMRECOVER Version 2.4.3. Contacting server on localhost ... 220 praha AMANDA index server (2.4.3) ready. 200 Access OK Setting restore date to today (2003-02-11) 200 Working date set to 2003-02-11. 200 Config set to ks. 501 No index records for host: praha. Invalid? Trying host praha.kscanners.no ... 501 No index records for host: praha.kscanners.no. Invalid? Trying host praha.advim.no ... 501 No index records for host: praha.advim.no. Invalid? Trying host praha ... 501 No index records for host: praha. Invalid? Trying host www ... 501 No index records for host: www. Invalid? Trying host ftp ... 501 No index records for host: ftp. Invalid? Trying host mx ... 501 No index records for host: mx. Invalid? Trying host fileserv ... 200 Dump host set to fileserv. Trying disk /dumps ... Trying disk dks2d11s7 ... Can't determine disk and mount point from $CWD '/dumps/misc/jfo' amrecover setdate 2003-01-31 200 Working date set to 2003-01-31. amrecover sethost mercedes-benz 200 Dump host set to mercedes-benz. amrecover setdisk /usr/people/jfo Scanning /dumps/amanda/hd... 200 Disk set to /usr/people/jfo. No index records for disk for specified date If date correct, notify system administrator # tail -f amindexd.20030211172336.debug amindexd: time 0.752: HOST ftp amindexd: time 0.753: 501 No index records for host: ftp. Invalid? amindexd: time 0.953: HOST mx amindexd: time 0.953: 501 No index records for host: mx. Invalid? amindexd: time 1.153: HOST fileserv amindexd: time 1.154: 200 Dump host set to fileserv. amindexd: time 1.355: DISK /dumps amindexd: time 1.356: 501 No index records for disk: /dumps. Invalid? amindexd: time 1.555: DISK dks2d11s7 amindexd: time 1.556: 501 No index records for disk: dks2d11s7. Invalid? amindexd: time 16.563: DATE 2003-01-31 amindexd: time 16.563: 200 Working date set to 2003-01-31. amindexd: time 37.592: HOST mercedes-benz amindexd: time 37.593: 200 Dump host set to mercedes-benz. amindexd: time 53.566: DISK /usr/people/jfo amindexd: time 53.567: 200 Disk set to /usr/people/jfo. amindexd: time 53.568: OISD / amindexd: time 53.568: 500 No dumps available on or before date 2003-01-31 amindexd: time 118.826: QUIT amindexd: time 118.827: 200 Good bye. amindexd: time 118.827: pid 47431195 finish time Tue Feb 11 17:25:35 2003 # tail amrecover.20030211172336.debug guess_disk: 6: 9: /scanner2: /dev/xlv/stripedvol3 guess_disk: 6: 6: /dumps: /dev/dsk/dks2d11s7 guess_disk: 6: 3: /u2: /dev/dsk/dks2d14s7 guess_disk: 6: 14: /usr/doc-linux: linuxdoc:/usr/share/doc guess_disk: 6: 15: /var/www-server: localhost:/var/www guess_disk: 6: 8: /imgproc: raid1:/imgproc guess_disk: 6: 9: /imgproc2: imgproc:/imgproc2 guess_disk: 6: 9: /imgproc3: imgproc:/imgproc3 guess_disk: 6: 9: /scanner4: raid2:/scanner4 amrecover: pid 48822211 finish time Tue Feb 11 17:25:35 2003 -- Toralf Lund [EMAIL PROTECTED] +47 66 85 51 22 ProCaptura AS +47 66 85 51 00 (switchboard) http://www.procaptura.com/~toralf +47 66 85 51 01 (fax)
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: Cannot connect, then No index records for host
amrecover setdisk /data 501 No index records for disk: /data. Invalid? Nope, doesn't work. You disklist entry is exactly /data? Well, I simplified things a bit, in addition to naming the server foo. It's actually: % grep data /usr/local/etc/amanda/Daily/disklist foo /data/mm5_uw/calmm5 my-low-tar but I don't see how that's any different. You're setting configname properly on the amrecover command line? Yes: I'm using amrecover -C Daily -s foo -t foo. Interestingly, if I substitute the IP address of foo: amrecover -C Daily -s 10.26.21.151 -t 10.26.21.151, I get the following: % amrecover -C Daily -s 10.26.21.151 -t 10.26.21.151 AMRECOVER Version 2.4.2p2. Contacting server on 10.26.21.151 ... amrecover: Unexpected server end of file The amrecover.*.debug file contains amrecover: debug 1 pid 16657 ruid 0 euid 0 start time Mon Jan 13 13:48:58 2003 amrecover: stream_client: connected to 10.26.21.151.10082 amrecover: stream_client: our side is 0.0.0.0.859 and the amindexd.*.debug file contains amindexd: debug 1 pid 16658 ruid 507 euid 507 start time Mon Jan 13 13:48:58 200 3 amindexd: version 2.4.2p2 gethostbyaddr: Success amindexd: pid 16658 finish time Mon Jan 13 13:48:58 2003 If I use the name (not the IP) I get amrecover: stream_client: connected to 127.0.0.1.10082 in the amrecover.*.debug file. This is because of my admittedly odd /etc/hosts file (see below). You've checked the amindexd...debug logs on the server? It looks almost the same, but you may be on to something here. When I cd to /data/mm5_uw/calmm5 and start amrecover, I see this in the debug log: amindexd: debug 1 pid 16629 ruid 507 euid 507 start time Mon Jan 13 13:42:49 200 3 amindexd: version 2.4.2p2 220 foo AMANDA index server (2.4.2p2) ready. SECURITY USER root bsd security: remote host foo.bar.com user root local user amanda amandahosts security check passed 200 Access OK DATE 2003-01-13 200 Working date set to 2003-01-13. SCNF Daily 200 Config set to Daily. HOST foo.bar.com 501 No index records for host: foo.bar.com. Invalid? HOST foo.bar.com 501 No index records for host: foo.bar.com. Invalid? HOST localhost.localdomain 501 No index records for host: localhost.localdomain. Invalid? HOST localhost 501 No index records for host: localhost. Invalid? HOST foo 200 Dump host set to foo. DISK /data 501 No index records for disk: /data. Invalid? DISK sdb1 501 No index records for disk: sdb1. Invalid? That is, I was in /data/mm5_uw/calmm5, but it tried to start in /data! However, doing a setdisk /data/mm5_uw/calmm5 produces the same result (appended to the debug file): DISK /data/mm5_uw/calmm5/ 501 No index records for disk: /data/mm5_uw/calmm5/. Invalid? Setting the date to last Friday (using setdate) doesn't help. Any ideas on why it went to /data instead of /data/mm5_uw/calmm5? You can do something like: % gzcat .../Daily/index/foo/_data/20030112_0.gz and get what you expect? % zcat /var/lib/amanda/Daily/index/foo/_data_mm5__uw_calmm5/20030110_3.gz has a list of file that were backed up on Friday night's run, as expected. You don't have your disklist host field set to localhost, do you? No. I suppose it could be a problem with the indexdir in amanda.conf; there's no way you could be reading multiple amanda.conf files, is there? I don't think so: % grep indexdir /usr/local/etc/amanda/Daily/amanda.conf indexdir /var/lib/amanda/Daily/index # index directory % amgetconf Daily indexdir /var/lib/amanda/Daily/index It sounds like *some* kind of mismatch in host name between disklist, /etc/hosts, DNS, nsswitch.conf, etc. My thoughts exactly. That's why I included the info about my /etc/hosts file and its oddities. If I change from 127.0.0.1 foo.bar.com localhost.localdomain localhost foo #10.26.21.151 foo.bar.com foo to 127.0.0.1 localhost.localdomain localhost 10.26.21.151foo.bar.com foo then I break OpenPBS, so I'd like to avoid that. Either that, or I should recompile all of OpenPBS with the new /etc/hosts file. I'm not sure how that would work, since the slave nodes know the head node not at 10.26.21.151, but as 192.168.3.1, which isn't mentioned in /etc/hosts at all. Any hints (or better yet specific command lines) that I can use to figure out which IP address my machine thinks it is? Does amanda do a reverse-lookup that might be failing? nslookup queries the local DNS server (a WinNT Server box), not /etc/hosts. Keep in mind I have 2 NIC cards, one public and one private for the slave nodes in the cluster. Also, note that trying amrestore from another amanda client produced the same result. That box knows nothing about the private NIC card. I did try to switch to the 2nd form of the /etc/hosts file, and recompiled amanda, with the same results. It seems to be something completely different. Thanks for all your help, Bart -- Bart Brashers MFG Inc. Air Quality Meteorologist
RE: Amrecover: Cannot connect, then No index records for host
However, doing a setdisk /data/mm5_uw/calmm5 produces the same result (appended to the debug file): DISK /data/mm5_uw/calmm5/ 501 No index records for disk: /data/mm5_uw/calmm5/. Invalid? Bingo (maybe!). I think you did: amrecover setdisk /data/mm5_uw/calmm5/ and you needed to do: amrecover setdisk /data/mm5_uw/calmm5 If we're lucky, it's just a trailing / in your setdisk command. That was indeed the problem! Leaving off the trailing / makes setdisk commands work, and by using settime I can get listings of the files available on my various tapes. I use tcsh, and use the TAB key to autocomplete path/filenames all the time, including on this command line (amrecover /da[TAB]mm[TAB]/ca[TAB]). I note that TAB also autocompletes from the amrecover prompt as well, and includes the trailing / for you. It's a bummer that (A) such a subtlety completely escaped me. (B) amanda's authors didn't put in a little test for trailing slashes. (C) the handy autocomplete at the amrecover prompt includes the trailing slash, even though amanda doesn't want it. (D) all of the above. Thanks Jay! Bart -- Bart Brashers MFG Inc. Air Quality Meteorologist 19203 36th Ave W Suite 101 [EMAIL PROTECTED]Lynnwood WA 98036-5707 http://www.mfgenv.com 425.921.4000 Fax: 425.921.4040
Amrecover: Cannot connect, then No index records for host
Ok, it appears lots of people successfully use amrecover with indexing, so
here's my sob story...
For the first time ever (after testing during setup, that is) I need to
recover a file from my amanda tapes (Amanda version 2.4.2p2). The same
machine holds the disks, is the amanda server, and is the tape server.
So I become su, cd to the directory listed in my disklist, and type
amrecover (since my default set is Daily). I get:
[root]% amrecover Daily
AMRECOVER Version 2.4.2p2. Contacting server on foo.bar.com ...
amrecover: cannot connect to foo.bar.com: Connection refused
I tried a bunch of things, including re-compiling (my subnet had changed,
thus changing the IPs of the server). After looking closely at the
FAQ-o-matic, I changed /etc/xinetd.d/amandaidx to have wait = no (it was
wait = yes) and restarted xinetd. I've included the above in this email
so other users can find the fix in the archives. This produced better
results:
[root]% amrecover
AMRECOVER Version 2.4.2p2. Contacting server on foo.bar.com ...
220 foo AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2003-01-10)
200 Working date set to 2003-01-10.
200 Config set to Daily.
501 No index records for host: foo.bar.com. Invalid?
Trying foo.bar.com ...
501 No index records for host: foo.bar.com. Invalid?
Trying foo ...
200 Dump host set to foo.
Can't determine disk and mount point from $CWD
And yet the entry in /var/lib/amanda/Daily/index/foo for the directory in
question exists, and has 20030109_3.gz in it from last night's dump. That
file even lists the file I need to recover.
I'm using gtar 1.13.19, so that's ok. I tried amrecover -C Daily -s foo -t
foo, with the same result.
I was able to extract the file I needed by using amrestore (along with a
bunch I didn't, and only on the 2nd identical try). So I'm off the hook for
now, but I feel I should fix this so it's not an issue the next time I need
to restore a file.
I have index yes in the dumptype global, but in one of my dumptypes I
had just index on the line, no yes or no. Could this be the issue? I
don't think so, because the index is there. The files under
/var/lib/amanda/Daily/index/foo are all owned by amanda:disk; dirs have
permissions drwxr-sr-x and files have -rw---, so amanda should be
able to read them all.
The disklist entry:
foo /data my-low-tar
i.e. not the FQDN, just foo. The relevant dumptypes:
define dumptype global {
index yes
record yes
}
define dumptype root-tar {
global
program GNUTAR
compress none
exclude list /usr/local/lib/amanda/exclude.gtar
priority low
}
define dumptype my-low-tar {
root-tar
compress none
priority low
index
}
So the only possibility for things I'm doing wrong I see is using disklist
entries like:
foo.bar.com /data my-low-tar
but the example disklist that comes with the tarball doesn't use FQDNs...
Any hints would be greatly appreciated.
Bart
---
Bart Brashers MFG Inc.
Air Quality Meteorologist 19203 36th Ave W Suite 101
[EMAIL PROTECTED]Lynnwood WA 98036-5707
http://www.mfgenv.com 425.921.4000 Fax: 425.921.4040
RE: Amrecover: Cannot connect, then No index records for host
[root]% amrecover AMRECOVER Version 2.4.2p2. Contacting server on foo.bar.com ... 220 foo AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2003-01-10) 200 Working date set to 2003-01-10. 200 Config set to Daily. 501 No index records for host: foo.bar.com. Invalid? Trying foo.bar.com ... 501 No index records for host: foo.bar.com. Invalid? You backed it up as foo, and you're trying (unintentionally, but nonetheless) to recover it as foo.bar.com, not the same thing. Doing amrecover -s foo -t foo produces the same result. It tries all variations listed in /etc/hosts, and fails with each one. Trying foo ... But that's a frequent mistake, so it tries to Do What You Mean. It's just trying the alias in /etc/hosts. 200 Dump host set to foo. And that works. No, index records were never found. A Dump host was found, but no index records. Can't determine disk and mount point from $CWD So it's ready to go now, I think, but you haven't told it what you want: setdisk /whatever amrecover setdisk /data 501 No index records for disk: /data. Invalid? Nope, doesn't work. Bart --- Bart BrashersMFG Inc. Air Quality Meteorologist19203 36th Ave W Suite 101 [EMAIL PROTECTED]Lynnwood WA 98036-5707 http://www.mfgenv.com 425.921.4000 Fax: 425.921.4040
Re: No index records for host
--On Friday, January 03, 2003 22:18:18 -0500 John R. Jackson [EMAIL PROTECTED] wrote: Is there a reason indexing isn't on by default? They don't really take up that much space ... I beg to differ: $ du -sk /var/amanda/index/champion 4641743 /var/amanda/index/champion Yup. Four and a half *GBytes*. Now, granted, this is on a very large Amanda configuration. But it's not peanuts even in my small configs. OK, size is a relative thing. If all you back up is a 9 gig disk then 4,5 G would be huge, if you are backing up terabytes then it is just dust. I would still guess that as a percentage of total disk backed up it is a relatively small number, unless you have an unusually high percentage of your disk occupied by tiny files. ... and recovery is an all or nothing deal without them. ... Not at all, although it depends on how things are set up. Using dump (instead of GNU tar) provides a fairly easy to manage shell to pick and choose what to restore. Knowing which tapes are needed might be an issue -- it depends on the restore scenerio. But dump limits you to filesystems smaller than your tape since Amanda won't span tapes on a single DLE. So those of us that prefer larger filesystems are forced to use GNU tar, and indexes make restoring with tar much simpler. Just curious as why some of the defaults are the way they are. Ah, now that's a completely different question :-). The answer, as is often the case, is because it's always been that way. Changing the default could be a *big* surprise to folks who upgrade. Like suddenly making the existance of a listed exclude file required in 2.4.3 when it used to be optional? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: No index records for host
On Saturday 04 January 2003 03:03, Frank Smith wrote: --On Friday, January 03, 2003 22:18:18 -0500 John R. Jackson [EMAIL PROTECTED] wrote: Is there a reason indexing isn't on by default? They don't really take up that much space ... I beg to differ: $ du -sk /var/amanda/index/champion 4641743 /var/amanda/index/champion Yup. Four and a half *GBytes*. Wow, here its maybe 50 megs [...] Just curious as why some of the defaults are the way they are. Ah, now that's a completely different question :-). The answer, as is often the case, is because it's always been that way. Changing the default could be a *big* surprise to folks who upgrade. Like suddenly making the existance of a listed exclude file required in 2.4.3 when it used to be optional? Frank I just got curious, and commented that line out of the dumptype, then removed the empty, made by touch file. amcheck didn't notice. == #amanda@coyote DailySet1]$ amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /dumps: 32758100 KB disk space available, using 27638100 KB amcheck-server: slot 0: date 20021209 label DailySet1-23 (exact label match) NOTE: skipping tape-writable test Tape DailySet1-23 label ok Server check took 13.840 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.091 seconds, 0 problems found (brought to you by Amanda 2.4.3-20030102) = So its apparently only needed if you specify it. Putting the line back in gets me 36 errors because there are 36 entries in the disklist that include that dumptype. Since the error can be treated with a touch of the specified file, or a comment in front of it in the dumptype, it doesn't seem like a real problem. Even when it was optional, I think I can recall it was a problem for tar if it was passed as argument but didn't exist. So makeing it an ERROR to amcheck does seem to make a wee bit of sense from this users viewpoint. But I honestly can't say when that change was made. I build them and put them in service when Jean-Louis puts up a fresh 2.4.3 snapshot, so that was probably many installs back up the log now. Its in the Changelog maybe? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.21% setiathome rank, not too shabby for a WV hillbilly
Re: No index records for host
On Sat, Jan 04, 2003 at 04:55:37AM -0500, Gene Heskett wrote: On Saturday 04 January 2003 03:03, Frank Smith wrote: --On Friday, January 03, 2003 22:18:18 -0500 John R. Jackson [EMAIL PROTECTED] wrote: [...] Just curious as why some of the defaults are the way they are. Ah, now that's a completely different question :-). The answer, as is often the case, is because it's always been that way. Changing the default could be a *big* surprise to folks who upgrade. Like suddenly making the existance of a listed exclude file required in 2.4.3 when it used to be optional? Frank I just got curious, and commented that line out of the dumptype, then removed the empty, made by touch file. amcheck didn't notice. [[ snip ]] So its apparently only needed if you specify it. Putting the line back in gets me 36 errors because there are 36 entries in the disklist that include that dumptype. Since the error can be treated with a touch of the specified file, or a comment in front of it in the dumptype, it doesn't seem like a real problem. Even when it was optional, I think I can recall it was a problem for tar if it was passed as argument but didn't exist. So makeing it an ERROR to amcheck does seem to make a wee bit of sense from this users viewpoint. But I honestly can't say when that change was made. Some more data points from a 2.4.2 user. The exclude list option is defined in the root-tar dumptype in both 2.4.2 and 2.4.3. So no change there. No surprises for anyone. amcheck in my installation (2.4.2) does not complain if the exclude file is missing. It does in 2.4.3. That could be a surprise to a user. However gtar complains and aborts the backup if the exclude file is missing. That would be a real big surprise and disappointment!! Seems to me, as Gene points out, this new check is a GOOD THING. It may notify you of a backup that will fail. Don't knock the change, appreciate it. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: No index records for host
On Sat, Jan 04, 2003 at 12:21:44PM -0500, Jon LaBadie wrote: Some more data points from a 2.4.2 user. The exclude list option is defined in the root-tar dumptype in both 2.4.2 and 2.4.3. So no change there. No surprises for anyone. amcheck in my installation (2.4.2) does not complain if the exclude file is missing. It does in 2.4.3. That could be a surprise to a user. It was... However gtar complains and aborts the backup if the exclude file is missing. That would be a real big surprise and disappointment!! Again, it was :-) -- 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: No index records for host
Is there a reason indexing isn't on by default? They don't really take up that much space ... I beg to differ: $ du -sk /var/amanda/index/champion 4641743 /var/amanda/index/champion Yup. Four and a half *GBytes*. Now, granted, this is on a very large Amanda configuration. But it's not peanuts even in my small configs. ... and recovery is an all or nothing deal without them. ... Not at all, although it depends on how things are set up. Using dump (instead of GNU tar) provides a fairly easy to manage shell to pick and choose what to restore. Knowing which tapes are needed might be an issue -- it depends on the restore scenerio. Just curious as why some of the defaults are the way they are. Ah, now that's a completely different question :-). The answer, as is often the case, is because it's always been that way. Changing the default could be a *big* surprise to folks who upgrade. Frank John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
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
No index records for host
[root@backup DailySet1]# 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-19) 200 Working date set to 2002-12-19. 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? amrecover quit 200 Good bye. Googling for help on this, I found several posts that indicate that index yes needs to be in the dumptype in amanda.conf But, if this is so, why isn't it already in there? Or is it possible that something else is really the issue? -- 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: No index records for host
In order to have indexing on your backups, you must specify 'index yes'
inside of the backup type in amanda .conf. ie:
define dumptype nocomp-user {
comp-user
comment Whatever comment you want
compress client fast
priority medium
index yes
}
The next backups using your dumptype with index yes inserted will be
indexed for amrecover.
Steve Bertrand
John Oliver wrote:
[root@backup DailySet1]# 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-19)
200 Working date set to 2002-12-19.
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?
amrecover quit
200 Good bye.
Googling for help on this, I found several posts that indicate that
index yes needs to be in the dumptype in amanda.conf But, if this is
so, why isn't it already in there? Or is it possible that something
else is really the issue?
Re: No index records for host
--On Thursday, December 19, 2002 18:53:44 -0500 Steve Bertrand [EMAIL PROTECTED] wrote:
In order to have indexing on your backups, you must specify 'index yes' inside of the backup type in amanda .conf. ie:
define dumptype nocomp-user {
comp-user
comment Whatever comment you want
compress client fast
priority medium
index yes
}
The next backups using your dumptype with index yes inserted will be indexed for amrecover.
Steve Bertrand
Is there a reason indexing isn't on by default? They don't really take up
that much space, and recovery is an all or nothing deal without them. Just
curious as why some of the defaults are the way they are.
Frank
--
Frank Smith [EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: No index records for host
On Thu, Dec 19, 2002 at 06:53:44PM -0500, Steve Bertrand wrote:
In order to have indexing on your backups, you must specify 'index yes'
inside of the backup type in amanda .conf. ie:
define dumptype nocomp-user {
comp-user
comment Whatever comment you want
compress client fast
priority medium
index yes
}
Why does the conf file come without index yes in it already?
--
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: 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]
amrecover: No index records for disk for specified date
Hello, I know this problem is described in FAQ-O-MATIC section , but it didn't help. I also searched google couple of days, still haven't found an answer. My configuration is called test. In amanda.conf I have these entries: infofile /usr/local/etc/amanda/test/curinfo# database DIRECTORY logdir /usr/local/etc/amanda/test/log # log directory indexdir /usr/local/etc/amanda/test/index # index directory In dumptype there is entry index yes, and when doing backup I get zipped index file in directory $indexdir/host/_mountpoint/ . For example, 20020527_0.gz Everything seems ok, but when runing amrecover I get 200 Working date set to 2002-05-27. 200 Config set to test. 200 Dump host set to sunny.5ci.lt. Trying disk /usr ... $CWD '/usr/home/simas' is on disk '/usr' mounted at '/usr'. Scanning /usr/amanda... 200 Disk set to /usr. No index records for disk for specified date If date correct, notify system administrator Runing history on amrecover prompt gives empty list for disk... Also I tried compiling amanda without gnutar support, but it didn't help either. Amanda is runing on FreeBSD 4.5-RELEASE-p4, amanda's version - 2.4.3b2. Any ideas? Simas Cepaitis [EMAIL PROTECTED]
No index records
Hi,
I started to use amanda since last week .
My amanda server host name is "bakubak" .
My amanda client host name is "mailde" .
I could get remote client "mailde" backup .
The log file is following..
START driver date 20020218
START planner date 20020218
WARNING planner Last full dump of mailde:/ on tape overwritten in 1 run.
FINISH planner date 20020218
STATS driver startup time 0.488
START taper datestamp 20020218 label DailySet10 tape 0
SUCCESS dumper mailde / 20020218 0 [sec 38.255 kb 74336 kps 1943.1 orig-kb
74330]
SUCCESS taper mailde / 20020218 0 [sec 91.759 kb 74368 kps 810.5 {wr:
writers 2324 rdwait 0.000 wrwai
t 81.280 filemark 9.842}]
INFO taper tape DailySet10 kb 74368 fm 1 [OK]
FINISH driver date 20020218 time 149.664
I am getting error such as the following. when I executed amrecover command
.
[root@bakubak mailde]# amrecover mailde
AMRECOVER Version 2.4.2p2. Contacting server on bakubak ...
220 bakubak AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2002-02-18)
200 Working date set to 2002-02-18.
200 Config set to mailde.
501 No index records for host: bakubak. Invalid?
Trying bakubak ...
501 No index records for host: bakubak. Invalid?
Trying bakubak ...
501 No index records for host: bakubak. Invalid?
amrecover
Now, I can not access remote client "mailde" backup data.
My disklist and amanda.conf include the following line .
disklist file:
mailde / root-tar
amanda.conf file:
indexdir "/usr/local/etc/amanda/mailde/index"
define dumptype global {
comment "Global definitions"
index yes
}
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index yes
exclude list "/usr/local/lib/amanda/exclude.gtar"
priority low
}
Why am I getting "No index records for host" ?
What value should I include "/usr/local/lib/amanda/exclude.gtar" file ?
How is it recoverable if backup data carries out?
Best regards,
Masafumi Hikawa
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
amrecover: No index records for host?
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
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
SOLUTION FOUND for No index records for host...
Hello, Can someone please update the FAQ under Troubleshooting, amrecover: For the following errors: 501 No index records for host: 500 No dumps available on or before date Further to what the FAQ says is to get back to basics and set the permissions correctly on the holding disk, so that amanda can read the files. (eg chown -R amanda.amanda /holdingDisk) So easy yet so fustrating. Thanks to all who offered suggestions. 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
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
amrecover: No index records for host?
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
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/
Re: No index records for host on date xxxxx
On 8 Sep 2001 at 12:23pm, Dan Smith wrote OK, the server that runs the amanda stuff is what gets backed up. I added another host to the list, flare:/etc. It seems to backup fine; I get a size and time and everything in the email reports. When I run amrecover, I can sethost and setdisk, but there is no index records for the host on any backup date. The other machine is solaris 8. The amanda box is Linux. If I look in daily/index/flare/_etc, there are .gz files for all the dates. What are you using to backup flare? If tar, what version? Do the contents of the index files look right? What version(s) of amanda? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
No index records for host on date xxxxx
OK, the server that runs the amanda stuff is what gets backed up. I added another host to the list, flare:/etc. It seems to backup fine; I get a size and time and everything in the email reports. When I run amrecover, I can sethost and setdisk, but there is no index records for the host on any backup date. The other machine is solaris 8. The amanda box is Linux. If I look in daily/index/flare/_etc, there are .gz files for all the dates. Can someone help me diagnose this? --Dan
AMRECOVER-No index records for disk for specified date
I have just installed Amanda 2.4.2p1 on SuSE 7.0. I have troubles with
AMRECOVER.
I am sure, that my index file is:
/etc/amanda/csd/index/linux1/_dev_ida_c0d0p4/20010314_0.gz
-
When I write in AMRECOVER :
amrecover setdisk /dev/ida/c0d0p4
Scanning /var/amanda...
200 Disk set to /dev/ida/c0d0p4.
No index records for disk for specified date
If date correct, notify system administrator
-
When I write wilfully incorrect:
amrecover setdisk /dev/ida/c0d0p5
501 No index records for disk: /dev/ida/c0d0p5. Invalid?
-
I conclude, that I can correctly reach directory, but cannot reach index
file.
cat /tmp/amanda/amindexd.debug gives:
amindexd: debug 1 pid 16111 ruid 37 euid 37 start time Mon Mar 19 13:03:12
2001
amindexd: version 2.4.2p1
220 linux1 AMANDA index server (2.4.2p1) ready.
SECURITY USER root
bsd security: remote host linux1.local user root local user amanda
amandahosts security check passed
200 Access OK
DATE 2001-03-19
200 Working date set to 2001-03-19.
SCNF csd
200 Config set to csd.
HOST linux1
200 Dump host set to linux1.
DISK /
501 No index records for disk: /. Invalid?
DISK root
501 No index records for disk: root. Invalid?
DISK /dev/ida/c0d0p4
200 Disk set to /dev/ida/c0d0p4.
OISD /
500 No dumps available on or before date "2001-03-19"
OISD /
500 No dumps available on or before date "2001-03-19"
DISK /dev/ida/c0d0p5
501 No index records for disk: /dev/ida/c0d0p5. Invalid?
DISK /dev/ida/c0d0p4
200 Disk set to /dev/ida/c0d0p4.
OISD /
500 No dumps available on or before date "2001-03-19"
OISD /
500 No dumps available on or before date "2001-03-19"
QUIT
200 Good bye.
If I debug amrecover, in set_commands.c
if (server_happy())
{
suck_dir_list_from_server();
}
else
{ /* Here goes after test in server_happy()*/
printf("No index records for cwd on new date\n");
printf("Setting cwd to mount point\n");
disk_path = newstralloc(disk_path, "/");/* fake it */
clear_dir_list();
}
inside server_happy() I see: server_line[0]=53'5', which is ( I hope) error
code, but what does it mean?.
Do You have any idea ? Thank You in advance.
Martin Novacek
Re: listing files with amrecover - No index records for disk (fwd)
I was not in my root directory when I ran amrecover initially. When I moved to my root directory and then ran amrecover - I was able to view the tree of files/directories via the 'ls' command on my tape. thanks much: amadmin daily disklist cloudy1.com sda6 | grep index index YES -- Forwarded message -- Date: Fri, 23 Feb 2001 19:19:59 -0500 From: John R. Jackson [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Denise Ives [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: listing files with amrecover - No index records for disk 200 Dump host set to cloudy1.com. amrecover ls Must select a disk before listing files amrecover setdisk sda6 501 No index records for disk: sda6. Invalid? First, find your index directory. Is there a directory in it named "cloudy1.com"? Is there a directory in that directory named "sda6"? And finally, are there gzip'd files in there? What do you get for this: amadmin config disklist cloudy1.com sda6 | grep index Does it say you've been gathering index files? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
listing files with amrecover - No index records for disk
I haven't used amrecover in a while. I used to be able to list file with the ls command: #my disklist file cloudy1.com sda6default sunny1.com dsa10 default #running amrecover [root@sunny1 dives]# amrecover -C daily -s sunny1.com -t sunny1.com -d /dev/rmt/0cbn AMRECOVER Version 2.4.1p1. Contacting server on sunny1.com ... 220 sundev1 AMANDA index server (2.4.1p1) ready. 200 Access OK Setting restore date to today (2001-02-23) 200 Working date set to 2001-02-23. 200 Config set to daily. 501 No index records for host: sunny1. Invalid? Trying sunny1.com ... 200 Dump host set to sunny1.com. $CWD '/cloudy1-home/user/dives' is on a network mounted disk so you must 'sethost' to the server amrecover sethost cloudy1 501 No index records for host: cloudy1. Invalid? Trying cloudy1.com ... 200 Dump host set to cloudy1.com. amrecover ls Must select a disk before listing files amrecover setdisk sda6 501 No index records for disk: sda6. Invalid?
