Dear All
I think I have resolved this issue.
My mistake was to use a different FileSet for the migration job - it MUST
match the original FileSet used to create the disc file.
The reason some jobs were getting promoted from incremental to full and
others were not was due to a FileSet mismatch - the newer clients did not
have a matching FileSet in the catalog.
I must stop thinking a migration is a clone operation it is a pseudo
"normal" backup operation. I think the manual should warn users of this.
Thanks
Stephen Carr
Kern Sibbald wrote:
> On Tuesday 20 February 2007 04:10, Support wrote:
>> Dear All
>>
>> I have adopted job migration and all seems to work well with clients
>> that
>> were already in the Catalog when the backup was direct to tape (after
>> spooling).
>>
>> I have an old client that had not been backed up for 6 weeks and so had
>> no
>> Full backup in the catalog. The incremental Job on the Client was
>> converted to a Full backup
>
> The above sounds reasonable.
>
>> but this is occurring every day.
>
> You are probably using two different Jobs with different names, which will
> do
> what you describe. For Full, Diff, Inc jobs to work together, you must
> use a
> single Job name.
>
>> It did not
>> happen with direct backup to tape. Other old clients are working
>> correctly
>> and I have not had to add a new client to the system.
>
> Maybe someone else can understand this, but I cannot. It seems you are
> discussing several things at once.
>
>>
>> Now using Job migration it seems the Volume retention period of the
>> migration pool is assigned to the Volume and not the Volume retention
>> period of the the Next Pool.
>
> When a Volume is created it takes on the Volume retention time associated
> with
> the pool in which it is created. This volume retention period is retained
> with the Volume until you explicitly change it. As a consequence, what
> you
> say above does not correspond with how I believe Bacula works.
>
>>
>> Here are the Pools
>>
>> Pool {
>> Name = Migrate-Full
>> Pool Type = Backup
>> Recycle = yes
>> AutoPrune = yes
>> Next Pool = Full
>> Storage = File
>> Maximum Volume Jobs = 100
>> Volume Retention = 1 days
>> Maximum Volumes = 40
>> LabelFormat = Full
>> }
>>
>> Pool {
>> Name = Full
>> Storage = Autochanger
>> Pool Type = Backup
>> Recycle = yes
>> AutoPrune = yes
>> Volume Retention = 35 days
>> }
>>
>> The Migrate-Full pool Volume retention period is small so to conserve
>> disc
>> space.
>>
>> When a client is migrated does it inherit the Volume Retention perion of
>> the Next Pool?
>>
>> Thanks
>> Stephen Carr
>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your opinions on IT & business topics through brief surveys-and earn
>> cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
