Ok, you've rubbed my nose in it long enough ;). BTW, I never agreed to your bet, thankfully!
Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 281-584-4693 Keeping People and Information Connected® ▪ http://availability.sungard.com/ P Think before you print CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system. "bob944" <bob...@attglobal.net> Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 06/04/2009 01:26 AM Please respond to bob...@attglobal.net To <rusty.ma...@sungard.com> cc veritas-bu@mailman.eng.auburn.edu, steve.hud...@ironmountain.com Subject Re: [Veritas-bu] Frequency Based Schedules > > > [bob944] and the longest frequency will win--the > > > monthly will run. > > > > [Rusty] Bob, that's what usually happens, but that's > > not why. The trump card is the retention level, which > > usually is matched to a longer frequency, but may not > > always be the case. > > [bob944] I'm always glad to learn new things, but I'm > not sure this is one of them. To me, the logic _has_ > to be that longer frequency wins, else a longer-frequency > schedule would never win out--and this has always been > the behavior that I've observed and relied upon. But > since I have never set up, say, a weekly full with a > retention shorter than its "matching" daily diff, maybe > it really works as you say, but I'll need to see it to > believe it. > > Any interest on ... oh, I dunno.. how about a bottle of > single-malt Scotch to the winner? ;-) > > "One test is worth a thousand expert opinions." I win. When multiple schedules are due; the schedule with the longer frequency interval runs; retention has nothing to do with it. Details on request, but here's the edited summary of the class and bpdbjobs: # /usr/openv/netbackup/bin/admincmd/bppllist TEST-std-freq -L Policy Name: TEST-std-freq Policy Type: Standard (0) Residence: TEST-dsu Client/HW/OS/Pri: mouse Solaris Solaris9 2068001349 0 0 0 ? Include: /etc/hosts Schedule: full-f2h-r1d [goofy name guide: freq:2hours-ret:1day Type: FULL (0) Frequency: 0+ day(s) (7200 seconds) Retention Level: 22 (1 day) Day Open Close W-Open W-Close [Sun-Sat] 020:00:00 028:00:00 020:00:00 028:00:00 Schedule: diff-f1h-r1w [freq:1hour-ret:1week] Type: INCR (1) Frequency: 0+ day(s) (3600 seconds) Retention Level: 0 (1 week) [Sun-Sat] 020:00:00 028:00:00 020:00:00 028:00:00 # date Wed Jun 3 19:58:01 EDT 2009 "full" has a frequency of two hours and a retention of one day. "diff" has a frequency of one hour and a retention of one week. # /usr/openv/netbackup/bin/admincmd/bpdbjobs|head -20 Time Type State Status Policy Schedule 01:00 Backup Done 0 TEST-std-freq diff-f1h-r1w 00:00 Backup Done 0 TEST-std-freq full-f2h-r1d 23:00 Backup Done 0 TEST-std-freq diff-f1h-r1w 22:00 Backup Done 0 TEST-std-freq full-f2h-r1d 21:00 Backup Done 0 TEST-std-freq diff-f1h-r1w 20:00 Backup Done 0 TEST-std-freq full-f2h-r1d Summary: despite its shorter retention, the schedule with the longer frequency interval always wins out. Hmmmm. Macallen is a little pricey; Glenlivet will do nicely. :-) _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
