|
bpimagelist returns with the "start time" of the image.
The image name contains the ctime of the start of the image.
Because of these reasons, I believe that "Freq is measured when the backup STARTS if you are using Freq based scheduling."
But I have no proof and I have read conflicting posts from users using different versions of Netbackup.
Again I ask for documentation from:
OpenVision
VERITAS Software
symantec
So, is it midnight on the first stoke of midnight or the last stroke of midnight?
I have been looking for said "official" documentation for almost a decade.
>>> Steve <[EMAIL PROTECTED]> 5/18/2006 9:08 AM >>>
Sorry, I had the INTERVAL and FREQ parts backwards and it was not very clear. The write-up below may make more sense:
Freq is measured when the backup ends if you are using Freq based scheduling. If you are using Interval mode scheduling when the backup ends does not matter. Its a bit confusing but as everyone knows there are only 2 types of schedules, calendar and freq. But if you chose freq based schedules then bpsched has 2 processing modes it can use and that is freq and interval. Here are a few snips from a verbose bpsched that shows this.
06:03:03 [2116.2240] <4> in_interval_mode: IN INTERVAL MODE
.....
15:31:26 [1820.1800] <4> in_interval_mode: NOT INTERVAL MODE -- not an integral number of days
15:31:26 [1820.1800] <4> backup_due: using frequency-only mode
Hope that helps
Steve
On 5/18/06, Steve <[EMAIL PROTECTED]> wrote:
I hate to send this out 3 times in a row but it does address the question. I hate to send this out 3 times in a row but it does address the question. Freq ONLY depends on when the backup ends for INTERVAL based schedules. This is what used to cause sliding windows of old. Freq based Freq schedules do not care when the backup last finished.
Below is a small write-up concerning the 2 processing types that NBU uses for Freq. based schedules. Freq based schedules can use either Freq or Interval mode depending on the Interval setting that is chosen.
Frequency based Sched vs Interval
Interval = 24 hour frequency(24 hours, 1 day, 7days ect.)
Frequency = Any non-24 hour frequency (12 hours, 27, hours 80 hours ect.)
If Interval mode scheduling is used the time of the backup is calculated from when the windows was initially open. So if the window opens for a class-sched at 8pm on a Monday and the frequency is 24 hours but the backup does not start until Midnight the job will be available to run at 8pm the next day. But if the sched was setup to run every 26 hours then that same job would not be available to run until 2am the next day.
Hope that helps
On 5/18/06, Bob Stump <[EMAIL PROTECTED] > wrote:
"frequency is measured from when the backup ends"
Will someone please provide me the documentation that states this?
I have been looking for it for literally YEARS...
Yes - and be aware that the frequency is measured from when the backup ends!
I use 5 days on my "weekly" backups, and 12 hours on my nightly's. :-)
t.
---
Tristan Ball
System Administrator
Vision Systems
+61-3-9211-7064
Hi,
I'm trying to understand how this actually works as I think it works a little differently from how I thought it worked. We have a couple of polices that do a full backup weekly, with the frequency set to 1 week. However, the jobs didn't run on the weekend; there were no errors, they just didn't run.
The only reason I can think of this happening is the job falling outside of the start window. From what I've read, the frequency is the minimum amount of tim that must pass before the next schedule runs, which means that we should probably set the weekly jobs to having a frequency of 6 days to avoid it falling outside the start window. Would this be correct?
Cheers,
---------------------------------------------------------------------
Tim Wilkinson
I.T. Support Officer
Science Corporate Information Systems
Defence Science & Technology Organisation
Department of Defence
Tel: (02) 96921484
Fax: (02) 96921562
Email: [EMAIL PROTECTED]
|
