On Thu, Apr 19, 2007 at 03:31:33PM -0700, Paul Yeatman wrote: > ->>In response to your message<<- > --received from Jon LaBadie-- > > On Tue, Apr 17, 2007 at 07:13:09PM -0700, Paul Yeatman wrote: > > > Hi, I'm testing my backup system and am finding something unexpected. > > > ... > > > > I would presume that this is a fairly stable, unchanging storage. > > I base that guess on the fact that the last full backup was May 2005 > > and the first incremental a year later in May of 2006. Another clue > > is that the incrementals haven't been moved from the holding disk > > to tape (physical or virtual) in the last year. > > So, as I continue to look at the problem, I haven't seen before > that an amflush is require for the directories on holding disk to > be included in a recovery yet . . . this kinda of seems to be the > case now (that is as much a question as it is a statement). I see > in the amindexd.###.debug log that it is trying to "gzip -dc ... " > files in the amanda index directory for the disk being restored > yet these files don't exist. For instance, the log says this is > being executed > > /bin/gzip -dc '/etc/amanda/cass/index/cass246/_/20070331_6.gz' > 2>/dev/null | sort > '/etc/amanda/cass/index/cass246/_/20070331_6' > > yet "/etc/amanda/cass/index/cass246/_/20070331_6.gz" does not exist; > It is instead on the holding disk.
This surprises me, are you sure your index files are on the holding disk? I.e. you can "ls /etc/amanda/cass/index/cass246/_/20070331_6.gz" and it is not there, but it is on the holding disk? What is its holding disk path? I may have missed it, but I didn't think index files ever end up on the holding disk. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)