On Sat, Jan 11, 2014 at 10:33:26PM -0800, Andrius D. Ilgunas wrote: > Excellent discussion Jon! Thank you so very much for your thoughts!! > > I was aware of Amanda's philosophy of "I want one full dump every dumpcycle > which is n days" and then to let Amanda find the optimal combination of > full/incrementals, and that's one of the reasons that Amanda was so > attractive, other than it uses native compression tools (BIG plus for me). > > Heck, I even learned about the Tower of Hanoi scheme! But one piece of > advice stuck with me, and that is "when restoring data, you don't have time > to try to remember/decipher which files are on which tapes". In other > words, backup / on a regular schedule, even if it'll cost you some disk > space/time....it'll be worth it when it comes time to recover. I suppose I > can make things more complex when I get really bored. ;)
Assuming you have your config keep an index, amrecover is an interactive tool that does this for you. With a date set it can determine which 'tapes' contain the file as of that date. > > As I'm working out the backup plan, it's starting to seem that I'll want to > have a dumpcycle of 7 days, and then keep those weekly full dumps > elsewhere. Again, you are thinking there will be a weekly full dump. Unless that is a separate config that does only full dumps, and you run it once each dumpcycle. Sounds like a lot of duplication of effort. There has been regular talk about adding a feature to extract a set of full dumps. I think amvault is a command that may implement this feature. I'm unsure of its status. Jon -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (609) 477-8330 (C)
