Re: [Bacula-users] Verify Jobs not pruning cache when using S3 storage

[Eric Bollengier via Bacula-users]

Hello Martin,

On 6/19/24 12:57, Martin Reissner wrote:

Hello,

we're running a Bacula 15.0.2 setup which stores everything in S3 storage and 
due to having a lot of data to backup every day

we use

   Truncate Cache = AfterUpload
   Upload = EachPart

in our "Cloud" ressources, to ensure the systems running the SDs do not run out 
of diskspace. This works pretty well but I recently

started to configure Verifyjobs with

   Level = VolumeToCatalog

for some important jobs and it looks like when running the Verifyjob, data gets 
transferred from S3 to the directory specified
as "Archive Device" in the "Device" ressource, sometimes also known as 
"cloudcache" and is then compared to the respective data in the catalog.
So far so good, but it seems that even after a successful verification the 
volume data remains there, probably until the volume is reused and for

large jobs this takes up quite some space which causes diskspace issues on the 
SD.

Am I maybe missing something there and is there some option that can be used to 
prune the cache after a (successful) verifyjob?


Yes, you have a cloud command to prune the cache, I suggest to run it at a
regular interval inside an admin job for example. (cloud prune allpools 
storage=XXX)

Hope it helps!

Best Regards,
Eric



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] volumes, pools, media types and labels

[Stefan G. Weichinger]

Am 19.06.24 um 09:46 schrieb Radosław Korzeniewski:


Did you label your tapes? You can't use tapes in Bacula without labeling.


Sure I did!

When you label your tapes, just use "barcodes" options and Bacula will 
read all barcodes from tapes and label them to match.
Then you should put all your new tapes in the Scratch pool during 
labeling, so Bacula can take one to the selected pool when required.


That's new to me. Is it relevant for my current issue?
I want it to use existing volumes, not new ones.

Pool "daily" should not create a "Vol-" volume in the "File" storage ... 
it shouldn't use "File" at all.


Finally you should configure the "Recycle" pool parameter pointing to 
the Scratch pool, so all your unused tapes will return to it, closing 
the cycle.
When carefully configured it will automatically rotate all your tapes, 
which is good for them.


I hope it helps


phew, sounds even more complicated to me right now

-> adding Scratch pool


addon: for weekly and monthly the catalog should run to the according
tapes, not to a "daily" tape, right?


The rule of thumb for the tape backups in Bacula is to use as few pools 
as possible. Especially for catalog backup which is technically 
redundant (unneeded, see below) and you save it for time saving only 
during recovery.
If you have a single tape drive then you are limited to a single pool 
usage at any given time, and all your jobs which require another pool 
will wait. When your backup window is tight then you want to avoid this.
I personally create tape pools based on required retention, i.e. Tape1W 
or Tape1M and join all the pools with similar retention time.


Somewhere I read the catalog should (additionally?) be written to File,
that would complicate it even more.


You should save your BSR file offsite in a secure place this will save a 
lot of your precious time during recovery.
A file based volumes are easier to handle, a tape based volumes could be 
easier to handle for offsite storage.

So, it all depends on your requirements and ability to fulfill them.
*) your volumes archive all data required for future catalog recovery; 
this kind of recovery requires volume scan to populate catalog data, 
which can take time to complete; so, it is better and faster to save 
catalog backup to avoid volume scan.


ok, I think I understand ... but actually I don't see the todo for my 
original issue right now.






___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] libmysqlclient.so.21

[Davide F. via Bacula-users]

Ok, there was a misunderstanding from my side, my bad.

I thought you wanted to build the rom yourself.

Now I understand better.

In your specific context, if you get this error, it means the rpm package
has a bug (missing dependency or something else).

I’ll leave people from Bacula Systems answer here then.

Good luck

Davide

On Wed, Jun 19, 2024 at 13:08 Mehrdad Ravanbod 
wrote:

