NDMP Support

[Peter Reilly]

The README.NDMP file shows examples of storage of NDMPFile, but not
NDMPTape. I would like to backup a netapp filer to tape, via ndmp. Is
backup to tape via NDMP supported?

Thanks!

[Marco van Wieringen]

The answer kind of depends on how your tape subsystem is connected.
Any device controlled by a Bareos Storage Daemon can be used for
performing NDMP backups so also tapes. With NDMP you just specify
a paired storage which is any native storage of the Bareos storage
daemon. Some installs however have their tape subsystem controlled
via NDMP e.g. also connected to the NetAPP that won't work as we
don't have support for controlling the tape subsystem via NDMP the
Bareos Storage Daemon emulates a NDMP tape subsystem and we control
that via the native Bareos SD protocol.

The library that we imported has support for native NDMP tape support
but the DMA (Data Management Agent) in the Bareos Director has no code
to support it and its not envisioned that adding this missing piece will
happen any time soon as its a lot of work with little payback.

--
Marco van Wieringen marco.van...@bareos.com
Bareos GmbH & Co. KG Phone: +49-221-63069389
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens,
P. Storz, M. v. Wieringen

[Peter Reilly]

On 09/04/2014 05:03 AM, Marco van Wieringen wrote:
> Peter Reilly <peter_reilly <at> wycliffe.org> writes:
>
>> The README.NDMP file shows examples of storage of NDMPFile, but not
>> NDMPTape. I would like to backup a netapp filer to tape, via ndmp. Is
>> backup to tape via NDMP supported?
> The answer kind of depends on how your tape subsystem is connected.
> Any device controlled by a Bareos Storage Daemon can be used for
> performing NDMP backups so also tapes. With NDMP you just specify
> a paired storage which is any native storage of the Bareos storage
> daemon. Some installs however have their tape subsystem controlled
> via NDMP e.g. also connected to the NetAPP that won't work as we
> don't have support for controlling the tape subsystem via NDMP the
> Bareos Storage Daemon emulates a NDMP tape subsystem and we control
> that via the native Bareos SD protocol.
>
> The library that we imported has support for native NDMP tape support
> but the DMA (Data Management Agent) in the Bareos Director has no code
> to support it and its not envisioned that adding this missing piece will
> happen any time soon as its a lot of work with little payback.
>

Thanks, that helps. I'm using a Dell ML6000 loader, with two drives,
attached to the bareos host. I've added "PairedStorage = tape" to the
Storage definition for tape.

I don't understand the function of the DMA for the Director.

My DMA configuration in the SD looks like this:

Ndmp {
Name = orlbacula-ndmp-dma
Username = root
Password = password
AuthType = Clear
}


The message I'm getting currently when I try to dump to tape is:

Start NDMP Backup JobId 145585,
Job=NDMP-SMTAPE-boaz4-backup.2014-09-04_15.24.37_03
Using Device "Drive-0" to write.
Fatal error: Illegal protocol 0 for NDMP Job
Error: Director's comm line to SD dropped.

[Marco van Wieringen]

Peter Reilly <peter_reilly <at> wycliffe.org> writes:


>
> Thanks, that helps. I'm using a Dell ML6000 loader, with two drives,
> attached to the bareos host. I've added "PairedStorage = tape" to the
> Storage definition for tape.
>
> I don't understand the function of the DMA for the Director.
>

The DMA is the Data Management Agent and is the code that performs
the actual NDMP backup e.g. connect to your storage and to your NetAPP
box and get them to perform a NDMP backup.

> My DMA configuration in the SD looks like this:
>
> Ndmp {
> Name = orlbacula-ndmp-dma
> Username = root
> Password = password
> AuthType = Clear
> }
>

I hope this is a happy typo orlbacula ...

The above is the entry used by the DMA in the director to login into
the Bareos SD using the NDMP protocol.

> The message I'm getting currently when I try to dump to tape is:
>
> Start NDMP Backup JobId 145585,
> Job=NDMP-SMTAPE-boaz4-backup.2014-09-04_15.24.37_03
> Using Device "Drive-0" to write.
> Fatal error: Illegal protocol 0 for NDMP Job
> Error: Director's comm line to SD dropped.
>

Seems you didn't specify a protocol for the NDMP client. Take a good
look at the example you are at least missing the protocol.

#
# A NDMP Client.
#
Client {
Name = <ndmp_data_server>-ndmp
Address = ...
Port = 10000
Protocol = NDMPv4
Auth Type = Clear # Clear == Clear Text, MD5 ==
Challenge protocol
Username = "ndmp" # username of the NDMP user on the
DATA AGENT e.g. storage box being backuped.
Password = "test" # password of the NDMP user on the
DATA AGENT e.g. storage box being backuped.
}

Its also better to test things before even trying to run a backup job.
e.g. a status client=ndmp-client-name will query the NDMP server via the
NDMP protocol and show you things like what filesystems it has etc. This
also verifies that you configured the things right. Same you can do a
status storage=ndmp-storage name and it will see that its a NDMP storage
and contact the storage via its paired storage entry which also verifies
if that is setup right.

[Adam Podstawka]

Hi,

is there a possibility to get an daily Summary Report for the Backups
through mail instead of a mail for every job?

Greets
Adam


--
Adam Podstawka
Informatician - Bioinformatics
Leibniz Institute DSMZ-German Collection of Microorganisms and Cell Cultures

[Frank Bergkemper]

Hi Adam,

one solution that might fit your needs is a shell script, which
generates a daily report for you and is executed via cron every 24 hours
or something like that, sending you the mail.

How to run the console from a shell script is described here:

http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-15600015.2.2

You may also consider the usage of a web interface, as it gives you a
quick overview whenever you want.

Perhaps you want to try out the new Bareos WebUI. It's currently in
early alpha state, but might be interesting for you, as it e.g. shows
you past 24 hour overviews/reports and more.

There are packages for all major distributions available now.

http://bareos.github.io/bareos-webui/

http://download.bareos.org/bareos/contrib/

https://github.com/bareos/bareos-webui/blob/master/doc/install/INSTALL.md

Regards
Frank

