Chances are you have a one week frequency, and your duration between the
start/activation time of your last backup and the end of the window was
greater than 7 days.
|- Last backup -|
|-------------------------- 1 week frequency --------------------|
|- Sunday backup window -|
In the example above, you have last week's backup and the backup window for
Sunday's backup? A frequency backup with a frequency of one week won't start
until it's been more than 604800 (24 * 7 * 3600) seconds since the start time
of the last good backup. If 604800 seconds later than that start time is
beyond the window you specified, it won't run until the next time a Window is
open. See how the frequency period in my drawing goes just past the end of the
backup window? It won't run until the next time the backup runs.
This is why I use calendar-based schedules for anything other than backups that
run once a day. I'd create a calendar based schedule that's set to run every
Sunday, tell it to allow it run after run day, and give it an open window on
Sunday-Thursday. That way if it doesn't run on Sunday, it'll run again on
Monday, Tuesday, etc, until it gets it right. But next week's backup will
still run on Sunday.
If you want to stick with frequency schedules, you could also leave the window
only on Sunday and set the frequency to less than a week (e.g. four days).
That'll make sure the frequency will always be less than the desired time, and
it will always run on Sunday. (I don't like that method, because I would also
want it to run on Monday/Tuesday night if Sunday failed, but doing that with
frequency backups gets really yucky.)
I also concur with the other person who said run it manually just to see
everything's working ok. Just realize that if you're using frequency-based
backups, manual backups count. If you run a manual backup on Monday and tell
it to run a backup once a week, it will NOT run a backup on the next Sunday
because it hasn't been a week since the last backup. (Another reason why I'm
not a fan.)
---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies
________________________________________
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Daniel
Sigrist
Sent: Tuesday, July 10, 2007 11:45 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Doubt about scheduled backups
Hi all,
I have a doubt about scheduled backups. I'm doing oracle backups (10g and 9i)
using rman and netbackup 4.5_SP6. I create a policy that do a full database
backup once a week (on Saturday). I set the frequency of the policy to 1 week,
and my start windows is from Saturday 06:00 am to Monday 06:00 am. So I tested
my policy doing a manual backup on Wednesday. On Saturday the scheduled policy
didn't ran. Netbackup simply ignored my policy. Is this a expected behavior?
Because I set my policy to run once a week and I ran manually on Wednesday,
then netbackup only will run the policy again after a week?
Thank you advance,
__________________________
Daniel Abramides Sigrist
DBA Oracle Projeto SIGRES
Tel: (11) 3824-2074
Telefonica Pesquisa e Desenvolvimento
Rua Brigadeiro Galvao, 291 - 7º Andar
Barra Funda - Sao Paulo, SP
dasigrist AT tpd.com DOT br
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
