Re: [Bacula-users] Reducing the maximum number of volumes in a pool

2013-03-12 Thread John Drescher
> some more observations on reducing the numbers of volumes in a pool: I
> changed the max volumes from 14 to 8 for a disk based incremental
> pool, reloaded the director config and then started manually deleting
> volumes using bconsole.
>
> "list pool" still showed numvols = maxvols = 14 until I manually
> started the "update pool from resource" command, then the volume count
> for both numvols and maxvols would decrease by one for each volume
> deleted.
>
> Now I'm asking myself is this a bug or a feature? Sure bacula tries to
> keep my data as long as possible (which is nice), but I'd expect the
> following to happen:

I believe this is a feature.

John

--
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Reducing the maximum number of volumes in a pool

2013-03-12 Thread Uwe Schuerkamp
On Wed, Feb 27, 2013 at 08:11:44AM -0500, Dan Langille wrote:

> 
> In bconsole, did you issue the reload command before issuing the update 
> command?
> 

Hi folks, 

some more observations on reducing the numbers of volumes in a pool: I
changed the max volumes from 14 to 8 for a disk based incremental
pool, reloaded the director config and then started manually deleting
volumes using bconsole.

"list pool" still showed numvols = maxvols = 14 until I manually
started the "update pool from resource" command, then the volume count
for both numvols and maxvols would decrease by one for each volume
deleted. 

Now I'm asking myself is this a bug or a feature? Sure bacula tries to
keep my data as long as possible (which is nice), but I'd expect the
following to happen: 

- Bacula sees numvols > maxvols once it's starting a job (maxjobs = 1
  per volume), so it deletes the oldest volume from the pool and
  recycles the next oldest until numvols is equal maxvols again. 

What really bugs me about this is that even after reloading the config
and updating the pool from resource manually, "maxvols" is still on
the old value and not the one found in bacula-dir.conf, so one has no
indication on a database level that the pool contains more volumes
that it should.

All the best, Uwe 


-- 
NIONEX --- Ein Unternehmen der Bertelsmann SE & Co. KGaA



--
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Reducing the maximum number of volumes in a pool

2013-03-01 Thread Humphrey Bryant
In my experience changing pool/volume configurations on Bacula (whether 
max volume or max volume size) the changes do not reflect until after a 
new volume is created; meaning ONLY after the current volumes in use are 
marked full/used and a new volume is created that's the only time i see 
the new configuration changes on the volumes.

(I reload and restart bacuala-dir/fd/sd even restart with no luck as well ).

Good Luck!
On 02/27/2013 09:05 AM, Uwe Schuerkamp wrote:

On Wed, Feb 27, 2013 at 08:11:44AM -0500, Dan Langille wrote:

for the incremental pools, but following an "update pool from
resource" the db record still shows the previous number of volumes in
the pool for Max, not the one defined in the director config.

Any idea why this would happen or how to fix it, short of writing
some
custom sql to manually set the new value in the database? I've also
tried to restart bacula, but that hasn't helped, either.

All the best & thanks in advance for your help,

In bconsole, did you issue the reload command before issuing the update
command?

--
Dan Langille - http://langille.org/

Yep, I did, I even restarted all bacula components, still the number
of maximum volumes remains the same as before. Some additional info on
the situation: Some of the pools have not yet reached their previous
max volume count, could this interfere with the update pool from
resource command?

All the best, Uwe



<>--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Reducing the maximum number of volumes in a pool

2013-02-27 Thread Uwe Schuerkamp
On Wed, Feb 27, 2013 at 08:11:44AM -0500, Dan Langille wrote:
> >
> >for the incremental pools, but following an "update pool from
> >resource" the db record still shows the previous number of volumes in
> >the pool for Max, not the one defined in the director config.
> >
> >Any idea why this would happen or how to fix it, short of writing 
> >some
> >custom sql to manually set the new value in the database? I've also
> >tried to restart bacula, but that hasn't helped, either.
> >
> >All the best & thanks in advance for your help,
> 
> In bconsole, did you issue the reload command before issuing the update 
> command?
> 
> -- 
> Dan Langille - http://langille.org/

Yep, I did, I even restarted all bacula components, still the number
of maximum volumes remains the same as before. Some additional info on
the situation: Some of the pools have not yet reached their previous
max volume count, could this interfere with the update pool from
resource command? 

All the best, Uwe 

-- 
NIONEX --- Ein Unternehmen der Bertelsmann SE & Co. KGaA



--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Reducing the maximum number of volumes in a pool

2013-02-27 Thread Dan Langille
On 2013-02-27 03:57, Uwe Schuerkamp wrote:
> Hi folks,
>
> I'm trying to save a bit of disk space by reducing the number of
> volumes in the "incremental" pool (we use separate pools for for full
> and incremental backups for each client, bacula 5.2.13 compiled from
> source). Previously we had 15 incremental volumes per pool, now I'd
> like to retain 7 for each client.
>
> I've changed all the pool definitions in the director config from
>
> Maximum Volumes = 15
>
> to
>
> Maximum Volumes = 7
>
> for the incremental pools, but following an "update pool from
> resource" the db record still shows the previous number of volumes in
> the pool for Max, not the one defined in the director config.
>
> Any idea why this would happen or how to fix it, short of writing 
> some
> custom sql to manually set the new value in the database? I've also
> tried to restart bacula, but that hasn't helped, either.
>
> All the best & thanks in advance for your help,

In bconsole, did you issue the reload command before issuing the update 
command?

-- 
Dan Langille - http://langille.org/

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users