On Tue, Oct 29, 2002 at 10:29:32AM -0500, Brian Kennedy wrote:
> I've got the backups running smoothly, some scripts to change "tapes"
> (move symlinks) but I cant get a recover to work.
OK - a little background on my setup so that later becomes clear - I have a
partition /backup on a server called backup. In /backup I have created my
"tapes" and I backup to backup:/backup/tape where tape is a symlink to the
appropriate "tape" (I've a notion that a more 'elegant' olsution to this
whole kludge would be a hacked mtx of some sort, but I digress)
> amrecover conf
> .. select some files and extract..
> Restore files into..
> continue? Y
> Load tape ...
> continue? Y
> and then:
> amrecover: error reading tape: Connection reset by peer
> extract_list - child returned non-zero status: 1
>
> any clues as to what is wrong?
I think amanda doesn't know where it should be looking - below an extract
from our local operations manual:
At this point using physical tapes, it's time to load the desired tape. But
because we are using amanda's ability to use virtual tapes on disk, rather
than loading a tape we must tell amanda where the "tape" is. The 't' option
at this prompt allows us to do so
Continue [?/Y/n/t]? t
New tape device [?]: backup:file:/backup/TIZdaily04
Here we've told amanda where the "tape" is. The syntax is as in the example
above backup:file:/backup/ followed by the tape name.
Now here's the bit that ISN'T in our operations manual - you can't tell
amanda to use a tape called file:/backup/store because then it tries to
use a host called file. I'm presuming your store is a symlink analogous to
my tape ? I start amrecover like this (my configuration is TIZ)
amrecover TIZ -s backup -t backup
and I don't even bother specifying a tape device.
I have moaned about this already, and the problem is essentially the
overloading of : . As it's an eminently workaroundable :-) problem, I don't
suppose there's a huge incentive to fix it.
Kindest regards,
Niall O Broin
