Bacula-users

[Bacula-users] Bacula goes crazy creating dozens of new volumes in catalog

2008-06-04 16:08:23
Subject: [Bacula-users] Bacula goes crazy creating dozens of new volumes in catalog
From: Pasi Kärkkäinen <pasik AT iki DOT fi>
To: bacula-users AT lists.sourceforge DOT net
Date: Wed, 4 Jun 2008 23:08:07 +0300
Hi!

I've noticed this bug (?) happening multiple times now while testing Bacula
(2.3.22 SVN).. I think the same happened also earlier with Bacula 2.2.8.

So.. when I run a job this is what happens sometimes.. not very often:

Run Backup job
JobName:  server1
Level:    Incremental
Client:   server1-fd
FileSet:  DefaultWindowsFileSet
Pool:     Pool3 (From Job resource)
Storage:  FileStorage3 (From Pool resource)
When:     2008-06-04 22:38:58
Priority: 10
OK to run? (yes/mod/no): yes

Job queued. JobId=34
04-Jun 22:38 backup1-dir JobId 34: No prior Full backup Job record found.
04-Jun 22:38 backup1-dir JobId 34: No prior or suitable Full backup found in 
catalog. Doing FULL backup.

04-Jun 22:39 backup1-dir JobId 34: Start Backup JobId 34, 
Job=server1.2008-06-04_22.38.37
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0076" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0077" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0078" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0079" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0080" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0081" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0082" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0083" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0084" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0085" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0086" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0087" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0088" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0089" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0090" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0091" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0092" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0093" in 
catalog.
04-Jun 22:39 backup1-dir JobId 34: Created new Volume "Pool3-Vol-0094" in 
catalog.

Actual files are not created on disk, just to the catalog.. When this
happened Pool3 was already in use by another job.. (disk volume mounted and
in use).

The funny thing is that this job should have NOT been started in the first
place.. same Pool already had a running job, and another job waiting for
turn.. so this new job should have been created in the waiting mode also.

I'm running multiple pools.. each pool uses single volume per job. Each pool
has it's own Storage definition.. so with 4 pools I'm able to run 4 jobs
simultaneously, each being backup up to a different directory on the server.

Each Storage definition has maximum concurrent jobs = 1.

Any ideas what could cause this? 

Pool and Storage configuration:

Pool {
  Name = Pool1
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Maximum Volume Jobs = 1
  Use Volume Once = yes
  Maximum Volume Bytes = 8G
  Volume Retention = 14 days
  Maximum Volumes = 56
  Label Format = "Pool1-Vol-"
  Storage = FileStorage1
}

Pool {
  Name = Pool2
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Maximum Volume Jobs = 1
  Use Volume Once = yes
  Maximum Volume Bytes = 8G
  Volume Retention = 14 days
  Maximum Volumes = 56
  Label Format = "Pool2-Vol-"
  Storage = FileStorage2
}

Pool {
  Name = Pool3
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Maximum Volume Jobs = 1
  Use Volume Once = yes
  Maximum Volume Bytes = 8G
  Volume Retention = 14 days
  Maximum Volumes = 56
  Label Format = "Pool3-Vol-"
  Storage = FileStorage3
}

Pool {
  Name = Pool4
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Maximum Volume Jobs = 1
  Use Volume Once = yes
  Maximum Volume Bytes = 8G
  Volume Retention = 14 days
  Maximum Volumes = 56
  Label Format = "Pool4-Vol-"
  Storage = FileStorage4
}

Storage {
  Name = FileStorage1
  Address = sd.dom.tld
  SDPort = 9103
  Password = ""
  Device = FSDevice1
  Media Type = File1
  Maximum Concurrent Jobs = 1
}

Storage {
  Name = FileStorage2
  Address = sd.dom.tld
  SDPort = 9103
  Password = ""
  Device = FSDevice2
  Media Type = File2
  Maximum Concurrent Jobs = 1
}

Storage {
  Name = FileStorage3
  Address = sd.dom.tld
  SDPort = 9103
  Password = ""
  Device = FSDevice3
  Media Type = File3
  Maximum Concurrent Jobs = 1
}

Storage {
  Name = FileStorage4
  Address = sd.dom.tld
  SDPort = 9103
  Password = ""
  Device = FSDevice4
  Media Type = File4
  Maximum Concurrent Jobs = 1
}

-- Pasi

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Bacula-users] Bacula goes crazy creating dozens of new volumes in catalog, Pasi Kärkkäinen <=