Thanks Arno. I just wanted confirmation from someone more experienced.
On Fri, Feb 29, 2008 at 11:55 AM, Arno Lehmann [EMAIL PROTECTED] wrote:
Hi,
29.02.2008 17:30, John Drescher wrote:
By changing the Volume Use Duration in the Pool config, Bacula will
pick up
the change after a reload
This is great too. Thanks Brian. This actually answers a question I was
going to pose about tapes. I have some tapes that I changed pool definitions
for, but wasn't quite sure how to update that on tape.
Thanks again
On Fri, Feb 29, 2008 at 1:27 PM, Brian Debelius [EMAIL PROTECTED]
wrote:
If
Hi all,
I recently made a change in my Pool configs to change the Volume Use
Duration from 7d to 6d 23h.
Pool {
Name = My_Disks
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 27d
Volume Use Duration = 6d 23h
LabelFormat = ${Pool}-${NumVols}
}
I made this
By changing the Volume Use Duration in the Pool config, Bacula will pick up
the change after a reload and I don't need to update the volume in the
catalog?
Is there a better way to address this issue?
I may be wrong on this case but I have found that any changes in the
pool resource do not
I figured out the Duration part, but I'm still not sure if this change is
the correct way to address the larger issue of jobs failing.
*query
Available queries:
1: List up to 20 places where a File is saved regardless of the
directory
2: List where the most recent copies of a file are
Hi,
29.02.2008 17:30, John Drescher wrote:
By changing the Volume Use Duration in the Pool config, Bacula will pick up
the change after a reload and I don't need to update the volume in the
catalog?
Is there a better way to address this issue?
I may be wrong on this case but I have found
If I understand you correctly, This is how I do it
**reload*
You have messages.
**update*
Automatically selected Catalog: MyCatalog
Using Catalog MyCatalog
Update choice:
1: Volume parameters
*2: Pool from resource*
3: Slots from autochanger
*Choose catalog item to update (1-3): 2*
