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
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
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
[ ... ]
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. The
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
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.
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
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.
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
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!
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
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
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
19 matches
Mail list logo
