ADSM-L

[ADSM-L] ANR9999D: BlueARC NDMP backup

2008-02-07 15:06:23
Subject: [ADSM-L] ANR9999D: BlueARC NDMP backup
From: "c.hanover" <chanover AT UMICH DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 7 Feb 2008 14:49:55 -0500
I'm trying to get NDMP backups working for a client of ours.  This is
my first time playing with NDMP, so I may just be doing something
completely wrong.
What we've got:
TSM 5.4.1.2 on Linux, 3584 library with 4x 3592 drives.
Client has a BlueARC NAS device we're trying to get backed up via NDMP
using filer-to-server.  I don't have any data on the model, though I
could get it if it matters.

What I've done:
I set up a domain/policy/management class and copy groups for the
client (each client gets their own domain, it's how we do our
billing).  Copygroup type=backup specified a tocdestination.
I registered the node, type=nas.  I then registered a datamover, using
userid/password to access NDMP as set up on the NAS,
dataformat=ndmpdump.  Storage pools (disk/tape/copy) are all native
format, TOC gets its own set of destinations different than the
default management class storage pool (not necessary, but we have the
space)

From what I can tell from the documentation I've read, this is all
right.  (NDMPDUMP format pools are only required for filer-to-tape
configs, right?)  Judging by this:
http://www-1.ibm.com/support/docview.wss?uid=swg21242762
TSM should work happily with a BlueARC NAS.  Unfortunately, I get the
same error when I define the data mover as when I attempt a backup:

02/07/08   11:03:56  ANR9999D ndmpspi.c(1075): ThreadId <41> NDMP
Server does
                     not support Token Base Incremental Backup.
(SESSION: 34)
02/07/08   11:03:56  ANR1763E UPDATE DATAMOVER: Command failed - see
previous
                     error messages or view the activity log.
(SESSION: 34)

Google, unfortunately, has nothing on this error.  Searching this list
for BlueARC reveals one person who asked if anybody else had tried to
back them up with no responses.  There is no firewall between TSM and
NAS.  tcpdump shows communications going back and forth, and a
username is sent.
Is there something I've done wrong in my setup?  Is there something
that needs to be set up differently on the client side?  Any other
ideas?

-
Cameron Hanover
chanover AT umich DOT edu

"Necessity is the plea for every infringement of human freedom.  It is
the argument of tyrants; it is the creed of slaves."
--William Pitt, House of Commons, 11/18/1783

<Prev in Thread] Current Thread [Next in Thread>