In the message dated: Mon, 24 Nov 2014 16:59:30 +0100,
The pithy ruminations from =?UTF-8?B?RMOhbmllbCBMLg==?= on
<[Bacula-users] Retention periods & full backup> were:
=> Hello Bacula Users,
=>
=> I have a problem.
=> I hope someone can point me to the right direction.
=
Hello,
Backups "1 month back" is a time frame, not a time point. The time frame moves
over the days of the month, regardless of full, differential, incremental
backups running. Your backup definition has to taken into account this time
frame. So in my opinion you need at least 2 full backup volu
Hello Daniel,
One solution for this is to retain your full backups for 2 months if you
want to keep your differential and incremental backups valid during all the
second month until the second full is done.
Best regards,
Ana
On Mon, Nov 24, 2014 at 12:59 PM, Dániel L.
wrote:
> Hello Bacula Use
Hello Bacula Users,
I have a problem.
I hope someone can point me to the right direction.
My schedules are the following:
Run = Full 1st fri at 23:05
Run = Differential 2nd-5th fri at 23:05
Run = Incremental sun-thu at 23:05
I would like keep backups for 1 month.
See my retention p
Hi,
I have a dummy "None"-client for copy jobs which by the time I just copied
from the docs. Now I saw that this client has retention periods of 0 and
all my data gets pruned after 6 months. I added file and job retentions to
the client but the database entry is not updated (even after copy job
Am Thursday 02 April 2009 22:13:41 schrieb John Drescher:
> > File Retention = 30 days
> > Job Retention = 6 months
> > Volume Retention = 1 year
>
> Fine. After 30 days you will either only be able to do a full restore
> or have to use bscan before restoring.
Correct.
>
> > Then am I correct in
> File Retention = 30 days
> Job Retention = 6 months
> Volume Retention = 1 year
>
Fine. After 30 days you will either only be able to do a full restore
or have to use bscan before restoring.
>
> Then am I correct in thinking that when I back up my catalog, I should only
> keep it for 6 months?
M
Hi,
If I have the following retention settings
File Retention = 30 days
Job Retention = 6 months
Volume Retention = 1 year
Then am I correct in thinking that when I back up my catalog, I should only
keep it for 6 months? My thinking being that the catalog itself contains 6
months of Job records
On Wed, Oct 8, 2008 at 1:54 PM, John Drescher <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 8, 2008 at 1:47 PM, RYAN vAN GINNEKEN <[EMAIL PROTECTED]> wrote:
>> What is stopping bacula from using volume 44???
>> <[EMAIL PROTECTED]> wrote:
>>
> Last Written time on that was 2008-10-02 02:42:07
>
> so then
What is stopping bacula from using volume 44???
<[EMAIL PROTECTED]> wrote:
> On Wed, Oct 8, 2008 at 11:49 AM, RYAN vAN GINNEKEN
> <[EMAIL PROTECTED]> wrote:
> > Hello all i am still having difficulty with retention periods and
> the like could someone kindly help me with this.
> >
> > Basically fo
On Wed, Oct 8, 2008 at 11:49 AM, RYAN vAN GINNEKEN <[EMAIL PROTECTED]> wrote:
> Hello all i am still having difficulty with retention periods and the like
> could someone kindly help me with this.
>
> Basically for the local intranet i would like bacula to take a full back at
> the first of each
Hello all i am still having difficulty with retention periods and the like
could someone kindly help me with this.
Basically for the local intranet i would like bacula to take a full back at the
first of each month ie (October 1) then incremental each night until the first
of the next month. H
On Wednesday 21 February 2007 13:16, Ralf Gross wrote:
> Kern Sibbald schrieb:
> > It is quite possible that Bacula will re-create all the pools the next
> > time the Director is restarted.
>
> Indeed. And the pool id's now are different too. Is there any way that I
> can prevent bacula to re-creat
Kern Sibbald schrieb:
> It is quite possible that Bacula will re-create all the pools the next time
> the Director is restarted.
Indeed. And the pool id's now are different too. Is there any way that I can
prevent bacula to re-create the deleted pools? I'm sure at some point someone
(maybe me) wi
On Wednesday 21 February 2007 10:30, Ralf Gross wrote:
> Kern Sibbald schrieb:
> > 1. You might want to use two different databases, one for regular backups
> > and one for archives. This will clearly separate your archive data from
> > your regular data.
>
> Basically this working now. But I'm a
Kern Sibbald schrieb:
> 1. You might want to use two different databases, one for regular backups and
> one for archives. This will clearly separate your archive data from your
> regular data.
Basically this working now. But I'm a bit confused about the handling
of pools and the assigned volume
Ralf Gross schrieb:
> But now bacula-dir does not start with the second catalog:
>
> 20-Feb 22:07 bacula-dir: Fatal error: Database not created or server not
> running.
> 20-Feb 22:07 bacula-dir: Fatal error: Could not open Catalog
> "ArchiveCatalog",
> database "bacula_archive".
> 20-Feb 22:
Kern Sibbald schrieb:
> > I created differnt pools for regular backups and long term archival. I
> > think the retention times are reasonable. We are aware that we can't handle
> > a _real_ long time archival (copy to new media, verify...), but we want to
> > keep the volumes for 30 years.
>
> Be
Just a few quick responses ...
On Tuesday 20 February 2007 17:24, Ralf Gross wrote:
> Hi,
>
> I had a very simple setup for the last 12 months.
>
> * backup everything to tape and keep the last 2 weeks before
> recycling old volumes
> * keep the monthly tape(s) for 3 years
>
> I didn't care much
Hi,
I had a very simple setup for the last 12 months.
* backup everything to tape and keep the last 2 weeks before
recycling old volumes
* keep the monthly tape(s) for 3 years
I didn't care much about the retention periods of the monthly tapes. I
just set the Volume Retention to 3 years for th
20 matches
Mail list logo
