This is a multi-part message in MIME format.
------_=_NextPart_001_01C48B92.2B20EF22
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Currently, our Oracle database backup schedules are being "managed" by
the database administrators. We provide one schedule that calls their
"wrapper" script -- this script determines, based on the day of the
week, if a full, diff or cumulative to run. It is very basic and does
not account for failed backups - if a full fails to run, it will not run
until the next scheduled day.
=20
We are investigating NetBackup's ability to tie in directly with the
rman utility to run and schedule backups -- so, if a full fails to run
on Monday, it will automatically be rerun the next window (probably the
next day). However, with frequency based backups, this will of course
effectively move the full backup day from Monday to Tuesday until the
next failure moves it again. This is not the behavior the DBA's want --
they want it to run on Sundays except in the case of a failure in which
case it should rerun at the next window -- but then would run on Sundays
again after the failed backup completes.
=20
Other than running the job manually after a failure, doe anyone have any
suggestions?
=20
Thanx!
Tracie Edelson
Unix Systems Administrator
MMS Operations
ATTWS
<mailto:tracie.edelson AT attws DOT com> =20
=20
------_=_NextPart_001_01C48B92.2B20EF22
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D509431817-26082004><FONT face=3DArial =
size=3D2>Currently, our=20
Oracle database backup schedules are being "managed" by the database=20
administrators. We provide one schedule that calls their "wrapper" =
script --=20
this script determines, based on the day of the week, if a full, diff or =
cumulative to run. It is very basic and does not account for failed =
backups - if=20
a full fails to run, it will not run until the next scheduled=20
day.</FONT></SPAN></DIV>
<DIV><SPAN class=3D509431817-26082004><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D509431817-26082004><FONT face=3DArial size=3D2>We are =
investigating=20
NetBackup's ability to tie in directly with the rman utility to run and =
schedule=20
backups -- so, if a full fails to run on Monday, it will automatically =
be rerun=20
the next window (probably the next day). However, with frequency based =
backups,=20
this will of course effectively move the full backup day from Monday to =
Tuesday=20
until the next failure moves it again. This is not the behavior the =
DBA's want=20
-- they want it to run on Sundays except in the case of a failure in =
which case=20
it should rerun at the next window -- but then would run on Sundays =
again after=20
the failed backup completes.</FONT></SPAN></DIV>
<DIV><SPAN class=3D509431817-26082004><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D509431817-26082004><FONT face=3DArial size=3D2>Other =
than running=20
the job manually after a failure, doe anyone have any=20
suggestions?</FONT></SPAN></DIV>
<DIV><SPAN class=3D509431817-26082004><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D509431817-26082004><FONT face=3DArial=20
size=3D2>Thanx!</FONT></SPAN></DIV>
<DIV><SPAN class=3D509431817-26082004>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Tracie =
Edelson</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Unix Systems =
Administrator</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>MMS =
Operations</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>ATTWS</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><A=20
href=3D"mailto:tracie.edelson AT attws DOT com"></A></FONT> </DIV>
<DIV align=3Dleft><FONT face=3DArial=20
size=3D2></FONT> </DIV></SPAN></DIV></BODY></HTML>
=00
------_=_NextPart_001_01C48B92.2B20EF22--
|
