Backup Central

Hello!

I've some problems with bacula 5.2.5 (maybe < 5.2.5) Volume
Retention.... It looks bacula is recycling volumes when no one is left,
even before volume retention period expires.... Although bacula purged
all jobs and files from volume, it should respect volume retention,
don't it?

For testing purposes, I've downloaded, compiled and installer bacula
5.2.5, changing only Pool file settings:
Volume Use Duration = 1 minute
Volume Retention = 1 day
and Client bacula-fd:
File Retention = 1 minute
Job Retention = 1 minute

So, I've created 2 volumes, Vol1 and Vol2. Then, I ran a backup job,
that was stored at Vol1. 1 minute later, ran another backup, Vol1 was
marked as used, files and job at Vol1 was purged, and backup was stored
at Vol2.

Another minute later I ran another backup. This time, Vol1 was recycled
and backup was stored on it. Since Volume Retention was set to 1 day and
manual says about Recycling Algorithm: "Prune volumes applying Volume
retention period (Volumes with VolStatus Full, Used, or Append are
pruned). Note, even if all the File and Job records are pruned from a
Volume, ***the Volume will not be marked Purged until the Volume
retention period expires***."
(http://www.bacula.org/5.2.x-manuals/en/main/main/Automatic_Volume_Recycling.html),
Vol1 shouldn't have been recycled... But log shows "There are no more
Jobs associated with Volume "Vol1". Marking it purged."

Any ideas?

Regards,
Diego

--
--

Diego P. Rubert
Coordenadoria de Informática
Procuradoria da República no Estado de Mato Grosso do Sul
Ministério Público Federal


------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

On Fri, Feb 3, 2012 at 4:43 PM, Diego Rubert <dprubert < at > prms.mpf.gov.br> wrote:
Hello!

I've some problems with bacula 5.2.5 (maybe < 5.2.5) Volume
Retention.... It looks bacula is recycling volumes when no one is left,
even before volume retention period expires.... Although bacula purged
all jobs and files from volume, it should respect volume retention,
don't it?

For testing purposes, I've downloaded, compiled and installer bacula
5.2.5, changing only Pool file settings:
  Volume Use Duration = 1 minute
  Volume Retention = 1 day
and Client bacula-fd:
  File Retention = 1 minute
  Job Retention = 1 minute

So, I've created 2 volumes, Vol1 and Vol2. Then, I ran a backup job,
that was stored at Vol1. 1 minute later, ran another backup, Vol1 was
marked as used, files and job at Vol1 was purged, and backup was stored
at Vol2.

Another minute later I ran another backup. This time, Vol1 was recycled
and backup was stored on it. Since Volume Retention was set to 1 day and
manual says about Recycling Algorithm: "Prune volumes applying Volume
retention period (Volumes with VolStatus Full, Used, or Append are
pruned). Note, even if all the File and Job records are pruned from a
Volume, ***the Volume will not be marked Purged until the Volume
retention period expires***."
(http://www.bacula.org/5.2.x-manuals/en/main/main/Automatic_Volume_Recycling.html),
Vol1 shouldn't have been recycled... But log shows "There are no more
Jobs associated with Volume "Vol1". Marking it purged."

Any ideas?

Did you change definition of the pool after the volumes existed?

John

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Em 03-02-2012 20:35, John Drescher escreveu:
On Fri, Feb 3, 2012 at 4:43 PM, Diego Rubert<dprubert < at > prms.mpf.gov.br> wrote:
Hello!

I've some problems with bacula 5.2.5 (maybe< 5.2.5) Volume
Retention.... It looks bacula is recycling volumes when no one is left,
even before volume retention period expires.... Although bacula purged
all jobs and files from volume, it should respect volume retention,
don't it?

For testing purposes, I've downloaded, compiled and installer bacula
5.2.5, changing only Pool file settings:
Volume Use Duration = 1 minute
Volume Retention = 1 day
and Client bacula-fd:
File Retention = 1 minute
Job Retention = 1 minute

So, I've created 2 volumes, Vol1 and Vol2. Then, I ran a backup job,
that was stored at Vol1. 1 minute later, ran another backup, Vol1 was
marked as used, files and job at Vol1 was purged, and backup was stored
at Vol2.

Another minute later I ran another backup. This time, Vol1 was recycled
and backup was stored on it. Since Volume Retention was set to 1 day and
manual says about Recycling Algorithm: "Prune volumes applying Volume
retention period (Volumes with VolStatus Full, Used, or Append are
pruned). Note, even if all the File and Job records are pruned from a
Volume, ***the Volume will not be marked Purged until the Volume
retention period expires***."
(http://www.bacula.org/5.2.x-manuals/en/main/main/Automatic_Volume_Recycling.html),
Vol1 shouldn't have been recycled... But log shows "There are no more
Jobs associated with Volume "Vol1". Marking it purged."

Any ideas?
Did you change definition of the pool after the volumes existed?

John
No, the volumes were created after changing/reloading/updating the pool.

Diego

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

On Fri, 03 Feb 2012 18:43:51 -0300, Diego Rubert said:

Hello!

I've some problems with bacula 5.2.5 (maybe < 5.2.5) Volume
Retention.... It looks bacula is recycling volumes when no one is left,
even before volume retention period expires.... Although bacula purged
all jobs and files from volume, it should respect volume retention,
don't it?

For testing purposes, I've downloaded, compiled and installer bacula
5.2.5, changing only Pool file settings:
Volume Use Duration = 1 minute
Volume Retention = 1 day
and Client bacula-fd:
File Retention = 1 minute
Job Retention = 1 minute

So, I've created 2 volumes, Vol1 and Vol2. Then, I ran a backup job,
that was stored at Vol1. 1 minute later, ran another backup, Vol1 was
marked as used, files and job at Vol1 was purged, and backup was stored
at Vol2.

Another minute later I ran another backup. This time, Vol1 was recycled
and backup was stored on it. Since Volume Retention was set to 1 day and
manual says about Recycling Algorithm: "Prune volumes applying Volume
retention period (Volumes with VolStatus Full, Used, or Append are
pruned). Note, even if all the File and Job records are pruned from a
Volume, ***the Volume will not be marked Purged until the Volume
retention period expires***."
(http://www.bacula.org/5.2.x-manuals/en/main/main/Automatic_Volume_Recycling.html),
Vol1 shouldn't have been recycled... But log shows "There are no more
Jobs associated with Volume "Vol1". Marking it purged."

Any ideas?

I don't know if that is a bug in software or the doc, but is has been that way
for a long time.

Volumes with no remaining jobs will be recycled before their Volume Retention
has expired, so the best option is to use a much larger Job Retention. That
won't affect size of the catalog database too badly, because it is mainly
affected by the number of file records (from the File Retention).

__Martin

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Em 06-02-2012 14:12, Martin Simmons escreveu:
On Fri, 03 Feb 2012 18:43:51 -0300, Diego Rubert said:
Hello!

I've some problems with bacula 5.2.5 (maybe< 5.2.5) Volume
Retention.... It looks bacula is recycling volumes when no one is left,
even before volume retention period expires.... Although bacula purged
all jobs and files from volume, it should respect volume retention,
don't it?

For testing purposes, I've downloaded, compiled and installer bacula
5.2.5, changing only Pool file settings:
Volume Use Duration = 1 minute
Volume Retention = 1 day
and Client bacula-fd:
File Retention = 1 minute
Job Retention = 1 minute

So, I've created 2 volumes, Vol1 and Vol2. Then, I ran a backup job,
that was stored at Vol1. 1 minute later, ran another backup, Vol1 was
marked as used, files and job at Vol1 was purged, and backup was stored
at Vol2.

Another minute later I ran another backup. This time, Vol1 was recycled
and backup was stored on it. Since Volume Retention was set to 1 day and
manual says about Recycling Algorithm: "Prune volumes applying Volume
retention period (Volumes with VolStatus Full, Used, or Append are
pruned). Note, even if all the File and Job records are pruned from a
Volume, ***the Volume will not be marked Purged until the Volume
retention period expires***."
(http://www.bacula.org/5.2.x-manuals/en/main/main/Automatic_Volume_Recycling.html),
Vol1 shouldn't have been recycled... But log shows "There are no more
Jobs associated with Volume "Vol1". Marking it purged."

Any ideas?
I don't know if that is a bug in software or the doc, but is has been that way
for a long time.

Volumes with no remaining jobs will be recycled before their Volume Retention
has expired, so the best option is to use a much larger Job Retention. That
won't affect size of the catalog database too badly, because it is mainly
affected by the number of file records (from the File Retention).

__Martin
Well, if it has been that way for a long time, maybe it's a bug in
algorithm description at doc. Bacula acts like if
RecycleOldestVolume=yes was the default option, although it says the
default is *no*. I've no problem with that, but it may cause confusion,
since the manual says explicitly: "Prune volumes applying Volume
retention period (Volumes with VolStatus Full, Used, or Append are
pruned). Note, even if all the File and Job records are pruned from a
Volume, the Volume will not be marked Purged until the Volume retention
period expires.". Should I report that? How?

manual page:
http://www.bacula.org/5.2.x-manuals/en/main/main/Automatic_Volume_Recycling.html

Diego
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

On Mon, 06 Feb 2012 15:13:30 -0300, Diego Rubert said:

Em 06-02-2012 14:12, Martin Simmons escreveu:
On Fri, 03 Feb 2012 18:43:51 -0300, Diego Rubert said:
Hello!

I've some problems with bacula 5.2.5 (maybe< 5.2.5) Volume
Retention.... It looks bacula is recycling volumes when no one is left,
even before volume retention period expires.... Although bacula purged
all jobs and files from volume, it should respect volume retention,
don't it?

For testing purposes, I've downloaded, compiled and installer bacula
5.2.5, changing only Pool file settings:
Volume Use Duration = 1 minute
Volume Retention = 1 day
and Client bacula-fd:
File Retention = 1 minute
Job Retention = 1 minute

So, I've created 2 volumes, Vol1 and Vol2. Then, I ran a backup job,
that was stored at Vol1. 1 minute later, ran another backup, Vol1 was
marked as used, files and job at Vol1 was purged, and backup was stored
at Vol2.

Another minute later I ran another backup. This time, Vol1 was recycled
and backup was stored on it. Since Volume Retention was set to 1 day and
manual says about Recycling Algorithm: "Prune volumes applying Volume
retention period (Volumes with VolStatus Full, Used, or Append are
pruned). Note, even if all the File and Job records are pruned from a
Volume, ***the Volume will not be marked Purged until the Volume
retention period expires***."
(http://www.bacula.org/5.2.x-manuals/en/main/main/Automatic_Volume_Recycling.html),
Vol1 shouldn't have been recycled... But log shows "There are no more
Jobs associated with Volume "Vol1". Marking it purged."

Any ideas?
I don't know if that is a bug in software or the doc, but is has been that way
for a long time.

Volumes with no remaining jobs will be recycled before their Volume Retention
has expired, so the best option is to use a much larger Job Retention. That
won't affect size of the catalog database too badly, because it is mainly
affected by the number of file records (from the File Retention).

__Martin
Well, if it has been that way for a long time, maybe it's a bug in
algorithm description at doc. Bacula acts like if
RecycleOldestVolume=yes was the default option, although it says the
default is *no*.

Kind of, but it isn't affected by RecycleOldestVolume. Moreover,
RecycleOldestVolume=yes is also supposed to respect Volume retention periods
(but it doesn't).


I've no problem with that, but it may cause confusion,
since the manual says explicitly: "Prune volumes applying Volume
retention period (Volumes with VolStatus Full, Used, or Append are
pruned). Note, even if all the File and Job records are pruned from a
Volume, the Volume will not be marked Purged until the Volume retention
period expires.". Should I report that? How?

manual page:
http://www.bacula.org/5.2.x-manuals/en/main/main/Automatic_Volume_Recycling.html

Doc bugs can be reported at http://bugs.bacula.org via the Category dropdown.

__Martin

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users