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!
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
