On Tuesday 25 June 2019 00:42:38 Nathan Stratton Treadway wrote: > On Mon, Jun 24, 2019 at 15:03:35 -0400, Gene Heskett wrote: > > But right now I need to reach back about 10 days and recover > > my /home/pi/linuxcnc directory which contains the configs and > > nc_files to run this 1500 lb lathe. > > > > But it won't let me run it on the client. On this host, it won't > > let me setdisk to /home/pi > > Session: > > gene@coyote:~$ sudo amrecover Daily > > [sudo] password for gene: > > AMRECOVER Version 3.5.1.git.19364c7b. Contacting server on coyote > > ... 220 coyote AMANDA index server (3.5.1.git.19364c7b) ready. > > Setting restore date to today (2019-06-24) > > 200 Working date set to 2019-06-24. > > 200 Config set to Daily. > > 200 Dump host set to coyote. > > Use the setdisk command to choose dump disk to recover > > amrecover> sethost picnc > > 200 Dump host set to picnc. > > amrecover> setdisk / > > 200 Disk set to /. > > amrecover> setdate --06-08 > > 200 Working date set to 2019-06-08. > > amrecover> cd /home/pi > > /home/pi > > amrecover> lcd /home/pi > > /home/pi: No such file or directory > > amrecover> > > > > > > so that both lpwd and pwd show the same paths. > > which should be /home/pi > > but I cannot > > amrecover> lcd pi > > pi: No such file or directory > > > > What I want is to extract the /home/pi/linuxcnc directory insitu > > I've setdate to the date of the last full of this particular file. > > That was on --06-08, and there were about 4 incrementals since. > > > > How do I do this? Thank you. > > Looks like you have already retrieved the files you needed, but to > (attempt to) answer your original question: > > From the above transcript you appear to be running amrecover on > coyote, but trying to change the local directory to "/home/pi".... but > I assume that directory only exists on picnc, right? > > (Note that you actually do seem to have successfully set the amrecover > "extraction source directory" to /home/pi on the "picnc /" disk; the > error came when you tried to use the "lcd" command to set the > extraction destination directory.) > > If you were running amrecover on picnc it might make sense to recover > directly in-place, but presumably since you are extracting on coyote > you would want to create a temporary working directory to hold the > recovered directory tree, run the amrecover session from within that > temporary directory, then copy/move the files you need from that > directory tree over to the appropriate locations on picnc.... > > > Nathan I tried to run amrecover on picnc, but was NAK'd at every step. This even though I have added the root line to /var/backups/.amandahosts.
So I located the last full which was on the 16th, and using the usual dd if=/path/to/file._.0 bs=32k skip-1 | gzip -d | tar x - command, unpacked it to some spare space on the /amandatapes drive, then copied what I needed from that tree to /home/gene/linuxcnc/transfer-dir, where I chowned it to match the picnc stuffs, then mc'd it to an /sshnet/picnc//home/pi/linuxcnc/configs, and nc_files dirs. And I had it done in 20 minutes, not the 2 days I had been battling amrecover to try and get it done. I have no clue what I was doing wrong, but I do consider the man pages wordings as less than helpfull at schooling me on how to do it. Likewise the online help sucks, And while I can and have amrecovered insitu on the server itself, I'd have to say that my inability to do the same for a client machine is a serious bug. One that really ought to be fixed. Since amanda uses a different rights image than /sshnet, which is strictly a user 1000 access path, the whole /sshnet thing is blocked for root as a security measure in case someone actually gains root thru my router. That has only happened once in 20 years and I had to give Jim the credentials to do it. I needed help with an internal networking problem and it took Jim less than a minute to fix it once in. dd-wrt is the best guard dog I've never had to feed or clean up after. If you don't have it flashed into your router between your local net and the world on the other side of your modem, you simply are leaving your systems open for the worlds black hats to exploit. It blocks out the world noise so well that I don't have any iptables or other security things running on this side of the router except portsentry and fail2ban. They only run on this machine, the other 6 are running naked, and that includes a win10 home edition machine. > > ---------------------------------------------------------------------- >------ 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 Copyright 2019 by Maurice E. Heskett Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
