You need to separate the non-qtree data first before TSM looks at it.
We use snapvault for our short-term backups and TSM NDMP for the long term
stuff.

So we created one snapvault destination to grab all of the non-qtree stuff
using the ""/vol/xyz/-"  as the source.
Then you can backup that with TSM for longterm storage.

You might not have snapvault, but maybe it'll spark an idea with the tools
you do have.  I haven't tried with any of the other netapp tools, but
maybe you can use a netapp procedure to copy the non-qtree data somewhere
else, before backing up with TSM. Maybe using snapmirror or ndmpcopy.


Regards,
Shawn
________________________________________________
Shawn Drew





Internet
KMueller AT MCARTA DOT COM

Sent by: ADSM-L AT VM.MARIST DOT EDU
06/16/2009 01:05 PM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
[ADSM-L] NDMP backup of non-qtree data






We have an IBM N-Series 6040 (a thinly veiled NetApp 3140) that amoung
other things contains several large volumes (2TB, 35 million files).
These volumes have qtrees defined for the larger top-level directories.
There are numerous other small top-level directories that are not in
qtrees.

We are running TSM 5.5.2.0 and using the Filer->TSM->Library method of
NDMP backup (storing the backups in TSM native storage pools).

It is not practical to backup the entire volume in one shot, but backing
up the individual qtrees via BACKUP NODE is manageable.  The problem
that I have is how to specify backing up the non-qtree portion of the
volume.  The NetApp commands use a trailing dash after the volume name
to indicate non-qtree data (ie:  /vol/xyz/-  ) however BACKUP NODE
complains of an invalid parameter when I use that convention.  I tried
setting up a virtualfsmapping with the trailing dash and it is accepted
for the mapping, however the subsequent BACKUP NODE process fails after
it starts with an ANR9999D catchall: "Error beginning NDMP backup -
illegal arguements.Check that the filespace/path '/vol/xyz/-' exists."

Anybody backing up these filers at the qtree level?  How do you handle
the non-qtree data?

We're new to the whole NDMP world - seems a few steps back from what TSM
can do natively.  Any sage advice is welcome!

-Ken Mueller



This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.