I've run into a problem of late. For some strange reason, Bacula is
marking my tape USED in the middle of the nightly backup jobs. It just
started to do this over the last week. We rotate tapes daily and the
volume use duration is set to 12 hours. The first job kicks off at 5PM
but around m
> -Ursprüngliche Nachricht-
> Von: Phil Stracchino [mailto:ala...@metrocast.net]
> Gesendet: Donnerstag, 24. November 2011 18:15
> An: bacula-users@lists.sourceforge.net
> Betreff: Re: [Bacula-users] Volume Use Duration not working in 5.2.1
>
> On 11/24/11 11:01,
Fahrer, Julian:
> Hi,
>
> Am I missing something or is the "Volume Use Duration" parameter in the
> pool not working in 5.2.1?
[...]
>
> Mediaid 5 & 8 should actually be in status "used". It is 2011-11-24
> 17:00 right now...
> Same thing for other pools with "Volume Use Duration = 12 days"
>
>
On 11/24/11 11:01, Fahrer, Julian wrote:
> Hi,
>
> Am I missing something or is the "Volume Use Duration" parameter in the
> pool not working in 5.2.1?
>
> I defined the pool like this:
> ---
> Pool {
> Name = NEO200S_Weekly_Pool
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
>
On Thu, Nov 24, 2011 at 11:01 AM, Fahrer, Julian wrote:
> Hi,
>
> Am I missing something or is the "Volume Use Duration" parameter in the
> pool not working in 5.2.1?
>
> I defined the pool like this:
> ---
> Pool {
> Name = NEO200S_Weekly_Pool
> Pool Type = Backup
> Recycle = yes
> AutoPrune
On 24.11.2011 17:01, Fahrer, Julian wrote:
> Hi,
>
> Am I missing something or is the "Volume Use Duration" parameter in the
> pool not working in 5.2.1?
>
> I defined the pool like this:
> ---
> Pool {
>Name = NEO200S_Weekly_Pool
>Pool Type = Backup
>Recycle = yes
>AutoPrune = yes
Hi,
Am I missing something or is the "Volume Use Duration" parameter in the
pool not working in 5.2.1?
I defined the pool like this:
---
Pool {
Name = NEO200S_Weekly_Pool
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 31 days
Volume Use Duration = 72h
Storage =
Hi,
I purged some volumes of a failed backup and manually changed the state to
recycle. Now I see this in the bacula log:
11-Feb 08:19 VU0EA003-sd JobId 9460: Recycled volume "A00045L4" on device
"ULTRIUM-TD4-D2" (/dev/ULTRIUM-TD4-D2), all previous data lost.
11-Feb 08:19 VUMEM004-dir JobId 946
On Monday 08 January 2007 16:35, Amiche wrote:
> Whan bacula start the backup of the night on a tape volume, I want the
status of
> the volume pass immediatly as Used when the last job is terminated.
Bacula changes the status only the next time it wants to use the volume.
> So I defined "Volume
On 8 Jan 2007 at 16:36, James Cort wrote:
> Bill Moran wrote:
> > In response to Amiche <[EMAIL PROTECTED]>:
> >
> >
> >> Whan bacula start the backup of the night on a tape volume, I want the
> >> status of
> >> the volume pass immediatly as Used when the last job is terminated.
> >> So I def
Bill Moran wrote:
> In response to Amiche <[EMAIL PROTECTED]>:
>
>
>> Whan bacula start the backup of the night on a tape volume, I want the
>> status of
>> the volume pass immediatly as Used when the last job is terminated.
>> So I defined "Volume Use Duration = 10h" but Bacula wait for the n
In response to Amiche <[EMAIL PROTECTED]>:
> Whan bacula start the backup of the night on a tape volume, I want the status
> of
> the volume pass immediatly as Used when the last job is terminated.
> So I defined "Volume Use Duration = 10h" but Bacula wait for the next job
> using
> this volume
Whan bacula start the backup of the night on a tape volume, I want the status of
the volume pass immediatly as Used when the last job is terminated.
So I defined "Volume Use Duration = 10h" but Bacula wait for the next job using
this volume to mark it as Used,and not immediatly after the last job.
Beren said:
> I've got a Volume Use Duration of 23h on my pool, but for some reason
> bacula (1.38.5) marks it as used after only a couple of hours after it
> starts backing up.
Have there been volumes in that pool before you added the 'Volume Use
Duration' parameter? If so, you have to update th
Hi Everyone,
I've got a Volume Use Duration of 23h on my pool, but for some reason
bacula (1.38.5) marks it as used after only a couple of hours after it
starts backing up.
Any ideas?
Cheers,
Beren
---
This SF.Net email is sponsored by xPML,
I remove the ^M's
On 14 Feb 2006 at 17:40, Brian A. Seklecki wrote:
> ...with -d9, here are the relevant decision making parts:
>
> Without looking at the code, I think this may be a database error
> related to:
>
> mindwipe-dir: postgresql.c:334 my_postgresql_fetch_row finishes
> returning
...with -d9, here are the relevant decision making parts:
Without looking at the code, I think this may be a database error
related to:
mindwipe-dir: postgresql.c:334 my_postgresql_fetch_row finishes
returning 8128018^M
mindwipe-dir: next_vol.c:62 catreq after find_next_vol ok=1 FW=0^M
mindwi
Platform:
$ uname -a
FreeBSD mindwipe 5.3-RELEASE-p23 FreeBSD 5.3-RELEASE-p23 #0: Wed Oct 12
-bash-2.05b$ pkg_info |grep -i bacula
bacula-client-1.38.5_1 The network backup solution (client)
bacula-server-1.38.5_1 The network backup solution (server)
Here's what I know so far:
*) This bug is n
On Wed, 2005-04-13 at 11:59 +0200, Alexander Bergolth wrote:
> Hi!
>
> The manual says that the Pool directive "Volume Use Duration" is only
> checked at the end of a job that writes to a volume.
> Is there a way to manually trigger this check? (E.g. to mark all
> "Appendable" daily volumes as U
Hi!
The manual says that the Pool directive "Volume Use Duration" is only
checked at the end of a job that writes to a volume.
Is there a way to manually trigger this check? (E.g. to mark all
"Appendable" daily volumes as Used when doing a full backup?)
I could set the Volume Use Duration so tha
20 matches
Mail list logo
