Thanks John.
All tapes were labeled after volume retention was implemented.
> Bacula will not do that. It only recycles volumes when it needs a
> volume and there are no acceptable volumes in the current pool.
Then is there a way force Bacula to do it?
During the weekend Bacula will need a media, it will find one in the
database, it will purge it but the media itself is not in the
autochanger. Somebody needs to go there and load it. And this can't be
done upfront because there is no clear way to find out which tape can be
recycled. I know that with some programming this information can be
extracted from the database but before doing that I'm trying to get
better understanding how things work and some best practices advice.
Basically, what I'm after is a hard forced policy. If I setup an
incremental backup to expire in two weeks that means after two weeks, 0
hours, 0 minutes and 1 second I don't want to know anything about this
backup. I want all file records and job records gone from the database
and the tape purged and moved to the Scratch pool regardless if the tape
is in the changer or off line.
I'd like to have full sync between what is in the database and what is
on the tapes. File records and job records never expire unless the media
they are saved on is recycled. I don't ever want to use bscan.
I do understand that this setup will destroy data that otherwise can
still be restored but it will also give me better control and planning
over the tape inventory and database growth.
Is this setup posible? Does it even make sense? :-)
Thanks
Peter
John Drescher wrote:
>> I'm running Bacula 5.0.1 on CentOS5.4 with Overland tape library (this
>> setup went with very little customization and I'm very pleased but I'll
>> write another email when all set and done with all hardware details and
>> install roadmap and hopefully it will help somebody).
>>
>> I need some help with media management.
>>
>> I setup a pool called FullTapes. Full type backup jobs can write only on
>> tapes in the FullTapes pool.
>>
>> ---<snip>---
>> Pool {
>> Name = FullTapes
>> Pool Type = Backup
>> File Retention = 1 years
>> Job Retention = 1 years
>>
>> Volume Retention = 2 days
>> AutoPrune = yes
>> Recycle = yes
>> RecyclePool = Scratch
>> }
>> ---<snip>---
>>
>> I have one tape in the library that is in pool FullTapes and is marked
>> "Full" and it's Volume Retention period expired. Also I have a hundred
>> tapes offsite. Most of them are in pool FullTapes and are marked "Full"
>> with expired Retention period.
>>
>> What I'm expecting is next time a full backup job runs to look into all
>> tapes in FullTapes pool and mark the ones that expired as Purged and
>> moved them in pool Scratch. Then recycle the one that is in the library
>> and use it for the currently running job.
>>
>
> Bacula will not do that. It only recycles volumes when it needs a
> volume and there are no acceptable volumes in the current pool.
>
>> What happened is that the backup job ran, found the tape in the library
>> and recycle it but it didn't touch any of the other tapes in pool FullTapes.
>>
>> Now I want to put more tapes in the library that can be recycled but I
>> don't know which ones out of the hundred I have off site because my
>> Scratch pool is empty. I have to manually get the details for each tape,
>> find the "lastwritten" date and apply the RetentionPeriod to find out if
>> this tape can be recycled.
>>
>> Did I miss something in the configuration that prevents me to get the
>> expected behavior? Is there a command that will look into all tapes,
>> purge the ones that expired and move them in Scratch?
>>
>> If not, then what do you guys do in this case? If you know you'll need
>> more tapes for your weekend full backups how do you find out which can
>> be recycled so you can put them in the library?
>>
>
> Did you implement the volume retention after tapes were labeled? If so
> you need to open up bconsole and
>
> update pool from resource
>
> and then update all volumes in pool.
>
> John
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
