[prev in list] [next in list] [prev in thread] [next in thread]
List: bacula-users
Subject: Re: [Bacula-users] exclude day from schedule
From: Süleyman_Kuran <skuran () ayk ! gov ! tr>
Date: 2013-09-30 14:40:18
Message-ID: 52498D52.1080500 () ayk ! gov ! tr
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Sample schedule is missing weekly and montly pools. Each pools retention
time is different. Daily pool expires after a week. Weekly pool expires
after 4 weeks, monthly pool expires after 12 months. Sometimes it is
necessary to restore previous backups not the latest. This way I have a
wide range of options to restore.
But i'm not sureif itis better by including weekly and montly pool media
to daily pool and set the expiration time to 365 daysand only backup to
daily pool. If you want to restore a 6 months old backup, how do you
configureyour schedule?
On 03/08/13 07:06, Gary Dale wrote:
> On 02/08/13 05:56 PM, Süleyman Kuran wrote:
>> I export the Offsite media on Friday morning from the library and move
>> it to another location. Because there is no monthly backup in the
>> library I also schedule a job a day after the offsite backupin case I
>> need to recover from a montly backup immediately. 1stsat is always 1
>> day after the 1st friday, or am i wrong?
>>
>> You are right that I have two full backups on sunday, it is a mistake.
>> I should remove daily backup on sundays.
>>
> The really strange thing is that you are running a full backup to the
> Daily pool at 3:17 each morning and an incremental each day except
> Sunday at 19:05 to the Weekly pool. Assuming normal business hours, that
> means you are doing an incremental followed by a full each day. Do you
> need two backups each day?
>
> The sample schedule looks pretty good and appears to do what you want:
>
> Schedule {
> Name = "ScheduleTest"
> Run = Full 1st sun at 23:05
> Run = Differential 2nd-5th sun at 23:05
> Run = Incremental mon-sat at 23:05
> }
>
> In fact, you could even simplify it to running a full every Sunday and
> incrementals in between.
>
> Schedule {
> Name = "ScheduleTest2"
> Run = Full sun at 23:05
> Run = Incremental mon-sat at 23:05
> }
>
> If you put the incrementals into a different pool from the
> full/differential then you keep the size of the pool you want offsite
> manageable.
>
> If you are backing up the catalogue (a common practise) along with the
> files, then you don't need to run a full backup to an Offsite pool. I
> just copy the Weekly pool to a removable drive/media each week after the
> weekly Full or Differential backup finishes. This can be done as a
> RunAfterJob script or as a cron job. Should you need to restore the
> pool, just copy it back to your disk drive.
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
[Attachment #5 (text/html)]
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="+1"><font face="Times New Roman">Sample schedu<font
size="+1">le is missing weekly and montly pools<font size="+1"><font
size="+1">. Each pools retention <font size="+1">ti<font
size="+1">me is different. Daily pool expires after a
week. Weekly pool expires after 4 weeks<font size="+1">,
monthly pool expires after 12 months. Sometimes it
is necessary to res<font size="+1">tore previous
backups not the latest. This way I have a wide <font
size="+1">range of options to res<font size="+1">tore.<br>
<br>
<font size="+1">Bu<font size="+1">t i'm not
sure<font size="+1"> if it<font size="+1">
is bette<font size="+1">r</font></font>
by including weekly and montly pool
media to daily po<font size="+1">ol and
set the expiration time to 365 days<font
size="+1"> and only <font size="+1">backup
to daily pool<font size="+1">. If
you wan<font size="+1">t to
restore a 6 month<font
size="+1">s</font> old
backup<font size="+1">, how do
you configure<font size="+1">
your \
schedule?</font></font></font></font></font></font></font></font></font></font><br>
</font></font></font></font></font></font></font></font><br>
<br>
<br>
<br>
</font></font></font>
<div class="moz-cite-prefix">On 03/08/13 07:06, Gary Dale wrote:<br>
</div>
<blockquote cite="mid:51FC81B5.5040800@torfree.net" type="cite">
<pre wrap="">On 02/08/13 05:56 PM, Süleyman Kuran wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I export the Offsite media on Friday morning from the library \
and move it to another location. Because there is no monthly backup in the
library I also schedule a job a day after the offsite backupin case I
need to recover from a montly backup immediately. 1stsat is always 1
day after the 1st friday, or am i wrong?
You are right that I have two full backups on sunday, it is a mistake.
I should remove daily backup on sundays.
</pre>
</blockquote>
<pre wrap="">
The really strange thing is that you are running a full backup to the
Daily pool at 3:17 each morning and an incremental each day except
Sunday at 19:05 to the Weekly pool. Assuming normal business hours, that
means you are doing an incremental followed by a full each day. Do you
need two backups each day?
The sample schedule looks pretty good and appears to do what you want:
Schedule {
Name = "ScheduleTest"
Run = Full 1st sun at 23:05
Run = Differential 2nd-5th sun at 23:05
Run = Incremental mon-sat at 23:05
}
In fact, you could even simplify it to running a full every Sunday and
incrementals in between.
Schedule {
Name = "ScheduleTest2"
Run = Full sun at 23:05
Run = Incremental mon-sat at 23:05
}
If you put the incrementals into a different pool from the
full/differential then you keep the size of the pool you want offsite
manageable.
If you are backing up the catalogue (a common practise) along with the
files, then you don't need to run a full backup to an Offsite pool. I
just copy the Weekly pool to a removable drive/media each week after the
weekly Full or Differential backup finishes. This can be done as a
RunAfterJob script or as a cron job. Should you need to restore the
pool, just copy it back to your disk drive.
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
<a class="moz-txt-link-freetext" \
href="http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk" \
>http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk</a> \
> _______________________________________________
Bacula-users mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:Bacula-users@lists.sourceforge.net">Bacula-users@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" \
href="https://lists.sourceforge.net/lists/listinfo/bacula-users">https://lists.sourceforge.net/lists/listinfo/bacula-users</a>
</pre>
</blockquote>
<br>
</body>
</html>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic