On Wed, 5 Dec 2001 at 12:08am, Gregory LeBaron wrote > Recently, my drive ate daily32. I continued to run without > problems until today when I did what I thought would be the > Right Thing: > $ amrmtape daily daily32 > And then with a new tape: > $ amlabel daily daily32 > > Now I'm getting: > $ amadmin daily tape > The next Amanda run should go onto a new tape. > > And: > [amanda@msr01 amanda]$ amflush daily > Expecting a new tape. (The last dumps were to tape daily28) > > The tapelist file no longer contains an entry for the tape daily32 > I'd thought that the amlabel would add that but I guess not...
Whenever you have less active tapes than 'tapecycle', amanda expects a new tape on the next run. I *believe* that a tape isn't marked active until it's used -- IOW, just amlabeling one isn't going to do it. You could just feed amanda daily32 on the next run, but then your tapes will be "out of order" (note: only to you, not to amanda). Or you could try adding it to the tapelist by hand until after daily31 is used, then removing it and *then* using daily32 as your "new" tape. Personally, I'd go with the former -- it's annoying, but there's less chance of screwing things up. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
