View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000770bareos-corestorage daemonpublic2017-01-18 14:382017-01-23 15:04
Reporterhop Assigned Tomaik  
PrioritynormalSeveritytextReproducibilityalways
Status closedResolutionno change required 
PlatformLinuxOSUbuntuOS Version12.04
Product Version16.2.4 
Summary0000770: Virtual Backup Problem mit mehreren Storage Locations
DescriptionWenn man den Incremental und den Consolidation Pool auf unterschiedliche HW-Devices legen möchte, muss man dafür zwei Storage-Locations (und lt. Dokumentation File-Types) anlegen.
Wenn man dies nach Dokumentation macht, scheitert der Consolidation Job kläglich, denn es scheint, als störe er sich an den File-Types der Locations.

Siehe Fehlermeldung unter add. Info.
Additional Information18-Jan 13:05 qdehd4-dir JobId 126586: Start Virtual Backup JobId 126586, Job=elvis-fs-job.2017-01-18_13.05.03_38
18-Jan 13:05 qdehd4-dir JobId 126586: Consolidating JobIds 126520,126188 18-Jan 13:05 qdehd4-dir JobId 126586: Bootstrap records written to /var/lib/bareos/qdehd4-dir.restore.5.bsr
18-Jan 13:05 qdehd4-dir JobId 126586: Using Device "FileStorage" to read.
18-Jan 13:05 qdehd4-dir JobId 126586: Using Device "SANStorage" to write.
18-Jan 13:05 qdehd4-sd JobId 126586: acquire.c:114 Changing read device. Want Media Type="File2" have="File"
  device="FileStorage" (/var/lib/bareos/storage) 18-Jan 13:05 qdehd4-sd JobId 126586: Fatal error: acquire.c:168 No suitable device found to read Volume "AI-Consolidate-5719"
18-Jan 13:05 qdehd4-sd JobId 126586: Elapsed time=412428:05:06, Transfer rate=0 Bytes/second 18-Jan 13:05 qdehd4-dir JobId 126586: Error: Bareos qdehd4-dir 16.2.4 (01Jul16):
  Build OS: x86_64-pc-linux-gnu ubuntu Ubuntu 14.04 LTS
  JobId: 126586
  Job: elvis-fs-job.2017-01-18_13.05.03_38
  Backup Level: Virtual Full
  Client: "elvis-fs-fd" 16.2.4 (01Jul16) x86_64-pc-linux-gnu,ubuntu,Ubuntu 16.04 LTS,xUbuntu_16.04,x86_64
  FileSet: "elvis-fileserver-fileset" 2016-10-05 18:05:01
  Pool: "AI-Consolidated" (From Job Pool's NextPool resource)
  Catalog: "MyCatalog" (From Client resource)
  Storage: "SANFile" (From Storage from Pool's NextPool resource)
  Scheduled time: 18-Jan-2017 13:05:03
  Start time: 11-Jan-2017 10:22:21
  End time: 11-Jan-2017 10:22:25
  Elapsed time: 4 secs
  Priority: 10
  SD Files Written: 0
  SD Bytes Written: 0 (0 B)
  Rate: 0.0 KB/s
  Volume name(s):
  Volume Session Id: 118
  Volume Session Time: 1484572517
  Last Volume Bytes: 0 (0 B)
  SD Errors: 1
  SD termination status: Fatal Error
  Accurate: yes
  Termination: *** Backup Error ***
Tagsalways incremental, support

Activities

maik

maik

2017-01-20 13:04

administrator   ~0002515

Please add an English description.
maik

maik

2017-01-20 13:06

administrator   ~0002516

Probably configuration / consulting issue
hop

hop

2017-01-20 15:56

reporter   ~0002518

The Documentation states, that one has to Define seperate File-Types for two Storages (eg. two mount-points) on the same Storage-Server(=Daemon):

Device {
  Name = FileStorage
  Media Type = File
  Archive Device = /var/lib/bareos/storage
  ...
}

Device {
  Name = SANStorage
  Media Type = File2
  Archive Device = /var/lib/bareos/SAN
  ...
}

Doing so and placing Incremental- and Consolidation-Pool on each one, leads to the stated Error Message (under Additional Info).
maik

maik

2017-01-20 16:05

administrator   ~0002519

Documentation says:
"For the Always Incremental Backup Scheme at least two storages are needed."

It does _not_ say you need different storage _types_

http://doc.bareos.org/master/html/bareos-manual-main-reference.html#StoragesAndPools
maik

maik

2017-01-20 16:06

administrator   ~0002520

Please use Mailinglist or Support for configuration help.
hop

hop

2017-01-20 16:59

reporter   ~0002521

It does not say so THERE !!
Maybe you are right, and my problem is solvable with reconfiguration, but then this still is an documentation issue, because I clearly states in the last sentence under:
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveSdDeviceMedia%20Type

Media Type = <strname>
    (required)
    The specified value ...
...configuration file.

    Even though the ...
... incompatible media.

    For example, if you ...
...for all devices.

    In addition, if you are using disk storage, each Device resource will generally have a different mount point or directory. In order for Bareos to select the correct Device resource, each one must have a unique Media Type.

<quote-end>

So I did like the dok says, which leads to the probs.
maik

maik

2017-01-23 15:04

administrator   ~0002524

Last edited: 2017-01-23 15:04

 For Always Incremental you need to have identical Media Type on involved devices. Documentation will get revised.

Issue History

Date Modified Username Field Change
2017-01-18 14:38 hop New Issue
2017-01-20 13:04 maik Note Added: 0002515
2017-01-20 13:05 maik Tag Attached: support
2017-01-20 13:06 maik Note Added: 0002516
2017-01-20 13:06 maik Severity block => text
2017-01-20 15:56 hop Note Added: 0002518
2017-01-20 16:03 maik Tag Attached: always incremental
2017-01-20 16:05 maik Note Added: 0002519
2017-01-20 16:06 maik Note Added: 0002520
2017-01-20 16:06 maik Status new => closed
2017-01-20 16:06 maik Resolution open => no change required
2017-01-20 16:59 hop Note Added: 0002521
2017-01-20 16:59 hop Status closed => feedback
2017-01-20 16:59 hop Resolution no change required => reopened
2017-01-23 15:04 maik Note Added: 0002524
2017-01-23 15:04 maik Status feedback => closed
2017-01-23 15:04 maik Assigned To => maik
2017-01-23 15:04 maik Resolution reopened => no change required
2017-01-23 15:04 maik Note Edited: 0002524