Sounds like NDMP does things along the lines of the Oracle TDP.  TSM
doesn't know, and can't manage what's in the data sent to it.  Is that
about right?  We're considering dumping the oracle TDP because of that.
I don't want my TSM system just being a dumping grounds for data, I can
use setups that are a lot cheaper for that.

See Ya'
Howard
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Allen S. Rout
Sent: Thursday, February 14, 2008 9:41 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Backing up PST files

>> On Wed, 13 Feb 2008 21:23:25 -0500, "Strand, Neil B."
<NBStrand AT LMUS.LEGGMASON DOT COM> said:

> Have you looked into ndmp from the filer to your tsm server?  If you 
> are at TSM V5.4 you can do this over ethernet and handle the data just

> like any other node - move, copy etc.  It also minimizes impact on DB 
> size.  The trick is to recognize ndmp full/differential methodology in

> the TSM incremental methodology climate.


NDMP: Avoid, avoid, avoid.

I've elaborated on this opinion in the past, but the succinct summary is
that NDMP turns all your fancy TSM infrastructure into a big remote-tape
structure.

Only the very most recent and fancy NDMP clients even give TSM any sense
of the contents of the data.

You have to come up with device drivers on all your NDMP clients.

Ick.  Assiduously investigate other options before discarding all the
advantages TSM gives you.

I spent years doing rmt on unix: I don't want to go back, and you don't
want to go there.


- Allen S. Rout