View Issue Details

IDProjectCategoryView StatusLast Update
0000795bareos-core[All Projects] directorpublic2019-07-15 10:50
ReporterwilfulAssigned To 
PriorityhighSeverityminorReproducibilityhave not tried
Status feedbackResolutionopen 
PlatformLinuxOSCentOSOS Version7.1
Product Version16.2.4 
Target VersionFixed in Version 
Summary0000795: Invalid name for volume
DescriptionHi,

I have several servers with customized Bareos clients.
Recently I noticed that during a night backup, one file incorrectly creates a volume file.

Installed packages:

bareos-bconsole-16.2.4-12.1.el7.x86_64
bareos-filedaemon-16.2.4-12.1.el7.x86_64
bareos-database-common-16.2.4-12.1.el7.x86_64
bareos-director-16.2.4-12.1.el7.x86_64
bareos-common-16.2.4-12.1.el7.x86_64
bareos-storage-16.2.4-12.1.el7.x86_64
bareos-client-16.2.4-12.1.el7.x86_64
bareos-database-mysql-16.2.4-12.1.el7.x86_64
bareos-database-tools-16.2.4-12.1.el7.x86_64
bareos-16.2.4-12.1.el7.x86_64
bareos-webui-16.2.4-31.1.el7.noarch
python-bareos-0.3.1487336620.94de78e-42.1.el7.x86_64

Installed from official repositories

Clients installed via bconsole

For example:
configure add client name=$NAME address=$IP password=$PW
configure add job name=$NAME-mysql client=$NAME jobdefs=StandardLinuxJobMysql

client]# cat client1.conf client2.conf
Client {
  Name = client1
  Address = ip1
  Password = ***
}
Client {
  Name = client2
  Address = ip2
  Password = ***
}

job]# cat *client1* *client2*
Job {
  Name = client2-common
  Client = client2
  JobDefs = StandardLinuxJobCommon
}
Job {
  Name = client2-content
  Client = client2
  JobDefs = StandardLinuxJobContent
}
Job {
  Name = client2-mysql
  Client = client2
  JobDefs = StandardLinuxJobMysql
}
Job {
  Name = client1-common
  Client = client1
  JobDefs = StandardLinuxJobCommon
  Storage = another-storage
}
Job {
  Name = client1-content
  Client = client1
  JobDefs = StandardLinuxJobContent
  Storage = another-storage
}
Job {
  Name = client1-mysql
  Client = client1
  JobDefs = StandardLinuxJobMysql
  Storage = another-storage
}

jobdefs]# cat StandardLinuxJob*
JobDefs {
    Name = StandardLinuxJobCommon
    Type = Backup
    FileSet = StandardLinuxFileSetCommon
    Storage = first-storage
    Pool = DefaultCommonPool
    Full Backup Pool = FullCommonPool
    Incremental Backup Pool = IncCommonPool
    Differential Backup Pool = DiffCommonPool
    Prefer Mounted Volumes = no
    Write Bootstrap = "%c_%n.bsr"
    Schedule = PrimaryBackupCycle
    Priority = 7
    Messages = Standard
    Maximum Bandwidth = 10Mb/s
    Maximum Concurrent Jobs = 2
}
JobDefs {
    Name = StandardLinuxJobContent
    Type = Backup
    FileSet = StandardLinuxFileSetContent
    Storage = first-storage
    Pool = DefaultContentPool
    Full Backup Pool = FullContentPool
    Incremental Backup Pool = IncContentPool
    Differential Backup Pool = DiffContentPool
    Prefer Mounted Volumes = no
    Write Bootstrap = "%c_%n.bsr"
    Schedule = PrimaryBackupCycle
    Priority = 10
    Messages = Standard
    Maximum Bandwidth = 10Mb/s
    Maximum Concurrent Jobs = 2
}
JobDefs {
    Name = StandardLinuxJobMysql
    Client Run Before Job = /root/scripts/templates/bacula/mysqldump.sh
    Type = Backup
    FileSet = StandardLinuxFileSetMysql
    Storage = first-storage
# Level = Full
    Pool = DefaultMysqlPool
    Full Backup Pool = FullMysqlPool
    Incremental Backup Pool = IncMysqlPool
    Differential Backup Pool = DiffMysqlPool
    Prefer Mounted Volumes = no
    Write Bootstrap = "%c_%n.bsr"
    Schedule = PrimaryBackupCycle
    Priority = 10
    Messages = Standard
    Maximum Bandwidth = 10Mb/s
}
See what happens:
1355 is a backup for the client "Client1", and it creates a volume named "client2-IncMysqlPool-20170310-0012-1360"

