On 09/27/2014 05:35 AM, Marco van Wieringen wrote:
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.
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
.
.
.
Ok then we can at least exclude the fact that there is a problem in
the setup of the
client config.
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"?
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.
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".
--
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.
