On Fri, Apr 30, 2010 at 5:49 AM, Jean-Francois Malouin <ma...@bic.mni.mcgill.ca> wrote: > no, the dump used 2 vtapes, vtape-1 and vtape-2, and there is only one > `drive'. I did 2 run with amrecover just to convince me that it really > asked for vtape-2 *before* vtape-1. Since I have `amrecover_changer' > set I just hit return to see what would happen and vtape-1 got loaded > first.
Actually, looking at the amrecover output: > amrecover> list > TAPE vtape-2:3 LEVEL 0 DATE 2010-04-28-17-12-43 and the amidxtaped logfile: > Thu Apr 29 16:13:31 2010: amidxtaped: CTL << LABEL=vtape-2:3 the particular dump you're looking for is only on vtape-2, filenum 3. However, what's odd is that amidxtaped then goes on to look for vtape-1: > Thu Apr 29 16:13:31 2010: amidxtaped: find_volume labeled 'vtape-1' It looks like there is some disagreement between amindexd and amdixtaped as to which volumes contain this file. Can you apply this temporary patch: --- a/server-src/amidxtaped.pl +++ b/server-src/amidxtaped.pl @@ -428,6 +428,8 @@ sub plan_cb { my $self = shift; my ($err, $plan) = @_; + use Data::Dumper; + Amanda::Debug::debug(Dumper($plan)); if ($err) { $self->sendmessage("$err"); return $self->quit(); and re-run, pasting the new amidxtaped debug log. Also, please send the output of amadmin test find gustav /raid/hrrt/SCS_SCANS Thanks! Dustin -- Open Source Storage Engineer http://www.zmanda.com