>
> Tbh, i am not too keen on building my own package from source, and none of
> these packages seem to have anything to do with mysql
>
> i did check the version libmysqlclient which is installed under
> /usr/lib64/mysql and it is version 20, i probably could install a later
> version of MySQL hoping for it to install the 21-version that the
> bacula-mysql rpm seems to need but i am pretty sure this will give me other
> problems
>
> So i just give up on this and try the postgres database, not a very good
> choice from my point of view since i am pretty unfamiliar with that DB but
> well, it's  a test installation
>
> Regards /Mehrdad
> On 2024-06-19 12:43, Davide F. wrote:
>
> Hi,
>
> Then try installing below packages (used on Centos 7, some packages name
> may have changed for Rocky Linux).
>
> openssh-clients rpm-sign mariadb-devel \gcc gcc-c++ make autoconf glibc-devel 
> \ ncurses-devel readline-devel libstdc++-devel \
> zlib-devel openssl-devel libacl-devel bzip2-devel \
> openldap-devel libxml2-devel rpmdevtools \
> rpmlint postgresql-devel libcurl-devel
>
> I remember the rpm package build process is documented somewhere in Bacula 
> documentation but I can't find it.
>
> Best,
>
>
> On Wed, Jun 19, 2024 at 12:33 PM Mehrdad Ravanbod <
> mehrdad.ravan...@ampfield.se> wrote:
>
>> Installed the mysql-community-devel.x86** and the i686 versions, fails
>> again with same error
>>
>> But thanks for answering
>>
>> Reagrds /Mehrdad
>> On 2024-06-19 12:16, Davide F. wrote:
>>
>> Hi,
>>
>> Not 100% sure, but as far as I remember, you need MySQL devel package
>> installed
>>
>> Let me know if it helps.
>>
>> Davide
>>
>> On Wed, Jun 19, 2024 at 11:44 Mehrdad Ravanbod <
>> mehrdad.ravan...@ampfield.se> wrote:
>>
>>>
>>> Hi guys
>>>
>>> Trying to install Bacula 13.0.4 community on a RockyLinux9(Rhel9)
>>> computer to test it for our backup needs
>>>
>>> Installation went well, upto and including MySQl5.7, but now I am stuck
>>>
>>> Trying:  yum install bacula-mysq fails with message that
>>>
>>> -nothing provides libmysqlclient.so.21 needed by
>>> bacula-mysql-13.0.4..el9.x86_64 from bacula-community
>>>
>>>  From what i understand this file is a part of MySQL8, trying to install
>>> the file libmysqlclient.so.21 fails too since it conflicts with file
>>> already installed by MySQL5.7
>>>
>>> I had installed Bacula 13.0.1 earlier without problems but this time i
>>> am stuck and the docmentation is so outdated it is not even funny
>>>
>>> So anyone that has a solution? Or should i just try to install an older
>>> version??( i know 13.0.4 is already an old version but well )
>>>
>>>
>>> --
>>> 
>>> Ampfield Aktiebolag
>>> Mehrdad Ravanbod System administrator
>>>
>>>
>>>
>>> ___
>>> Bacula-users mailing list
>>> Bacula-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>
>> --
>>  Ampfield
>> Aktiebolag Mehrdad Ravanbod System administrator
>>
> --
>  Ampfield
> Aktiebolag Mehrdad Ravanbod System administrator
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] libmysqlclient.so.21

[Davide F. via Bacula-users]

Hi,

Not 100% sure, but as far as I remember, you need MySQL devel package
installed

Let me know if it helps.

Davide

On Wed, Jun 19, 2024 at 11:44 Mehrdad Ravanbod 
wrote:

>
> Hi guys
>
> Trying to install Bacula 13.0.4 community on a RockyLinux9(Rhel9)
> computer to test it for our backup needs
>
> Installation went well, upto and including MySQl5.7, but now I am stuck
>
> Trying:  yum install bacula-mysq fails with message that
>
> -nothing provides libmysqlclient.so.21 needed by
> bacula-mysql-13.0.4..el9.x86_64 from bacula-community
>
>  From what i understand this file is a part of MySQL8, trying to install
> the file libmysqlclient.so.21 fails too since it conflicts with file
> already installed by MySQL5.7
>
> I had installed Bacula 13.0.1 earlier without problems but this time i
> am stuck and the docmentation is so outdated it is not even funny
>
> So anyone that has a solution? Or should i just try to install an older
> version??( i know 13.0.4 is already an old version but well )
>
>
> --
> 
> Ampfield Aktiebolag
> Mehrdad Ravanbod System administrator
>
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] libmysqlclient.so.21

