I for one, think this would be an excellent topic for a meeting. Amanda is one of the things that's been on my list to learn for quite a while now.
Now, seeing as you seem fairly well versed in it Paul..... --rdp On Thu, 21 Feb 2002, Paul Lussier wrote: > > In a message dated: Thu, 21 Feb 2002 11:03:32 EST > Brian Chabot said: > > >Hello, > > > >I was wonderring if there was a quick and easy HOWTO for Amanda out > >there.... > > No, but she comes with extensice documentation in the docs/ subdir of > the source. If you installed the RPMs from RH, I highly recommend > you 'rpm -e' immediately and install from source. RH not only places > the amanda stuff in really bizarre locations, but they don't even > configure the package properly. Most problems I've seen on the > amanda-user's mailing list over the past couple of years have been > easily solved by installing from source over the RH rpms. > > >Anyone out there have a relatively simple set of instructions for > >getting it up and running with minimal hassle? > > No, other than following the docs/* files. Amanda is an incredibly > complex package, and as a result, it's not *easy* to do anything with > it until you really know and understand how she works. I've been > using Amanda for years, so I'm quite familiar with her quirks and > idiosynchrosies (for a while my wife was referring to Amanda as "the > other woman" because fighting with her cause me to get home so late > so many times :) > > >For those interested, here's what I'm trying to do: > >At work, we need backups made nightly, with weekly fulls. > >Amanda to run on a PIII800/384 Mandrake8.1 to later be moved to an > >Athlon1900+/1024/RH7.2. Tape drive is an HP Surestore Autoloader (1/9) > >with Ultrium tapes. There is about half a TB that needs to be backed up > >at the moment. > > First thing is this: Amanda uses a "dumpcycle" during which you are > guaranteed to get fulldumps done at least once per file system, but > not all at once, nor on the same tape. That's just the way amanda > works. Amanda is designed to load balance everything for you and > take the hassle out of trying to figure out which level to do when. > > That being said, you can do what you want, you just need to be > creative. I've been doing this for quite some time. What I did was > create 2 configurations: 'fulldumps' and 'incrementals'. > > Both run from cron, 'fulldumps' on Sun nights at 23:55, and > 'incrementals' Mon-Fri at 23:55. The 'incrementals' dumpcycle is 17 > days (basically 3 weeks plus a couple extra tapes). The 'fulldumps' > dumpcycle is 1 week, but in the disklist file, I force a level 0 on > every run. > > I offsite the fulldumps, and keep the incrementals on site. This > allows for quick recovery of a file lost to the 'oops factor' > without having to resort to getting the tapes from offsite. > I'm also usually able to restore the file from the most recent backup > rather than being several days or a week off. > > I hope that helps. Feel free to e-mail me privately if you get stuck! > -- Rich Payne http://talisman.mv.com ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
