URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header
I have also noticed that since writing the last email that the indexed appear to exist in $ pwd /var/adm/amanda/Weekly/index/telhp6/_opt $ ls -al total 11796 drwxr-sr-x 2 amanda amanda 512 Aug 24 17:45 . drwxr-sr-x 9 amanda amanda 512 Apr 23 22:43 .. -rw--- 1 amanda amanda843781 Jun 8 07:36 20040607_0.gz -rw--- 1 amanda amanda844327 Jun 26 06:26 20040625_0.gz -rw--- 1 amanda amanda843765 Jul 24 07:19 20040723_0.gz -rw--- 1 amanda amanda849580 Aug 4 08:47 20040803_0.gz -rw--- 1 amanda amanda853483 Aug 7 08:23 20040806_0.gz -rw--- 1 amanda amanda853500 Aug 14 09:26 20040813_0.gz -rw--- 1 amanda amanda854630 Aug 21 08:57 20040820_0.gz PLEASE REPLY SOMEONE - DESPARATE -Original Message- From: Ranveer Attalia Sent: 25 August 2004 09:45 To: 'Paul Bijnens' Subject: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header Importance: High 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!!) 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 $ $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 # HELP PLEASE! I NEED TO GET THIS SORTED FAST! Thanks v. much - Ranveer -Original Message- From: Paul Bijnens [mailto:[EMAIL PROTECTED] Sent: 24 August 2004 16:01 To: Ranveer Attalia; '[EMAIL PROTECTED]' Subject: Re: Anyone please reply! System Disk recovery - UNKNOWN file. amrecover: Cant read file header Ranveer Attalia wrote: > >>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. > > These all live in /tmp/amanda yes? If so then everytime the machine > reboots this means that the amanda log files get automatically cleared. No, the files /tmp/amanda are debug files. The log.DATESTAMP.X files live in the ~amanda/Name-Of-Config/ directory, next to the amdump.X files and others, like tapelist etc. > >>EOF, check amidxtaped..debug file on tsssun1. >>ok, what does that file say? > > > NOt much more info: But enough for me :-) > $ cat amidxtaped.20040823170009.debug > amidxtaped: debug 1 pid 23046 ruid 6558 euid 6558: start at Mon Aug 23 > 17:00:09 2004 > amidxtaped: version 2.4.4p1 > amidxtaped: time 0.000: > SECURITY USER root > amidxtaped: time 0.002: bsd security: remote host pethp1.tertio.com > user root local user amanda > amidxtaped: time 0.003: amandahosts security check passed > amidxtaped: time 0.003: > CONFIG=Weekly > amidxtaped: time 0.003: > LABEL=Fri3.1 So it is looking for a tape named "Fri3.1" (remember that's what amrecover asked to load!) > amidxtaped: time 0.003: > FSF=132 And it would be file 132 on that tape. > amidxtaped: time 0.003: > HEADER > amidxtaped: time 0.003: > DEVICE=/dev/rmt/1ubn > amidxtaped: time 0.065: > HOST=^pesthp1$ > amidxtaped: time 0.065: > DISK=^/opt$ > amidxtaped: time 0.065: > DATESTAMP=20040820 > amidxtaped: time 0.065: > END > amidxtaped: time 0.093: amrestore_nargs=0 > amidxtaped: time 0.093: Ready to execv amrestore with: > path = /opt/amanda/sbin/amrestore > argv[0] = "amrestore" > argv[1] = "-p" > argv[2] = "-h" > argv[3] = "/dev/rmt/1ubn" > argv[4] = &quo
URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header
Hi I am having other problems now where I have attempted to use vxrestore and restored back most of the system. However, there appear to be some files missing so I am having to use amrecover to restore certain directories in /usr/local on my HPUX machine I am using my July full backup tape which was successful but amrecover keeps me for the last full backup tape (Fri3.1) which is a corrupt tape. Also I have noticed that when I load the July tape and set it to the correct directory to restore, on the client when I do a listing of whats on the July tape, its giving me the date of last Friday (Fri3.1) WHY? It should be giving me the date of the July full backup. How can I force amrecover to read off the correct tape and not ask me to load Fri3.1 $ amadmin Weekly find telhp6 /usrWarning: no log files found for tape Fri4.1 written 2004-04-23Warning: no log files found for tape Mar0.1 written 2004-03-28Warning: no log files found for tape Weekly5 written 2004-02-28Warning: no log files found for tape Weekly4 written 2004-02-14Warning: no log files found for tape Weekly3 written 2004-02-07Warning: no log files found for tape Weekly2 written 2004-01-30Warning: no log files found for tape Weekly1 written 2004-01-23Scanning /amanda...Scanning /amanda1... date host disk lv tape or file file status2004-06-25 telhp6 /usr 0 Jun0.1 95 OK2004-07-23 telhp6 /usr 0 Fri4.2 75 OK2004-08-03 telhp6 /usr 0 Jul0.1 84 OK2004-08-06 telhp6 /usr 0 Fri1.1 109 OK2004-08-13 telhp6 /usr 0 Fri2.1 100 OK2004-08-20 telhp6 /usr 0 Fri3.1 87 OK Here I load Jul0.1 and fsf to 84 Then I go to my client: # /opt/amanda/sbin/amrecover -C Weekly -t tsssun1 -s tsssun1AMRECOVER Version 2.4.4p2. Contacting server on tsssun1 ...220 tsssun1 AMANDA index server (2.4.4p1) ready.200 Access OKSetting restore date to today (2004-08-26)200 Working date set to 2004-08-26.200 Config set to Weekly.200 Dump host set to telhp6.Trying disk /tmp ...Trying disk /dev/vg00/lvol5 ...Can't determine disk and mount point from $CWD '/tmp/usr-local-bin'amrecover> setdisk /usrScanning /amanda...Scanning /amanda1...200 Disk set to /usr.amrecover> ls2004-08-20 .2004-08-20 TT_DB/2004-08-20 adm Notice that it is showing the wrong date on July's tape. amrecover> add bin/Added dir /local/bin at date 2004-08-20amrecover> extract Extracting files using tape drive /dev/rmt/1ubn on host tsssun1.The following tapes are needed: Fri3.1 Restoring files into directory /tmp/usr-local-binContinue [?/Y/n]? Y Extracting files using tape drive /dev/rmt/1ubn on host tsssun1.Load tape Fri3.1 nowContinue [?/Y/n/s/t]? YEOF, check amidxtaped..debug file on tsssun1.amrecover: short block 0 bytesUNKNOWN fileamrecover: Can't read file headerextract_list - child returned non-zero status: 1Continue [?/Y/n/r]? namrecover> Tertio Telecoms (www.telco-tertio.com) Head Office: One Angel Square Torrens Street London EC1V 1PL Tel: +44 (0)20 7843 4000 - Fax: +44 (0)20 7843 4001 Bath Office: Riverside Buildings 108 Walcot Street Bath BA1 5BG Tel: +44 (0)1225 478000 - Fax: +44 (0)1225 478001 Munich Office: Freisinger Strasse 10, 85737 Ismaning/Munich, Germany, Tel: +49 (0)89 665506 41 - Fax: +49 (0)89 665506 99 Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Tertio Ltd. This email has been scanned by the MessageLabs Email Security System.
Re: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header
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, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * 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 * ***
FW: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header
amidx debug file info: amidxtaped: version 2.4.4p1amidxtaped: time 0.000: > SECURITY USER rootamidxtaped: time 0.002: bsd security: remote host telhp6.tertio.com user root local user amandaamidxtaped: time 0.003: amandahosts security check passedamidxtaped: time 0.003: > CONFIG=Weeklyamidxtaped: time 0.003: > LABEL=Fri3.1amidxtaped: time 0.003: > FSF=87amidxtaped: time 0.003: > HEADERamidxtaped: time 0.003: > DEVICE=/dev/rmt/1ubnamidxtaped: time 0.003: > HOST=^telhp6$amidxtaped: time 0.003: > DISK=^/usr$amidxtaped: time 0.066: > DATESTAMP=20040820amidxtaped: time 0.066: > ENDamidxtaped: time 0.095: amrestore_nargs=0amidxtaped: time 0.095: Ready to execv amrestore with:path = /opt/amanda/sbin/amrestoreargv[0] = "amrestore"argv[1] = "-p"argv[2] = "-h"argv[3] = "-l"argv[4] = "Fri3.1"argv[5] = "-f"argv[6] = "87"argv[7] = "/dev/rmt/1ubn"argv[8] = "^telhp6$"argv[9] = "^/usr$"argv[10] = "20040820"Wrong label: 'Jul0.1'amidxtaped: time 116.504: amrestore terminated normally with status: 1amidxtaped: time 116.505: rewinding tape ...amidxtaped: time 118.872: doneamidxtaped: time 118.890: pid 22531 finish time Thu Aug 26 15:55:59 2004 From: Ranveer Attalia Sent: 26 August 2004 16:01To: 'Paul Bijnens'Cc: '[EMAIL PROTECTED]'Subject: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header Hi I am having other problems now where I have attempted to use vxrestore and restored back most of the system. However, there appear to be some files missing so I am having to use amrecover to restore certain directories in /usr/local on my HPUX machine I am using my July full backup tape which was successful but amrecover keeps me for the last full backup tape (Fri3.1) which is a corrupt tape. Also I have noticed that when I load the July tape and set it to the correct directory to restore, on the client when I do a listing of whats on the July tape, its giving me the date of last Friday (Fri3.1) WHY? It should be giving me the date of the July full backup. How can I force amrecover to read off the correct tape and not ask me to load Fri3.1 $ amadmin Weekly find telhp6 /usrWarning: no log files found for tape Fri4.1 written 2004-04-23Warning: no log files found for tape Mar0.1 written 2004-03-28Warning: no log files found for tape Weekly5 written 2004-02-28Warning: no log files found for tape Weekly4 written 2004-02-14Warning: no log files found for tape Weekly3 written 2004-02-07Warning: no log files found for tape Weekly2 written 2004-01-30Warning: no log files found for tape Weekly1 written 2004-01-23Scanning /amanda...Scanning /amanda1... date host disk lv tape or file file status2004-06-25 telhp6 /usr 0 Jun0.1 95 OK2004-07-23 telhp6 /usr 0 Fri4.2 75 OK2004-08-03 telhp6 /usr 0 Jul0.1 84 OK2004-08-06 telhp6 /usr 0 Fri1.1 109 OK2004-08-13 telhp6 /usr 0 Fri2.1 100 OK2004-08-20 telhp6 /usr 0 Fri3.1 87 OK Here I load Jul0.1 and fsf to 84 Then I go to my client: # /opt/amanda/sbin/amrecover -C Weekly -t tsssun1 -s tsssun1AMRECOVER Version 2.4.4p2. Contacting server on tsssun1 ...220 tsssun1 AMANDA index server (2.4.4p1) ready.200 Access OKSetting restore date to today (2004-08-26)200 Working date set to 2004-08-26.200 Config set to Weekly.200 Dump host set to telhp6.Trying disk /tmp ...Trying disk /dev/vg00/lvol5 ...Can't determine disk and mount point from $CWD '/tmp/usr-local-bin'amrecover> setdisk /usrScanning /amanda...Scanning /amanda1...200 Disk set to /usr.amrecover> ls2004-08-20 .2004-08-20 TT_DB/2004-08-20 adm Notice that it is showing the wrong date on July's tape. amrecover> add bin/Added dir /local/bin at date 2004-08-20amrecover> extract Extracting files using tape drive /dev/rmt/1ubn on host tsssun1.The following tapes are needed: Fri3.1 Restoring files into directory /tmp/usr-local-binContinue [?/Y/n]? Y Extracting files using tape drive /dev/rmt/1ubn on host tsssun1.Load tape Fri3.1 nowContinue [?/Y/n/s/t]? YEOF, check amidxtaped..debug file on tsssun1.amrecover: short block 0 bytesUNKNOWN fileamrecover: Can't read file headerextract_list - child returned non-zero status: 1Continue [?/Y/n/r]? namrecover> Tertio Telecoms (www.telco-tertio.com) Head Office: One Angel Square Torrens Street London EC1V 1PL Tel: +44 (0)20 7843 4000 - Fax: +44 (0)20 7843 4001 Bath Office: Riverside Buildings 108 Walcot Street Bath BA1 5BG Tel: +44 (0)1225 478000 - Fax: +44 (0)1225 478001 Munich Office: Freisinger Strasse 10, 85737 Ismaning/Munich, Germany, Tel: +49 (0)89 665506 41 - Fax: +49 (0)89 665506 99 Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Tertio Ltd. This email has been scanned by the MessageLabs Email Security System.
Re: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header
Ranveer Attalia wrote: Hi I am having other problems now where I have attempted to use vxrestore and restored back most of the system. However, there appear to be some files missing so I am having to use amrecover to restore certain directories in /usr/local on my HPUX machine I am using my July full backup tape which was successful but amrecover keeps me for the last full backup tape (Fri3.1) which is a corrupt tape. Also I have noticed that when I load the July tape and set it to the correct directory to restore, on the client when I do a listing of whats on the July tape, its giving me the date of last Friday (Fri3.1) WHY? That's because amrecover does not read the tape, but uses the online index files. After you have specified the files, amrecover would then tell you which tapes it needed! It should be giving me the date of the July full backup. How can I force amrecover to read off the correct tape and not ask me to load Fri3.1 $ amadmin Weekly find telhp6 /usr 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... date host disk lv tape or file file status 2004-06-25 telhp6 /usr 0 Jun0.1 95 OK 2004-07-23 telhp6 /usr 0 Fri4.2 75 OK 2004-08-03 telhp6 /usr 0 Jul0.1 84 OK 2004-08-06 telhp6 /usr 0 Fri1.1109 OK 2004-08-13 telhp6 /usr 0 Fri2.1100 OK 2004-08-20 telhp6 /usr 0 Fri3.1 87 OK Here I load Jul0.1 and fsf to 84 Then I go to my client: # /opt/amanda/sbin/amrecover -C Weekly -t tsssun1 -s tsssun1 AMRECOVER Version 2.4.4p2. Contacting server on tsssun1 ... 220 tsssun1 AMANDA index server (2.4.4p1) ready. 200 Access OK Setting restore date to today (2004-08-26) The default is to use the most current date. You can change this with the command: setdate 2004-08-03 I got that date from the info above. And now amrecover will ask for the last tape just before that date. And that seems to be the tape named "Jul0.1". 200 Working date set to 2004-08-26. 200 Config set to Weekly. 200 Dump host set to telhp6. Trying disk /tmp ... Trying disk /dev/vg00/lvol5 ... Can't determine disk and mount point from $CWD '/tmp/usr-local-bin' amrecover> setdisk /usr Scanning /amanda... Scanning /amanda1... 200 Disk set to /usr. amrecover> ls 2004-08-20 . 2004-08-20 TT_DB/ 2004-08-20 adm Notice that it is showing the wrong date on July's tape. amrecover does not yet did anything with the tape. amrecover> add bin/ Added dir /local/bin at date 2004-08-20 amrecover> extract Extracting files using tape drive /dev/rmt/1ubn on host tsssun1. The following tapes are needed: Fri3.1 See here it says, that to restore what you asked, then you need tape "Fri3.1". Restoring files into directory /tmp/usr-local-bin 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 And only now, it reads the tape. Which of course does not contain what amrecover asks. EOF, check amidxtaped..debug file on tsssun1. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue [?/Y/n/r]? n amrecover> -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * 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 * ***
Re: FW: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header
Ranveer Attalia wrote:
I realised that I had commented out the WEEKLY/disklist (being over
cautius last night) so thats why there was no dump to list. When I do it
now - it works ok:
Fine.
Was this backup made by "dump", then you need "restore", but if it was
created by "gnutar" than then you gnutar to restore.
Looks like it was done by dump. Below is a cut of the WEEKLY/disklist
file for telhp6 and the WEEKLY/amanda.conf file.
DISKLIST
...
telhp6 /opt always-full
...
define dumptype always-full {
global
comment "Full dump of this filesystem always"
compress none
index
priority high
dumpcycle 0
Unless dumptype "global" does not contains "program GNUTAR", then
it is indeed dump.
You can also verify this on the amanda tape header, which contains
this information too!
mt -f /dev/rmt/1ubn rewind
mt -f /dev/rmt/1ubn fsf 4
dd bs=32k count=1 if=+dev+rmt/1ubn
and voila; you should see something like:
AMANDA: FILE 20040623 host /the/dir lev 0 comp N program /usr/bin/gtar
To restore, position tape at start of file and run:
dd if= bs=32k skip=1 | /usr/bin/gtar -f... -
But I guess you'll see "restore" instead of "gtar".
Or do you see a variant of restore, like vxrestore? See below.
When trying the amrestore its still complaining about "Tape is not a
dump tape"
First you need to be sure about which program is generating that error
message.
I guess it is the "restore" command.
Try doing a "strings -a /usr/sbin/restore" and verify if there is
message "Tape is not a dump tape".
How do I use GNUTAR (please plase give me an example using hostname:
telhp6, partition: opt, amanda server: tsssun1
(although I dont think its using GNUTAR from the info above)
as root:
cd /the/destination/folder
remsh ...amrestore-cmd-as-used-is-ok... | tar -xpvf -
But I believe you are correct in using restore.
Are you using the restore on the correct architecture?
You need restore from the HP-machine for HP-dumps, and if
the filesystem was a special format like veritas, you need
the corresponding restore for that filesystem.
The amanda tapeheader for that backup does contain that information!
Instead of reading the slow tape over and over again, you can
dump the backup image on a disk (leave out the -p from amrestore).
And then try to find out what kind of image it is, with e.g.
using "file telhp6._opt.20040824.0", and trying tar and/or
restore to generate a table of contents.
Just ignore the users (temporarily)
I do that anyway ;-)
Its my boss I'm more worried about !
Never mind about him, especially in these cases. (And he should know
that too!)
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* 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 *
***
Re: FW: URGENT!!! System Disk recovery - UNKNOWN file. amrecover: Cant read file header
Ranveer Attalia wrote: amidx debug file info: > amidxtaped: version 2.4.4p1 amidxtaped: time 0.000: > SECURITY USER root amidxtaped: time 0.002: bsd security: remote host telhp6.tertio.com user root local user amanda amidxtaped: time 0.003: amandahosts security check passed amidxtaped: time 0.003: > CONFIG=Weekly amidxtaped: time 0.003: > LABEL=Fri3.1 Notice it asks for tape label "Fri3.1". amidxtaped: time 0.003: > FSF=87 amidxtaped: time 0.003: > HEADER amidxtaped: time 0.003: > DEVICE=/dev/rmt/1ubn amidxtaped: time 0.003: > HOST=^telhp6$ amidxtaped: time 0.003: > DISK=^/usr$ amidxtaped: time 0.066: > DATESTAMP=20040820 And it asks for date"20040820". amidxtaped: time 0.066: > END amidxtaped: time 0.095: amrestore_nargs=0 amidxtaped: time 0.095: Ready to execv amrestore with: path = /opt/amanda/sbin/amrestore argv[0] = "amrestore" argv[1] = "-p" argv[2] = "-h" argv[3] = "-l" argv[4] = "Fri3.1" argv[5] = "-f" argv[6] = "87" argv[7] = "/dev/rmt/1ubn" argv[8] = "^telhp6$" argv[9] = "^/usr$" argv[10] = "20040820" Wrong label: 'Jul0.1' You see here? amrestore asked you to load "Fri3.1", but it found the wrong tape, and quits immediately. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * 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 * ***
