On 10/ 6/14 09:41 PM, Peter Reilly wrote:
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
}
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
--
Marco van Wieringen [email protected]
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
--
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.
