Amanda-Users

Re: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header

2004-08-25 05:58:21
Subject: Re: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header
From: Paul Bijnens <paul.bijnens AT xplanation DOT com>
To: Ranveer Attalia <Ranveer.Attalia AT tertio DOT com>
Date: Wed, 25 Aug 2004 11:46:00 +0200
Ranveer Attalia wrote:

SOrry about this, but I'm having a nightmare I attempted the amrecover
again last night on a file and it worked. I took the tapes out of the drive and put in the daily incremental tapes
and hashed out the server that failed so it doesnt attempt to back it
up.

However, this morning I have tried to do a amrestore but when I run an
amadmin Weekly telhp6 /opt it is telling me its not a dump list (what
does this mean? nothing has changed on the tapes since last night!!)

"No dump to list" (real error message) has a different meaning than
"not a dump list" (what you seem to be reading).  It means that amadmin
is unable to find information about any dumps (== "backups").

And that's because:


AMANDA SERVER:
$  amadmin Weekly find telhp6
Warning: no log files found for tape Fri4.1 written 2004-04-23
Warning: no log files found for tape Mar0.1 written 2004-03-28
Warning: no log files found for tape Weekly5 written 2004-02-28
Warning: no log files found for tape Weekly4 written 2004-02-14
Warning: no log files found for tape Weekly3 written 2004-02-07
Warning: no log files found for tape Weekly2 written 2004-01-30
Warning: no log files found for tape Weekly1 written 2004-01-23 Scanning
/amanda...
Scanning /amanda1...

No dump to list
$

Yes, that's because the log files are gone.  And the log files are
what "amadmin find" uses go find out which tape contains what :-)

Don't remove the log files!

The lucky thing is that amanda does not DEPEND on the log files
to be able to restore anything.  It just becomes a little less
easy.


$mtx load 1
$ amtape Weekly current
amtape: scanning current slot in tape-changer rack:
slot 2: date 20040820 label Fri3.2
$ mt -f /dev/rmt/1ubn rew

AMANDA CLIENT:
#remsh tsssun1 -l amanda -n /opt/amanda/sbin/amrestore -p /dev/rmt/1ubn
telhp6 /opt | restore rbf 2 -
amrestore:   0: skipping start of tape: date 20040820 label Fri3.2
amrestore:   1: skipping pedlinux1._scratch.20040820.0
amrestore:   2: skipping telsun4._projects.20040820.0
amrestore:   3: skipping telhp3._home.20040820.0
amrestore:   4: restoring telhp6._opt.20040820.0
Tape is not a dump tape
#

Ok. Now it did find the correct tape, and did find the relevant
backup image (number 4 it seems).

Was this backup made by "dump", then you need "restore", but if
it was created by "gnutar" than then you gnutar to restore.


HELP PLEASE! I NEED TO GET THIS SORTED FAST!

Welcome to the wonderful stress of restoring  :-)
Tip:  first be calm, think slowly, better take 5 minutes
more to investigate something than rushing and panicking.
Even take half an hour to read the documentation again!
Just ignore the users (temporarily).


--
Paul Bijnens, Xplanation                            Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* 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          *
***********************************************************************