Hi Peter,
Bacula will always prefer to take a new volume (in Append state) rather than
reuse an existing one (in the Purged, Recycled state) so as to preserve your
backed up data for as long as possible. It will also use volumes in the backup
pool and only resort to taking volumes from the Scratch pool when there are
none suitable for writing in the pool.
I’m not entirely certain which of those two criteria will win out; I think
purged volumes in the backup pool will be used before Bacula tries to use an
unused volume from the Scratch pool but you may wish to check this.
I can understand why you’d want Bacula to reuse old volumes within one of your
backup pools first (so as to maximise the number of volumes left in the scratch
pool), but can’t see a reason why you’d prefer to reuse recycled volumes
already moved back into the scratch pool before unused ones. If you did mean
the latter, perhaps you can reply with your reasoning.
Ben Roberts
From: Peter Wood [mailto:peterwood...@gmail.com]
Sent: 01 October 2014 22:01
To: Roberts, Ben
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] File volumes and scratch pool
Thank you Ben.
I applied the changes and I'll monitor the behavior to confirm I did it right.
If I have mix of recycled volumes and brand new, never used volumes in Scratch,
which ones Bacula will grab first?
I'd really prefer to setup Bacula so it will reuse the old ones instead of
grabbing brand new volumes.
On Wed, Oct 1, 2014 at 1:07 PM, Roberts, Ben
<ben.robe...@gsacapital.com<mailto:ben.robe...@gsacapital.com>> wrote:
Hi Peter,
You need to set “Recycle Pool = Scratch” in your Scratch pool (and make sure
you haven’t overridden it in any other poo)l. Note that this setting is applied
to the volume when it’s created, so after changing the Scratch pool definition
you will need to update all your volumes to re-apply the Recycle pool. It might
be easiest to do this by directly modifying the catalog, else you can use a
quick bash script to generate a sequence of “update volume…” commands to echo
into bconsole.
Regards,
Ben Roberts
From: Peter Wood [mailto:peterwood...@gmail.com<mailto:peterwood...@gmail.com>]
Sent: 01 October 2014 20:56
To:
bacula-users@lists.sourceforge.net<mailto:bacula-users@lists.sourceforge.net>
Subject: [Bacula-users] File volumes and scratch pool
In Bacula-5.2.13 how do I setup expired volumes to go in the Scratch pool?
I create new file type volumes like this:
label storage=File volume=vol001 pool=Scratch
When needed volumes are taken out of Scratch and assigned to the appropriate
pool and used. Once in the pull they are never released back to Scratch after
they expire.
After retentionperiod ends volumes are reused but only within the pool they
have been originally assigned.
I see volume properties that may be related but I can't find documentation
about them:
scratchpoolid: 0
recyclepoolid: 0
Any help in making volumes go in Scratch after retention period expire so they
can be reused by any job.
Thank you,
-- Peter
________________________________
This email and any files transmitted with it contain confidential and
proprietary information and is solely for the use of the intended recipient. If
you are not the intended recipient please return the email to the sender and
delete it from your computer and you must not use, disclose, distribute, copy,
print or rely on this email or its contents. This communication is for
informational purposes only. It is not intended as an offer or solicitation for
the purchase or sale of any financial instrument or as an official confirmation
of any transaction. Any comments or statements made herein do not necessarily
reflect those of GSA Capital. GSA Capital Partners LLP is authorised and
regulated by the Financial Conduct Authority and is registered in England and
Wales at Stratton House, 5 Stratton Street, London W1J 8LA, number OC309261.
GSA Capital Services Limited is registered in England and Wales at the same
address, number 5320529.
This email and any files transmitted with it contain confidential and
proprietary information and is solely for the use of the intended recipient.
If you are not the intended recipient please return the email to the sender and
delete it from your computer and you must not use, disclose, distribute, copy,
print or rely on this email or its contents.
This communication is for informational purposes only.
It is not intended as an offer or solicitation for the purchase or sale of any
financial instrument or as an official confirmation of any transaction.
Any comments or statements made herein do not necessarily reflect those of GSA
Capital.
GSA Capital Partners LLP is authorised and regulated by the Financial Conduct
Authority and is registered in England and Wales at Stratton House, 5 Stratton
Street, London W1J 8LA, number OC309261.
GSA Capital Services Limited is registered in England and Wales at the same
address, number 5320529.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