[Davide F. via Bacula-users]

Hi,

Then try installing below packages (used on Centos 7, some packages name
may have changed for Rocky Linux).

openssh-clients rpm-sign mariadb-devel \gcc gcc-c++ make autoconf
glibc-devel \ ncurses-devel readline-devel libstdc++-devel \
zlib-devel openssl-devel libacl-devel bzip2-devel \
openldap-devel libxml2-devel rpmdevtools \
rpmlint postgresql-devel libcurl-devel

I remember the rpm package build process is documented somewhere in
Bacula documentation but I can't find it.

Best,


On Wed, Jun 19, 2024 at 12:33 PM Mehrdad Ravanbod <
mehrdad.ravan...@ampfield.se> wrote:

> Installed the mysql-community-devel.x86** and the i686 versions, fails
> again with same error
>
> But thanks for answering
>
> Reagrds /Mehrdad
> On 2024-06-19 12:16, Davide F. wrote:
>
> Hi,
>
> Not 100% sure, but as far as I remember, you need MySQL devel package
> installed
>
> Let me know if it helps.
>
> Davide
>
> On Wed, Jun 19, 2024 at 11:44 Mehrdad Ravanbod <
> mehrdad.ravan...@ampfield.se> wrote:
>
>>
>> Hi guys
>>
>> Trying to install Bacula 13.0.4 community on a RockyLinux9(Rhel9)
>> computer to test it for our backup needs
>>
>> Installation went well, upto and including MySQl5.7, but now I am stuck
>>
>> Trying:  yum install bacula-mysq fails with message that
>>
>> -nothing provides libmysqlclient.so.21 needed by
>> bacula-mysql-13.0.4..el9.x86_64 from bacula-community
>>
>>  From what i understand this file is a part of MySQL8, trying to install
>> the file libmysqlclient.so.21 fails too since it conflicts with file
>> already installed by MySQL5.7
>>
>> I had installed Bacula 13.0.1 earlier without problems but this time i
>> am stuck and the docmentation is so outdated it is not even funny
>>
>> So anyone that has a solution? Or should i just try to install an older
>> version??( i know 13.0.4 is already an old version but well )
>>
>>
>> --
>> 
>> Ampfield Aktiebolag
>> Mehrdad Ravanbod System administrator
>>
>>
>>
>> ___
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
> --
>  Ampfield
> Aktiebolag Mehrdad Ravanbod System administrator
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] libmysqlclient.so.21

[Mehrdad Ravanbod]

Tbh, i am not too keen on building my own package from source, and none 
of these packages seem to have anything to do with mysql


i did check the version libmysqlclient which is installed under 
/usr/lib64/mysql and it is version 20, i probably could install a later 
version of MySQL hoping for it to install the 21-version that the 
bacula-mysql rpm seems to need but i am pretty sure this will give me 
other problems


So i just give up on this and try the postgres database, not a very good 
choice from my point of view since i am pretty unfamiliar with that DB 
but well, it's  a test installation


Regards /Mehrdad

On 2024-06-19 12:43, Davide F. wrote:

Hi,

Then try installing below packages (used on Centos 7, some packages 
name may have changed for Rocky Linux).

openssh-clients rpm-sign mariadb-devel \
gcc gcc-c++ make autoconf glibc-devel \ ncurses-devel readline-devel 
libstdc++-devel \
zlib-devel openssl-devel libacl-devel bzip2-devel \
openldap-devel libxml2-devel rpmdevtools \
rpmlint postgresql-devel libcurl-devel
I remember the rpm package build process is documented somewhere in Bacula 
documentation but I can't find it.
Best,

On Wed, Jun 19, 2024 at 12:33 PM Mehrdad Ravanbod 
mailto:mehrdad.ravan...@ampfield.se>> 
wrote:


Installed the mysql-community-devel.x86** and the i686 versions,
fails again with same error

But thanks for answering

Reagrds /Mehrdad

On 2024-06-19 12:16, Davide F. wrote:

Hi,

Not 100% sure, but as far as I remember, you need MySQL devel
package installed

Let me know if it helps.

Davide

On Wed, Jun 19, 2024 at 11:44 Mehrdad Ravanbod
mailto:mehrdad.ravan...@ampfield.se>> wrote:


