LAZARO Bruno wrote:
>
> Hello,
>
>
>
> Attached is the job history "BackupCatalog »:
>
>
>
> 16-Sep 15:07 tis002-dir JobId 4631: shell command: run BeforeJob
> ""F:\Serveur_Sauvegarde\Bacula\bin\make_catalog_backup""
> 16-Sep 15:07 tis002-dir JobId 4631: BeforeJob:
> 16-Sep 15:07 tis002
My 2 cents it option 2.
changing configuration of the pool Default to get rid of this issue
in the future.
regards.
Le 16/09/2011 15:32, LAZARO Bruno a écrit :
Hello,
Attached is the job history “BackupC
It sounds like this is a volume of the a "File" pool
which is used to store the SQL backups of your catalog.
this file can be big for several reason:
1 - Your catalog is big/huge
or
2 - Your backup pool have only one volume that is used for ever and
ever.
Hello,
Attached is the job history "BackupCatalog »:
16-Sep 15:07 tis002-dir JobId 4631: shell command: run BeforeJob
""F:\Serveur_Sauvegarde\Bacula\bin\make_catalog_backup""
16-Sep 15:07 tis002-dir JobId 4631: BeforeJob:
16-Sep 15:07 tis002-dir JobId 4631: BeforeJob: C:\WINDOWS\system3
Hello,
Server configuration:
Windows 2003
MYSQL (5.1.36)
BACULA (3.0.3A)
On the server disk is full F (100%), that is a 135 GB disk.
On this record, at the following location:
F:\serveur_sauvegarde\bacula\savegardes
There is a "file" which is called "VOLLOCALN1" that which is 80GB in a
Ba
