View Issue Details

IDProjectCategoryView StatusLast Update
0000759bareos-coredirectorpublic2017-01-09 12:13
Reporterfearnop Assigned Topstorz  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
PlatformLinuxOSUbuntu ServerOS Version 16.04.1 LTS
Summary0000759: Wrong incrementation of pool volume names
DescriptionHi,

actually we're in testing phase of bareos.
While setting up the environment and taking the first drives, i've took a notice about a strange behaviour in the automatic volume naming regarding the number at the end of the volume.


The environment:


Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial


ii bareos-bconsole 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - text console
ii bareos-common 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - common files
ii bareos-database-common 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - common catalog files
ii bareos-database-mysql 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - MySQL backend
ii bareos-database-tools 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - database tools
ii bareos-director 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - director daemon
ii bareos-filedaemon 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - file daemon
ii bareos-filedaemon-python-plugin 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - file daemon Python plugin
ii bareos-storage 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - storage daemon
ii bareos-storage-fifo 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - storage daemon FIFO backend
ii bareos-storage-tape 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - storage daemon tape support
ii bareos-tools 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - common tools
ii bareos-webui 16.2.4-31.1 all Backup Archiving Recovery Open Sourced - webui






The config layout:

We have 3 kind of pools: A, B, C
In each of these we have Incremental, Differential and Full.


# pool/Class_A_Incremental.conf
Pool {
  Name = Class_A_Incremental
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 30 days
  Maximum Volume Bytes = 10G
  Maximum Volumes = 100
  Label Format = "Class_A_Incremental-"
}

# pool/Class_A_Differential.conf
Pool {
  Name = Class_A_Differential
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 30 days
  Maximum Volume Bytes = 10G
  Maximum Volumes = 100
  Label Format = "Class_A_Differential-"
}

# pool/Class_A_Full.conf
Pool {
  Name = Class_A_Full
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 30 days
  Maximum Volume Bytes = 10G
  Maximum Volumes = 100
  Label Format = "Class_A_Full-"
}


# pool/Class_B_Incremental.conf
Pool {
  Name = Class_B_Incremental
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 30 days
  Maximum Volume Bytes = 10G
  Maximum Volumes = 100
  Label Format = "Class_B_Incremental-"
}

# pool/Class_C_Differential.conf
Pool {
  Name = Class_C_Differential
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 30 days
  Maximum Volume Bytes = 10G
  Maximum Volumes = 100
  Label Format = "Class_C_Differential-"
}

# pool/Class_C_Full.conf
Pool {
  Name = Class_C_Full
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 30 days
  Maximum Volume Bytes = 10G
  Maximum Volumes = 100
  Label Format = "Class_C_Full-"
}


Starting environment:

1) Stopped director and storage daemon via init.d
2) Dropped tables via drop_bareos_tables
3) Generated tables via make_bareos_tables
4) Deleted all .bsr, .state and bareos-dir.bareos-dir.* files under /var/lib/bareos/
5) Deleted any volumes physically
6) Started director and storage daemon via init.d


My expecting behaviour is, that if i run a full job that fills data in Pool_A_Full, it will generate a file called Class_A_Full-0001 and will append upcoming full data till the limits are reached.
If i do the same with Pool B, i expect that bareos creates a file called Class_B_Full-0001 and so on. The same for differential and incremental.

But bareos has other plans.

Ive started a full job within class B. He created the file Class_B_Full-0001. As expected.
Then ive started a full job within class C. He created the file Class_C_Full-0002. What the hell?
After this ive started a full A job. He created the file Class_A_Full-0003. Ehhhm?

The time between the 3 tests are max. 1 minute.


Is this behaviour as expected and im wrong with my guess?



Best regards
Jens
Steps To ReproduceSee Description
TagsNo tags attached.

Activities

fearnop

fearnop

2017-01-07 13:21

reporter   ~0002499

There is a error in copy & pasting the pool configuration but in fact on the system, each pool is built like the A Pool, each with its class prefix.
fearnop

fearnop

2017-01-07 13:23

reporter   ~0002500

Pool {
  Name = Class_A_Differential
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 30 days
  Maximum Volume Bytes = 10G
  Maximum Volumes = 100
  Label Format = "Class_A_Differential-"
}
Pool {
  Name = Class_A_Full
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 30 days
  Maximum Volume Bytes = 10G
  Maximum Volumes = 100
  Label Format = "Class_A_Full-"
}
Pool {
  Name = Class_A_Incremental
  Pool Type = Backup
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 30 days
  Maximum Volume Bytes = 10G
  Maximum Volumes = 100
  Label Format = "Class_A_Incremental-"
}
pstorz

pstorz

2017-01-09 12:13

administrator   ~0002501

Hello,

the numbering is exactly as documented here:
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#AutomaticVolumeLabeling

"This number starts at 0001 and is incremented for each Volume the catalog contains".

Issue History

Date Modified Username Field Change
2017-01-07 13:17 fearnop New Issue
2017-01-07 13:21 fearnop Note Added: 0002499
2017-01-07 13:23 fearnop Note Added: 0002500
2017-01-09 12:13 pstorz Note Added: 0002501
2017-01-09 12:13 pstorz Status new => closed
2017-01-09 12:13 pstorz Assigned To => pstorz
2017-01-09 12:13 pstorz Resolution open => no change required