On Mon, Jan 06, 2003 at 10:03:02AM -0600, Josh More wrote: > > >>* Oddly, when you've navigated to what you want to restore, add it, > >> and extract it, it does the extract from the disk level, not the > >> directory you were in when you added it. Not a big problem, but > >> it caused a wee bit of confusion. > > > >Huh? Again, can you show an example. > > > >In general, if you told Amanda to back up disk "/usr" and one of the files > >backed up was "/usr/a/b/xxx", then if you start amrecover in directory > >"/tmp/restore", the file brought back will be "/tmp/restore/a/b/xxx". > >In other words, things backed up only know themselves relative to the > >top level being processed (i.e. "a/b/xxx"), and they should come back > >relative to whatever directory you do the restore into. > > /usr/local/sbin/amrecover Daily > AMRECOVER Version 2.4.3. Contacting server on cclcsup ... > 220 cclcsup AMANDA index server (2.4.3) ready. > 200 Access OK > Setting restore date to today (2003-01-06) > 200 Working date set to 2003-01-06. > 200 Config set to Daily. > 501 No index records for host: cclcsup.remote-print.com. Invalid? > Trying host cclcsup ... > 200 Dump host set to cclcsup. > Can't determine disk and mount point from $CWD >'/home/development/3rdparty_tools/amanda-2.4.3' > amrecover> sethost cclcsup > 200 Dump host set to cclcsup. > amrecover> setdisk /home > Scanning /usr/local/amanda/dumps... > 200 Disk set to /home. > amrecover> ls > 2003-01-03 . > 2003-01-03 development/ > 2003-01-03 todo/ > 2003-01-03 users/ > amrecover> cd users > /home/users > amrecover> ls > 2003-01-03 . > 2003-01-03 andrew-backup/ > 2003-01-03 andrew/ > amrecover> add andrew > Added dir /users/andrew at date 2003-01-03 > amrecover> extract > > Extracting files using tape drive /dev/nrStp0 on host cclcsup. > The following tapes are needed: DailySet101 > > Restoring files into directory /home/development/3rdparty_tools/amanda-2.4.3 > Continue [?/Y/n]? > > Extracting files using tape drive /dev/nrStp0 on host cclcsup. > Load tape DailySet101 now > Continue [?/Y/n/t]? > ./users/andrew/ > amrecover> quit > 200 Good bye. > > ls -al > drwxr-xr-x 18 1029 203 1024 Jan 6 08:47 . > drwxr-xr-x 17 root sys 512 Dec 27 11:52 .. > drwxr-xr-x 3 andrew users 512 Jan 6 08:47 users > > ls -al users > total 3 > drwxr-xr-x 3 andrew users 512 Jan 6 08:47 . > drwxr-xr-x 18 1029 203 1024 Jan 6 08:47 .. > drwxr-xr-x 2 root sys 512 Jan 6 08:47 andrew >
I may be missing something, but I see nothing unexpected in the above session. As John said above, thing come back relative to where you started amrecover. > > My guess is that the configure script detected the wrong tar. specifying > the location of tar with the --with-gnutar option works, as does > making a symlink of: /usr/local/bin/gtar -> /usr/local/bin/tar Possibility of finding a wrong version is why I always specify gnutar's location. I also rename it "amgtar" so it can easily be replaced with a different version or with a wrapper script and not affect the rest of the system. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