Am 08.09.2014 07:26, schrieb Adam Podstawka:
> Hi,
>
> is there a possibility to get an daily Summary Report for the Backups
> through mail instead of a mail for every job?
>
> Greets
> Adam
>
>


--

Frank Bergkemper frank.be...@dass-it.de
dass IT GmbH Phone: +49.221.3565666-94
http://www.dass-IT.de/ Fax : +49.221.3565666-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRB52500
GF: Stephan Dühr, Maik Außendorf, Jörg Steffens, Philipp Storz

[Peter Reilly]

On 09/05/2014 04:00 AM, Marco van Wieringen wrote:
> Peter Reilly <peter_reilly <at> wycliffe.org> writes:
>
>
>> Thanks, that helps. I'm using a Dell ML6000 loader, with two drives,
>> attached to the bareos host. I've added "PairedStorage = tape" to the
>> Storage definition for tape.
>>
>> I don't understand the function of the DMA for the Director.
>>
> The DMA is the Data Management Agent and is the code that performs
> the actual NDMP backup e.g. connect to your storage and to your NetAPP
> box and get them to perform a NDMP backup.
>
>
>> My DMA configuration in the SD looks like this:
>>
>> Ndmp {
>> Name = orlbacula-ndmp-dma
>> Username = root
>> Password = password
>> AuthType = Clear
>> }
>>
> I hope this is a happy typo orlbacula ...

Actually the configuration was imported from bacula 5.0.2. Perhaps I
should rename the director...

> The above is the entry used by the DMA in the director to login into
> the Bareos SD using the NDMP protocol.
>
>> The message I'm getting currently when I try to dump to tape is:
>>
>> Start NDMP Backup JobId 145585,
>> Job=NDMP-SMTAPE-boaz4-backup.2014-09-04_15.24.37_03
>> Using Device "Drive-0" to write.
>> Fatal error: Illegal protocol 0 for NDMP Job
>> Error: Director's comm line to SD dropped.
>>
> Seems you didn't specify a protocol for the NDMP client. Take a good
> look at the example you are at least missing the protocol.
>
> #
> # A NDMP Client.
> #
> Client {
> Name = <ndmp_data_server>-ndmp
> Address = ...
> Port = 10000
> Protocol = NDMPv4
> Auth Type = Clear # Clear == Clear Text, MD5 ==
> Challenge protocol
> Username = "ndmp" # username of the NDMP user on the
> DATA AGENT e.g. storage box being backuped.
> Password = "test" # password of the NDMP user on the
> DATA AGENT e.g. storage box being backuped.
> }

Thanks, sorry to take so long to reply. I did have a protocol
specified. But I probably haven't provided enough information.

Here are the clients.

Client {
Name = boaz3-ndmp
Address = 10.10.10.50
FDPort = 10000

Protocol = NDMPv4
Auth Type = Clear

Username = "username"
Password = "password"
}

Client {
Name = boaz4-ndmp
Address = 10.10.10.52
FDPort = 10000

Protocol = NDMPv4
Auth Type = Clear

Username = "username"
Password = "password"

}

> Its also better to test things before even trying to run a backup job.
> e.g. a status client=ndmp-client-name will query the NDMP server via the
> NDMP protocol and show you things like what filesystems it has etc. This
> also verifies that you configured the things right. Same you can do a
> status storage=ndmp-storage name and it will see that its a NDMP storage
> and contact the storage via its paired storage entry which also verifies
> if that is setup right.
>

Status client works. Here is a sample:

Select Client (File daemon) resource (1-149): 4

Data Agent 10.10.10.50 NDMPv4
Host info
hostname boaz3
os_type NetApp
os_vers NetApp Release 8.1.3P3 7-Mode
hostid 2014020112

Server info
vendor Network Appliance
product Network Appliance NDMP server FAS3220
revision 5.0
auths (1) NDMP4_AUTH_TEXT

Connection types
addr_types (2) NDMP4_ADDR_LOCAL NDMP4_ADDR_TCP

.
.
.
File system /vol/PROD_RV_T1_VOL00
physdev
unsupported 0x0
type WAFL
status online
space 2200414924800 total, 651923996672 used, 1548490928128 avail
inodes 31876689 total, 198 used
empty default env
.
.
.

Here is the jobdefs configuration for NDMP:

JobDefs {
Name = "DefaultNDMPJob"
Type = Backup
Protocol = NDMP
Level = Incremental
Backup Format = dump
FileSet = "NDMP-NFS-Fileset"
Schedule = "WeeklyCycle"
#Storage = NDMPFile
Storage = tape
Messages = Standard
Pool = Daily
Priority = 10
Write Bootstrap = "/var/lib/bareos/%c.bsr"
}

Here is a fileset:

###################################
# NDMP NFS Set
###################################

Fileset {
Name = "NDMP-NFS-Fileset"
Include {
Options {
meta = "USER=root"
}
File = /vol/nfs_oracle
}
}


Here is the job:

Run Backup job
JobName: NDMP-NFS-boaz4-backup
Level: Incremental
Client: boaz4-ndmp
Format: dump
FileSet: NDMP-NFS-Fileset
Pool: Daily (From Job IncPool override)
Storage: tape (From Job resource)
When: 2014-09-22 09:44:59
Priority: 10

And here is the full error:

