Hi Again Would it be simplier to create a Monthly config for a monthly full backup that con exists with my Daily. If So is there and examples of this setup.
Cheers On Tue, 2005-06-14 at 16:43 -0400, Gene Heskett wrote: > On Tuesday 14 June 2005 09:03, Chuck Amadi Systems Administrator > wrote: > >Hi Great > > > >Yes I am going to use 10 tapes in total and reuse the first tape > > after 10 week days worth of backups. > > > >Thus is it fine to pull the last Friday tape at the end of the Month > > for archiving and then re-label the tape I pulled. > > Unless you are doing an 'always full' all the time, then that tape you > remove on friday is not going to be a complete, usable image you can > restore from and get a full restore. I think in a previous message > you said you were using dat's but didn't spec which one. But here, > even the largest DDS4 wouldn't begin to hold an always full of this 2 > machine home system. > > Also, keep in mind that amanda performs index file housekeeping based > on the tapelist. That means the indice files for that tape will be > removed from amandas database when that tape is > replaced/reused/relabled. This is one of the reasons that I wrote a > wrapper that appends this data to the individual tape after amanda is > done. You'll have to reduce the tapes size slightly in the tapetype > entry in order to ascertain there is space on the tape for its > indices. I write the config directory too just in case its a bare > metal recovery, but that file is relatively small compared to the > indice tree's current 805 megs here. > > Things to ponder... > > >Thanks I am nearly there . > > > >Cheers > > > >On Tue, 2005-06-14 at 08:21 -0400, Jon LaBadie wrote: > >> On Tue, Jun 14, 2005 at 12:45:07PM +0100, Chuck Amadi Systems > Administrator wrote: > >> > Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day > >> > week. Thus every fortnight. > >> > I am correctly concluding I need only a tapecycle of 10 tapes > >> > I hope to pull out the last Friday tape in that Month to archive > >> > and thus label another tape to replace it. > >> > > >> > Here's my config file. > >> > > >> > dumpcycle 0 weeks # the number of days in the normal dump > >> > cycle runspercycle 1 # the number of amdump runs in > >> > dumpcycle days # (4 weeks * 5 amdump runs per week -- just > >> > weekdays) > >> > tapecycle 10 tapes # the number of tapes in rotation > >> > # 4 weeks (dumpcycle) times 5 tapes per > >> > week (just > >> > # the weekdays) plus a few to handle > >> > errors that > >> > >> Think of tapecycle as how many "different" tapes amanda must use > >> before it will reuse the first one. In your setup, it looks like > >> full backups every run, tapecycle is as critical as a setup doing > >> mixed full and incrementals. Set it to whatever you want, or are > >> comfortable, having amanda not overwrite before being allowed to > >> reuse. If you want the last 10 full dumps to be sure to be > >> around, then set it to 10. If the last 5 is comfortable, you can > >> set it to 5, but still use 10 tapes. Amanda will only check that > >> at least 5 are still the most recent. > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
