> Bacula Version: 5.2.5
>
> I have configured bacula to write volumes to disk, however bacula
> stops
> writing to the volume as soon as it reaches 2gb. The file system is
> not an
> issue as I have stored files larger than 2gb.
>
>
> 06-Dec 17:22 backup-sd JobId 8421: End of Volume "Full-Monthl
> All
>
> I have the following in my bacula-dir.conf:
>
> FileSet{
> Name = "Microsoft_MTA3"
> Include {
> Options {
> Compression = GZIP
> signature = MD5
> Exclude = yes
> IgnoreCase = yes
>
I didn't see this in your configuration you sent to the list, but I saw you
mention a question about multiple pools. I also saw you have retention
settings defined in both client and pool resources. Volume retention is the
only one out of the three that is a pool attribute. Job and client rete
I believe that is letting you know the database schema is not at the correct
version. So in the process of moving to F17 you probably went to a newer
version of bacula if installing from repositories. In the /etc/bacula folder
there should be a update_bacula_tables script you can run to update
What are the connections rated for in terms of bandwidth between these two
machines? I would check if you have a network issue outside of bacula first.
After our deployment of bacula a few years ago, I noticed a couple computers on
our network would backup extremely slow (300-500kbps) on a 1gi
Change Address = Robert-HP in the configuration to the IP or DNS of your
Windows 7 machines. Whatever is in this field, the CentOS box should be able
to ping unless you are blocking the icmp traffic.
Also, make sure to add the bacula-fd.exe to the windows 7 firewall program
allow list, or add
