On Fri, Aug 27, 2010 at 10:54:15AM -0400, Valeriu Mutu wrote: > Hi Ranjan, > > My reponses are inline. > > On Fri, Aug 27, 2010 at 11:26:03AM +0530, Ranjan Das wrote: > > Hi Valeriu, > > > > Thank you very much for the guidance. This was very much informative. > > I have another doubt, as this configuration is for weekly backup and if i > > start using this config daily what will happen?? Or in the other way, if we > > schedule daily backups and we dont do it daily and does it at a random > > fashion what will happen, will there be any problem with the integrity of > > data. What are the consequences that will arise if we miss out the correct > > timing.? > > You should sitdown first and decide what your backup strategy will > be. Based on that, decide what the 'dumpcycle' will be. A day, a week, > 2 weeks? Then you should decide how many runs will you do per > 'dumpcycle'. Why wouldn't you be able to do it daily? How many times > per week could you do with certainty? These are questions you have to > answer yourself. > > If you plan on doing backups daily, you'd have to set 'runspercycle' > to 7 (7 runs total; 1 run per day each week, assuming your backup > finishes within one day; AFAIK, you just need a good estimate here). > Ranjan, in his initial post, indicated all dumps were to be full and that they would only be run weekly. Thus there is no "dumpcycle", each dump is its own complete cycle. Thus 0 or 1 is a suitable dumpcycle and there is only 1 dump per cycle, thus runpercycle is 1.
-- Jon H. LaBadie [email protected] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