Hi guys

Trying to install Bacula 13.0.4 community on a
RockyLinux9(Rhel9)
computer to test it for our backup needs

Installation went well, upto and including MySQl5.7, but now
I am stuck

Trying:  yum install bacula-mysq fails with message that

-nothing provides libmysqlclient.so.21 needed by
bacula-mysql-13.0.4..el9.x86_64 from bacula-community

 From what i understand this file is a part of MySQL8, trying
to install
the file libmysqlclient.so.21 fails too since it conflicts
with file
already installed by MySQL5.7

I had installed Bacula 13.0.1 earlier without problems but
this time i
am stuck and the docmentation is so outdated it is not even funny

So anyone that has a solution? Or should i just try to
install an older
version??( i know 13.0.4 is already an old version but well )


-- 


Ampfield Aktiebolag
Mehrdad Ravanbod System administrator



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/bacula-users


-- 
 Ampfield

Aktiebolag Mehrdad Ravanbod System administrator


--
 Ampfield 
Aktiebolag Mehrdad Ravanbod System administrator
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Verify Jobs not pruning cache when using S3 storage

[Martin Reissner]

Hello,

we're running a Bacula 15.0.2 setup which stores everything in S3 storage and 
due to having a lot of data to backup every day
we use

  Truncate Cache = AfterUpload
  Upload = EachPart

in our "Cloud" ressources, to ensure the systems running the SDs do not run out 
of diskspace. This works pretty well but I recently
started to configure Verifyjobs with

  Level = VolumeToCatalog

for some important jobs and it looks like when running the Verifyjob, data gets 
transferred from S3 to the directory specified
as "Archive Device" in the "Device" ressource, sometimes also known as 
"cloudcache" and is then compared to the respective data in the catalog.
So far so good, but it seems that even after a successful verification the 
volume data remains there, probably until the volume is reused and for
large jobs this takes up quite some space which causes diskspace issues on the 
SD.

Am I maybe missing something there and is there some option that can be used to 
prune the cache after a (successful) verifyjob?

Thanks,

Martin

  
--

Wavecon GmbH
 
Anschrift:  Thomas-Mann-Straße 16-20, 90471 Nürnberg

Website:www.wavecon.de
Support:supp...@wavecon.de
 
Telefon:+49 (0)911-1206581 (werktags von 9 - 17 Uhr)

Hotline 24/7:   0800-WAVECON
Fax:+49 (0)911-2129233
 
Registernummer: HBR Nürnberg 41590

GF: Cemil Degirmenci
UstID:  DE251398082


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] libmysqlclient.so.21

[Mehrdad Ravanbod]

Installed the mysql-community-devel.x86** and the i686 versions, fails 
again with same error


But thanks for answering

Reagrds /Mehrdad

On 2024-06-19 12:16, Davide F. wrote:

Hi,

Not 100% sure, but as far as I remember, you need MySQL devel package 
installed


Let me know if it helps.

Davide

On Wed, Jun 19, 2024 at 11:44 Mehrdad Ravanbod 
mailto:mehrdad.ravan...@ampfield.se>> 
wrote:



Hi guys

Trying to install Bacula 13.0.4 community on a RockyLinux9(Rhel9)
computer to test it for our backup needs

Installation went well, upto and including MySQl5.7, but now I am
stuck

Trying:  yum install bacula-mysq fails with message that

-nothing provides libmysqlclient.so.21 needed by
bacula-mysql-13.0.4..el9.x86_64 from bacula-community

 From what i understand this file is a part of MySQL8, trying to
install
the file libmysqlclient.so.21 fails too since it conflicts with file
already installed by MySQL5.7

I had installed Bacula 13.0.1 earlier without problems but this
time i
am stuck and the docmentation is so outdated it is not even funny

So anyone that has a solution? Or should i just try to install an
older
version??( i know 13.0.4 is already an old version but well )


-- 


Ampfield Aktiebolag
Mehrdad Ravanbod System administrator



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/bacula-users



--
 Ampfield 
Aktiebolag Mehrdad Ravanbod System administrator
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] volumes, pools, media types and labels

[Radosław Korzeniewski]

Hello,

