This is a multi-part message in MIME format.
------=_NextPart_000_0102_01C48B9B.2F2A7580
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
What is the NetBackup Version?
=20
In the Version 4.5 you can do the schedule by calendar. You can =
choice
to do the backup every Sunday to full backup, If happened a error you =
can
rerun the backup manually or specify how many times the Netbackup will =
try
do a backup again, and do a another schedule daily by frequency to do =
the
diff backups.
=20
T+
=20
Carlos Alberto Lima dos Santos
Eng. de Computa=E7=E3o
Campinas-SP - Brasil
* carlos_listas AT yahoo.com DOT br=20
_____ =20
De: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] Em nome de Edelson, =
Tracie
Enviada em: quinta-feira, 26 de agosto de 2004 14:29
Para: veritas-bu AT mailman.eng.auburn DOT edu
Assunto: [Veritas-bu] scheduling question
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_000_0102_01C48B9B.2F2A7580
Content-Type: text/html;
charset="iso-8859-1"
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=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1458" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D444122321-26082004> What is the NetBackup=20
Version?</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D444122321-26082004></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D444122321-26082004> In the Version 4.5 you can =
do the=20
schedule by calendar. You can choice to do the backup every Sunday =
to full=20
backup, If happened a error you can rerun the backup manually or specify =
how many times the Netbackup will try do a backup again, and do a =
another=20
schedule daily by frequency to do the diff backups.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D444122321-26082004></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D444122321-26082004>T+</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D444122321-26082004></SPAN></FONT> </DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D444122321-26082004><!-- Converted from text/rtf format -->
<P><B><FONT face=3DTahoma color=3D#000040 size=3D2>Carlos Alberto Lima =
dos=20
Santos<BR></FONT></B><I></I><I><FONT face=3DTahoma color=3D#000040 =
size=3D1>Eng. de=20
Computa=E7=E3o</FONT></I><BR><I></I><I><FONT face=3DTahoma =
color=3D#000040=20
size=3D1>Campinas-SP - Brasil</FONT></I><BR><B></B><B><FONT =
face=3DWingdings=20
color=3D#000040 size=3D2>*</FONT></B><FONT face=3DWingdings =
color=3D#000040 size=3D1><FONT=20
face=3D"Courier New"></FONT></FONT> <FONT=20
face=3D"Times New Roman">carlos_listas AT yahoo.com DOT br</FONT><B></B><B></B>
=
</P></SPAN></FONT></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Dpt-br dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>De:</B> =
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>Em nome de =
</B>Edelson,=20
Tracie<BR><B>Enviada em:</B> quinta-feira, 26 de agosto de 2004=20
14:29<BR><B>Para:</B> =
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Assunto:</B>=20
[Veritas-bu] scheduling question<BR></FONT><BR></DIV>
<DIV></DIV>
<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>
------=_NextPart_000_0102_01C48B9B.2F2A7580--
|
