On Wed, 2015-05-06 at 22:02 -0400, Gene Heskett wrote:
> On Wednesday 06 May 2015 18:57:45 Debra S Baddorf wrote:
> > Second try at the commands, possibly in better detail:
> > Check file permissions (in case Joe Schmuck will later need to
> > delete the files). Then
> > cp -pnv /tmp/home/gene/linuxcnc/*
> > theRealDisk/home/gene/linuxcnc
> >
> > # n is a “no-clobber” on my current version, but doesn’t
> > work on my prev version # that’s in case my commands are
> > wrong — don’t rely blindly on what I’ve typed!!! # And “n”
> > may not work, so maybe take it out.
> > # v only cuz I like to see the files going where I told them to
> > go; maybe you don’t
> >
> This sounds like I had better get nfs4 setup, which is not yet, new
> install on the target machine "lathe". Working from the server, coyote.
>
> There is not anything precious in the target directory right now, so it
> wouldn't bother me if the whole tree got clobbered with the recovered
> data. Is there not a way to cd to that machine/home/gene, and recover
> the linuxcnc tree directly to it? If amdump can pull it from that
> machine, it seems like amrecover ought to be able to write it back to
> that same machine without needing the copy operation.
>
Sure, then just run amrecover from that machine. The amrecover command
can be run from any Amanda client that the Amanda server is configured
in its /var/lib/amanda/.amandahosts to allow a connection from, for
example:
clientA.mycompany.com root amindexd amidxtaped
Use "-s hostname" when running amrecover to specify the hostname or IP
address of the Amanda server you want to pull data from.
> So I go thru the exersize, but when I 'extract' the directory it shows,
> exists on all 3 machines, so how do I verify that it will extract to
> lathe.coyote.den/home/gene/linuxcnc?
>
Data will only be extracted in the directory in which you executed
amrecover, regardless of which host is set (sethost) or disk is set
(setdisk). This would thus generally be restoring data only to the host
on which you are running amrecover although you could be in a directory
that is not a local volume when executing amrecover. You can run "lpwd"
at the amrecover prompt to see which directory amrecover considers to be
its working directory. Per amrecover man page:
lpwd
Display the amrecover working directory. Files will be restored
under this directory, relative to the backed up filesystem.
lcd path
Change the amrecover working directory to path.
Cheers!
Paul
