Yeah, that's what I meant to say ;-) Go Paul.
-----Original Message-----
From: owner-amanda-users AT amanda DOT org
[mailto:owner-amanda-users AT amanda DOT org]On Behalf Of Paul Bijnens
Sent: 24 August 2004 14:51
To: Ranveer Attalia
Cc: amanda-users AT amanda DOT org
Subject: Re: Anyone please reply! System Disk recovery - UNKNOWN file.
amrecover: Cant read file header
Ranveer Attalia wrote:
> I am trying to test restore before I run a system disk recover from
> amanda server to my client machine.
> The restore file is any one from /opt onto the client telhp6 onto a
> /scratch/restored directory but its giving me file header errors...
> I cannot understand why though because it looks as if it backed up fine
> and its displaying the tape labels with no problem on the amanda server:
> Please can someone help
>
> Thanks
>
> - Ranveer
>
> $ amtape Weekly show
> amtape: scanning all 7 slots in tape-changer rack:
> slot 1: date 20040822 label Fri3.1
> slot 2: date 20040820 label Fri3.2
> amtape: could not load slot source: Element Address 8 is Empty
Labeling tapes with "day of the week", is not a good practice,
just in case you didn't read the earlier warnings about this issue.
> $
>
> $ amadmin Weekly find telhp6 /opt
> 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
It seems some overly active system administrator removed
the log.DATESTAMP.x files. Do not do that. They are needed by
amanda to find information about tape contents. They are cleaned
automatically by amanda, when needed, too.
> Scanning /amanda...
> Scanning /amanda1...
>
> date host disk lv tape or file file status
> 2004-06-07 telhp6 /opt 0 Peg0.1 1 OK
> 2004-06-25 telhp6 /opt 0 Jun0.1 145 OK
> 2004-07-23 telhp6 /opt 0 Fri4.2 136 OK
> 2004-08-03 telhp6 /opt 0 Jul0.2 3 OK
> 2004-08-06 telhp6 /opt 0 Fri1.2 4 OK
> 2004-08-13 telhp6 /opt 0 Fri2.2 6 OK
> 2004-08-20 telhp6 /opt 0 Fri3.2 4 OK
>
> amrecover> add amanda.tar
> Added /amanda.tar
> amrecover> extract
>
> Extracting files using tape drive /dev/rmt/1ubn on host tsssun1.
> The following tapes are needed: Fri3.1
>
> Restoring files into directory /scratch/restored
> Continue [?/Y/n]? Y
>
> Extracting files using tape drive /dev/rmt/1ubn on host tsssun1.
> Load tape Fri3.1 now
> Continue [?/Y/n/s/t]? Y
> EOF, check amidxtaped.<timestamp>.debug file on tsssun1.
ok, what does that file say?
> amrecover: short block 0 bytes
0 bytes is frequently a sign of forgetting to rewind the tape.
> UNKNOWN file
> amrecover: Can't read file header
Yes, indeed, there is no header in a 0 byte file.
> extract_list - child returned non-zero status: 1
> Continue [?/Y/n/r]? Y
> amrecover>
>
>
> and it doesnt actually extract anything.
--
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 *
***********************************************************************
|
