This is a multipart message in MIME format.
--=_alternative 006DC3D385256DC1_=
Content-Type: text/plain; charset="us-ascii"
Mark:
We have been using the Oracle agent to run RMAN backups . Here is my
experience.
When creating a Veritas scheduled policy for an RMAN backup I have three
policies
One for weekly full backups (green)
One for dailty cumulative (aqua)
One Application backup (red) -- I'll explain this one.
When Veritas schedules a Netbackup job it calls a script that runs on the
Unix system and
calls rman with a parameter that refers to the .rcv file
Veritas schedules one "master" job to control the backup. It then
schedules as many
sub jobs that run as "default policy" (I have renamed it to refer to the
instance I am backing up) as it
needs to actually do the backups. For example doing a full backup on a
70G database
will result in one master job and up to 10 or more "child" jobs. If you
look at the activity
monitor details you will see that those are the jobs that actually mount
the tape and
transfer the data to the tape. The master job will terminate when all the
child jobs are complete.
you can change the name of the default policy to whatever you want, just
be sure the
"send"parameter has the exact name (it is case sensitive) you have set for
the "default policy"
I have found that I need unique names for all my "default" policies so
that Vertias does not confuse the
child jobs between my various RMAN backups. I run abouit 17 RMAN backups
every night.
I don't know if this will help, I hope I have understood your question
Regards,
=============================
Carl Stehman
PHI Services Company
202-331-6619
Pager 301-765-2703
ckstehman AT pepco DOT com
"Tindall, Mark" <mark.tindall AT derwent.co DOT uk>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
10/16/2003 09:23 AM
To: "'veritas-bu AT mailman.eng.auburn DOT edu'" <veritas-bu AT
mailman.eng.auburn DOT edu>
cc:
Subject: [Veritas-bu] Veritas NetBackup 3.4 / RMAN 8.1.7
Hi,
up until now I have only used RMAN and NetBackup very rarely due to
database
version / network traffic etc etc. but now am trying to implement it on
two
servers - the first to perform archive log backups and the second to
perform
level0 and level1 backups if the whole database. I am having problems
concerning how to set-up the NetBackup Class schedules so that the backups
run correctly. After having read the NetBackup Adminguide 3.4 and various
posts to this list I am having varying amounts of success.
My problem is that when I start a backup from the NetBackup side (i.e.
change the schedule to Full Automatic / Cumulative / Differential rather
than just Backup Policy) the backup runs, but seems to produce 2 entries
in
the Netbackup monitor. The first entry that appears has the correct Class
and Schedule by it, but seems not to backup any data. The second entry
that
appears to backup data and has the correct Class, but the schedule is set
to
Default Policy even though I am using the "send" command to specifically
select one. Changing the policy type to "Backup Policy" and then running
an
.rcv script file from the appropriate server however produces only one
entry
and works fine - BUT - due to it not using an "Automatic" policy,
NetBackup
will not start it off automatically. How do I configure NetBackup / RMAN
to
automatically perform the backup but only running the required Class /
Schedule and not starting a "Default Policy" therefore causing two entry's
to be displayed ?
Head of .rcv file
============================================================================
===============================
# Begin.
run {
# Assign backup device and required parameters.
allocate channel t1 type 'SBT_TAPE';
send 'NB_ORA_CLASS=PROD_CMS_daily_archivelog_backup,
NB_ORA_SCHED=daily_archivelog_backup, NB_ORA_SERV=dom1-y2k,
NB_ORA_CLIENT=dom6-y2k';
...
..
..
}
============================================================================
===============================
Thanks in advance,
Mark Tindall
Database Administrator
Thomson Scientific
( Tel: 0207 424 2093
( Fax: 0207 344 2815
* Email: mark.tindall AT derwent.co DOT uk
__________________________________________________________________
The information contained in this email is confidential and
intended only for the use of the individual or entity named
above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly
prohibited. Thomson Scientific will accept no responsibility
or liability in respect to this email other than to the addressee.
If you have received this communication in error, please
notify us immediately via email: ITHelpdesk AT derwent.co DOT uk
__________________________________________________________________
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 006DC3D385256DC1_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">Mark:</font>
<br>
<br><font size=2 face="sans-serif">We have been using the Oracle agent to run
RMAN backups . Here is my experience.</font>
<br>
<br><font size=2 face="sans-serif">When creating a Veritas scheduled policy for
an RMAN backup I have three policies</font>
<br>
<br><font size=2 face="sans-serif">One for weekly full backups (green)</font>
<br><font size=2 face="sans-serif">One for dailty cumulative (aqua)</font>
<br><font size=2 face="sans-serif">One Application backup (red) -- I'll explain
this one.</font>
<br>
<br><font size=2 face="sans-serif">When Veritas schedules a Netbackup job it
calls a script that runs on the Unix system and</font>
<br><font size=2 face="sans-serif">calls rman with a parameter that refers to
the .rcv file</font>
<br>
<br><font size=2 face="sans-serif">Veritas schedules one "master" job
to control the backup. It then schedules as many</font>
<br><font size=2 face="sans-serif">sub jobs that run as "default
policy" (I have renamed it to refer to the instance I am backing up) as
it</font>
<br><font size=2 face="sans-serif">needs to actually do the backups. For
example doing a full backup on a 70G database</font>
<br><font size=2 face="sans-serif">will result in one master job and up to 10
or more "child" jobs. If you look at the activity</font>
<br><font size=2 face="sans-serif">monitor details you will see that those are
the jobs that actually mount the tape and </font>
<br><font size=2 face="sans-serif">transfer the data to the tape. The
master job will terminate when all the child jobs are complete.<br>
you can change the name of the default policy to whatever you want, just be
sure the</font>
<br><font size=2 face="sans-serif">"send"parameter has the exact name
(it is case sensitive) you have set for the "default policy"
</font>
<br><font size=2 face="sans-serif"> I have found that I need unique names
for all my "default" policies so that Vertias does not confuse
the</font>
<br><font size=2 face="sans-serif">child jobs between my various RMAN backups.
I run abouit 17 RMAN backups every night.</font>
<br>
<br><font size=2 face="sans-serif">I don't know if this will help, I hope I
have understood your question</font>
<br>
<br><font size=2 face="sans-serif">Regards,<br>
=============================<br>
Carl Stehman<br>
PHI Services Company<br>
202-331-6619<br>
Pager 301-765-2703<br>
ckstehman AT pepco DOT com</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Tindall, Mark"
<mark.tindall AT derwent.co DOT uk></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">10/16/2003 09:23 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'"
<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:
[Veritas-bu] Veritas NetBackup 3.4 / RMAN
8.1.7</font></table>
<br>
<br>
<br><font size=2 face="Courier New">Hi,<br>
<br>
up until now I have only used RMAN and NetBackup very rarely due to database<br>
version / network traffic etc etc. but now am trying to implement it on two<br>
servers - the first to perform archive log backups and the second to perform<br>
level0 and level1 backups if the whole database. I am having problems<br>
concerning how to set-up the NetBackup Class schedules so that the backups<br>
run correctly. After having read the NetBackup Adminguide 3.4 and various<br>
posts to this list I am having varying amounts of success.<br>
My problem is that when I start a backup from the NetBackup side
(i.e.<br>
change the schedule to Full Automatic / Cumulative / Differential rather<br>
than just Backup Policy) the backup runs, but seems to produce 2 entries in<br>
the Netbackup monitor. The first entry that appears has the correct Class<br>
and Schedule by it, but seems not to backup any data. The second entry that<br>
appears to backup data and has the correct Class, but the schedule is set to<br>
Default Policy even though I am using the "send" command to
specifically<br>
select one. Changing the policy type to "Backup Policy" and then
running an<br>
.rcv script file from the appropriate server however produces only one entry<br>
and works fine - BUT - due to it not using an "Automatic" policy,
NetBackup<br>
will not start it off automatically. How do I configure NetBackup / RMAN to<br>
automatically perform the backup but only running the required Class /<br>
Schedule and not starting a "Default Policy" therefore causing two
entry's<br>
to be displayed ?<br>
<br>
<br>
Head of .rcv file<br>
============================================================================<br>
===============================<br>
# Begin.<br>
run {<br>
<br>
# Assign backup device and required parameters.<br>
allocate channel t1 type 'SBT_TAPE';<br>
send 'NB_ORA_CLASS=PROD_CMS_daily_archivelog_backup,<br>
NB_ORA_SCHED=daily_archivelog_backup, NB_ORA_SERV=dom1-y2k,<br>
NB_ORA_CLIENT=dom6-y2k';<br>
...<br>
..<br>
..<br>
}<br>
============================================================================<br>
===============================<br>
<br>
Thanks in advance,<br>
<br>
Mark Tindall<br>
Database Administrator<br>
Thomson Scientific<br>
( Tel: 0207 424 2093<br>
( Fax: 0207 344 2815<br>
* Email: mark.tindall AT derwent.co DOT uk<br>
<br>
<br>
__________________________________________________________________<br>
<br>
The information contained in this email is confidential and <br>
intended only for the use of the individual or entity named <br>
above. If the reader of this message is not the intended <br>
recipient, you are hereby notified that any dissemination, <br>
distribution, or copying of this communication is strictly <br>
prohibited. Thomson Scientific will accept no responsibility <br>
or liability in respect to this email other than to the addressee. </font>
<br><font size=2 face="Courier New">If you have received this communication in
error, please <br>
notify us immediately via email: ITHelpdesk AT derwent.co DOT uk<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>
<br>
--=_alternative 006DC3D385256DC1_=--
|
