This is a multipart message in MIME format.
--=_alternative 006345DA8625701D_=
Content-Type: text/plain; charset="us-ascii"
Hello,
I believe the discussion so far has taken the wrong track...
Each policy may contain several different schedules.
All schedules within the policy must use the same File Selections,
Clients, and Attributes (incl Storage Unit, queue Priority, Multiple Data
Stream toggle, etc...).
! 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. !
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.
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.
We have 3 schedules:
full-daily: Frequency (Sun-Fri - 16 hours), retained
for 21 days
full: Calendar (Recur WeekDay - 2/3/4/Last
Saturday), retained for 2 months
full-month: Calendar (Recur WeekDay - 1st Saturday),
retained for 7 months
The 7 month retention is local site custom (Host Properties ->
Master Server -> Properties -> Retention Periods).
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.
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
"Hampus Lind" <hampus.lind AT rps.police DOT se>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
06/11/2005 08:02 AM
To: "Kim Hennvall" <kim AT hjemmekontor DOT nu>, "Dean" <dean.deano
AT gmail DOT com>
cc: <veritas-bu AT mailman.eng.auburn DOT edu>
Subject: Re: [Veritas-bu] database policy and several
schedules...
Hi!
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..
Thanks anyway!
Best regards,
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 -----
From: Kim Hennvall
To: 'Hampus Lind'
Sent: Saturday, June 11, 2005 11:31 AM
Subject: RE: [Veritas-bu] database policy and several schedules...
Hi Hampus.
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.
best regards
Kim Hennvall
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!
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??
Best regards,
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
--=_alternative 006345DA8625701D_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="Arial">Hello,</font>
<br><font size=2 face="Arial"> I believe the
discussion so far has taken the wrong track...</font>
<br>
<br><font size=2 face="Arial"> Each policy may
contain several different schedules.</font>
<br><font size=2 face="Arial"> All schedules within
the policy must use the same File Selections, Clients, and Attributes (incl
Storage Unit, queue Priority, Multiple Data Stream toggle, etc...).</font>
<br>
<br><font size=2 face="Arial">! <b>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. !</b></font>
<br>
<br><font size=2 face="Arial"> 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.</font>
<br>
<br><font size=2 face="Arial"> 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.</font>
<br><font size=2 face="Arial"> We have 3
schedules:</font>
<br><font size=2><tt>
full-daily: Frequency (Sun-Fri - 16 hours), retained
for 21 days</tt></font>
<br><font size=2><tt>
full: Calendar (Recur
WeekDay - 2/3/4/Last Saturday), retained for 2 months</tt></font>
<br><font size=2><tt>
full-month: Calendar (Recur WeekDay - 1st Saturday),
retained for 7 months</tt></font>
<br>
<br><font size=2 face="Arial"> The 7 month retention
is local site custom (Host Properties -> Master Server -> Properties
-> Retention Periods).</font>
<br><font size=2 face="Arial"> 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.</font>
<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>"Hampus Lind" <hampus.lind
AT rps.police DOT se></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 08:02 AM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
"Kim Hennvall" <kim AT hjemmekontor DOT
nu>, "Dean" <dean.deano AT gmail DOT com></font>
<br><font size=1 face="sans-serif"> cc:
<veritas-bu AT mailman.eng.auburn DOT edu></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="Arial">Hi!</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">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..</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">Thanks anyway!</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">Best regards,</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">MVH / Hampus Lind<br>
Rikspolisstyrelsen<br>
National Police Board<br>
Tele arb: +46 (0)8 - 401 99 43<br>
Tele mob: +46 (0)70 - 217 92 66<br>
E-mail: </font><a href=mailto:hampus.lind AT rps.police DOT se><font size=3
color=blue face="Times New Roman"><u>hampus.lind AT rps.police DOT
se</u></font></a>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">----- Original Message ----- </font>
<br><font size=3 face="Times New Roman"><b>From:</b> </font><a href=mailto:kim
AT hjemmekontor DOT nu><font size=3 color=blue face="Times New Roman"><u>Kim
Hennvall</u></font></a><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman"><b>To:</b> </font><a
href=mailto:hampus.lind AT rps.police DOT se><font size=3 color=blue
face="Times New Roman"><u>'Hampus Lind'</u></font></a><font size=3 face="Times
New Roman"> </font>
<br><font size=3 face="Times New Roman"><b>Sent:</b> Saturday, June 11, 2005
11:31 AM</font>
<br><font size=3 face="Times New Roman"><b>Subject:</b> RE: [Veritas-bu]
database policy and several schedules...</font>
<br>
<br><font size=2 color=blue face="Arial">Hi Hampus.</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 color=blue face="Arial">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.</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 color=blue face="Arial">best regards</font>
<br><font size=2 color=blue face="Arial">Kim Hennvall</font>
<br>
<br>
<hr><font size=2 face="Tahoma"><b>From:</b> veritas-bu-admin AT
mailman.eng.auburn DOT edu [mailto:veritas-bu-admin AT mailman.eng.auburn DOT
edu] <b>On Behalf Of </b>Hampus Lind<b><br>
Sent:</b> 10. juni 2005 21:33<b><br>
To:</b> veritas-bu AT mailman.eng.auburn DOT edu<b><br>
Cc:</b> Fredrik Dahlberg<b><br>
Subject:</b> [Veritas-bu] database policy and several schedules...</font><font
size=3 face="Times New Roman"><br>
</font>
<br><font size=2 face="Arial">Hi all!</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">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??</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">Best regards,</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">MVH / Hampus Lind<br>
Rikspolisstyrelsen<br>
National Police Board<br>
Tele arb: +46 (0)8 - 401 99 43<br>
Tele mob: +46 (0)70 - 217 92 66<br>
E-mail: </font><a href=mailto:hampus.lind AT rps.police DOT se><font size=2
color=blue face="Arial"><u>hampus.lind AT rps.police DOT se</u></font></a>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman"> </font>
<br>
<br>
--=_alternative 006345DA8625701D_=--
|
