Re: restore from vtapes written by amvault
Nathan Stratton Treadway <[email protected]>
| Newsgroups | gmane.comp.archivers.amanda.user |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Oct 08, 2020 at 14:29:48 -0400, Nathan Stratton Treadway wrote: > On Thu, Oct 08, 2020 at 20:00:18 +0200, Bernhard Erdmann wrote: > > $ amadmin be-full find svr / > > > > date host disk lv storage pool tape or file file part status > > 2000-01-19 svr / 0 vtape vtape vBE-full-001 2 1/1 OK > > 2000-01-19 svr / 0 be-full be-full BE-full-00 2 1/-1 OK > > Okay, that's good news. > > > > > But amfetchdump still does not know about tape vBE-full-001: > > > > $ amfetchdump -d vtape be-full svr '^/$' 20000119 > > 1 volume(s) needed for restoration > > The following volumes are needed: BE-full-00 > > Have you looked into explicitly specifying the storage that amfetchdump > is looking for/at? That would be my first thing to investigate at this > point. If I get a chance later this evening I'll try to look back > through my notes to see if I can remember the details of how that > works.... Well.... looking through the source code for amfetchdump, it seems like the program does not pull storage names from the amanda.conf file after all, but instead it seems to assume that it can determine the storage to use based on the changer specified by the"-d vtape" parameter. Based on the fact that it's prompting for tape BE-full-00, though, that doesn't seem to be working as expected.... It looks like amfetchdump should be creating a "$logdir/fetchdump.$timestamp" log file. If so, does that include any mention of opening the vtape changer and/or detecting storage names? (Assuming it's not super long, you could post that log file here for us to take a look at...) Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - [email protected] - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239