bareos-dir JobId 1355: Bareos bareos-dir 16.2.4 (01Jul16):
Build OS: x86_64-redhat-linux-gnu redhat Red Hat Enterprise Linux Server release 7.0 (Maipo)
JobId: 1355
Job: client1-mysql.2017-03-10_00.05.14_19
Backup Level: Incremental, since=2017-03-09 00:11:56
Client: "client1" 16.2.4 (01Jul16) x86_64-redhat-linux-gnu,redhat,Red Hat Enterprise Linux Server release 6.5 (Santiago),RHEL_6,x86_64
FileSet: "StandardLinuxFileSetMysql" 2017-02-16 10:53:08
Pool: "IncMysqlPool" (From Job IncPool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "another-storage" (From Job resource)
Scheduled time: 10-Mar-2017 00:05:14
Start time: 10-Mar-2017 00:12:23
End time: 10-Mar-2017 00:12:28
Elapsed time: 5 secs
Priority: 10
FD Files Written: 3
SD Files Written: 3
FD Bytes Written: 35,636,512 (35.63 MB)
SD Bytes Written: 35,636,896 (35.63 MB)
Rate: 7127.3 KB/s
Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s): client2-IncMysqlPool-20170310-0012-1360
Volume Session Id: 26
Volume Session Time: 1488542340
Last Volume Bytes: 35,664,110 (35.66 MB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

bareos-sd JobId 1355: Labeled new Volume "client2-IncMysqlPool-20170310-0012-1360" on device "storage-device-01" (/mnt/backup/bareos-dir)

After that, Client2 "creates" a file with the same name:

bareos-dir JobId 1360: Bareos bareos-dir 16.2.4 (01Jul16):
Build OS: x86_64-redhat-linux-gnu redhat Red Hat Enterprise Linux Server release 7.0 (Maipo)
JobId: 1360
Job: client2-mysql.2017-03-10_00.05.14_24
Backup Level: Incremental, since=2017-03-09 00:20:51
Client: "client2" 16.2.4 (01Jul16) x86_64-redhat-linux-gnu,redhat,Red Hat Enterprise Linux Server release 6.5 (Santiago),RHEL_6,x86_64
FileSet: "StandardLinuxFileSetMysql" 2017-02-16 10:53:08
Pool: "IncMysqlPool" (From Job IncPool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "first-storage" (From Job resource)
Scheduled time: 10-Mar-2017 00:05:14
Start time: 10-Mar-2017 00:20:36
End time: 10-Mar-2017 00:23:09
Elapsed time: 2 mins 33 secs
Priority: 10
FD Files Written: 4
SD Files Written: 4
FD Bytes Written: 1,458,860,749 (1.458 GB)
SD Bytes Written: 1,458,861,269 (1.458 GB)
Rate: 9535.0 KB/s
Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s): client2-IncMysqlPool-20170310-0020-1360
Volume Session Id: 260
Volume Session Time: 1488775384
Last Volume Bytes: 1,459,943,955 (1.459 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK

bareos-sd JobId 1360: Labeled new Volume "client2-IncMysqlPool-20170310-0020-1360" on device "storage-device-02" (/mnt/backup/bareos-dir).

I can not understand how this is possible, why it happens, and how to deal with it. On this and I will forgive the help from you.
         
This happens only at night, according to the planned schedule. If I start manually, then everything is called correct.
Schedule {
  Name = "PrimaryBackupCycle"
  run = Full 1st Sun at 00:05
  run = Differential 2nd-5th Sun at 00:05
  run = Incremental Mon-Sat at 00:05
}
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

wilful

wilful

2017-03-20 05:58

reporter   ~0002613

I found the problem

If Job failed, when next job use prelabeled volume from failed job.

Can I change this behavior? It is necessary that a new Label and Volume
arogge

arogge

2019-07-15 10:50

developer   ~0003472

These two are not the same (0012 vs. 0020):
client2-IncMysqlPool-20170310-0012-1360
client2-IncMysqlPool-20170310-0020-1360

So what is the issue?

Issue History

Date Modified Username Field Change
2017-03-10 07:15 wilful New Issue
2017-03-20 05:58 wilful Note Added: 0002613
2019-07-15 10:50 arogge Status new => feedback
2019-07-15 10:50 arogge Note Added: 0003472