On Thursday 01 August 2002 07:34, Hery Zo RAKOTONDRAMANANA wrote: >Hi all, > >I have a running config for amanda now. Somehow, I had some "out > of tape" errors for the last three dumps. I wanted to adjust my > tapetype (I have a HP Surestore DDS2 4/8Go). >Thought that it's a problem on my tapetype definition so I wanted > to run "tapetype -f /dev/nst0" on my tape server. Unfortunately, > I had an amanda tape on and I think this has erased my datas on > this tape (TestConf03).
It sure did... >TestConf03 is what amanda is expecting for tonight's dump. I'm >hesitating on two options: >- re-label my erased tape to TestConf03 and insert it for > tonight's dump - remove TestConf03 from my amanda cycle. Label > this tape into TestConf(lastnumber)+1 and then use this "new" > tape for tonight's dump. > >Is there something I missed or is there other way to do this? I > think I'll opt for the second solution. I'd do the first by doing an 'amrmtape /config/ tapename' first, so that its records and indexes will be removed from amanda's history files. Then relabel it as the same old number it had before. This won't necessarily put it in the right order in the tapelist, but will use it someplace in the recycle sequence. You could edit the tapelist to restore the order *before* the tape has new data written to it though. Just be sure you don't modify any lines in this file other than moving the newly added by amlabel line for that tape up or down in the listing. The second option should work ok too. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.09% setiathome rank, not too shabby for a WV hillbilly
