On 10/ 7/14 07:12 PM, Peter Reilly wrote:

On 10/06/2014 04:14 PM, Marco van Wieringen wrote:
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.

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
...
}

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.

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
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.

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
The rest is not to interesting as it failed to establish the connection the NDMP state machine gets
a bit messed up.

--
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.

Reply via email to