śr., 19 cze 2024 o 08:27 Stefan G. Weichinger  napisał(a):

>
> I have an annoying issue that I don't yet understand
>
> I read the howtos around volumes and media type etc but so far couldn't
> get it working:
>
> There are 2 storages "File" and "HP-Autoloader" ... so disk- and
> tape-based backups.
>
> There are pools like "daily" "weekly" "monthly" that contain physical
> tapes.
>
> "daily" and "weekly" have labels like "CMR123L6" (side question: I'd
> like to configure that as well into the pools. What would be the
> LabelFormat here?)
>
> "monthly" has "ARC123L6"
>
> and the file-based volumes get LabelFormat = "Vol-"
>
> The physical tapes use
>
> MediaType = "LTO-6"
>
> the disk-based virtual tapes use
>
> MediaType = "File"
>
> Now where´s the problem?
>
> It seems that the Job "BackupCatalog" (sometimes?) creates a new volume
> like "Vol-252", but with MediaType "LTO-6", which is then NOT FOUND in
> the tape autoloader. Sure, this one doesn't exist. "Vol-" volumes are
> for storage "File" only.
>

Did you label your tapes? You can't use tapes in Bacula without labeling.
When you label your tapes, just use "barcodes" options and Bacula will read
all barcodes from tapes and label them to match.
Then you should put all your new tapes in the Scratch pool during labeling,
so Bacula can take one to the selected pool when required.
Finally you should configure the "Recycle" pool parameter pointing to the
Scratch pool, so all your unused tapes will return to it, closing the cycle.
When carefully configured it will automatically rotate all your tapes,
which is good for them.

I hope it helps


> addon: for weekly and monthly the catalog should run to the according
> tapes, not to a "daily" tape, right?
>

The rule of thumb for the tape backups in Bacula is to use as few pools as
possible. Especially for catalog backup which is technically redundant
(unneeded, see below) and you save it for time saving only during recovery.
If you have a single tape drive then you are limited to a single pool usage
at any given time, and all your jobs which require another pool will wait.
When your backup window is tight then you want to avoid this.
I personally create tape pools based on required retention, i.e. Tape1W or
Tape1M and join all the pools with similar retention time.


> Somewhere I read the catalog should (additionally?) be written to File,
> that would complicate it even more.
>

You should save your BSR file offsite in a secure place this will save a
lot of your precious time during recovery.
A file based volumes are easier to handle, a tape based volumes could be
easier to handle for offsite storage.
So, it all depends on your requirements and ability to fulfill them.

*) your volumes archive all data required for future catalog recovery; this
kind of recovery requires volume scan to populate catalog data, which can
take time to complete; so, it is better and faster to save catalog backup
to avoid volume scan.
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] libmysqlclient.so.21

[Mehrdad Ravanbod]

Hi guys

Trying to install Bacula 13.0.4 community on a RockyLinux9(Rhel9)  
computer to test it for our backup needs


Installation went well, upto and including MySQl5.7, but now I am stuck

Trying:  yum install bacula-mysq fails with message that

-nothing provides libmysqlclient.so.21 needed by 
bacula-mysql-13.0.4..el9.x86_64 from bacula-community


From what i understand this file is a part of MySQL8, trying to install 
the file libmysqlclient.so.21 fails too since it conflicts with file 
already installed by MySQL5.7


I had installed Bacula 13.0.1 earlier without problems but this time i 
am stuck and the docmentation is so outdated it is not even funny


So anyone that has a solution? Or should i just try to install an older 
version??( i know 13.0.4 is already an old version but well )



--

Ampfield Aktiebolag
Mehrdad Ravanbod System administrator



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] volumes, pools, media types and labels

[Stefan G. Weichinger]

I have an annoying issue that I don't yet understand

I read the howtos around volumes and media type etc but so far couldn't 
get it working:


There are 2 storages "File" and "HP-Autoloader" ... so disk- and 
tape-based backups.


There are pools like "daily" "weekly" "monthly" that contain physical tapes.

"daily" and "weekly" have labels like "CMR123L6" (side question: I'd 
like to configure that as well into the pools. What would be the 
LabelFormat here?)


"monthly" has "ARC123L6"

and the file-based volumes get LabelFormat = "Vol-"

The physical tapes use

