John,
I have 4 pools total, two pools defined by me: Offsite and Onsite and two that
I believe are default to Bacula: Catalog and Scratch.
Offsite retention period is 6 months, Onsite is 3 months. Once a volume is
marked full from Onsite the volume goes on the shelf to the back of the stack.
With our offsite volumes, full tapes are sent away and returned 3 months later,
leaving us 3 more months on the shelf before the tapes are rewritten. Once the
expiration date is met (calculated from last written date + 3 months for
onsite, + 6 months from offsite) they are available to be reused. They do not
necessarily go back into the same pool they were previously used since I
allocate them all to 'scratch' after issuing 'label barcodes'
Any errors in my process?
Again, thanks for your reply.
JJ
*show pools
Pool: name=Catalog PoolType=Backup
use_cat=1 use_once=0 cat_files=1
max_vols=0 auto_prune=1 VolRetention=1 year
VolUse=0 secs recycle=1 LabelFormat=*None*
CleaningPrefix=*None* LabelType=0
RecyleOldest=0 PurgeOldest=0 ActionOnPurge=0
MaxVolJobs=0 MaxVolFiles=0 MaxVolBytes=0
MigTime=0 secs MigHiBytes=0 MigLoBytes=0
JobRetention=0 secs FileRetention=0 secs
Pool: name=Offsite PoolType=Backup
use_cat=1 use_once=0 cat_files=1
max_vols=0 auto_prune=1 VolRetention=6 months
VolUse=0 secs recycle=1 LabelFormat=*None*
CleaningPrefix=*None* LabelType=0
RecyleOldest=0 PurgeOldest=0 ActionOnPurge=0
MaxVolJobs=0 MaxVolFiles=0 MaxVolBytes=0
MigTime=0 secs MigHiBytes=0 MigLoBytes=0
JobRetention=0 secs FileRetention=0 secs
Pool: name=Onsite PoolType=Backup
use_cat=1 use_once=0 cat_files=1
max_vols=0 auto_prune=1 VolRetention=3 months
VolUse=0 secs recycle=1 LabelFormat=*None*
CleaningPrefix=*None* LabelType=0
RecyleOldest=0 PurgeOldest=0 ActionOnPurge=0
MaxVolJobs=0 MaxVolFiles=0 MaxVolBytes=0
MigTime=0 secs MigHiBytes=0 MigLoBytes=0
JobRetention=0 secs FileRetention=0 secs
Pool: name=Scratch PoolType=Backup
use_cat=1 use_once=0 cat_files=1
max_vols=0 auto_prune=1 VolRetention=1 year
VolUse=0 secs recycle=1 LabelFormat=*None*
CleaningPrefix=*None* LabelType=0
RecyleOldest=0 PurgeOldest=0 ActionOnPurge=0
MaxVolJobs=0 MaxVolFiles=0 MaxVolBytes=0
MigTime=0 secs MigHiBytes=0 MigLoBytes=0
JobRetention=0 secs FileRetention=0 secs
-----Original Message-----
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Wednesday, July 21, 2010 10:36 AM
To: Jeremiah D. Jester
Cc: bacula-users
Subject: Re: [Bacula-users] requesting old volume.
On Wed, Jul 21, 2010 at 1:11 PM, Jeremiah D. Jester
<jj...@u.washington.edu> wrote:
> Bacula is asking for a volume that is no longer in the changer because it was
> marked as full and sent offsite. As you can see the volume was last written
> to on July 9th.
>
> Current snippet for this volume 'list media pool=Offsite' below.
>
> 103 | KL0451 | Append | 1 | 163,962,667,008 | 172 |
> 15,552,000 | 1 | 0 | 0 | LTO2 | 2010-07-09 17:22:05 |
>
Inchanger and slot are both 0 which is good. I think there is a
directive for bacula to prefer volumes that are in the changer versus
offsite. I am not sure though. I do not move volumes offsite and I
also have a very long retention.
> What is the best way to resolve this issue?
>
Well the quick hack is to mark that volume full by using update volume status.
How often do you move volumes offsite? Can you explain the policy a
little bit? I am thinking you want more than one Offsite pool and
rotate the pools when you swap out volumes. If you do this monthly or
something like that you can have your schedule do the rotation of the
pools.
John
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
