ADSM-L

Re: [ADSM-L] ANR9999D: BlueARC NDMP backup

2008-02-12 11:25:00
Subject: Re: [ADSM-L] ANR9999D: BlueARC NDMP backup
From: "c.hanover" <chanover AT UMICH DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 12 Feb 2008 11:22:15 -0500
Just in case anybody runs into this in the future:

BlueARC support pointed me in the right direction.
`ndmp-option -d tokens on`, followed by an NDMP service restart on the
NAS made backups work.  Now to figure out the rest of the NDMP voodoo..

-
Cameron Hanover
chanover AT umich DOT edu

Our integrity sells for so little, but it is all we really have. It is
the very last inch of us, but within that inch, we are free.
--Valerie (V for Vendetta)

On Feb 7, 2008, at 8:53 PM, Lloyd Dieter wrote:

It sounds like you're trying to backup to a disk pool, which is
supposed to work with 5.4 and above with Netapp/Nseries and Celerra.

In our case, the TSM server is Linux RH4, V5.4, to SAN attached 3584
with LTO3 drives.

I couldn't get it to work with BlueArc, and I went down the path
with their tech people...the response was that they'd never had
anyone try that yet...not sure if I believe that or not.  What I
gathered from the exercise was that the BlueArc apparently wasn't
capable of doing NDMP 3-way communication.

In our case, NDMP backups direct to tape work fine, albeit very
slowly, which was the reason for trying to run to the disk pools.

A snippet if the activity log is below, along with a help listing
for the ANR4794E message.  If you have any more luck than I did, I'd
love to hear about it....

ANR0984I Process 60 for BACKUP NAS (FULL) started in the BACKGROUND
at 09:27:53 AM.
ANR1063I Full backup of NAS node NAS01, file system /__VOLUME__/SW,
started as process 60 by administrator ADMIN.
ANR2017I Administrator ADMIN issued command: QUERY PROCESS
ANR2017I Administrator ADMIN issued command: QUERY MOUNT
ANR2034E QUERY MOUNT: No match found using this criteria.
ANR4794E The NAS file server xxx.xxx.x.xx failed to open an NDMP
data connection to the TSM tape server. Please verify that the file
server is capable of outbound data connections.
ANR4728E Server connection to file server NAS01 failed. Please check
the attributes of the file server specified during
definition of the datamover.
ANR1096E NAS Backup to TSM Storage process 60 terminated - storage
media inaccessible.
ANR0985I Process 60 for BACKUP NAS (FULL) running in the BACKGROUND
completed with completion state FAILURE at 09:29:08
AM.


tsm: TSM01>help 4794
-------------------------------------------------------------------------------

ANR4794E The NAS file server File server name failed to open an NDMP
data
connection to the TSM tape server. Please verify that the file
server is
capable of outbound data connections.

Explanation: During a NAS filer-to-server backup operation the data
connection from the file server to the TSM server failed. This may
occur
because a firewall exists between the file server and the TSM server
and is
preventing outbound network connections on the file server. This may
also
occur if the network configuration of the system running the TSM
server is
reporting an invalid TCP/IP host address, for example "127.0.0.1".

System Action: The TSM server backup operation on the file server
fails.

User Response: Verify that the NAS file server is capable of starting
outbound network connections to the TSM server. Verify that the file
server
supports NDMP 3-way operations. Verify that the network
configuration of the
system running the TSM server is reporting a valid TCP/IP host
address. .







On Thu, 07 Feb 2008 14:49:55 -0500
"c.hanover" <chanover AT UMICH DOT EDU> wrote thusly:

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>