> > "dumpcycle 4 weeks" > > This is a very long time for amanda to go thru the system making > sure she has one full backup of everything in your disklist. Most > run this at 1 week, or 7 days, although a business user may want > that to be a bit shorter just so there is less to play catchup with > in the event you are forced to recover from the last full backup. > A weeks worth of business transactions to have to repeat is > drudgery that sexytaries have been known to quit over.
Well I put 4 weeks because it was preposed that we do a full backup once a month. The amount of data that I am dealing is 2.1TB If I understand you creectly if I shorten it to something like 1 week then it will be eaiser forme to do a restore. Were there other benefits as well to shortning this options? > > "runspercycle 4 weeks" > > If amanda takes the weeks arguement as it takes it in terms of > dumpcycle, this is a total of 28 runs in one of your very elongated > dumpcycles, intimating that it will be run every nite. Nothing > wrong with the every night run, most of us do it. Most situations > would seem to want something in the line of 7 and 7 for the above > pair of variables. You may have to stretch it out to make it fit > on the tapes, but given amanda's ability to try to equalize the > amount of data taped each night once she gets into the rythm of > things, you probably could take the size of the data after > compression, divide that by runspercycle, and by adjusting > runspercycle and dumpcycle so it uses about 3/4ths of a tape per > run. If I choose 7 then your right I am going to have to strech it out but I am not sure how to do this. With the size of data that I am dealing with this will seem terribly complicated. I take if I go this way then I am going to have to play with the bumpsize. > > "tapecycle 25 tapes" > > Here you have insufficient tapes for the elongated dumpcycle chosen > as it would take a minimum of 28 tapes to satisfy the runspercycle > above. Amanda therefore has no tape she can use for the next > backup unless you label at least 3 new tapes and increment the > tapecycle to match. I am curious why you say 28 instead of 25. I think you added three because of the option I have runtapes. Also another question what exactly do you mean by increment the tape cycle. > > 25 tapes is normally enough, but I'd shorten both the dumpcycle and > runspercycle until it both fits on the tape, and you have at least > 2 full dumpcycles worth of full backups on hand at any one time. I > haven't run into this, so I have no idea if amanda will reuse the > oldest tape if you do nothing more than reduce the dumpcycle and > runspercycle to match the tapecycle. Its worth a try just for > effects. :-) Could you be a little more specific as to the benefit of this :) > > Not having any idea of how much data you have to cover, what I would > do is to reduce the dumpcycle and runspercycle in unison, first to > 14 days each, and let amanda play catchup with that for one > dumpcycle or maybe two. Watching the tape usage report amanda > mails you, then reduce it one or 2 each cycle until she is using > about 3/4ths of a tape every night. With only a 46 gig drive here, > part of which is an rsync'd mirror of my gateway machine, I'm only > averageing about 50% usage per nightly run on DDS2 tapes. At 4g > rated capacity, its about 2gigs that actualy gets written to tape > after compression. And its all covered at least once a week. I am dealing will a little bit over 2.1tb of data. What do you mean play catch up with that for one dumpcycle or maybe two. Forgive me lack of sleep but the Sentence starting with Watching the tape usage is confusing. Your scenerio states you have a 46gig drive and that your full backups is about 2gigs in capcity is that accurate. Can you possibly give me a scenrio of my case. -- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9P+Y5awsElDuSDs0RAgxoAJ40NBfXWSP5dwsRK6AWZRXP6fNm+wCgpWf4 MwLEwsq3TDVGR8ntq3+w65k= =qTeY -----END PGP SIGNATURE-----
