rather simple question around dumpcycle
At a customer we try to run 2 configs in parallel. I discussed this setup here in the past, and bring it back up again ;-) - We run a daily config with 58 tapes. This is run on weekdays 1-4 only. Until now we had: dumpcycle 2 weeks runspercycle 8 Would it be better to have dumpcycle 8 days ? - The 2nd config runs on FR and SAT: "weekly". With full backups only. I want to force lev0 here and archive a set of tapes every 3 months -> quartal and year archive sets. I have 31 active tapes there right now, a full set of data takes around 4-5 tapes. What parameters do you users use for such a setup? dumpcycle? runspercycle? - I'd appreciate optimization tips here. It seems my dumpcycles are too short so I get issues with too much data dumped per week etc
Re: rather simple question around dumpcycle
> On Nov 11, 2019, at 10:34 AM, Stefan G. Weichinger wrote: > > > At a customer we try to run 2 configs in parallel. > > I discussed this setup here in the past, and bring it back up again ;-) > > - > > We run a daily config with 58 tapes. > This is run on weekdays 1-4 only. > > Until now we had: > > dumpcycle 2 weeks > runspercycle 8 > > Would it be better to have > > dumpcycle 8 days ? > > - > > The 2nd config runs on FR and SAT: "weekly". With full backups only. > > I want to force lev0 here and archive a set of tapes every 3 months -> > quartal and year archive sets. > > I have 31 active tapes there right now, a full set of data takes around > 4-5 tapes. > > What parameters do you users use for such a setup? > > dumpcycle? runspercycle? > > - > > I'd appreciate optimization tips here. It seems my dumpcycles are too > short so I get issues with too much data dumped per week etc I run a similar config: daily for everyday (we include Saturday and Sunday too, cuz some people work then & make important changes - no big difference for you). I think you are good with config1 being “2 weeks, runspercycle 8”. That means it will do a FULL on each disk at least once every 2 weeks.Doing it once every 8 days is NOT really what you want. My alternate config is run once a month, but I think my params would work for your “every weekend” too. dumpcycle 0 # I plan to run it whenever I want to tapecycle 9000 # I will always give you a fresh tape. You would say 31. runtimes 3# the max you’ll allow to catch all the level-0 backups My dumptype definition includes strategy noinc #don’t even calculate partial sizes skip-incr yes # belt and suspenders record no # daily incrementals are based on the daily level-0s. # If I let this record, I think that messes the daily incrementals. And in true belt-plus-suspender-plus physically holding up the pants: I run a cronjob before each archive run that does amadmin force * (test this a little, manually — I found I needed to do force *.. ) Hope this is a little help. Deb Baddorf Fermilab
Re: rather simple question around dumpcycle
Am 11.11.19 um 22:10 schrieb Debra S Baddorf: > runtimes 3# the max you’ll allow to catch all the level-0 backups that parameter is not recognized here ;-) Aside from that: thanks a lot for your feedback, Debra
Re: rather simple question around dumpcycle
On Mon, Nov 11, 2019 at 05:34:14PM +0100, Stefan G. Weichinger wrote: > > At a customer we try to run 2 configs in parallel. > > I discussed this setup here in the past, and bring it back up again ;-) > > - > > We run a daily config with 58 tapes. > This is run on weekdays 1-4 only. > > Until now we had: > > dumpcycle 2 weeks > runspercycle 8 > > Would it be better to have > > dumpcycle 8 days ? > > - > > The 2nd config runs on FR and SAT: "weekly". With full backups only. > > I want to force lev0 here and archive a set of tapes every 3 months -> > quartal and year archive sets. > > I have 31 active tapes there right now, a full set of data takes around > 4-5 tapes. > > What parameters do you users use for such a setup? > > dumpcycle? runspercycle? > > - > > I'd appreciate optimization tips here. It seems my dumpcycles are too > short so I get issues with too much data dumped per week etc >>> End of included message <<< What about a single config incremental only. Via crontab, force level 0's when you want, maybe every other weekend FRI & SAT. The SAT dump serves as level 0's for the incrementals. The FRI dump can be used for your archiving as needed. Take the tape out of use but retain logs etc. Add a new tape to keep the same # of tapes in use. Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: rather simple question around dumpcycle
> On Nov 11, 2019, at 4:24 PM, Stefan G. Weichinger wrote: > > Am 11.11.19 um 22:10 schrieb Debra S Baddorf: > >> runtimes 3# the max you’ll allow to catch all the level-0 backups > > that parameter is not recognized here ;-) > > Aside from that: thanks a lot for your feedback, Debra I thing that was an “autocorrect” aka “monkey correct” runtapes (Yup, I WATCHED it change it to the wrong thing, this time. But I insisted!) Deb
