>I'm in the process of checking out amanda, and I've run into a slight >difficulty: the disk I was using as a holding disk has bad blocks and >amflush cannot flush out the dumps. What should I do? Can I make >amanda forget about the disk it failed to flush out so that it will get >rescheduled? Or forget about the whole amdump run?
I would suggest just forcing a full dump for the next run. That forgets most previous information: amadmin <CONFIG> force <HOST> <DISK> Or you could do let Amanda do a little less work and tell it to be sure not to bump to the next dump level: amadmin <CONFIG> force-no-bump <HOST> <DISK> That will cause it to repeat the same level it did last time (or it might jump back to a full dump, which is OK, too). > Alex John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]