This is a multipart message in MIME format.
--=_alternative 000E71B98625701F_=
Content-Type: text/plain; charset="us-ascii"
Hi,
OK, so a general discussion of multiple schedules within one
policy and implementing multiple retention schedules within this policy
has (via inattention by some responders to the original topic) moved into
a more interesting and less well understood area of NetBackup policy
management.
For the last year we've implemented multiple RMAN schedules of
different retention lengths within a single policy.
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 as Kim noted
yesterday, no two schedules within a policy may have the same name. The
name itself is not "special".
However, the "Default-Application-Backup" ersatz User Backup is often
used by our DBAs
for one-off RMAN backups. Don't delete this. Just don't use it for
normal scheduled RMAN backups
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.
Here is where our RMAN implementation seems to differ from most
others I've heard of. While the "Application Backup" can stand alone, it is
like a "UserBackup" Schedule
Type.
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". Tthe retention schedule of the "Application
Backup" which control the images used in recovery
A parallel example to the Oracle Cold Backup I gave yesterday is
three pairs of schedules:
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-driver
most weekends: Calendar (Recur WeekDay - 2/3/4/Last Saturday), retained
for 2 months
Application Backup rman-weekly
Automatic Full Backup rman-weekly-driver
monthly: Calendar (Recur WeekDay - 1st Saturday), retained for 7
months
Application Backup rman-monthly
Automatic Full Backup rman-monthly-driver
Disclosure: We have not implemented these specific schedules
above. Our implementation uses two Application Backups and only one
driver, but the above example mirrors the more complicated real
implementation for Cold Backups I gave yesterday. It also illustrates one
good use of the Default-Application-Backup schedule in a larger policy.
Michael F. Lavelle Abbott Labs,
Sr. Storage Engineer, CIT 100 Abbott Park Rd, AP14B-1
Phone: 847.937.1195 (Fx:935.9725) Abbott Park IL 60064-6042
Charles Ballowe <cballowe AT gmail DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
06/11/2005 11:52 PM
Please respond to Charles Ballowe
To: David Rock <dave-bu AT graniteweb DOT com>, veritas-bu AT
mailman.eng.auburn DOT edu
cc:
Subject: Re: [Veritas-bu] database policy and several
schedules...
The trick with databases, in order to get the multiple retentions, is
to have (at least with Oracle + RMAN) RMAN send some values back to
netbackup to tell it which policy and schedule to use handle the
backup as. I think the values are NB_ORA_CLASS and NB_ORA_SCHED but I
could be off - I haven't had any need to do that in a while and the
scripts I had to implement it are at a previous job.
This is also needed if you have different databases on a host and
they're covered by different policies as the connect back to the host
will match the first policy that contains that host.
-Charlie
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 000E71B98625701F_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="Arial">Hi,</font>
<br><font size=2 face="Arial"> OK, so a general
discussion of multiple schedules within one policy and implementing multiple
retention schedules within this policy has (via inattention by some responders
to the original topic) moved into a more interesting and less well understood
area of NetBackup policy management.</font>
<br>
<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>
<br>
<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 as
Kim noted yesterday, no two schedules within a policy may have the same name.
The name itself is not "special".</font>
<br><font size=2 face="Arial"> However, the
"Default-Application-Backup" ersatz User Backup is often used by our
DBAs for one-off RMAN backups. Don't delete this. Just don't use it
for normal scheduled RMAN backups</font>
<br><font size=2 face="Arial"> 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>
<br>
<br><font size=2 face="Arial"> Here is where our
RMAN implementation seems to differ from most others I've heard of. While
the "Application Backup" can stand alone, it is like a
"UserBackup" Schedule Type.</font>
<br><font size=2 face="Arial"> 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>
<br><font size=2 face="Arial"> You must remember the
"Automatic Full Backup" is a dummy schedule used to control the
initiation of the "Application Backup". Tthe retention schedule
of the "Application Backup" which control the images used in
recovery</font>
<br>
<br><font size=2 face="Arial"> A parallel example to
the Oracle Cold Backup I gave yesterday is three pairs of schedules:</font>
<br>
<br><font size=2 face="Courier New">One-off DBA: Frequency (Sun-Fri - 16
hours), retained for 21 days</font>
<br><font size=2 face="Courier New">
Application Backup Default-Application-Backup</font>
<br><font size=2 face="Courier New">
(the Start Window should not overlap the following driver
schedules)</font>
<br><font size=2 face="Courier New">
(no driver - above used as true User Backup)</font>
<br><font size=2 face="Courier New">daily:
Frequency (Sun-Fri - 16 hours), retained for 21 days</font><font size=3
face="Times New Roman"> </font>
<br><font size=2 face="Courier New">
Application Backup rman-daily</font>
<br><font size=2 face="Courier New">
Automatic Full Backup rman-daily-driver<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>
<br><font size=2 face="Courier New">
Automatic Full Backup rman-weekly-driver<br>
monthly: Calendar (Recur WeekDay - 1st Saturday), retained
for 7 months</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Courier New">
Application Backup rman-monthly</font>
<br><font size=2 face="Courier New">
Automatic Full Backup rman-monthly-driver<br>
</font>
<br>
<br><font size=2 face="Courier New"> Disclosure: We
have not implemented these specific schedules above. Our implementation
uses two Application Backups and only one driver, but the above example mirrors
the more complicated real implementation for Cold Backups I gave yesterday.
It also illustrates one good use of the Default-Application-Backup
schedule in a larger policy.</font>
<br>
<br>
<br><font size=2 face="Arial"><br>
<br>
Michael F. Lavelle
Abbott Labs, <br>
Sr. Storage Engineer, CIT
100 Abbott Park Rd, AP14B-1<br>
Phone: 847.937.1195 (Fx:935.9725) Abbott Park IL
60064-6042<br>
<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Charles Ballowe <cballowe AT gmail DOT
com></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">06/11/2005 11:52 PM</font>
<br><font size=1 face="sans-serif">Please respond to Charles Ballowe</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
David Rock <dave-bu AT graniteweb DOT com>,
veritas-bu AT mailman.eng.auburn DOT edu</font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
Re: [Veritas-bu] database policy and several
schedules...</font></table>
<br>
<br>
<br><font size=2 face="Courier New">The trick with databases, in order to get
the multiple retentions, is<br>
to have (at least with Oracle + RMAN) RMAN send some values back to<br>
netbackup to tell it which policy and schedule to use handle the<br>
backup as. I think the values are NB_ORA_CLASS and NB_ORA_SCHED but I<br>
could be off - I haven't had any need to do that in a while and the<br>
scripts I had to implement it are at a previous job.<br>
<br>
This is also needed if you have different databases on a host and<br>
they're covered by different policies as the connect back to the host<br>
will match the first policy that contains that host.<br>
<br>
-Charlie <br>
<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 000E71B98625701F_=--
|
