Bacula-users

Re: [Bacula-users] Incr/Diff upgrading to Full even after doing a Full?

2010-01-26 23:36:45
Subject: Re: [Bacula-users] Incr/Diff upgrading to Full even after doing a Full?
From: Dan Langille <dan AT langille DOT org>
To: Steve Costaras <stevecs AT chaven DOT com>
Date: Tue, 26 Jan 2010 23:34:14 -0500
Steve Costaras wrote:
> 
> On 01/26/2010 14:50, Arno Lehmann wrote:
>> Hi,
>>
>> 25.01.2010 22:51, Steve Costaras wrote:
>>    
>>> I am running into a problem here.   I have had to purge a previous full
>>> backup for a client machine.   I then manually ran a full backup from
>>> the console.    After that was completed I then tried to manually run an
>>> incremental (as the full took several days to run).   But if I try
>>> either a differential or incremental backup both are upgraded to full's
>>> with the message " No prior or suitable Full backup found in catalog.
>>> Doing FULL backup."
>>>
>>> The full backup is in the catalogue and I can restore files from it.
>>> It's as if there is no link to the full for some reason.
>>>      
>> That's indeed tha case - or it looks like that to me, at least.
>>
>> You have defined different jobs.
>>
>> What you need is one single job defined, and you run that at different
>> levels.
>>
>> Now, in your current situation, try
>>
>> run job=loki-FullBackup level=incremental yes' and see what happens...
>>
>> Unless you want to fiddle with the catalog manually, you'll keep the
>> "funny" job name, but that's all... just remove the lok-DiffBackup and
>> loki-IncrBackup jobs, and use the level override when running jobs and
>> everything should be ok.
>>
>> Arno
> 
> The different jobs were to make running ad-hoc backups of a client 
> outside of the schedule.    All the backup jobs have the same client and 
> fileset.  So are you suggesting that the job name is an index to the 
> catalogue?

Well, sort of, yes.  It doesn't matter that the two jobs have the same 
Client and FileSet.  They are two different jobs.

 > If so then how would you be able to configure bacula to
> run ad-hoc jobs against a client?   They would never match the catalogue?

Issue the run command.  Use the mod option, then alter the job 
parameters to suit.

What do you mean by NEVER match?  You're running the Job, and altering 
the items on the fly.  It's still the same job.  It is the Job Name that 
counts here.

> I also found a reference in a google search that a full backup needs to 
> be run from the schedule not manually for it to be linked?

I believe that to be false.


------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users