> Load tape DailySet1001 now > Continue? [Y/n]: y > EOF, check amidxtaped.debug file on localhost. > amrecover: short block 0 bytes > UNKNOWN file > amrecover: Can't read file header > extract_list - child returned non-zero status: 1 > Continue? [Y/n]: y > amrecover>
This is the same thing that is currently happening to me. When I do an amrestore on the tape, it tries to read the whole tape as whatever the first header is on the tape. Looking at the file, I can see the other Amanda headers. I recently did the unspeakable and began doing incrementals separate from my full backups. I did this by creating a symbolic link in /var/lib/amanda to my full backup directory for my incrementals so that they share the same log files and everything. This gets around the problem of the incrementals not knowing when a full backup was last done for them. Everything claims to be working, but now I can't seem to get the data off of the full backup tapes. Everything is there, I can see it, but amanda doesn't want to parse its headers correctly. It seems to me that it is hosing up seeing the separator between the headers, but I don't see why it should suddenly be doing that.
