This is a multipart message in MIME format.
--=_alternative 006BA66C862570BC_=
Content-Type: text/plain; charset="us-ascii"
Wayne,
For the last year we've implemented multiple RMAN schedules of
different retention lengths within a single policy. You must overlap an
"Automatic XXX Backup" schedule under an
"Application Backup" schedule.
What counts is the Type selected for each schedule. An
"Application Backup" type actually retains data and the retention length
is meaningful. The "Automatic <Full/Cum/Diff> Backup" specifies the start
time of the automatic backup, whether is is Full, Cumulative, or
Differential, but the retention length is meaningless.
You can create additional "Application Backup" schedules with
different retention lengths and the other applicable schedule attributes.
It is the "Application Backup" which counts within the catalog.
If you want to initiate the RMAN backup from the Master Server
like most other policies, create an "Automatic Full Backup" schedule. This
schedule's "Start Window" will initiate an RMAN backups where the window
of this "Automatic Full Backup" and ANY "Application Backup" schedules
within the same "Oracle" policy you create.
You must remember the "Automatic Full Backup" is a dummy schedule
used to control the initiation of the "Application Backup". The retention
schedule of the "Application Backup" which control the images used in
recovery
Within an "Oracle" Policy Type, upon creation there is one default
schedule of Schedule Type "Application Backup". This schedule's name is
"Default-Application-Backup". You can rename it. But no two schedules
within a policy may have the same name. The name itself is not "special".
The "Default-Application-Backup" ersatz User Backup is often used by our
DBAs for one-off manual RMAN backups. Don't delete this. Just don't use
it for normal scheduled RMAN backups. Fill in all the empty time left
unoccupied by specific automatic
backups.
For example, here are three pairs of RMAN full backup schedules
within one policy:
One-off DBA: Frequency (Sun-Fri - 16 hours), retained for 21 days
Application Backup Default-Application-Backup
(the Start Window should not
overlap the following driver schedules)
(no driver - above used as true
User Backup)
daily: Frequency (Sun-Fri - 16 hours), retained for 21 days
Application Backup rman-daily
Automatic Full Backup rman-daily-trigger
most weekends: Calendar (Recur WeekDay - 2/3/4/Last Saturday), retained
for 2 months
Application Backup rman-weekly
Automatic Full Backup rman-weekly-trigger
monthly: Calendar (Recur WeekDay - 1st Saturday), retained for 7
months
Application Backup rman-monthly
Automatic Full Backup rman-monthly-trigger
Remember, you can also schedule "Automatic Cumulative Incremental
Backup" or "Automatic Differential Incremental Backup" as your trigger
schedule.
If you administrate Legato Networker, the separation of schedules
and retentions will be more familiar. Otherwise, this looks very odd at
first.
Read thru the example a few times, and implement a test schedule
in order to become more familiar with it.
Michael F. Lavelle Abbott Labs,
Sr. Storage Engineer, CIT 100 Abbott Park Rd, AP14B-1
Ph: 847.937.1195 (Page:389.5746) Abbott Park IL 60064-6042
Wayne T Smith <wtsmith AT maine DOT edu>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
11/17/2005 10:50 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
cc: (bcc: Michael F Lavelle/LAKE/CHMS/ABBOTT)
Subject: [Veritas-bu] How to use multiple "Application-Backup"
schedules?
How to use multiple "Application-Backup" schedules?
Background:
I'm using the (v5.1) NetBackup Oracle Agent. All of my "Automatic"
backup schedules have used my one "Default-Application-Backup"
schedule. I have noticed that the retention period in the
*automatic* backup is *not* used for storage. The retention on the
Application-Backup schedule is always used!
I just recently defined a 2nd Application-Backup schedule with a
longer retention period and now it seems to be always used. Note:
Both of my Application-Backup schedules have 24x7 windows.
Question: How do I (is it possible?!) sometimes use the longer retention
period?
For example, my file system backups all do full backups early
Saturday morning. Every 4th one of these is for a much longer
retention than the "normal" ones. Can I do this with my Oracle
Agent backups? (I realize that I must tell RMAN to save information
for at least the longer time).
Thanks for sharing your experience ... I'm fairly new to Oracle Agent
usage.
cheers, wayne
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 006BA66C862570BC_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="Arial">Wayne,</font>
<br><font size=2 face="Arial"> For the last year
we've implemented multiple RMAN schedules of different retention lengths within
a single policy.</font><font size=3 face="Times New Roman"> You must overlap an
"Automatic XXX Backup" schedule under an "Application
Backup" schedule.<br>
</font><font size=2 face="Arial"><br>
What counts is the Type selected for each schedule.
An "Application Backup" type actually retains data and the
retention length is meaningful. The "Automatic <Full/Cum/Diff>
Backup" specifies the start time of the automatic backup, whether is is
Full, Cumulative, or Differential, but the retention length is meaningless.<br>
You can create additional "Application
Backup" schedules with different retention lengths and the other
applicable schedule attributes. It is the "Application Backup"
which counts within the catalog.</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
If you want to initiate the RMAN backup from the
Master Server like most other policies, create an "Automatic Full
Backup" schedule. This schedule's "Start Window" will
initiate an RMAN backups where the window of this "Automatic Full
Backup" and ANY "Application Backup" schedules within the same
"Oracle" policy you create.</font><font size=3 face="Times New
Roman"> </font><font size=2 face="Arial"><br>
You must remember the "Automatic Full
Backup" is a dummy schedule used to control the initiation of the
"Application Backup". The retention schedule of the
"Application Backup" which control the images used in
recovery</font><font size=3 face="Times New Roman"> <br>
</font>
<br><font size=2 face="Arial"> Within an
"Oracle" Policy Type, upon creation there is one default schedule of
Schedule Type "Application Backup". This schedule's name is
"Default-Application-Backup". You can rename it. But no
two schedules within a policy may have the same name. The name itself is
not "special".</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"> The
"Default-Application-Backup" ersatz User Backup is often used by our
DBAs for one-off manual RMAN backups. Don't delete this. Just don't
use it for normal scheduled RMAN backups</font><font size=3 face="Times New
Roman">. Fill in all the empty time left unoccupied by specific automatic
backups.</font><font size=2 face="Arial"><br>
<br>
For example, here are three pairs of RMAN full
backup schedules within one policy:</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Courier New"><br>
One-off DBA: Frequency (Sun-Fri - 16 hours), retained for 21
days</font><font size=3 face="Times New Roman"> </font><font size=2
face="Courier New"><br>
Application Backup
Default-Application-Backup</font><font size=3 face="Times New Roman">
</font><font size=2 face="Courier New"><br>
(the Start Window
should not overlap the following driver schedules)</font><font size=3
face="Times New Roman"> </font><font size=2 face="Courier New"><br>
(no driver - above used
as true User Backup)</font><font size=3 face="Times New Roman"> </font><font
size=2 face="Courier New"><br>
daily: Frequency (Sun-Fri - 16 hours), retained for
21 days</font><font size=3 face="Times New Roman"> </font><font size=2
face="Courier New"><br>
Application Backup
rman-daily</font><font size=3 face="Times New Roman"> </font><font
size=2 face="Courier New"><br>
Automatic Full Backup
rman-daily-trigger<br>
most weekends: Calendar (Recur WeekDay - 2/3/4/Last Saturday), retained for 2
months</font><font size=3 face="Times New Roman"> </font><font size=2
face="Courier New"><br>
Application Backup
rman-weekly</font><font size=3 face="Times New Roman"> </font><font
size=2 face="Courier New"><br>
Automatic Full Backup
rman-weekly-trigger<br>
monthly: Calendar (Recur WeekDay - 1st Saturday), retained
for 7 months</font><font size=3 face="Times New Roman"> </font><font size=2
face="Courier New"><br>
Application Backup
rman-monthly</font><font size=3 face="Times New Roman"> </font><font
size=2 face="Courier New"><br>
Automatic Full Backup
rman-monthly-trigger</font><font size=3 face="Times New Roman"><br>
</font><font size=2 face="Arial"><br>
Remember, you can also schedule "Automatic
Cumulative Incremental Backup" or "Automatic Differential Incremental
Backup" as your trigger schedule.</font>
<br>
<br><font size=2 face="Arial"> If you administrate
Legato Networker, the separation of schedules and retentions will be more
familiar. Otherwise, this looks very odd at first.</font>
<br><font size=2 face="Arial"> Read thru the example
a few times, and implement a test schedule in order to become more familiar
with it.</font>
<br><font size=2 face="Arial"><br>
</font>
<br><font size=2 face="Arial"><br>
Michael F. Lavelle
Abbott Labs, <br>
Sr. Storage Engineer, CIT
100 Abbott Park Rd, AP14B-1<br>
Ph: 847.937.1195 (Page:389.5746) Abbott Park IL
60064-6042</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Wayne T Smith <wtsmith AT maine DOT
edu></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">11/17/2005 10:50 AM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
veritas-bu AT mailman.eng.auburn DOT edu</font>
<br><font size=1 face="sans-serif"> cc:
(bcc: Michael F Lavelle/LAKE/CHMS/ABBOTT)</font>
<br><font size=1 face="sans-serif"> Subject:
[Veritas-bu] How to use multiple
"Application-Backup" schedules?</font></table>
<br>
<br>
<br><font size=2 face="Courier New">How to use multiple
"Application-Backup" schedules?<br>
<br>
Background: <br>
<br>
I'm using the (v5.1) NetBackup Oracle Agent. All of my
"Automatic"<br>
backup schedules have used my one
"Default-Application-Backup"<br>
schedule. I have noticed that the retention period in
the<br>
*automatic* backup is *not* used for storage. The retention on
the<br>
Application-Backup schedule is always used! <br>
<br>
I just recently defined a 2nd Application-Backup schedule with
a<br>
longer retention period and now it seems to be always used.
Note:<br>
Both of my Application-Backup schedules have 24x7 windows.<br>
<br>
<br>
Question: How do I (is it possible?!) sometimes use the longer retention <br>
period? <br>
<br>
For example, my file system backups all do full backups early<br>
Saturday morning. Every 4th one of these is for a much
longer<br>
retention than the "normal" ones. Can I do this
with my Oracle<br>
Agent backups? (I realize that I must tell RMAN to save
information<br>
for at least the longer time).<br>
<br>
<br>
Thanks for sharing your experience ... I'm fairly new to Oracle Agent usage.<br>
<br>
cheers, wayne<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
--=_alternative 006BA66C862570BC_=--
|