22-Sep 09:45 director-dir JobId 145587: No prior Full backup Job record
found.
22-Sep 09:45 director-dir JobId 145587: No prior or suitable Full backup
found in catalog. Doing FULL backup.
22-Sep 09:45 director-dir JobId 145587: Start NDMP Backup JobId 145587,
Job=NDMP-NFS-boaz4-backup.2014-09-22_09.45.41_03
22-Sep 09:45 director-dir JobId 145587: Using Device "Drive-0" to write.
22-Sep 09:45 director-dir JobId 145587: Fatal error: Illegal protocol 0
for NDMP Job
22-Sep 09:45 director-dir JobId 145587: Error: Director's comm line to
SD dropped.
22-Sep 09:45 director-dir JobId 145587: Error: Bareos director-dir
13.2.2 (12Nov13):
Build OS: x86_64-unknown-linux-gnu redhat CentOS
release 6.2 (Final)
JobId: 145587
Job: NDMP-NFS-boaz4-backup.2014-09-22_09.45.41_03
Backup Level: Full (upgraded from Incremental)
Client: "boaz4-ndmp"
FileSet: "NDMP-NFS-Fileset" 2014-09-03 16:46:01
Pool: "Monthly" (From Job FullPool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "tape" (From Job resource)
Scheduled time: 22-Sep-2014 09:44:59
Start time: 22-Sep-2014 09:45:43
End time: 22-Sep-2014 09:45:43
Elapsed time: 0 secs
Priority: 10
NDMP Files Written: 0
SD Files Written: 0
NDMP Bytes Written: 0 (0 B)
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Volume name(s):
Volume Session Id: 1
Volume Session Time: 1411393214
Last Volume Bytes: 0 (0 B)
Termination: *** Backup Error ***

Non NDMP jobs run fine.

How can I better troubleshoot the error "Fatal error: Illegal protocol 0
for NDMP Job"?

Thanks!

[Marco van Wieringen]

On 09/22/14 04:01 PM, Peter Reilly wrote:
> I hope this is a happy typo orlbacula ...
> Actually the configuration was imported from bacula 5.0.2. Perhaps I
> should rename the director...
>

Its not to important you can name it anything you like.

>
> Thanks, sorry to take so long to reply. I did have a protocol
> specified. But I probably haven't provided enough information.
>
> Here are the clients.
>
> Client {
> Name = boaz3-ndmp
> Address = 10.10.10.50
> FDPort = 10000
> Protocol = NDMPv4
> Auth Type = Clear
> Username = "username"
> Password = "password"
> }
>
> Client {
> Name = boaz4-ndmp
> Address = 10.10.10.52
> FDPort = 10000
> Protocol = NDMPv4
> Auth Type = Clear
> Username = "username"
> Password = "password"
> }
>

Those look fine as you probably define two NDMP data agents here.

Ok then we can at least exclude the fact that there is a problem in the
setup of the
client config.

For whatever reason the Job doesn't have the right protocol as protocol
0 means native
protocol not NDMP. Are you sure you reference the JobDefs
"DefaultNDMPJob" in the
actual Job definition ? e.g.

JobDefs = "DefaultNDMPJob"


I get the feeling you are very close to getting it to work.

[Peter Reilly]

Thanks. I do reference the JobDefs "DefaultNDMPJob" in the Job definition.

Here is an example:

Job {
Name = NDMP-NFS-boaz3-backup
Client = boaz3-ndmp
JobDefs = DefaultNDMPJob
Schedule = "WeeklyCycle"
Write Bootstrap = /var/lib/bareos/boaz3-ndmp.bsr
Full Backup Pool = Monthly
Incremental Backup Pool = Daily
Differential Backup Pool = Weekly
Fileset = NDMP-NFS-Fileset
}

The only difference I see in protocol, is that for the client, and the
storage, I specified NDMPv4. (bareos-dir -t -v -c
/etc/bareos/bareos-dir.conf fails otherwise). For the jobdefs, it gave
me an error with "Protocol = NDMPv4", so I used "Protocol = NDMP" like
the example in the bareos_ndmp_readme.txt.

29-Sep 13:39 bareos-dir: ERROR TERMINATION at dird_conf.c:2007
Config error: Expected a Protocol Type keyword, got: NDMPv4
: line 68, col 19 of file /etc/bareos/bareos-dir.conf
Protocol = NDMPv4

I commented the "Protocol = NDMPv4" line entirely, and now have a
different error.

*m
29-Sep 14:38 orlbacula-dir JobId 145729: No prior Full backup Job record
found.
29-Sep 14:38 orlbacula-dir JobId 145729: No prior or suitable Full

backup found in catalog. Doing FULL backup.

29-Sep 14:38 orlbacula-dir JobId 145729: Start Backup JobId 145729,
Job=NDMP-NFS-boaz4-backup.2014-09-29_14.38.19_18
29-Sep 14:38 orlbacula-dir JobId 145729: Using Device "Drive-0" to write.
29-Sep 14:38 orlbacula-dir JobId 145729: Fatal error: Unable to
authenticate with File daemon at "10.10.10.52:10000". Possible causes:
Passwords or names not the same or
Maximum Concurrent Jobs exceeded on the FD or
FD networking messed up (restart daemon).
Please see
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#AuthorizationErrors
for help.
29-Sep 14:38 orlbacula-dir JobId 145729: Error: getmsg.c:196 Malformed
message: T
29-Sep 14:38 orlbacula-dir JobId 145729: Fatal error: bsock.c:551 Packet
size too big from "Client: boaz4-ndmp:10.10.10.52:10000. Terminating
connection.
29-Sep 14:38 orlbacula-dir JobId 145729: Fatal error: No Job status
returned from FD.
29-Sep 14:38 orlbacula-dir JobId 145729: Error: Bareos orlbacula-dir

13.2.2 (12Nov13):
Build OS: x86_64-unknown-linux-gnu redhat CentOS
release 6.2 (Final)

JobId: 145729
Job: NDMP-NFS-boaz4-backup.2014-09-29_14.38.19_18

Backup Level: Full (upgraded from Incremental)
Client: "boaz4-ndmp"
FileSet: "NDMP-NFS-Fileset" 2014-09-03 16:46:01
Pool: "Monthly" (From Job FullPool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "tape" (From Job resource)

Scheduled time: 29-Sep-2014 14:38:11
Start time: 29-Sep-2014 14:38:21
End time: 29-Sep-2014 14:38:26
Elapsed time: 5 secs
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0 (0 B)

SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s

Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 8
Volume Session Time: 1412014705

Last Volume Bytes: 0 (0 B)

Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Error
SD termination status: Waiting on FD

Termination: *** Backup Error ***

*

Looking at the network traffic, I see the following.

ngrep -d any -nn "" "port 9103 or 9102 or 9101 or 10000" -s1514 -q -Wbyline
interface: any
filter: ( port 9103 or 9102 or 9101 or 10000 ) and (ip or ip6)

T 127.0.0.1:52911 -> 127.0.0.1:9101 [AP]
....yes

T 127.0.0.1:9101 -> 127.0.0.1:52911 [AP]
....Job queued. JobId=145729


T 127.0.0.1:9101 -> 127.0.0.1:52911 [AP]
....You have messages.
....

T 172.18.2.31:36318 -> 172.18.2.31:9103 [AP]
...%Hello Director orlbacula-dir calling


T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
...9auth cram-md5 <1950766065.1412015901@orlbacula-sd> ssl=0


T 172.18.2.31:36318 -> 172.18.2.31:9103 [AP]
....password.

T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
....1000 OK auth


T 172.18.2.31:36318 -> 172.18.2.31:9103 [AP]
...:auth cram-md5 <1501389973.1412015901@orlbacula-dir> ssl=0


T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
....password.

T 172.18.2.31:36318 -> 172.18.2.31:9103 [AP]
....1000 OK auth


T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
....3000 OK Hello


T 172.18.2.31:36318 -> 172.18.2.31:9103 [AP]
...^JobId=145729 job=NDMP-NFS-boaz4-backup.2014-09-29_14.38.19_18
job_name=NDMP-NFS-boaz4-backup client_name=boaz4-ndmp type=66 level=70
FileSet=NDMP-NFS-Fileset NoAttr=0 SpoolAttr=0
FileSetMD5=669foH/s29+RP7+4a+Qu/C SpoolData=0 PreferMountedVols=1
SpoolSize=0 rerunning=0 VolSessionId=0 VolSessionTime=0 Quota=0
Protocol=0 BackupFormat=dump DumpLevel=0


T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
...[3000 OK Job SDid=8 SDtime=1412014705
Authorization=IBFM-NIOA-MPKM-GGMC-MFHA-PMDA-CNBK-IPOB


T 172.18.2.31:36318 -> 172.18.2.31:9103 [AP]
...fuse storage=tape media_type=ULTRIUM-LTO-4 pool_name=Monthly
pool_type=Backup append=1 copy=0 stripe=0


T 172.18.2.31:36318 -> 172.18.2.31:9103 [AP]
....use device=Autochanger
........

T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
...ZCatReq Job=NDMP-NFS-boaz4-backup.2014-09-29_14.38.19_18 GetVolInfo
VolName=WBT022 write=1


T 172.18.2.31:36318 -> 172.18.2.31:9103 [AP]
...L1000 OK VolName=WBT022 VolJobs=2 VolFiles=221 VolBlocks=1696807
VolBytes=109464477696 VolMounts=2 VolErrors=0 VolWrites=1696808
MaxVolBytes=0 VolCapacityBytes=0 VolStatus=Append Slot=20 MaxVolJobs=0
MaxVolFiles=0 InChanger=1 VolReadTime=7560 VolWriteTime=13651952500
EndFile=219 EndBlock=7306 LabelType=0 MediaId=353 EncryptionKey=


T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
..."3000 OK use device device=Drive-0


T 172.18.2.31:36318 -> 172.18.2.31:9103 [AP]
....run

T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
...EStatus Job=NDMP-NFS-boaz4-backup.2014-09-29_14.38.19_18 JobStatus=70


T 10.10.10.17:55335 -> 10.10.10.52:10000 [AP]
...%Hello Director orlbacula-dir calling


T 10.10.10.17:55335 -> 10.10.10.52:10000 [AP]
...%Hello Director orlbacula-dir calling


T 10.10.10.52:10000 -> 10.10.10.17:55335 [AP]
...<....T)..............................Connection successful...

T 172.18.2.31:36320 -> 172.18.2.31:9103 [AP]
...%Hello Director orlbacula-dir calling


T 172.18.2.31:9103 -> 172.18.2.31:36320 [AP]
...9auth cram-md5 <2074485908.1412015906@orlbacula-sd> ssl=0


T 172.18.2.31:36320 -> 172.18.2.31:9103 [AP]
....password.

T 172.18.2.31:9103 -> 172.18.2.31:36320 [AP]
....1000 OK auth


T 172.18.2.31:36320 -> 172.18.2.31:9103 [AP]
...9auth cram-md5 <619509447.1412015906@orlbacula-dir> ssl=0


T 172.18.2.31:9103 -> 172.18.2.31:36320 [AP]
....password.

T 172.18.2.31:36320 -> 172.18.2.31:9103 [AP]
....1000 OK auth


T 172.18.2.31:9103 -> 172.18.2.31:36320 [AP]
....3000 OK Hello


T 172.18.2.31:36320 -> 172.18.2.31:9103 [AP]
...8cancel Job=NDMP-NFS-boaz4-backup.2014-09-29_14.38.19_18


T 172.18.2.31:9103 -> 172.18.2.31:36320 [AP]
...\3000 JobId=145729 Job="NDMP-NFS-boaz4-backup.2014-09-29_14.38.19_18"
marked to be canceled.


T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
....

T 172.18.2.31:9103 -> 172.18.2.31:36318 [AP]
........

T 172.18.2.31:9103 -> 172.18.2.31:36320 [AP]
....

T 172.18.2.31:36320 -> 172.18.2.31:9103 [AP]
....


To me it looks like authentication is working, but then the job is
getting canceled by bareos. Perhaps this error is the revelant one:
"Packet size too big from".

[Marco van Wieringen]

Peter Reilly <peter_reilly <at> wycliffe.org> writes:


>

> Thanks. I do reference the JobDefs "DefaultNDMPJob" in the Job definition.
>
> Here is an example:
>
> Job {
> Name = NDMP-NFS-boaz3-backup
> Client = boaz3-ndmp
> JobDefs = DefaultNDMPJob
> Schedule = "WeeklyCycle"
> Write Bootstrap = /var/lib/bareos/boaz3-ndmp.bsr
> Full Backup Pool = Monthly
> Incremental Backup Pool = Daily
> Differential Backup Pool = Weekly
> Fileset = NDMP-NFS-Fileset
> }

Are you sure you also do that in the NDMP-NFS-boaz4-backup Job ?
As that is what the previous example run was about. I find it strange
that the protocol doesn't get inherited from the JobDef as I cannot
reproduce that on my install.

>
> The only difference I see in protocol, is that for the client, and the
> storage, I specified NDMPv4. (bareos-dir -t -v -c
> /etc/bareos/bareos-dir.conf fails otherwise). For the jobdefs, it gave
> me an error with "Protocol = NDMPv4", so I used "Protocol = NDMP" like
> the example in the bareos_ndmp_readme.txt.
>
> 29-Sep 13:39 bareos-dir: ERROR TERMINATION at dird_conf.c:2007
> Config error: Expected a Protocol Type keyword, got: NDMPv4
> : line 68, col 19 of file /etc/bareos/bareos-dir.conf
> Protocol = NDMPv4
>

Yes that is right backup protocol is native or ndmp the ndmpvX is only
for the client and storage authentication and specifies what version
of NDMP to use for the client or storage.

> I commented the "Protocol = NDMPv4" line entirely, and now have a
> different error.
>

No this is normal now it thinks it talking to a native client and
tries to authenticate using the normal authentication protocol
but on the NDMP port that is of course never going to work. I think
we need to concentrate on the Job parsing what does show jobs give
in bconsole ? (Most importantly for the Job you are trying to run.)

[Peter Reilly]

*show job=NDMP-NFS-boaz4-backup
Job: name=NDMP-NFS-boaz4-backup JobType=66 protocol=1 level=Incremental
Priority=10 Enabled=1
MaxJobs=1 Resched=0 Times=5 Interval=1,800 Spool=0
Accurate=0
--> Client: name=boaz4-ndmp protocol=3 authtype=1 address=10.10.10.52
FDport=10000 MaxJobs=1
JobRetention=6 months FileRetention=2 months AutoPrune=0
Passive=0 SoftQuota=0 SoftQuotaGrace=0 secs HardQuota=0 StrictQuotas=0
--> Catalog: name=MyCatalog address= DBport=0 db_name=bareos
db_driver=mysql db_user=bareos MutliDBConn=0
--> FileSet: name=NDMP-NFS-Fileset
O
N
I /vol/nfs_oracle
N
--> Schedule: name=WeeklyCycle
--> Run Level=Full
hour=21
mday=0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
23 24 25 26 27 28 29 30
month=0 1 2 3 4 5 6 7 8 9 10 11
wday=5
wom=0
woy=0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49 50 51 52 53
mins=5
--> Run Level=Differential
hour=21
mday=0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
23 24 25 26 27 28 29 30
month=0 1 2 3 4 5 6 7 8 9 10 11
wday=5
wom=1 2 3 4
woy=0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49 50 51 52 53
mins=5
--> Run Level=Incremental
hour=21
mday=0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
23 24 25 26 27 28 29 30
month=0 1 2 3 4 5 6 7 8 9 10 11
wday=0 1 2 3 4 6
wom=0 1 2 3 4
woy=0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49 50 51 52 53
mins=5
--> WriteBootstrap=/var/lib/bareos/boaz4-ndmp.bsr
--> Storage: name=tape protocol=0 authtype=0
address=gideon2.wycliffe.org SDport=9103 MaxJobs=8
DeviceName=Autochanger MediaType=ULTRIUM-LTO-4 PairedStorage=tape
StorageId=2
--> Pool: name=Daily PoolType=Backup
use_cat=1 use_once=0 cat_files=1
max_vols=10 auto_prune=1 VolRetention=6 days
VolUse=0 secs recycle=1 LabelFormat=*None*
CleaningPrefix=CLN LabelType=0
RecyleOldest=0 PurgeOldest=0 ActionOnPurge=0
MaxVolJobs=0 MaxVolFiles=0 MaxVolBytes=0
MigTime=0 secs MigHiBytes=0 MigLoBytes=0
JobRetention=0 secs FileRetention=0 secs
--> Pool: name=Monthly PoolType=Backup
use_cat=1 use_once=0 cat_files=1
max_vols=107 auto_prune=1 VolRetention=6 months
VolUse=0 secs recycle=1 LabelFormat=*None*
CleaningPrefix=CLN LabelType=0
RecyleOldest=0 PurgeOldest=0 ActionOnPurge=0
MaxVolJobs=0 MaxVolFiles=0 MaxVolBytes=0
MigTime=0 secs MigHiBytes=0 MigLoBytes=0
JobRetention=0 secs FileRetention=0 secs
--> Pool: name=Daily PoolType=Backup
use_cat=1 use_once=0 cat_files=1
max_vols=10 auto_prune=1 VolRetention=6 days
VolUse=0 secs recycle=1 LabelFormat=*None*
CleaningPrefix=CLN LabelType=0
RecyleOldest=0 PurgeOldest=0 ActionOnPurge=0
MaxVolJobs=0 MaxVolFiles=0 MaxVolBytes=0
MigTime=0 secs MigHiBytes=0 MigLoBytes=0
JobRetention=0 secs FileRetention=0 secs
--> Pool: name=Weekly PoolType=Backup
use_cat=1 use_once=0 cat_files=1
max_vols=21 auto_prune=1 VolRetention=14 days
VolUse=0 secs recycle=1 LabelFormat=*None*
CleaningPrefix=CLN LabelType=0
RecyleOldest=0 PurgeOldest=0 ActionOnPurge=0
MaxVolJobs=0 MaxVolFiles=0 MaxVolBytes=0
MigTime=0 secs MigHiBytes=0 MigLoBytes=0
JobRetention=0 secs FileRetention=0 secs
--> Messages: name=Standard
mailcmd=/usr/lib/bareos/bsmtp -h localhost -f "(Bareos) <%r>" -s
"Bareos: %t %e of %c %l" %r
opcmd=/usr/lib/bareos/bsmtp -h localhost -f "(Bareos) <%r>" -s
"Bareos: Intervention needed for %j" %r

[Marco van Wieringen]

Peter Reilly <peter_reilly <at> wycliffe.org> writes:


>

> *show job=NDMP-NFS-boaz4-backup
...

That all looks good. I had a look inside the DMA code and I confused
the error you got by some new code I added for making sure people are
not running normal Jobs against NDMP clients etc. The error you got
is generated when either the client or the storage has the wrong
protocol. As we have seen that the client looks alright I guess the
storage setup is wrong. What storage does the Job message show it will
use and how does the storage definition with that name look like in the
bareos-dir.conf ?

[Peter Reilly]

On 10/06/2014 03:06 PM, Marco van Wieringen wrote:
> Peter Reilly <peter_reilly <at> wycliffe.org> writes:
>
>
>> *show job=NDMP-NFS-boaz4-backup
> ...
>
> That all looks good. I had a look inside the DMA code and I confused
> the error you got by some new code I added for making sure people are
> not running normal Jobs against NDMP clients etc. The error you got
> is generated when either the client or the storage has the wrong
> protocol. As we have seen that the client looks alright I guess the
> storage setup is wrong. What storage does the Job message show it will
> use and how does the storage definition with that name look like in the
> bareos-dir.conf ?
>

# job
Select Job resource (1-156): 10

Run Backup job
JobName: NDMP-NFS-boaz4-backup
Level: Incremental
Client: boaz4-ndmp
Format: dump
FileSet: NDMP-NFS-Fileset
Pool: Daily (From Job IncPool override)
Storage: tape (From Job resource)

When: 2014-10-06 15:13:30
Priority: 10
OK to run? (yes/mod/no):

# from bareos-dir.conf
Storage {
Name = tape
Address = gideon2.wycliffe.org
SDPort = 9103
Maximum Concurrent Jobs = 8
Password = "password"
Device = Autochanger
Media Type = ULTRIUM-LTO-4
Autochanger = yes
PairedStorage = tape
}




--
Peter Reilly
Wycliffe Bible Translators
peter_...@wycliffe.org

[Marco van Wieringen]

Ah great you created a recursive definition where the Paired Storage
points to the native
storage. Yes that ain't going to work and is something I didn't think
about someone configuring
it that way.

You probably need something like this:

#
# Same storage daemon but via NDMP protocol.
# We link via the PairedStorage config option the Bareos SD instance
definition to a NDMP TAPE AGENT.
#
Storage {
Name = NDMPTape
Address = ... # N.B. Use a fully qualified name
here

Port = 10000
Protocol = NDMPv4

Auth Type = Clear # Clear == Clear Text, MD5 ==
Challenge protocol
Username = ndmp # username of the NDMP user on

the TAPE AGENT e.g. the Bareos SD but accessed via the NDMP protocol.

Password = test # password of the NDMP user on

the TAPE AGENT e.g. the Bareos SD but accessed via the NDMP protocol.
Device = FileStorage
Media Type = File
PairedStorage = Tape
}

e.g. a paired storage for the native storage. So leave the tape storage but
loose the PairedStorage there and create a new NDMP storage that points to
the NDMP port of the Bareos SD.

And then use NDMPTape as storage in your NDMP Job.

I also assume you have a NDMP definition in your bareos-sd.conf (see
README.NDMP)
https://github.com/bareos/bareos/blob/master/README.NDMP

That entry is referenced in the Storage definition in the bareos-dir.conf

[Peter Reilly]

Thanks. I wasn't sure I had storage correct.

The sd configuration now looks like this:

Storage {
Name = orlbacula-sd
SDPort = 9103
...
NDMP Enable = yes
#NDMP Snooping = yes
#NDMP Loglevel = 9
NDMP Port = 10000
}

Ndmp {
Name = orlbacula-dir
Username = username # same as username on netapp
Password = password # same as username on netapp
AuthType = Clear
}

Autochanger {
Name = Autochanger
Device = Drive-0, Drive-1
...
}

Device {
Name = Drive-0
Drive Index = 0
Media Type = ULTRIUM-LTO-4
...
}

Device {
Name = Drive-1
Drive Index = 1
Media Type = ULTRIUM-LTO-4
...
}



The dir configuration now looks like this:

Storage {
Name = NDMPTape
Address = gideon2.wycliffe.org

Port = 10000
Protocol = NDMPv4
Auth Type = Clear

Username = username # same as username on netapp
Password = password # same as username on netapp
Device = FileStorage # should this match Device= of
tape storage?
Media Type = File # should this match Media Type= of
tape storage?
PairedStorage = tape
}

PairedStorage is no longer listed in tape storage:

Storage {
Name = tape
...

Device = Autochanger
Media Type = ULTRIUM-LTO-4
Autochanger = yes

#PairedStorage = tape
}


Job refers to NDMPTape.

JobDefs {
Name = "DefaultNDMPJob"
...
Storage = NDMPTape
}




Now I have a different error.

Run Backup job
JobName: NDMP-NFS-boaz4-backup
Level: Incremental
Client: boaz4-ndmp
Format: dump
FileSet: NDMP-NFS-Fileset
Pool: Daily (From Job IncPool override)

Storage: NDMPTape (From Job resource)
When: 2014-10-07 13:00:47
Priority: 10
OK to run? (yes/mod/no): yes
Job queued. JobId=145875

07-Oct 13:00 orlbacula-dir JobId 145875: No prior Full backup Job record
found.
07-Oct 13:00 orlbacula-dir JobId 145875: No prior or suitable Full

backup found in catalog. Doing FULL backup.

07-Oct 13:00 orlbacula-dir JobId 145875: Start NDMP Backup JobId 145875,
Job=NDMP-NFS-boaz4-backup.2014-10-07_13.00.57_03
07-Oct 13:00 orlbacula-dir JobId 145875: Using Device "Drive-0" to write.
07-Oct 13:00 orlbacula-dir JobId 145875: Opening tape drive
AMMI-OMBC-EMBA-FBAF-BDOA-FFMN-DLPP-IGGC@/vol/nfs_oracle read/write
*m
07-Oct 13:01 orlbacula-sd JobId 145875: 3304 Issuing autochanger "load
slot 12, drive 0" command.
*m
07-Oct 13:01 orlbacula-sd JobId 145875: 3305 Autochanger "load slot 12,
drive 0", status is OK.
07-Oct 13:02 orlbacula-sd JobId 145875: Volume "WBT028" previously
written, moving to end of data.
07-Oct 13:02 orlbacula-sd JobId 145875: Ready to append to end of Volume
"WBT028" at file=2.
07-Oct 13:02 orlbacula-dir JobId 145875: Commanding tape drive to rewind
07-Oct 13:02 orlbacula-dir JobId 145875: ERR NDMP4_DATA_CONNECT
NDMP4_CONNECT_ERR
07-Oct 13:02 orlbacula-dir JobId 145875: Waiting for operation to halt
*m
07-Oct 13:02 orlbacula-dir JobId 145875: ERR NDMP4_DATA_ABORT
NDMP4_ILLEGAL_STATE_ERR
07-Oct 13:02 orlbacula-dir JobId 145875: ERR NDMP4_DATA_ABORT
NDMP4_ILLEGAL_STATE_ERR
07-Oct 13:02 orlbacula-dir JobId 145875: ERR NDMP4_DATA_ABORT
NDMP4_ILLEGAL_STATE_ERR
07-Oct 13:02 orlbacula-dir JobId 145875: ERR NDMP4_DATA_ABORT
NDMP4_ILLEGAL_STATE_ERR
07-Oct 13:02 orlbacula-dir JobId 145875: ERR NDMP4_DATA_ABORT
NDMP4_ILLEGAL_STATE_ERR
07-Oct 13:02 orlbacula-dir JobId 145875: ERR NDMP4_DATA_ABORT
NDMP4_ILLEGAL_STATE_ERR
07-Oct 13:02 orlbacula-dir JobId 145875: ERR NDMP4_DATA_ABORT
NDMP4_ILLEGAL_STATE_ERR
07-Oct 13:02 orlbacula-dir JobId 145875: Commanding tape drive to
NDMP9_MTIO_EOF 2 times
07-Oct 13:02 orlbacula-dir JobId 145875: Commanding tape drive to rewind
07-Oct 13:02 orlbacula-dir JobId 145875: Closing tape drive
AMMI-OMBC-EMBA-FBAF-BDOA-FFMN-DLPP-IGGC@/vol/nfs_oracle
07-Oct 13:02 orlbacula-dir JobId 145875: Operation did not halt,
something wrong
07-Oct 13:02 orlbacula-dir JobId 145875: Operation halted, stopping
07-Oct 13:02 orlbacula-dir JobId 145875: Operation ended in failure
07-Oct 13:02 orlbacula-dir JobId 145875: ERR NDMP4_DATA_STOP
NDMP4_ILLEGAL_STATE_ERR
07-Oct 13:02 orlbacula-dir JobId 145875: Error: Director's comm line to
SD dropped.
07-Oct 13:02 orlbacula-dir JobId 145875: Error: Bareos orlbacula-dir

13.2.2 (12Nov13):
Build OS: x86_64-unknown-linux-gnu redhat CentOS
release 6.2 (Final)

JobId: 145875
Job: NDMP-NFS-boaz4-backup.2014-10-07_13.00.57_03

Backup Level: Full (upgraded from Incremental)
Client: "boaz4-ndmp"
FileSet: "NDMP-NFS-Fileset" 2014-09-03 16:46:01
Pool: "Monthly" (From Job FullPool override)
Catalog: "MyCatalog" (From Client resource)

Storage: "NDMPTape" (From Job resource)
Scheduled time: 07-Oct-2014 13:00:47
Start time: 07-Oct-2014 13:00:59
End time: 07-Oct-2014 13:02:26
Elapsed time: 1 min 27 secs

Priority: 10
NDMP Files Written: 0
SD Files Written: 0
NDMP Bytes Written: 0 (0 B)

SD Bytes Written: 84 (84 B)

Rate: 0.0 KB/s
Volume name(s):
Volume Session Id: 1

Volume Session Time: 1412700890

Last Volume Bytes: 0 (0 B)
Termination: *** Backup Error ***

[Marco van Wieringen]

That looks about right.

>
>
> The dir configuration now looks like this:
>
> Storage {
> Name = NDMPTape
> Address = gideon2.wycliffe.org
> Port = 10000
> Protocol = NDMPv4
> Auth Type = Clear
> Username = username # same as username on netapp
> Password = password # same as username on netapp
> Device = FileStorage # should this match Device= of
> tape storage?
> Media Type = File # should this match Media Type= of
> tape storage?
> PairedStorage = tape
> }
>

The Username/Password needs to be the same as in the NDMP section of the
storage daemon
above NOT the same as on the NetAPP e.g. the NDMP data agent. Unless
ofcourse you configured
the same but this comment is going to be confusing in some time.

Device needs to be Autochanger and MediaType ULTRIUM-LTO-4 e.g. you just
clone the original storage
definition and add the NDMP specific stuff.

That seems to be that the NDMP DMA (e.g. the NetAPP) cannot connect to
the port used by the
NDMP TAPE agent on he Bareos Storage Daemon.

Make sure the boxes can see each other (e.g. routing is ok) and there is
no nasty firewall
in between.

The rest is not to interesting as it failed to establish the connection
the NDMP state machine gets
a bit messed up.

[Peter Reilly]

On 10/07/2014 01:44 PM, Marco van Wieringen wrote:
> That seems to be that the NDMP DMA (e.g. the NetAPP) cannot connect to
> the port used by the
> NDMP TAPE agent on he Bareos Storage Daemon.
>
> Make sure the boxes can see each other (e.g. routing is ok) and there
> is no nasty firewall
> in between.

They are on different networks, so I needed to add an address, and then
it worked. THANKS!!!

Storage {
Name = NDMPTape
Address = 10.10.10.17
...
}

07-Oct 14:45 orlbacula-dir JobId 145884: Bareos orlbacula-dir 13.2.2

(12Nov13):
Build OS: x86_64-unknown-linux-gnu redhat CentOS
release 6.2 (Final)

JobId: 145884
Job: NDMP-NFS-boaz4-backup.2014-10-07_14.28.39_06

Backup Level: Full (upgraded from Incremental)
Client: "boaz4-ndmp"
FileSet: "NDMP-NFS-Fileset" 2014-09-03 16:46:01
Pool: "Monthly" (From Job FullPool override)
Catalog: "MyCatalog" (From Client resource)

Storage: "NDMPTape" (From Job resource)

Scheduled time: 07-Oct-2014 14:28:37
Start time: 07-Oct-2014 14:28:41
End time: 07-Oct-2014 14:45:41
Elapsed time: 17 mins
Priority: 10
NDMP Files Written: 9,047
SD Files Written: 1
NDMP Bytes Written: 39,316,013,056 (39.31 GB)
SD Bytes Written: 39,316,064,353 (39.31 GB)
Rate: 38545.1 KB/s
Volume name(s): WBT028
Volume Session Id: 2
Volume Session Time: 1412706436
Last Volume Bytes: 39,345,417,216 (39.34 GB)
Termination: Backup OK

[Oliver Weinmann]

Hi,

I have a similar problem. I tried to backup a Netapp Filer running Clustered Data Ontap 8.3RC1.

I can lookup the client via NDMP just fine. Also the storage works.

Running the BackupNDMPSMTape backup job, I get the following error after a while:

08-Apr 16:55 bareos-dir JobId 337: No prior Full backup Job record found.
08-Apr 16:55 bareos-dir JobId 337: No prior or suitable Full backup found in catalog. Doing FULL backup.
08-Apr 16:55 bareos-dir JobId 337: Start NDMP Backup JobId 337, Job=BackupNDMPSMTape.2015-04-08_16.55.40_10
08-Apr 16:55 bareos-dir JobId 337: Using Device "FileStorage" to write.
08-Apr 16:57 bareos-dir JobId 337: err connect failed: Connection timed out
08-Apr 16:57 bareos-dir JobId 337: Error: getmsg.c:196 Malformed message:
08-Apr 16:57 bareos-dir JobId 337: Error: Director's comm line to SD dropped.
08-Apr 16:57 bareos-dir JobId 337: Error: Bareos bareos-dir 14.2.2 (12Dec14):
Build OS: x86_64-suse-linux-gnu suse openSUSE 13.2 (Harlequin) (x86_64)
JobId: 337
Job: BackupNDMPSMTape.2015-04-08_16.55.40_10

Backup Level: Full (upgraded from Incremental)

Client: "gedasanbak-ndmp"
FileSet: "NDMP SMtape Fileset" 2015-04-07 15:10:32
Pool: "NDMPFile" (From Job resource)

Catalog: "MyCatalog" (From Client resource)

Storage: "NDMPFile" (From Pool resource)
Scheduled time: 08-Apr-2015 16:55:39
Start time: 08-Apr-2015 16:55:42
End time: 08-Apr-2015 16:57:51
Elapsed time: 2 mins 9 secs
Priority: 10

NDMP Files Written: 0
SD Files Written: 0
NDMP Bytes Written: 0 (0 B)

SD Bytes Written: 0 (0 B)

Rate: 0.0 KB/s
Volume name(s):

Volume Session Id: 3
Volume Session Time: 1428504240

Last Volume Bytes: 0 (0 B)
Termination: *** Backup Error ***

Any clues?

[Marco van Wieringen]

Seems you have some network problem. The err connect failed comes from
the NDMP library. There are plenty of debug sessions explained on the
mailinglist regarding NDMP. Look into

NDMP Snooping = yes
NDMP Loglevel = 7

But also keep in mind that there needs to be an open network connection
between the NAS box and your Bareos SD as that emulates the NDMP tape agent
and that can listen on any port the NDMP protocol negotiates.

The network layout looks like this normally:

DIR DMA => NDMP Data Agent (10000)
DIR DMA => NDMP Tape Agent (10000)
NDMP Data Agent => NDMP Tape Agent (any negotiated port.)

So your problem can be in a numerous number of access
paths.

The protocol snooping and high loglevel will at least show where it tries
to connect although the output is a bit cryptic.

[Oliver Weinmann]

Yes it was indeed a networking problem. I had to add the NDMP address line in the configuration. Now it works fine. Only the restore doesn't work yet. I guess I have to try it with the unstable bareos version.

I'm hitting this bug:

https://bugs.bareos.org/view.php?id=374

I'm running 14.2.2 currently

[Marco van Wieringen]

Yes compile 14.2.3 yourself or buy a subscription.
I also never got feedback on the fact if things are now fully
fixed from the reporter of that bug. And as nobody is paying
anything for NDMP support it probably will stay in its current
form. So some trial on error then again we are one of the few
who have a free version of NDMP next to Amanda.

[Oliver Weinmann]

Ok, using the nightly build appliance I get another error:

Created /var/lib/bareos/bareos-sd.core.2039 for doing postmortem debugging

warning: /etc/gdbinit.d/gdb-heap.py: No such file or directory
[New LWP 2040]
[New LWP 2042]
[New LWP 2043]
[New LWP 2045]
[New LWP 2079]
[New LWP 2081]
[New LWP 2039]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/bareos-sd'.
#0 0x00007fa0d3c4814d in nanosleep () from /lib64/libpthread.so.0
$1 = 1701994850
$2 = 27208568
$3 = 27208632
/usr/lib/bareos/scripts/btraceback.gdb:4: Error in sourced command file:
No symbol table is loaded. Use the "file" command.


I copied across the same working config files from the stable appliance. I only had to append a block size to the client definition of the netapp filer.

[Marco van Wieringen]

Yes SM_TAPE NDMP dumps of NetAPP needs a specific blocksize with increments
of 4 Kb. Seems you run into a null pointer deference somewhere. But as you
don't have the debug packages loaded your binaries are missing any debug
symbols
so the crash dump is kind of useless.

So with this output I have no clue what goes wrong.

[Oliver Weinmann]

What packages do I need to install / load?

[Marco van Wieringen]

On 04/10/15 11:36 AM, Oliver Weinmann wrote:
> What packages do I need to install / load?

Depending on the packaging bareos-debug or bareos-dbg

[Oliver Weinmann]

I can only see the package bareos-debugsource... Do I need to add an additional installation source?

[Marco van Wieringen]

Oliver Weinmann <oliver.weinmann <at> googlemail.com> writes:

>
> I can only see the package bareos-debugsource... Do I need to add an
> additional installation source?

Nope for rpm based OSes its bareos-debuginfo and for debian based
OSes bareos-dbg

So its debuginfo not debug as I said earlier.