Michael,
On the server, the global tpchanger and tapedev are now synonymous, all
setting must be put in the changer section.
On the client, only tapedev can be set, but you should set it to the
name of the changer:
tapedev "my_vtapes"
Jean-Louis
On 12/16/2013 06:21 PM, Michael Stauffer wrote:
Hi Everyone,
I've gotten my focus back to this and sorted out my problems.
1) 'amrecover' on clients was unable to connect to server.
Turns out the server's firewall was blocking amanda's ports. Easy fix.
Should have thought of this when the tutorial said to check the
firewall on the clients which I did, but I forgot about the server.
2) 'amrecover' hangs as it tries to load a tape after 'extract' command:
I looked at the amidxtaped log on the server, and saw that the tape
device name/file was not recognized/found. Turns out I had a different
name defined for 'tpchanger' on the server set configuration, than for
the clients' configuration. Changing the clients' configuration fixed
this. I'm curious about the parameter naming - in the
server's /etc/amanda/DailySet1/amanda.conf file, I define
...
define changer my_vtapes {
tpchanger "chg-disk:/amandatest/vtape/DailySet1"
property "num-slot" "10"
property "auto-create-slot" "yes"
}
tpchanger "my_vtapes"
...
And in the clients' /etc/amanda/amanda-client.conf, it's
tapedev "chg-disk://amandatest/vtape/DailySet1" # your tape
device
Just curious where 'tapedev' gets mapped to 'tpchanger'.
-M
On Tue, Nov 26, 2013 at 9:04 AM, Debra S Baddorf <[email protected]
<mailto:[email protected]>> wrote:
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"
<[email protected] <mailto:[email protected]>> 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
<[email protected] <mailto:[email protected]>> 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
