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
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
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
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
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
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
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
.
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
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
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
/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
.
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
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
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
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
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.
--
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
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.
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
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
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.
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
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
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
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
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
--- 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
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
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
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
, 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
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/./
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,
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
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
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
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
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
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
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
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
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.
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
[ ... ]
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
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
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
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
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
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
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
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
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
[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
--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
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
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
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
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
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
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
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
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
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
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
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
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
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
[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
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
--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
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
-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
. 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
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
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
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
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
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
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
ilde
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 ...
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
.
--- 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
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
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
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
[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
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
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
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
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
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
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
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
, 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
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
/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
-- 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
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
98 matches
Mail list logo
