Hello Jean-Louis,

Thanks for the reply.

The output of 'amadmin <config_name> find' is as follows:

$ amadmin fullback find
Warning: no log files found for tape FULLBACK-19 written 2012-03-12
Warning: no log files found for tape FULLBACK-05 written 2012-02-07
Warning: no log files found for tape FULLBACK-18 written 2012-01-13
Warning: no log files found for tape FULLBACK-17 written 2011-12-09
Warning: no log files found for tape FULLBACK-16 written 2011-11-04
Warning: no log files found for tape FULLBACK-01 written 2011-09-30
Warning: no log files found for tape FULLBACK-15 written 2011-08-31
Warning: no log files found for tape FULLBACK-11 written 2011-08-01
Warning: no log files found for tape FULLBACK-10 written 2011-06-30
Warning: no log files found for tape FULLBACK-08 written 2011-06-02
Warning: no log files found for tape FULLBACK-07 written 2011-05-02
Warning: no log files found for tape FULLBACK-04 written 2011-04-12
Warning: no log files found for tape FULLBACK-14 written 2011-04-06
Warning: no log files found for tape FULLBACK-06 written 2011-04-06
Warning: no log files found for tape FULLBACK-03 written 2011-03-03
Warning: no log files found for tape FULLBACK-02 written 2010-12-14
Warning: no log files found for tape FULLBACK-13 written 2009-12-02
Warning: no log files found for tape FULLBACK-12 written 2008-08-05
Warning: no log files found for tape FULLBACK-09 written 2007-10-31

No dump to list

Yes the tapelist file does list all the tapes.
I don't have the log.<datestamp>.* files

The 'amcheck -s <config_name>' prints something similar to what is given below:

$ amcheck -s <config_name>
"/etc/amanda/<config_name>/amanda.conf", line 82: warning: Keyword tapebufs is 
deprecated.
Amanda Tape Server Host Check
-----------------------------
Holding disk /var/tmp/amanda: 122302464 KB disk space available, using 5120000 
KB as requested
read label `<config_name>-15', date `20120214'.
NOTE: skipping tape-writable test
Tape <config_name>-15 label ok
Server check took 0.210 seconds

(brought to you by Amanda 2.6.1p2)

Thanks in advance,
Yogesh



________________________________
 From: Jean-Louis Martineau <[email protected]>
To: Yogesh Hasabnis <[email protected]> 
Cc: "[email protected]" <[email protected]> 
Sent: Monday, April 2, 2012 6:29 PM
Subject: Re: amrecover problem with amanda 2.6.1p2
 
Do 'amadmin <config_name> find' list all dump?
Do the tapelist file list all tapes?
Do you have all the log.<datestamp>.* files?

Do 'amcheck -s <config_name>' print errors or warnings?

Jean-Louis

On 04/02/2012 06:36 AM, Yogesh Hasabnis wrote:
> Hi All,
> 
> Our AMANDA backup configuration consisted of AMANDA 2.5.2p1 on RHEL3 as the 
> backup server and AMANDA 2.6.1p2 on RHEL6 as the AMANDA client. Recently,the 
> RHEL 3 OS on amanda backup server crashed for some reason and I had to 
> install RHEL 5.5 OS on it. I had backed up my original amanda configuration 
> directories under /etc/amanda and also the contents of the /var/lib/amanda 
> directory which contained the index data, before the OS reinstallation. I 
> have installed AMANDA 2.6.1p2 on this new OS on the backup server and 
> reconfigured it. I have also copied the directories containing the index data 
> under the appropriate directories (/var/lib/amanda).
> 
> Now when I try to use the command (from my AMANDA client)
> 
> # amrecover -C <config_name> -s <index_server> -t <tape_server>
> 
> and use the proper "sethost", "setdisk" and "setdate" commands, I get the 
> error "No index records for disk for specified date".   The contents of the 
> amindexd*.debug under the /var/log/amanda/server/<config> are roughly as 
> follows:
> 
> 1333357832.225922: amindexd: > DATE 2012-04-02
> 1333357832.226013: amindexd: < 200 Working date set to 2012-04-02.
> 1333357832.226299: amindexd: > OISD /
> 1333357832.226341: amindexd: < 500 No dumps available on or before date 
> "2012-04-02"
> 
> Kindly suggest about what needs to be done to make the amrecover command work.
> 
> Thanks in advance,
> Yogesh Hasabnsi

Reply via email to