Hello List,
I have this Pool definition with autolabeling.
Pool {
Name = File
Pool Type = Backup
Recycle = yes # Bacula can automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 21 days # one year
On 01/27/11 04:29, ml ml wrote:
Hello List,
I have this Pool definition with autolabeling.
Pool {
Name = File
Pool Type = Backup
Recycle = yes # Bacula can automatically recycle
Volumes
AutoPrune = yes # Prune expired volumes
Volume
Hello,
Um, 1Mb volume size limit is reasonable on which planet?
Well, this was just for testing to see what happens if i run out of Volumes.
The big disadvantage is that i will run out of Volumes soon since each
Backup Job will create a Volume, even if its only 1MB big.
Can i set Maximum
On Thu, Jan 27, 2011 at 05:42:10AM -0500, Phil Stracchino wrote:
On 01/27/11 04:29, ml ml wrote:
Hello List,
I have this Pool definition with autolabeling.
Pool {
Name = File
Pool Type = Backup
Recycle = yes # Bacula can automatically recycle
On 01/27/11 06:12, Graham Keeling wrote:
Perhaps 10GB becomes more reasonable if you allow more than one job per
volume,
but then you still have the problem of disk space being wasted because you
cannot purge the volume until the last small 1MB job passes its retention
time.
I think this
On Thu, Jan 27, 2011 at 12:26 PM, Phil Stracchino ala...@metrocast.net wrote:
On 01/27/11 06:12, Graham Keeling wrote:
Perhaps 10GB becomes more reasonable if you allow more than one job per
volume,
but then you still have the problem of disk space being wasted because you
cannot purge the
If i set Maximum Volume Bytes = 10GB then it uses the full 10GB at the
very first run as full-backup. But the increments later get always
written to new Volume Files. E.g.
Volume-0001: 10GB (from full run)
Volume-0002: 10GB (from full run)
Volume-0003: 10GB (from full run)
Volume-0004:
On Thu, Jan 27, 2011 at 06:26:04AM -0500, Phil Stracchino wrote:
On 01/27/11 06:12, Graham Keeling wrote:
Perhaps 10GB becomes more reasonable if you allow more than one job per
volume,
but then you still have the problem of disk space being wasted because you
cannot purge the volume
On Thu, Jan 27, 2011 at 12:59:37PM +0100, ml ml wrote:
On Thu, Jan 27, 2011 at 12:26 PM, Phil Stracchino ala...@metrocast.net
wrote:
On 01/27/11 06:12, Graham Keeling wrote:
Perhaps 10GB becomes more reasonable if you allow more than one job per
volume,
but then you still have the
Op 27/01/2011 13:41, Graham Keeling schreef:
On Thu, Jan 27, 2011 at 12:59:37PM +0100, ml ml wrote:
On Thu, Jan 27, 2011 at 12:26 PM, Phil Stracchinoala...@metrocast.net
wrote:
On 01/27/11 06:12, Graham Keeling wrote:
Perhaps 10GB becomes more reasonable if you allow more than one job per
On 01/27/11 06:59, ml ml wrote:
If i set Maximum Volume Bytes = 10GB then it uses the full 10GB at the
very first run as full-backup. But the increments later get always
written to new Volume Files. E.g.
Volume-0001: 10GB (from full run)
Volume-0002: 10GB (from full run)
Volume-0003: 10GB
On 01/27/11 07:33, Graham Keeling wrote:
On Thu, Jan 27, 2011 at 06:26:04AM -0500, Phil Stracchino wrote:
On 01/27/11 06:12, Graham Keeling wrote:
I think this last problem is what Phil is trying to solve by setting either
Maximum Volume Jobs or Volume Use Duration. But these solutions seem
On Thu, Jan 27, 2011 at 08:56:54AM -0500, Phil Stracchino wrote:
On 01/27/11 07:33, Graham Keeling wrote:
On Thu, Jan 27, 2011 at 06:26:04AM -0500, Phil Stracchino wrote:
On 01/27/11 06:12, Graham Keeling wrote:
I think this last problem is what Phil is trying to solve by setting
either
On 01/27/11 09:28, Graham Keeling wrote:
I shall summarise what I thought I had already said, because it is quite clear
to me.
You have a terabyte disk that you want to use for backups.
You split it into 100 Volumes, set 10GB max volume size each, and 1 job
per volume.
All your backup
On 01/27/11 08:18, Jeremy Maes wrote:
If I recall correctly, bacula will always choose to create new volumes
over appending to an existing volume if it has a choice. In this case
that means you won't see any non-full Volumes appended to until you hit
the 500 volume mark.
You do not recall
On Thu, Jan 27, 2011 at 09:45:29AM -0500, Phil Stracchino wrote:
On 01/27/11 09:28, Graham Keeling wrote:
I shall summarise what I thought I had already said, because it is quite
clear
to me.
You have a terabyte disk that you want to use for backups.
You split it into 100
On Thu, Jan 27, 2011 at 10:48 AM, Graham Keeling gra...@equiinet.com wrote:
On Thu, Jan 27, 2011 at 09:45:29AM -0500, Phil Stracchino wrote:
On 01/27/11 09:28, Graham Keeling wrote:
I shall summarise what I thought I had already said, because it is quite
clear
to me.
You have a
Op 27/01/2011 15:45, Phil Stracchino schreef:
On 01/27/11 08:18, Jeremy Maes wrote:
If I recall correctly, bacula will always choose to create new volumes
over appending to an existing volume if it has a choice. In this case
that means you won't see any non-full Volumes appended to until you
On 01/27/11 10:48, Graham Keeling wrote:
The same problems exist in more realistic situations.
Assuming that I somehow know that all my backups will range from 100MB to
10GB,
then what should I set?
a) 1 volumes, 100MB max size?
b) 100 volumes, 10GB max size?
a) gives me
On Thu, Jan 27, 2011 at 11:15:59AM -0500, Phil Stracchino wrote:
On 01/27/11 10:48, Graham Keeling wrote:
The same problems exist in more realistic situations.
Assuming that I somehow know that all my backups will range from 100MB to
10GB,
then what should I set?
a) 1
On 01/27/11 12:09, Graham Keeling wrote:
Now follow the thinking through. Luckily, I have already done that for you.
Remember, at the start you had three obvious options:
a) Make more volumes, reduce the max sizes.
b) Make more volumes, keep the max sizes the same.
c) Increase the number of
21 matches
Mail list logo
