On Wed, Oct 31, 2018 at 08:25:39AM -0400, Chris Nighswonger wrote: > So, looking at this more, it may be self-inflicted. Last week I changed > blocksize to 512k, and began amrmtape and amlabel with the oldest tape > first and working backward day by day. I run backups 5 nights per week with > a cycle of 13 tapes (see below). I would have thought that this would have > allowed the change in blocksize to run seamlessly. Maybe not. I'm now > suspecting that by amrmtape --cleanup, this caused Amanda to bork and fall > back to level 0 backups. She did this two nights in a row!!! > > Anyway, I'm going to hold off any further concerns until I finish a > complete tapecycle. If the problem continues after that point, I'll pick > back up. > > Relevant lines from amanda.conf: > > dumpcycle 5 days > runspercycle 5 > tapecycle 13 tapes > runtapes 1 > flush-threshold-dumped 50 > bumpsize 10 Mbytes > bumppercent 0 > bumpmult 1.5 > bumpdays 2 > > Kind regards, > Chris >
When I introduce a lot of DLEs into the disklist (or start a new amanda instance) I typically will comment out all the new DLEs and only uncomment a few each amdump run. Jon -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
