This is a multi-part message in MIME format.
------=_NextPart_000_002B_01C570D9.7E68F8F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi all!
I`am sorry for the confusion... I was wondering about online database =
backup to same policy as the Subject of my email (database policy and =
several schedules) may give away...
Thanks for all info!!
MVH / Hampus Lind
Rikspolisstyrelsen
National Police Board
Tele arb: +46 (0)8 - 401 99 43
Tele mob: +46 (0)70 - 217 92 66
E-mail: hampus.lind AT rps.police DOT se
----- Original Message -----=20
From: Michael F Lavelle=20
To: Hampus Lind=20
Cc: Dean ; Kim Hennvall ; veritas-bu AT mailman.eng.auburn DOT edu ; =
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
Sent: Saturday, June 11, 2005 8:03 PM
Subject: Re: [Veritas-bu] database policy and several schedules...
Hello,=20
I believe the discussion so far has taken the wrong track...=20
Each policy may contain several different schedules.=20
All schedules within the policy must use the same File =
Selections, Clients, and Attributes (incl Storage Unit, queue Priority, =
Multiple Data Stream toggle, etc...).=20
! However, each schedule has an independent Schedule Type =
(Calendar or Freq.), Retention Period, Media Multiplexing, # of Copies, =
and, yes, you can over-ride the Storage Unit on a per-schedule basis. =
!=20
You can also exclude File Selections with a schedule specific =
exclude_list.<Policy>.<Schedule>. However, it's a bear to maintain. =
One could attempt this in order to have one policy per client. It's one =
way of doing things, but at the opposite end of the spectrum of where my =
environment is at.=20
As an example, there is a turnkey application running in our =
environment with an Oracle v8 runtime embedded beneath the application. =
There is (apparently) no known method to get a hot backup of the =
application data with the Oracle data (RMAN to disk?), so we have been =
asked to run cold backups 365 days of the year.=20
We have 3 schedules:=20
full-daily: Frequency (Sun-Fri - 16 hours), =
retained for 21 days=20
full: Calendar (Recur WeekDay - =
2/3/4/Last Saturday), retained for 2 months=20
full-month: Calendar (Recur WeekDay - 1st =
Saturday), retained for 7 months=20
The 7 month retention is local site custom (Host Properties -> =
Master Server -> Properties -> Retention Periods).=20
Remember, if the full-month uses 6 month retention, how old is =
the oldest backup in the catalog at 6 months + 2 days from one =
particular full-month? It's the next most recent full-month and it's 5 =
months and 2 days old. If your customer has been told backups are =
retained for 6 months, you better make sure you can live up to that and =
all other assurances you have given.=20
Michael F. Lavelle Abbott Labs,=20
Sr. Storage Engineer, CIT 100 Abbott Park Rd, =
AP14B-1
Phone: 847.937.1195 (Fx:935.9725) Abbott Park IL 60064-6042
"Hampus Lind" <hampus.lind AT rps.police DOT se>=20
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu=20
06/11/2005 08:02 AM=20
=20
To: "Kim Hennvall" <kim AT hjemmekontor DOT nu>, "Dean" =
<dean.deano AT gmail DOT com>=20
cc: <veritas-bu AT mailman.eng.auburn DOT edu>=20
Subject: Re: [Veritas-bu] database policy and =
several schedules...=20
Hi!=20
=20
Yeah, thats the way we do it here as well, i just want to check if =
there had been some changes to this one lately.. To bad it hasent..=20
=20
Thanks anyway!=20
=20
Best regards,=20
=20
MVH / Hampus Lind
Rikspolisstyrelsen
National Police Board
Tele arb: +46 (0)8 - 401 99 43
Tele mob: +46 (0)70 - 217 92 66
E-mail: hampus.lind AT rps.police DOT se=20
=20
=20
----- Original Message -----=20
From: Kim Hennvall=20
To: 'Hampus Lind'=20
Sent: Saturday, June 11, 2005 11:31 AM=20
Subject: RE: [Veritas-bu] database policy and several schedules...=20
Hi Hampus.=20
=20
You will have to have different policies for each retention category. =
This was atleast the only way with versions up to 5.1, and i don't think =
they have changed it with MPs. I have created 2 policies for this =
daily_full (1 month retention), and monthly_full (12 months retention) =
to come around this one. It's the default- application-backup that =
controls this one.=20
=20
best regards=20
Kim Hennvall=20
-------------------------------------------------------------------------=
-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu =
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Hampus =
Lind
Sent: 10. juni 2005 21:33
To: veritas-bu AT mailman.eng.auburn DOT edu
Cc: Fredrik Dahlberg
Subject: [Veritas-bu] database policy and several schedules...
Hi all!=20
=20
Is there any smart way to have several schedules with different =
retention (i.e incr_daily, full_weekly, full_monthly) within the same =
policy?? Or do we need to seperate all these schedules to different =
policies still??=20
=20
Best regards,=20
=20
MVH / Hampus Lind
Rikspolisstyrelsen
National Police Board
Tele arb: +46 (0)8 - 401 99 43
Tele mob: +46 (0)70 - 217 92 66
E-mail: hampus.lind AT rps.police DOT se=20
=20
=20
------=_NextPart_000_002B_01C570D9.7E68F8F0
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>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2627" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I`am sorry for the confusion... I was =
wondering=20
about online database backup to same policy as the Subject of my email =
(database=20
policy and several schedules) may give away...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for all info!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>MVH / Hampus =
Lind<BR>Rikspolisstyrelsen<BR>National=20
Police Board<BR>Tele arb: +46 (0)8 - 401 99 43<BR>Tele mob: +46 (0)70 - =
217 92=20
66<BR>E-mail: <A=20
href=3D"mailto:hampus.lind AT rps.police DOT se">hampus.lind AT rps.police DOT
se</A></=
FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3DMichael.F.Lavelle AT abbott DOT com=20
href=3D"mailto:Michael.F.Lavelle AT abbott DOT com">Michael F Lavelle</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dhampus.lind AT rps.police DOT se=20
href=3D"mailto:hampus.lind AT rps.police DOT se">Hampus Lind</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Ddean.deano AT gmail DOT com=20
href=3D"mailto:dean.deano AT gmail DOT com">Dean</A> ; <A =
title=3Dkim AT hjemmekontor DOT nu=20
href=3D"mailto:kim AT hjemmekontor DOT nu">Kim Hennvall</A> ; <A=20
title=3Dveritas-bu AT mailman.eng.auburn DOT edu=20
=
href=3D"mailto:veritas-bu AT mailman.eng.auburn DOT edu">veritas-bu AT mailman
DOT eng.=
auburn.edu</A>=20
; <A title=3Dveritas-bu-admin AT mailman.eng.auburn DOT edu=20
=
href=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT
edu">veritas-bu-admin@=
mailman.eng.auburn.edu</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Saturday, June 11, 2005 =
8:03=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Veritas-bu] =
database policy=20
and several schedules...</DIV>
<DIV><BR></DIV><BR><FONT face=3DArial size=3D2>Hello,</FONT> <BR><FONT =
face=3DArial=20
size=3D2> I believe the discussion so far =
has taken=20
the wrong track...</FONT> <BR><BR><FONT face=3DArial size=3D2> =
=20
Each policy may contain several different schedules.</FONT> =
<BR><FONT=20
face=3DArial size=3D2> All schedules within =
the policy=20
must use the same File Selections, Clients, and Attributes (incl =
Storage Unit,=20
queue Priority, Multiple Data Stream toggle, etc...).</FONT> =
<BR><BR><FONT=20
face=3DArial size=3D2>! <B>However, each =
schedule has=20
an independent Schedule Type (Calendar or Freq.), Retention Period, =
Media=20
Multiplexing, # of Copies, and, yes, you can over-ride the Storage =
Unit on a=20
per-schedule basis. !</B></FONT> =
<BR><BR><FONT=20
face=3DArial size=3D2> You can also exclude =
File=20
Selections with a schedule specific=20
exclude_list.<Policy>.<Schedule>. However, it's a =
bear to=20
maintain. One could attempt this in order to have one policy per =
client.=20
It's one way of doing things, but at the opposite end of the =
spectrum of=20
where my environment is at.</FONT> <BR><BR><FONT face=3DArial =
size=3D2> =20
As an example, there is a turnkey application =
running in=20
our environment with an Oracle v8 runtime embedded beneath the =
application.=20
There is (apparently) no known method to get a hot backup of the =
application data with the Oracle data (RMAN to disk?), so we have been =
asked=20
to run cold backups 365 days of the year.</FONT> <BR><FONT =
face=3DArial=20
size=3D2> We have 3 schedules:</FONT> =
<BR><FONT=20
size=3D2><TT> =
full-daily:=20
Frequency (Sun-Fri - 16 hours), retained =
for 21=20
days</TT></FONT> <BR><FONT size=3D2><TT> =
=20
full: =
=20
Calendar (Recur WeekDay - 2/3/4/Last Saturday), retained for 2=20
months</TT></FONT> <BR><FONT size=3D2><TT> =
=20
full-month: Calendar =
(Recur=20
WeekDay - 1st Saturday), retained for 7 months</TT></FONT> =
<BR><BR><FONT=20
face=3DArial size=3D2> The 7 month =
retention is local=20
site custom (Host Properties -> Master Server -> Properties =
->=20
Retention Periods).</FONT> <BR><FONT face=3DArial size=3D2> =
=20
Remember, if the full-month uses 6 month retention, how old is =
the=20
oldest backup in the catalog at 6 months + 2 days from one particular=20
full-month? It's the next most recent full-month and it's 5 =
months and 2=20
days old. If your customer has been told backups are retained =
for 6=20
months, you better make sure you can live up to that and all other =
assurances=20
you have given.</FONT> <BR><BR><FONT face=3DArial =
size=3D2><BR><BR>Michael F.=20
Lavelle =
=20
Abbott Labs, <BR>Sr. Storage =
Engineer, CIT=20
100 =
Abbott Park=20
Rd, AP14B-1<BR>Phone: 847.937.1195 (Fx:935.9725) Abbott =
Park=20
IL 60064-6042<BR><BR></FONT><BR><BR><BR>
<TABLE width=3D"100%">
<TBODY>
<TR vAlign=3Dtop>
<TD>
<TD><FONT face=3Dsans-serif size=3D1><B>"Hampus Lind"=20
<hampus.lind AT rps.police DOT se></B></FONT> <BR><FONT =
face=3Dsans-serif=20
size=3D1>Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>
=
<P><FONT face=3Dsans-serif size=3D1>06/11/2005 08:02 AM</FONT> =
<BR></P>
<TD><FONT face=3DArial size=3D1> =
</FONT><BR><FONT=20
face=3Dsans-serif size=3D1> To: =
=20
"Kim Hennvall" <kim AT hjemmekontor DOT nu>,
"Dean"=20
<dean.deano AT gmail DOT com></FONT> <BR><FONT
face=3Dsans-serif=20
size=3D1> cc: =20
<veritas-bu AT mailman.eng.auburn DOT edu></FONT> <BR><FONT
=
face=3Dsans-serif size=3D1> Subject: =
=20
Re: [Veritas-bu] database policy and several =
schedules...</FONT></TR></TBODY></TABLE><BR><BR><BR><FONT =
face=3DArial=20
size=3D2>Hi!</FONT> <BR><FONT face=3D"Times New Roman" =
size=3D3> </FONT>=20
<BR><FONT face=3DArial size=3D2>Yeah, thats the way we do it here as =
well, i just=20
want to check if there had been some changes to this one lately.. To =
bad it=20
hasent..</FONT> <BR><FONT face=3D"Times New Roman" =
size=3D3> </FONT>=20
<BR><FONT face=3DArial size=3D2>Thanks anyway!</FONT> <BR><FONT=20
face=3D"Times New Roman" size=3D3> </FONT> <BR><FONT face=3DArial =
size=3D2>Best=20
regards,</FONT> <BR><FONT face=3D"Times New Roman" =
size=3D3> </FONT>=20
<BR><FONT face=3D"Times New Roman" size=3D3>MVH / Hampus=20
Lind<BR>Rikspolisstyrelsen<BR>National Police Board<BR>Tele arb: +46 =
(0)8 -=20
401 99 43<BR>Tele mob: +46 (0)70 - 217 92 66<BR>E-mail: </FONT><A=20
href=3D"mailto:hampus.lind AT rps.police DOT se"><FONT face=3D"Times New =
Roman"=20
color=3Dblue size=3D3><U>hampus.lind AT rps.police DOT se</U></FONT></A> =
<BR><FONT=20
face=3D"Times New Roman" size=3D3> </FONT> <BR><FONT =
face=3D"Times New Roman"=20
size=3D3> </FONT> <BR><FONT face=3D"Times New Roman" =
size=3D3>----- Original=20
Message ----- </FONT><BR><FONT face=3D"Times New Roman" =
size=3D3><B>From:</B>=20
</FONT><A href=3D"mailto:kim AT hjemmekontor DOT nu"><FONT face=3D"Times New =
Roman"=20
color=3Dblue size=3D3><U>Kim Hennvall</U></FONT></A><FONT =
face=3D"Times New Roman"=20
size=3D3> </FONT><BR><FONT face=3D"Times New Roman" =
size=3D3><B>To:</B> </FONT><A=20
href=3D"mailto:hampus.lind AT rps.police DOT se"><FONT face=3D"Times New =
Roman"=20
color=3Dblue size=3D3><U>'Hampus Lind'</U></FONT></A><FONT =
face=3D"Times New Roman"=20
size=3D3> </FONT><BR><FONT face=3D"Times New Roman" =
size=3D3><B>Sent:</B> Saturday,=20
June 11, 2005 11:31 AM</FONT> <BR><FONT face=3D"Times New Roman"=20
size=3D3><B>Subject:</B> RE: [Veritas-bu] database policy and several=20
schedules...</FONT> <BR><BR><FONT face=3DArial color=3Dblue =
size=3D2>Hi=20
Hampus.</FONT> <BR><FONT face=3D"Times New Roman" =
size=3D3> </FONT> <BR><FONT=20
face=3DArial color=3Dblue size=3D2>You will have to have different =
policies for each=20
retention category. This was atleast the only way with versions up to =
5.1, and=20
i don't think they have changed it with MPs. I have created 2 policies =
for=20
this daily_full (1 month retention), and monthly_full (12 months =
retention) to=20
come around this one. It's the default- application-backup that =
controls this=20
one.</FONT> <BR><FONT face=3D"Times New Roman" size=3D3> </FONT> =
<BR><FONT=20
face=3DArial color=3Dblue size=3D2>best regards</FONT> <BR><FONT =
face=3DArial=20
color=3Dblue size=3D2>Kim Hennvall</FONT> <BR><BR>
<HR>
<FONT face=3DTahoma size=3D2><B>From:</B> =
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of =
</B>Hampus=20
Lind<B><BR>Sent:</B> 10. juni 2005 21:33<B><BR>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<B><BR>Cc:</B> Fredrik=20
Dahlberg<B><BR>Subject:</B> [Veritas-bu] database policy and several=20
schedules...</FONT><FONT face=3D"Times New Roman" =
size=3D3><BR></FONT><BR><FONT=20
face=3DArial size=3D2>Hi all!</FONT> <BR><FONT face=3D"Times New =
Roman"=20
size=3D3> </FONT> <BR><FONT face=3DArial size=3D2>Is there any =
smart way to=20
have several schedules with different retention (i.e incr_daily, =
full_weekly,=20
full_monthly) within the same policy?? Or do we need to seperate all =
these=20
schedules to different policies still??</FONT> <BR><FONT=20
face=3D"Times New Roman" size=3D3> </FONT> <BR><FONT face=3DArial =
size=3D2>Best=20
regards,</FONT> <BR><FONT face=3D"Times New Roman" =
size=3D3> </FONT>=20
<BR><FONT face=3DArial size=3D2>MVH / Hampus=20
Lind<BR>Rikspolisstyrelsen<BR>National Police Board<BR>Tele arb: +46 =
(0)8 -=20
401 99 43<BR>Tele mob: +46 (0)70 - 217 92 66<BR>E-mail: </FONT><A=20
href=3D"mailto:hampus.lind AT rps.police DOT se"><FONT face=3DArial =
color=3Dblue=20
size=3D2><U>hampus.lind AT rps.police DOT se</U></FONT></A> <BR><FONT=20
face=3D"Times New Roman" size=3D3> </FONT> <BR><FONT =
face=3D"Times New Roman"=20
size=3D3> </FONT> <BR><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_002B_01C570D9.7E68F8F0--
|
