Recovery from server would work if it's the same type node as the client (has to be able to run same version of system dump & able to read the saved file). It would place the recovered files in your current directory on the server, not on the client.
As for your client's new problem, I'm adding the Amanda-users back into this reply cuz I can diagnose that from home. Hope someone else can step in here. Deb (from phone) On Nov 25, 2013, at 9:08 PM, "Michael Stauffer" <mgsta...@gmail.com<mailto:mgsta...@gmail.com>> wrote: Thanks Deb. I found an amrecover log but first this: I realized I've been trying to recover from the server (i.e. run amrecover on the server), and not the client as directed in the tutorial (but shouldn't recovery from the server work too?). Running amrecover on the client, I get this: [root@cslim ~]# amrecover DailySet1 AMRECOVER Version 3.3.4. Contacting server on cback.uphs.upenn.edu<http://cback.uphs.upenn.edu> ... [request failed: No route to host] >From the client (cslim) I can ping and ssh to the server (even passwordless >ssh now). I'm using bsdtcp for auth - is there some other setup for that? Thanks. -M On Mon, Nov 25, 2013 at 6:16 PM, Debra S Baddorf <badd...@fnal.gov<mailto:badd...@fnal.gov>> wrote: > > > xtracting files using tape drive cback://amandatest/vtape/DailySet1 on host > localhost. > Load tape DailySet1-3 now > Continue [?/Y/n/s/d]? y > > [this is where it just hangs up] > > -- > Other info: > > /var/log/amanda/log.error/ is empty > > (As an aside, there are a large multitude of various log files - is there an > amanda command that parses them all to look for errors and reports them?) > Have you tried $ grep -ir "DailySet1-3" /tmp/amanda/ (substitute if your logs aren't being sent to that directory) There should also be a file *amrecover*yyyymmdd* though the hangup might be in a *taper* file or something else like that. Those are some first steps, in case better info doesn't come soon! Deb Baddorf Fermilab
