On Tue, 4 Feb 2014 13:12:49 +0100
Heiko Schlittermann 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 unsubsc
Saša Janiška (Di 04 Feb 2014 12:51:01 CET):
> On Tue, 4 Feb 2014 11:48:44 +0100
> Heiko Schlittermann wrote:
>
> > The directory reported by
> >
> > amgetconf INDEXDIR
> >
> > should contain folders named according the DLEs you backed up.
> > (With some substitutions for '/')
>
> gour
On Tue, 4 Feb 2014 11:48:44 +0100
Heiko Schlittermann wrote:
> The directory reported by
>
> amgetconf INDEXDIR
>
> should contain folders named according the DLEs you backed up.
> (With some substitutions for '/')
gour atmarama ~ $ amgetconf backup INDEXDIR
/var/db/amanda/state/in
Saša Janiška (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 s
On Thu, 30 Jan 2014 08:42:51 -0500
Jean-Louis Martineau 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
On Thu, Jan 30, 2014 at 2:42 PM, Jean-Louis Martineau
wrote:
> 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 '
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
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/aman
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
logd
00 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 adm
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.
.
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 spe
ort/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/
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 ”, I still got the same error”no 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
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 Febru
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.
st 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 adminis
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 rest
Mike Delaney wrote:
> On Sun, Oct 17, 2004 at 10:25:17PM -0400, Joe Konecny wrote:
>
>>
>>
>> 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 m
On Sun, Oct 17, 2004 at 10:25:17PM -0400, Joe Konecny wrote:
>
>
> 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
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.
thing. 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
stalled 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 contain
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
--- 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> histor
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 f
ontacting server on
localhost ...
220 Linx AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-10-10)
200 Working date set to 2003-10-10.
200 Config set to normal.
501 No index records for host: Linx. Invalid?
Trying host Linx ...
501 No index records
quot; with lowercase ell.
Sector Unknown wrote in a previous mail:
[EMAIL PROTECTED] amanda]# less amindexd.20031009154918.debug
...
amindexd: time 0.115: > HOST Linx
amindexd: time 0.115: < 501 No index records for host:
Linx. Invalid?
But your host seems to be named with an uppercase "L
--- Paul Bijnens <[EMAIL PROTECTED]> wrote:
> Date: Fri, 10 Oct 2003 15:09:47 +0200
> From: Paul Bijnens <[EMAIL PROTECTED]>
> To: Sector Unknown <[EMAIL PROTECTED]>
> Subject: Re: Fwd: Re: amrecover - No index records
>
>
> Any useful message in the deb
I'm currently using tar 1.13.25.
---
Message: 19
Date: Fri, 10 Oct 2003 10:04:47 +0200
From: "Martin" <[EMAIL PROTECTED]>
Subject: Re: amrecover - No index records
Hi,
I had the same problem a little while ago and it
seemed I was using a
--- Paul Bijnens <[EMAIL PROTECTED]> wrote:
> Date: Fri, 10 Oct 2003 10:12:02 +0200
> From: Paul Bijnens <[EMAIL PROTECTED]>
> To: C Hardee <[EMAIL PROTECTED]>
> Subject: Re: amrecover - No index records
>
> C Hardee wrote:
>
> > I am running Amanda
x 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
>
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
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
> > fil
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
;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 d
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
>
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, ver
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_111
27;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.
> &g
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 dateIf
date correct, notify system administrator
This results in no files being shown when I do an
[ ... ]
> >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 pe
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
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
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 messag
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 debu
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/
> > 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!).
>
> > 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
> > [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 Con
g 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
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 compl
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.
> >>
> >
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/amand
--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
>
>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
no
On Thursday 02 January 2003 10:29, Gene Heskett wrote:
What is this, is there an echo in here?
>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 Mo
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 am
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 pro
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 b
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
dy.
> > 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 re
On Tue, Dec 31, 2002 at 02:50:31AM -0500, Mitch Collinsworth wrote:
>
> 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.
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.
> [r
gt;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: bac
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
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
o 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 h
[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
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 cli
--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"
day (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?
ate 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. Inval
[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
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 wa
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 in
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
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 corr
ohn 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 followi
-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 d
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 rat
rectory
$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
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 ...
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
tent
> > 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?
> >
> >
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
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
y 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 t
> > > 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 J
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 t
xtent
> 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.
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 1
x
> 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 i
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
> t
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:
> > ...
>
ble. 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:
>
>
ee 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 s
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
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
1 - 100 of 106 matches
Mail list logo
