This is a multi-part message in MIME format.
--------------030600090507030305040200
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
There is a potential problem with David's approach ...
Each *individual* backup will run the longer frequency every 4th week.
A couple of scenarios might make my point clearer:
* Do the 26-day backup this Sunday. For the next 3 weeks, frequency
1-day will be run.
But ...
1) Let's say Client A backup fails this Sunday. The 26-day backup for it
will run next Sunday and will remain one week off from all the others.
2) Let's say we add a new Client N after this Sunday. It will use the
26-day backup next Sunday and will remain one week off from all the others.
Maybe it matters to you; maybe not. If I'm backing up to all of my tape
drives, have differing retentions and one retention per tape and MPX,
maybe I don't want the "rogue" backups potentially hogging drives. But
maybe that's a lot of "ifs"! A similar situation affects me, but I
live with it. The more drives you have, the less it probably matters.
Hope this helps, wayne
David Rock wrote:
>* Rob De Langhe <rob.delanghe AT telindus DOT be> [2004-04-21 07:46]:
>
>
>>Hi,
>>
>>anyone has suggestions on best practice to exclude the run of a specific
>>instance of weekly backups ?
>>
>>We have full backups going on, on a weekly basis running on Sundays.
>>
>>At the same time, we have archiving backups of the same files going on, on a
>>4-weekly basis also running on Sundays.
>>
>>So we want to avoid that, scheduled by Veritas, every 4th week there would
>>be 2 sets of backups running : the weekly full, plus the 4-weekly archiving.
>>
>>How to achieve this ?
>>
>>Any suggestions are kindly appreciated !
>>
>>
>
>If you set these up as two different schedules, this is pretty easy. Set
>up the normal weekly schedule, and then set up a 4week schedule that is
>set to run at the same time. The trick is NetBackup will look at the
>4week schedule as being less frequent than the weekly schedule.
>NetBackup gives a higher priority to the schedule with the lowest
>frequency and does not run both. So do something like this:
>
>weekly - Full - Sunday - 23:00 - Frequency 1 day
>4week - Full - Sunday - 23:00 - Frequency 26 days
>
>(The 26 days should make it ready to run every 4th Sunday)
>
>
>
--------------030600090507030305040200
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body>
There is a potential problem with David's approach ...<br>
<br>
Each *individual* backup will run the longer frequency every 4th week.
<br>
<br>
A couple of scenarios might make my point clearer:<br>
<br>
* Do the 26-day backup this Sunday. For the next 3 weeks, frequency
1-day will be run. <br>
<br>
But ...<br>
<br>
1) Let's say Client A backup fails this Sunday. The 26-day backup for
it will run next Sunday and will remain one week off from all the
others.<br>
<br>
2) Let's say we add a new Client N after this Sunday. It will use the
26-day backup next Sunday and will remain one week off from all the
others.<br>
<br>
Maybe it matters to you; maybe not. If I'm backing up to all of my tape
drives, have differing retentions and one retention per tape and MPX,
maybe I don't want the "rogue" backups potentially hogging drives. But
maybe that's a lot of "ifs"! A similar situation affects me, but I
live with it. The more drives you have, the less it probably matters.<br>
<br>
Hope this helps, wayne<br>
<br>
David Rock wrote:
<blockquote cite="mid20040422220409.GC21059 AT wdfs.graniteweb DOT com"
type="cite">
<pre wrap="">* Rob De Langhe <a class="moz-txt-link-rfc2396E"
href="mailto:rob.delanghe AT telindus DOT be"><rob.delanghe AT telindus DOT
be></a> [2004-04-21 07:46]:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
anyone has suggestions on best practice to exclude the run of a specific
instance of weekly backups ?
We have full backups going on, on a weekly basis running on Sundays.
At the same time, we have archiving backups of the same files going on, on a
4-weekly basis also running on Sundays.
So we want to avoid that, scheduled by Veritas, every 4th week there would
be 2 sets of backups running : the weekly full, plus the 4-weekly archiving.
How to achieve this ?
Any suggestions are kindly appreciated !
</pre>
</blockquote>
<pre wrap=""><!---->
If you set these up as two different schedules, this is pretty easy. Set
up the normal weekly schedule, and then set up a 4week schedule that is
set to run at the same time. The trick is NetBackup will look at the
4week schedule as being less frequent than the weekly schedule.
NetBackup gives a higher priority to the schedule with the lowest
frequency and does not run both. So do something like this:
weekly - Full - Sunday - 23:00 - Frequency 1 day
4week - Full - Sunday - 23:00 - Frequency 26 days
(The 26 days should make it ready to run every 4th Sunday)
</pre>
</blockquote>
<br>
</body>
</html>
--------------030600090507030305040200--
|
