Since this seems to revolve around a restore that needs two tapes, what happens if you specify the two tapes SEPARATELY, does anyone know?
mkdir /tmp/A mkdir /tmp/B cd /tmp/A amrecover> setdate “2015-11-29” <<<— new line I’ve inserted amrecover> add "2015_02_04 (E)” Added dir "/jmnavarr/2015_02_04 (E)/" at date 2015-11-29-23-30-01 do the recover from this tape exit; cd /tmp/B amrecover> setdate “2015-12-04” <<<— new line I’ve inserted amrecover> add "2015_02_04 (E) ”Added dir "/jmnavarr/2015_02_04 (E)/" at date 2015-12-04-23-30-02 do the am recover exit Might this work better? Has anyone tried this, and does it work around the bug perhaps? Deb Baddorf > On Dec 23, 2015, at 10:51 AM, Alan Hodgson <[email protected]> wrote: > > On Tuesday, December 22, 2015 03:42:33 PM you wrote: >> -------- Forwarded Message -------- >> Subject: amrecover seems to work but just leaves empty directory >> Date: Fri, 11 Dec 2015 14:58:08 -0500 >> From: Chris Hoogendyk <[email protected]> >> To: AMANDA users <[email protected]> >> >> >> >> I am trying to use amrecover to retrieve a directory that a user >> accidentally deleted. amrecover shows substantial contents via ls at the >> date that I'm recovering from. It requests the tape and spends a good bit >> of time working on it. When it is done, the folder that it recovered is >> empty. >> >> I have tried it from two different time periods that involved two different >> full backup tapes. >> >> I have no idea what is happening or how to figure it out. >> >> Here is part of my session: > > There's a bug in recent versions of tar that might be biting you. I don't > think a fixed version has even been released. There was some discussion of > this > on the list I think last year. > > You can work around this by pulling the whole image off of tape with > amrestore > and untar it manually to find the files you need to restore. > > http://lists.gnu.org/archive/html/bug-tar/2014-09/msg00006.html