MediaType = "LTO-6"

the disk-based virtual tapes use

MediaType = "File"

Now where´s the problem?

It seems that the Job "BackupCatalog" (sometimes?) creates a new volume 
like "Vol-252", but with MediaType "LTO-6", which is then NOT FOUND in 
the tape autoloader. Sure, this one doesn't exist. "Vol-" volumes are 
for storage "File" only.


So the whole queue of Jobs gets stuck because of this.

I read that Director and Storage Daemon somehow have to agree on Media 
Types etc . I have:



## sd

Device {
  Name = "FileStorage"
  MediaType = "File"
  ArchiveDevice = "/mnt/backup/bacula"
  RemovableMedia = no
  RandomAccess = yes
  AutomaticMount = yes
  LabelMedia = yes
  AlwaysOpen = no
  SpoolDirectory = "/mnt/amhold/bacula"
  MaximumSpoolSize = 800
}
Device {
  Name = "HP-Ultrium"
  MediaType = "LTO-6"
  ArchiveDevice = "/dev/nst0"
  RemovableMedia = yes
  RandomAccess = no
  LabelMedia = yes
  AlwaysOpen = yes
  Autochanger = yes
  MaximumBlockSize = 262144
  MaximumFileSize = 8589934592
  SpoolDirectory = "/mnt/amhold/bacula"
  MaximumSpoolSize = 1
}


## director


Storage {
  Name = "File"
  SdPort = 9103
  Address = "samba"
  Password = "xxx"
  Device = "FileStorage"
  MediaType = "File"
}
Storage {
  Name = "HP-Autoloader"
  SdPort = 9103
  Address = "samba"
  Password = "xxx"
  Device = "HP-Autoloader"
  MediaType = "LTO-6"
  Autochanger = "HP-Autoloader"
  MaximumConcurrentJobs = 1
}


# pools

Pool {
  Name = "Daily"
  Description = "daily backups"
  PoolType = "Backup"
  MaximumVolumes = 30
  VolumeRetention = 864000
  Storage = "HP-Autoloader"
}
Pool {
  Name = "Default"
  PoolType = "Backup"
  MaximumVolumes = 100
  MaximumVolumeBytes = 53687091200
  VolumeRetention = 31536000
  AutoPrune = yes
  Recycle = yes
}
Pool {
  Name = "File"
  PoolType = "Backup"
  LabelFormat = "Vol-"
  MaximumVolumes = 101
  MaximumVolumeBytes = 53687091200
  VolumeRetention = 432000
  NextPool = "Daily"
  Storage = "File"
  AutoPrune = yes
  Recycle = yes
}
Pool {
  Name = "Monthly"
  Description = "monthly backups"
  PoolType = "Backup"
  UseVolumeOnce = no
  Storage = "HP-Autoloader"
}
Pool {
  Name = "Scratch"
  PoolType = "Backup"
}
Pool {
  Name = "Weekly"
  Description = "weekly backups"
  PoolType = "Backup"
  UseVolumeOnce = no
  VolumeRetention = 2592000
  Storage = "HP-Autoloader"
}

# Job


Job {
  Name = "BackupCatalog"
  Level = "Full"
  Storage = "HP-Autoloader"
  Fileset = "Catalog"
  Schedule = "WeeklyCycleAfterBackup"
  JobDefs = "DefaultJob"
  WriteBootstrap = "/opt/bacula/working/%n.bsr"
  Runscript {
RunsOnClient = no
RunsWhen = "Before"
Command = "/opt/bacula/scripts/make_catalog_backup.pl MyCatalog"
  }
  Runscript {
RunsOnClient = no
RunsWhen = "After"
Command = "/opt/bacula/scripts/delete_catalog_backup"
  }
  Priority = 11
  Pool = "Daily"
}


Anything missing? I get a bit lost here and don't want to 
"overconfigure" things where there might be clever defaults or automatisms.


addon: for weekly and monthly the catalog should run to the according 
tapes, not to a "daily" tape, right?


Somewhere I read the catalog should (additionally?) be written to File, 
that would complicate it even more.


Thanks in advance for any help here. It seems that is the missing bit 
for this config to be running autonomously for a week or so (which isn't 
the case yet unfortunately ...)


Stefan


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users